DB2 entry definition attributes

The attributes are described in the following categories:

General attributes

The general attributes of a DB2ENTRY are:

Name
One to eight character name to identify a DB2® entry definition.
Description
(Optional.) Specifies a 1- to 30-character description of the resource.
Version
(Optional.) Specify an integer in the range 1 through 15. Specify 0 or leave blank for CICSPlex® SM to assign the first available version id in the range 1 through 15.
RESGROUP
(Optional.) Specify the name of an existing resource group to which the definition is to automatically added.
User data
(Optional.) Three 8-character fields provided for any site-specific data related to the DB2 entry. CICSPlex SM makes no use of this user data.

Thread selection attribute

The thread selection attributes of a DB2ENTRY are:

TRansid
Specifies the transaction id associated with the entry. Only one transaction can be specified here. However, the use of one or more wildcard characters in the TRANSID (see the CICS® Resource Definition Guide) allows a group of transactions to be represented. Additional transactions can be defined for this entry by defining a DB2 transaction that refers to this DB2 entry. Transid is optional on a DB2 entry. All transactions can be associated with a DB2 entry means of DB2 transactions instead. However, if only one transaction is associated with a DB2 entry it is easier to specify it on the DB2 entry.
Note:
Specifying a transaction id here causes a 'ghost' DB2 transaction object to be created when the DB2 entry definition is installed, and such DB2 transaction objects may appear on SYSRES and RDSCPROC views.
Attention: You can change the value of selected BAS objects using the Override field of a RASGNDEF object, as described in RASGNDEF (resource assignments) view. If you use this method to change the Transid field of a DB2EDEF and there is a resulting clash of names of DB2TRAN objects, CICSPlex SM does not detect this fact as part of inconsistent set processing.

Thread operation attributes

The thread operation attributes of a DB2ENTRY are:

ACcountrec
Specifies the minimum amount of DB2 accounting required for transactions using this DB2 entry. The specified minimum may be exceeded, as described in the following options.
NONE
No accounting records are required for transactions using threads from this DB2ENTRY
TASK
The CICS DB2 attachment facility causes a minimum of one accounting record for each CICS task to be produced.

A transaction containing multiple UOWs (assuming the thread is released at syncpoint) may use a different thread for each UOW. The result may be that an accounting record is produced for each UOW.

TXID
The CICS DB2 attachment facility causes an accounting record to be produced when the transid using the thread changes.
UOW
The CICS DB2 attachment facility causes an accounting to be produced for each UOW, assuming that the thread is released at the end of the UOW.
AUTHId
Specifies the id to be used for security checking when using this DB2ENTRY. If AUTHID is specified, AUTHTYPE may not be specified.
AUTHType
Specifies the type of id that can be used for security checking when using this DB2ENTRY. If AUTHTYpe is specified, AUTHid may not be specified.
USERID
The USERID associated with the CICS transaction is used as the authorization ID.

When the DB2 sample sign-on exit DSN3@SGN is used with AUTHTYPE(USERID), the exit sends the user ID to DB2 as the primary authorization ID and the connected group name to DB2 as the secondary ID. When the sample sign-on exit is used, there is no difference between AUTHTYPE(USERID) and AUTHTYPE(GROUP).

OPID
The operator identification that is associated with the userid that is associated with the CICS transaction sign-on facility, is used as the authorization ID (three characters padded to eight).
GROUP
Specifies the 1 to 8-character USERID and the connected group name as the authorization ID.

To use the GROUP option the CICS system must have RACF external security SEC=YES specified in the CICS system initialization table (SIT).

If no RACF group ID is available for this USERID, an 8-character field of blanks is passed to DB2 as the group ID.

SIGN
Specifies that the SIGNID attribute of the DB2CONN is used as the resource authorization ID.
TERM
Specifies the terminal identification (four characters padded to eight) as an authorization ID. An authorization ID cannot be obtained in this manner if a terminal is not connected with the transaction.

If a transaction is started (using a CICS command) and has no terminal associated with it, AUTHTYPE(TERM) should not be used.

TX
Specifies the transaction identification (four characters padded to eight) as the authorization ID.
DRollback
Specifies whether or not the CICS DB2 attachment should initiate a SYNCPOINT rollback in the event of a transaction being selected as victim of a deadlock resolution.
YES
The attachment facility issues a syncpoint rollback before returning control to the application. An SQL return code of -911 is returned to the program.

Do not specify YES if the DB2ENTRY is used by transactions running enterprise beans as part of an OTS transaction; CICS syncpoint rollback is not allowed in an OTS transaction.

NO
The attachment facility does not to initiate a rollback for this transaction. An SQL return code of -913 is returned to the application.
PLAN
Specifies the name of the plan to be used for this entry. If PLAN is specified, PLANEXITNAME cannot be specified.
PLANExitname
Specifies the name of the dynamic plan exit to be used for this DB2 entry definition. If you change the PLAN and PLANEXITNAME while there are active transactions for the DB2 entry definition, the next time the transaction releases the thread, the plan/exit will be determined using the new rules. If PLANEXITNAME is specified, PLAN cannot be specified.
PRiority
Specifies the priority of the thread subtasks for this DB2ENTRY relative to the CICS main task (QR TCB). If CICS is connected to DB2 Version 6 or later, this setting is ignored, as the task runs on an open L8 TCB that has the same priority as the QR TCB. However, the priority value specified on the DB2ENTRY definition is still installed into the relevant control block, in case CICS connects to a lower level of DB2 at a later time.
EQUAL
Subtasks have equal priority with the CICS main subtask.
HIGH
Subtasks attain a higher priority than the CICS main task from which the subtask was generated.
LOW
Subtasks have a lower priority than the CICS main task.
PROtectnum
Specifies the maximum number of protected threads allowed for this DB2 entry definition. A thread, when it is released by a transaction and there is no other work queued, can be protected, meaning that it is not terminated immediately. A protected thread is terminated after only two complete purge cycles if it has not been reused in the meantime. Hence, if the purge cycle is set to 30 seconds, a protected thread is terminated 30 - 60 seconds after it is released, assuming it is not reused in the meantime. The first purge cycle after the CICS DB2 attachment facility has been started is 5 minutes, after which the PURGECYCLE value is applied. Threads are only protected while they are inactive. If a transaction reuses a protected thread, the thread becomes active, and the current number of protected threads is decremented.
THREADLimit
Specifies the maximum number of threads for this DB2 entry definition that the CICS DB2 attachment allows active before requests are made to wait, are abended, or diverted to the pool.
THREADWait
Specifies whether or not transactions should wait for a DB2ENTRY thread, be abended, or overflow to the pool should the number of active DB2ENTRY threads reach the THREADLimit number.
POOL
If all threads are busy, the transaction is diverted to use the pool of threads. If the pool is also busy, and NO has been specified for the THREADWAIT attribute on the DB2 connection definition, the transaction is terminated with abend code AD3T.
NO
If all threads are busy, a transaction is terminated with an abend code AD2P.
YES
If all threads are busy, a transaction waits until one becomes available.

Related concepts
DB2 entry resource definitions
CICS Resource Definition Guide
Related tasks
Accessing BAS DB2 entry definitions
Working with the DB2EDEF view
Defining DB2 entries using BAS
Installing BAS DB2 entry definitions
[[ Contents Previous Page | Next Page Index ]]