The pool thread attributes of a DB2CONN are:
DB2 produces at least one accounting record for each thread when the thread is terminated. Authorization changes additionally cause accounting records to be produced.
A transaction containing multiple UOWs (assuming the thread is released at syncpoint) may use a different thread for each of its UOWs. The result may be an accounting record produced for each UOW.
Because pool threads are typically used by a number of different transaction IDs, there is an increased chance that a transaction containing multiple units of work (UOWs) will use a different thread for each UOW (assuming the thread is released at syncpoint). In this case an accounting record may be produced per UOW.
AUTHID is not suitable if you are using RACF® for some or all of the security checking in your DB2 address space; use AUTHTYPE instead, with the USERID or GROUP options. This is because threads using an AUTHID do not pass the required RACF access control environment element (ACEE) to DB2. The ACEE is not required if you are only using DB2 internal security, so in this case, you can use AUTHID.
The ID that you specify can be up to eight characters in length.Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
If you are using RACF for some or all of the security checking in your DB2 address space, you need to use the USERID or GROUP options. This is because only threads defined with these options pass the required RACF access control environment element (ACEE) to DB2. The ACEE is not required if you are only using DB2 internal security, so in this case, you can use any of the options.
IDs passed to DB2 | How DB2 interprets values |
---|---|
CICS sign-on user ID (USERID) | Represents the primary DB2 authorization ID. |
RACF connected group name | If the RACF list of group options is not active, DB2 uses the connected group name supplied by the CICS attachment facility as the secondary DB2 authorization ID. If the RACF list of group options is active, DB2 ignores the connected group name supplied by the CICS attachment facility, but the value appears in the DB2 list of secondary DB2 authorization IDs. |
To use the GROUP option, the CICS system must have 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.
If the transaction is not associated with a terminal (for example, if it is initiated with a START command), do not specify AUTHTYPE(TERM).
Do not specify YES if the pool is used by transactions running enterprise beans as part of an OTS transaction; CICS syncpoint rollback is not allowed in an OTS transaction. Consider defining a DB2ENTRY which specifies DROLLBACK(NO) for use by transactions which run enterprise beans as part of an OTS transaction.