Filter
Top Products
CEMT INQUIRE DB2CONN
CEMT INQUIRE DB2CONN
Function: Retrieves information about the CICS DB2
connection.
Description: INQUIRE DB2CONN returns information
about the 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.
Input: Press the Clear key to clear the screen, and type
CEMT INQUIRE DB2CONN. You get a display that lists the
current status. You can then tab to the highlighted or blank
fields and overtype them with the required values.
Sample screen
inquire db2conn
STATUS: RESULTS - OVERTYPE TO MODIFY
Accountrec( None ) Priority( High )
Authid( ) Purgecyclem( )
Authtype( Userid ) Purgecycles( 3 )
Comauthid( ) Signid( CICSHTC1 )
Comauthtype( Cuserid ) Security( )
Comthreadlim( 1 ) Standbymode( Reconnect )
Comthreads() Statsqueue( CDB2 )
Connecterror( Sqlcode ) Tcblimit( 12 )
Connectst( Notconnected ) Tcbs()
Db2id( DB2A ) Threaderror(N96d)
Db2release() Threadlimit( 3 )
Drollback(Rollback) Threads()
Msgqueue1( CDB2 ) Threadwait( Twait )
Msgqueue2( )
Msgqueue3( )
Nontermrel( Release )
Plan( )
Planexitname( DSNCUEXT )
Figure 55. CEMT INQUIRE DB2CONN screen
─ ──CEMT Inquire DB2Conn ─
Displayed fields
Accountrec
returns the minimum amount of DB2 accounting required
for transactions using pool threads. The specified
minimum may be exceeded, as described in the
following options. The values are:
UOW
The CICS DB2 attachment facility causes an
accounting record to be produced for each 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 containing multiple UOWs may use
a different thread for each of its UOWs (assuming
the thread is released at syncpoint). The result
may be an accounting record produced for each
UOW.
Txid The CICS DB2 attachment facility causes an
accounting record to be produced when the
transid using the thread changes.
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.
None
No accounting records are required for
transactions using pool threads.
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
returns an id to be used for security checking when
using pool threads. If an AUTHId is returned, AUTHType
is not applicable.
Authtype
returns the type of id to be used for security checking
when using pool threads. If an AUTHType is returned,
AUTHid is blank. The values are:
Group
The 8-character USERID and the connected group
name are used as the authorization ID. The
following table shows how these two values are
interpreted by DB2.
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 The SIGNID parameter of the DB2CONN is used
as the resource authorization ID.
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.
Chapter 11. Master terminal CEMT
63