Defines the attributes of the connection made between CICS and DB2.
INQUIRE DB2CONN .-----------------------------. V | >>-INQUIRE DB2CONN----+-ACCOUNTREC(cvda)--------+-+------------>< +-AUTHID(data-area)-------+ +-AUTHTYPE(cvda)----------+ +-COMAUTHID(data-area)----+ +-COMAUTHTYPE(cvda)-------+ +-COMTHREADLIM(data-area)-+ +-COMTHREADS(data-area)---+ +-CONNECTERROR(cvda)------+ +-CONNECTST(cvda)---------+ +-DB2GROUPID(data-area)---+ +-DB2ID(data-area)--------+ +-DB2RELEASE(data-area)---+ +-DROLLBACK(cvda)---------+ +-MSGQUEUE1(data-area)----+ +-MSGQUEUE2(data-area)----+ +-MSGQUEUE3(data-area)----+ +-NONTERMREL(cvda)--------+ +-PLAN(data-area)---------+ +-PLANEXITNAME(data-area)-+ +-PRIORITY(cvda)----------+ +-PURGECYCLEM(data-area)--+ +-PURGECYCLES(data-area)--+ +-RESYNCMEMBER(cvda)------+ +-SIGNID(data-area)-------+ +-STANDBYMODE(cvda)-------+ +-STATSQUEUE(data-area)---+ +-TCBLIMIT(data-area)-----+ +-TCBs(data-area)---------+ +-THREADS(data-area)------+ +-THREADERROR(cvda)-------+ +-THREADLIMIT(data-area)--+ '-THREADWAIT(cvda)--------'
Conditions: NOTAUTH, NOTFND
This command is threadsafe.
The INQUIRE DB2CONN command allows you to inquire about attributes of the currently installed DB2CONN which defines the connection to DB2.
Note that because there can be only one DB2CONN installed at a time, the name of the DB2CONN is not required on input.
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 the production of an accounting record for each UOW. For example, an accounting record is produced if a thread terminates after being released, or if a thread is reused but the primary AUTHID is changed.
Because pool threads are typically used by a number of different transaction IDs, there is an increased chance that a transaction containing multiple 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 for each UOW.For example, an accounting record is produced if a thread terminates after being released, or if a thread is reused but the primary AUTHID is changed.
DB2 nevertheless produces at least one accounting record for each thread when the thread is terminated. Additionally, authorization changes cause accounting records to be produced.
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. |
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 a transaction is started (using a CICS command) and has no terminal associated with it, AUTHTYPE(TERM) should not be used.
When the DB2 sample sign-on exit DSN3@.SGN is used with AUTHTYPE(USERID), the exit sends the USERID to DB2 as the primary authorization ID and the RACF group ID to DB2 as the secondary ID. When the sample sign-on exit is used, there is no difference between AUTHTYPE(USERID) and AUTHTYPE(GROUP).
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. |
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 a transaction is started (using a CICS command) and has no terminal associated with it, COMAUTHTYPE(CTERM) should not be used.
When the DB2 sample sign-on exit DSN3@.SGN is used with COMAUTHTYPE(CUSERID), the exit sends the USERID to DB2 as the primary authorization ID and the RACF group ID to DB2 as the secondary ID. When the sample sign-on exit is used, there is no difference between COMAUTHTYPE(CUSERID) and COMAUTHTYPE(CGROUP).
A protected thread is not terminated immediately when it is released. It is terminated only after two completed purge cycles, if it has not been reused in the meantime. Hence if the purge cycle is set to 30 seconds after it is released, a protected thread is purged 30 - 60 seconds after it is released. An unprotected thread is terminated when it is released (at syncpoint or end of task) if there are no other transactions waiting for a thread on that DB2ENTRY.
A protected thread is not terminated immediately when it is released. It is terminated only after two completed purge cycles, if it has not been reused in the meantime. Hence if the purge cycle is set to 30 seconds after it is released, a protected thread is purged 30 - 60 seconds after it is released. An unprotected thread is terminated when it is released (at syncpoint or end of task) if there are no other transactions waiting for a thread on that DB2ENTRY.