Returns the attributes of the DB2ENTRY that defines resources to be used by a specific transaction or by a group of transactions when accessing DB2.
INQUIRE DB2ENTRY >>-INQUIRE DB2ENTRY(data-value)--ACCOUNTREC(cvda)---------------> >--+-------------------+--AUTHTYPE(cvda)--DISABLEDACT(cvda)-----> '-AUTHID(data-area)-' >--DROLLBACK(cvda)--ENABLESTATUS(cvda)--+-----------------+-----> '-PLAN(data-area)-' >--+-------------------------+--PRIORITY(cvda)------------------> '-PLANEXITNAME(data-area)-' >--+-----------------------+--+---------------------+-----------> '-PROTECTNUM(data-area)-' '-PTHREADS(data-area)-' >--+------------------------+--+--------------------+-----------> '-THREADLIMIT(data-area)-' '-THREADS(data-area)-' >--THREADWAIT(cvda)--------------------------------------------><
Conditions: END,ILLOGIC,NOTAUTH, NOTFND
This command is threadsafe.
The entry is identified by the name it was defined with in the CSD by the DEFINE DB2ENTRY command. For RCTs migrated to the CSD, it is identified by the name of the first transaction on the DSNCRCT TYPE=ENTRY statement unless the RDONAME parameter has been specified.
You can also browse through all of the DB2ENTRYs installed in a CICS region by using the browse options (START, NEXT, and END) on INQUIRE DB2ENTRY commands. See Browsing resource definitions for general information about browsing, including syntax, exception conditions, and examples.
A transaction containing multiple UOWs may use a different thread for each UOW (assuming the thread is released at syncpoint). 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.
This option applies to DB2ENTRYs that are used by more than one transaction ID. As threads are typically released at syncpoint, a transaction containing multiple UOWs may use a different thread for each UOW. The result may be that an accounting record is 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 produces. however, at least one accounting record per 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, then 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, then 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).