Sets the attributes of a particular DB2ENTRY used to define resources to be used by a specific transaction or by a group of transactions when accessing DB2.
SET DB2ENTRY >>-SET DB2ENTRY--+-------------+--------------------------------> '-(data-area)-' .-----------------------------. V | >----+-------------------------+-+----------------------------->< +-+-ACCOUNTREC(cvda)-+----+ | +-UOW--------------+ | | +-TASK-------------+ | | +-TXID-------------+ | | '-NONE-------------' | +-AUTHID(data-area)-------+ +-+-AUTHTYPE(cvda)-+------+ | +-GROUP----------+ | | +-SIGN-----------+ | | +-TERM-----------+ | | +-TX-------------+ | | +-OPID-----------+ | | '-USERID---------' | +-+-BUSY(cvda)-+----------+ | +-WAIT-------+ | | +-NOWAIT-----+ | | '-FORCE------' | +-+-DISABLEDACT(cvda)-+---+ | +-ABEND-------------+ | | +-SQLCODE-----------+ | | '-POOL--------------' | +-+-ENABLESTATUS(cvda)-+--+ | +-ENABLED------------+ | | '-DISABLED-----------' | +-PLAN(data-area)---------+ +-PLANEXITNAME(data-area)-+ +-+-PRIORITY(cvda)-+------+ | +-HIGH-----------+ | | +-EQUAL----------+ | | '-LOW------------' | +-PROTECTNUM(data-area)---+ +-THREADLIMIT(data-area)--+ '-+-THREADWAIT(cvda)-+----' +-TWAIT------------+ +-NOWAIT-----------+ '-TPOOL------------'
Conditions: NOTAUTH, NOTFND, INVREQ
This command is threadsafe.
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The entry is identified by the name it was defined with in CEDA. For RCTs migrated to the CSD, the name is the name of the first transaction on the DSNCRCT TYPE=ENTRY statement.
DB2 produces at least one accounting record for each thread when the thread is terminated. Authorization changes additionally cause accounting records to be produced.
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.
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.
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 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.
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 user ID 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).
Note that when a DB2ENTRY is quiescing, all existing transactions are allowed to complete. Transactions already queued against the entry are also allowed to complete. New transactions that try to access the DB2ENTRY are routed to the POOL, or abended, or sent a SQLCODE depending on the setting of DISABLEDACT.
If PLAN is specified, PLANEXITNAME cannot be specified.
RESP2 values: