IBM CICS Transaction Server for OS/390 SC33-1686-02 - Manual (Page 188)

CEMT SET DB2CONN
PLANExitname
specifies the name of the dynamic plan exit to be used
for pool threads. If you change the PLAN and
PLANExitname while there are active transactions for
the pool, the next time the transaction releases the
thread, the plan/exit will be determined using the new
rules. If PLANExitname is specified, PLAN may not be
specified.
PRiority
specifies the priority of the pool thread subtasks relative
to the CICS main task (QR TCB). CVDA values are:
HIGH
subtasks attain a higher priority than the CICS
main task from which the subtask was generated.
EQUAL
subtasks have equal priority with the CICS main
task.
LOW
subtasks have a lower priority than the CICS main
task.
PURGECYCLEM
specifies in minutes the length of time of the protected
thread purge cycle. The default is 0,30; that is, 30
seconds.
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.
PURGECYCLES
specifies in seconds the length of time of the protected
thread purge cycle. The default is 0,30; that is, 30
seconds.
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.
SECURITY(REBUILD)
specifies that the CICS DB2 attachment should force all
existing threads to sign-on again at the next thread
reuse. It should be used when RACF profiles have been
updated by issuing the following commands:
CEMT PERFORM SECURITY REBUILD for RACF
1.9.2 or earlier
TSO SETROP TS RACLIST(xxxxxxxx) REFRESH
for RACF 2.1 or later
SIgnid
specifies the authorization ID to be used by the CICS
DB2 attachment when signing on to DB2 for pool and
DB2ENTRY threads specifying AUTHTYPE(SIGN), and
command threads specifying COMAUTHTYPE(CSIGN).
STANndbymode
specifies the action to be taken by the CICS DB2
attachment if DB2 is not active when an attempt is made
to start the connection from CICS to DB2. CVDA values
are:
NOCONNECT
The CICS DB2 attachment should terminate.
CONNECT
The CICS DB2 attachment goes into 'standby
mode' to wait for DB2.
RECONNECT
The CICS DB2 attachment goes into 'standby
mode' and waits for DB2. Having connected to
DB2, if DB2 subsequently fails the CICS DB2
attachment reverts again to standby mode and
subsequently reconnects to DB2 when it comes up
again.
STATSqueue
specifies the transient data destination for CICS DB2
attachment statistics produced when the CICS DB2
attachment is shutdown.
TCBLimit
specifies the maximum number of subtasks that can be
identified to DB2.
THREADLimit
specifies the current maximum number of pool threads
the CICS DB2 attachment allows active before requests
are made to wait or are rejected according to the
THREADWait parameter.
THREADWwait
specifies whether or not transactions should wait for a
pool thread or be abended if the number of active pool
threads reach the THREADlimit number.
The CICS DB2 attachment issues a unique abend code
AD3T, message DFHDB2011 when THREADWAIT=NO
is coded and the number of pool threads is exceeded.
CVDA values are:
TWAIT
If all threads are busy, a transaction must wait
until one becomes available. A transaction can
wait as long as CICS allows it to wait, generally
until a thread becomes available.
NOTWAIT
If all threads are busy, the transaction is
terminated with abend code AD3T or AD2P.
170 CICS Supplied Transactions