CEMT SET DB2ENTRY
Sets the attributes of a particular DB2ENTRY resource used to define resources for a specific transaction or a group of transactions when accessing DB2®.
In the CICS Explorer, the DB2 entries operations view provides a functional equivalent to this command.
Description
The entry is identified by the name it was identified with in CEDA.
All parameters on a SET DB2ENTRY command can be set while the CICS® DB2 attachment is active and the transactions are active.
Syntax
- Type
CEMT SET DB2ENTRY
(or suitable abbreviations for the keywords), followed by either a value that corresponds to a DB2 entry name, or ALL. The resulting display lists the current status, similar to that obtained by using the CEMT INQUIRE DB2ENTRY command. You can tab to the highlighted or blank fields and overtype them with the required values. - Type
CEMT SET DB2ENTRY
(or suitable abbreviations for the keywords), followed by either a value that corresponds to a DB2 entry name or ALL, then followed by one or more attribute settings that you want to change. For example,cemt s db2e all ena
enables all DB2ENTRY resources.
Typing ?
at the beginning of either the
first or second line gives a syntax prompt. Resetting the values takes
effect immediately.
Options
- ACCOUNTREC
- Specifies
the minimum amount of DB2 accounting
required for transactions using this DB2ENTRY resoource. The specified
minimum can be exceeded, as described in the following options.
- UOW
- The CICS DB2 attachment facility causes an accounting record to be produced for each unit of work (UOW), assuming that the thread is released at the end of the UOW.
- TASK
- The CICS DB2 attachment
facility causes a minimum of one accounting record to be produced
for each CICS task.
A transaction that contains multiple UOWs can use a different thread for each of its UOWs (assuming the thread is released at syncpoint). The result can be an accounting record produced for each UOW.
- TXID
- The CICS DB2 attachment
facility produces at least one accounting record to be produced when
the transid using the thread changes.
This option applies to DB2ENTRY resources that are used by more than one transaction ID. As threads are typically released at syncpoint, a transaction that contains multiple UOWs can use a different thread for each UOW. The result can be that an accounting record is produced per UOW.
- NONE
- No
accounting records are required for transactions using threads from
this DB2ENTRY resource.
DB2 does, however, produce at least one accounting record for each thread when the thread is terminated. Additionally, authorization changes cause accounting records to be produced.
- AUTHID
- Specifies the id to use for security checking when using this DB2ENTRY resource. If AUTHID is specified, AUTHTYPE is cleared.
- AUTHTYPE
- Returns
the type of id that can be used for security checking when using this
DB2ENTRY resource. If AUTHTYPE is specified, AUTHID is cleared.
- GROUP
- Specifies
the 8-character USERID and the connected group name as the authorization
ID. The following table shows how these two values are interpreted
by DB2.
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.
- SIGN
- Specifies the SIGNID parameter of the DB2CONN should be 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.
- OPID
- The operator identification associated with the CICS transaction is used as the authorization ID (three characters padded to eight).
- USERID
- The
8-character 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 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).
- DISABLEDACT
- Specifies
the action for new transactions that access a DB2ENTRY resource when
it has been disabled, or is disabling.
- POOL
- The CICS DB2 attachment facility routes the request to the pool. Message DFHDB2072 is sent to the transient data destination specified by MSGQUEUEn on the DB2CONN for each transaction routed to the pool.
- ABEND
- The CICS DB2 attachment facility abends the transaction. The abend code is AD26.
- SQLCODE
- An SQLCODE is returned to the application indicating that the DB2ENTRY resource is disabled.
- ENABLEDSTATUS
- Specifies
whether the DB2ENTRY resource can be accessed by applications.
- ENABLED
- The DB2ENTRY resource can be accessed by applications.
- DISABLED
- The DB2ENTRY resource cannot be accessed by applications. A DB2ENTRY resource must be disabled before it can be reinstalled or discarded.
- FORCEDISABLED
- All tasks using the DB2ENTRY resource and those queued against the DB2ENTRY resource are force purged. The DB2ENTRY resource is then disabled.
- PLAN
- Specifies
the name of the plan to be used for this DB2ENTRY resource.
If PLAN is specified, PLANEXITNAME is cleared.
- PLANEXITNAME
- Specifies the name of the dynamic plan exit to be used for this DB2ENTRY resource. If you change the PLAN and PLANEEXITNAME while there are active transactions for the DB2ENTRY resource, the next time the transaction releases the thread, the plan/exit is determined using the new rules. If PLANEXITNAME is specified, PLAN is cleared.
- PRIORITY
- Specifies the priority of the thread TCBs for this DB2ENTRY
resource relative to the CICS main
TCB (QR TCB). The thread TCBs are CICS open
L8 TCBs.
- HIGH
- Thread TCBs have a higher priority than the CICS QR TCB.
- EQUAL
- Thread TCBs have equal priority with the CICS QR TCB.
- LOW
- Thread TCBs have a lower priority than the CICS QR TCB.
- PROTECTNUM
- Specifies the maximum number of protected threads for this DB2ENTRY resource.
- THREADLIMIT
- Specifies the maximum number of threads for this DB2ENTRY resource that the CICS DB2 attachment allows active before requests are made to wait, are rejected, or are routed to the pool.
- THREADWAIT
- Specifies
whether or not transactions should wait for a DB2ENTRY thread, be
abended, or overflow to the pool if the number of active DB2ENTRY
threads reach the THREADLIMIT number.
- TWAIT
- If all threads are busy, the transaction waits until one becomes available.
- NOTWAIT
- If all threads are busy, the transaction is terminated with an abend code AD2P.
- TPOOL
- If all threads are busy, the transaction is diverted to use the pool of threads. If the pool is also busy, and NOTWAIT has been specified for the THREADWAIT parameter on the DB2CONN. The transaction is terminated with abend code AD3T.
All parameters on SET DB2ENTRY can be set while the CICS DB2 attachment is active and the transactions are active.