Connections - DB2CONN
The DB2 connections (DB2CONN) views display information about DB2 connections defined to CICSPlex SM via DB2CDEF objects.
Supplied views
To access from the main menu, click:
| View | Notes |
|---|---|
| DB2 connections EYUSTARTDB2CONN.CONNECT |
Cause a connection to be established between the CICS/DB2 attachment facility and the DB2 subsystem. |
| DB2 connections EYUSTARTDB2CONN.DETAIL1 |
Detailed connection statistics information about a selected DB2 connection. |
| DB2 connections EYUSTARTDB2CONN.DETAIL4 |
Detailed information about the resource signature. |
| DB2 connections EYUSTARTDB2CONN.DETAILED |
Detailed information about a selected DB2 connection. |
| DB2 connections EYUSTARTDB2CONN.DISCARD |
Discard a DB2 connection from the CICS system where it is installed. |
| DB2 connections EYUSTARTDB2CONN.DISCONNECT |
Cause disconnection of the CICS/DB2 attachment facility from the DB2 subsystem. |
| DB2 connections EYUSTARTDB2CONN.FORCE |
Force DB2 connections to be immediately purged. |
| DB2 connections EYUSTARTDB2CONN.REBUILD |
Force all existing threads to resignon at the next thread reuse. |
| DB2 connections EYUSTARTDB2CONN.SET |
Display the Set view in order to change the attributes of a selected DB2 connection. |
| DB2 connections EYUSTARTDB2CONN.TABULAR |
Tabular information about DB2 connections. |
Actions
| Action | Description |
|---|---|
| CONNECT | Cause a connection to be established between the CICS/DB2 attachment facility and the DB2 subsystem. |
| DISCARD | Discard a DB2 connection from the CICS system where it is installed. |
| DISCONNECT | Cause disconnection of the CICS/DB2 attachment facility from the DB2 subsystem. |
| FORCE | Force DB2 connections to be immediately purged. |
| REBUILD | Force all existing threads to resignon at the next thread reuse. |
| SET | Display the Set view in order to change the attributes of a selected DB2 connection. |
Fields
| Field | Attribute name | Description |
|---|---|---|
| Accounting record option | ACCOUNTREC | This defines whether the CICS DB2 attachment will produce a DB2 accounting record per unit of work (UOW), transid, transaction
or not at all for transactions using pool threads.
|
| Pool thread authorization ID | AUTHID | This defines the user identifier to be used for security checking when using pool threads. If Pool thread authorization ID is specified then Pool thread authorization type is not applicable. |
| Pool thread authorization type | AUTHTYPE | This indicates the type of user identifier to be used for security checking when using pool threads. If Pool thread
authorization type is specified, authorization ID is set to blanks.
|
| BAS resource definition version | BASDEFINEVER | The BAS version number of this definition. |
| Number of calls using command threads | CCALLS | This field indicates the number of DB2 commands issued using the DSNC transaction. |
| Last modification agent | CHANGEAGENT | The change agent identifier that made the last modification.
|
| Last modification agent release | CHANGEAGREL | The CICS release level of the agent that made the last modification to the resource definition. |
| Last modification time | CHANGETIME | The local date and time when the definition was last changed. |
| Last modification user ID | CHANGEUSRID | The user ID that made the last modification to the resource definition. |
| Command thread authorization ID | COMAUTHID | This defines the user identifier to be used for security checking when using command threads. If COMAUTHID is specified, COMAUTHTYPE is not applicable. |
| Command thread authorization type | COMAUTHTYPE | This indicates the type of user identifier to be used for security checking when using command threads. If COMAUTHTYPE is
specified then COMAUTHID is set to blanks.
|
| Maximum number of command threads | COMTHREADLIM | The current maximum number of command threads the CICS DB2 attachment facility allows active before requests overflow to the pool. |
| Number of active command threads | COMTHREADS | This indicates the current number of active command threads. |
| Connection error processing option | CONNECTERROR | This specifies the way that the information, that CICS is not connected to DB2 because the attachment facility is in
'standby mode', is reported back to an application that has issued an SQL request:
|
| Connection status | CONNECTST | This indicates the status of the CICS DB2 connection:
|
| Number of command thread signons | CSIGNONS | This field indicates the number of DB2 signons performed for command threads. |
| Current number of command threads | CTCURR | This field indicates the current number of command threads for this DB2 entry. |
| Peak number of command threads | CTHWM | This field indicates the peak number of active command threads. |
| GMT connect time | CTIMEGMT | This indicates the last connection time - with respect to GMT - at which this connection definition was connected. |
| Local connect time | CTIMELOC | This indicates the last connection time - with respect to local time - at which this connection definition was connected. |
| Maximum number of command threads | CTLIMIT | This field indicates the current maximum number of command threads the CICS DB2 attachment allows to be active before requests overflow into the pool. |
| Number of command thread overflows to pool | CTOVERF | This field indicates the number of times a DSNC DB2 command resulted in a pool thread being used because the number of active command threads exceeded the command thread limit. |
| Number of command thread terminations | CTTERM | This field indicates the number of terminate thread requests made to DB2 for command threads. |
| DB2 data sharing group ID | DB2GROUPID | This indicates the name of the DB2 data sharing group, or subgroup, to which CICS is connected or connecting. This can only be changed when the CICS-DB2 Attachment Facility is not active. |
| DB2 subsystem ID | DB2ID | This indicates the name of the DB2 subsystem to which CICS is connected or connecting. DB2 ID can only be changed when the CICS-DB2 Attachment Facility is not active. If you are using group attach and the CICS DB2 attachment is not connected and is not in the process of connecting, this field is blank. |
| DB2 version and release | DB2RELEASE | This indicates the version and release level of the DB2 subsystem to which CICS is connected. When CICS is not connected this field is set to blanks. |
| Source of the resource definition | DEFINESOURCE | The source of the definition, depending on which agent made the last change. |
| Creation time | DEFINETIME | The local date and time when the resource definition record was created on DFHCSD or EYUDREP. |
| Deadlock resolution rollback option | DROLLBACK | This field indicates whether or not the CICS DB2 attachment will initiate a syncpoint rollback in the event of transaction
being selected as a victim of a deadlock resolution.
|
| GMT disconnect time | DTIMEGMT | This indicates the last disconnection time - with respect to GMT - at which this connection definition was disconnected. |
| Local disconnect time | DTIMELOC | This indicates the last disconnection time - with respect to local time - at which this connection definition was disconnected. |
| Installation agent | INSTALLAGENT | The install agent identifier that made the installation.
|
| Installation time | INSTALLTIME | The local date and time when the definition was installed. |
| Installation user ID | INSTALLUSRID | The user ID that installed the resource definition. |
| Unsolicited error message TDQ name 1 | MSGQUEUE1 | This field indicates the name of the first transient data queue to which unsolicited messages from the CICS DB2 attachment facility are sent. This first transient data queue name cannot be blank. |
| Unsolicited error message TDQ name 2 | MSGQUEUE2 | This field indicates the name of the second transient data queue to which unsolicited messages from the CICS DB2 attachment facility are sent. |
| Unsolicited error message TDQ name 3 | MSGQUEUE3 | This field indicates the name of the third transient data queue to which unsolicited messages from the CICS DB2 attachment facility are sent. |
| DB2 connection name | NAME | The name of the DB2 connection definition. |
| Non-terminal transaction thread-release option | NONTERMREL | This indicates whether or not a non-terminal transaction releases threads for reuse at intermediate syncpoints:
|
| Number of pool thread aborts | PABORTS | This field indicates the number of units of work using pool threads that were rolled back. |
| Number of calls using pool threads | PCALLS | This field indicates the number of SQL calls made using pool threads. |
| Number of pool thread commits | PCOMMITS | This field indicates the number of two phase commits performed for units of work using pool threads. |
| Name of plan used for pool | PLAN | This indicates the name of the plan to be used for the pool. If a plan name is specified then the PLANEXITNAME field is set to blank. |
| Name of dynamic plan exit used for pool threads | PLANEXITNAME | This indicates the name of the dynamic plan exit used for pool threads. If a planexit name is specified then the PLAN field is set to blank. |
| Number of pool thread partial signons | PPSIGNONS | This field indicates the number of DB2 partial signons performed for pool threads. |
| Number of times a pool thread reached REUSELIMIT | PREUSELIMCT | This field indicates the number of times a pool thread reached reuselimit and had to be terminated. |
| TCB priority | PRIORITY | This field indicates the priority of the pool thread TCBs relative to the CICS main task.
|
| Current number of tasks waiting for pool thread | PRQCUR | This field indicates the current number of CICS tasks waiting for a pool thread to become available. |
| Peak number of tasks waiting for pool thread | PRQHWM | This field indicates the peak number of CICS tasks that waited for a pool thread to become available. |
| Number of pool thread signons | PSIGNONS | This field indicates the number of DB2 signons performed for pool threads. |
| Number of units of work with single phase commit | PSPHASE | This field indicates the number of units of work using pool threads that used single phase commit, either because they were read-only UOWs, or because DB2 was the only recoverable resource updated in the UOW. |
| Number of times threads created | PTCREATE | This field indicates the number of create thread requests made to DB2 for pool threads. |
| Current number of active pool threads | PTCURR | This field indicates the current number of protected threads for this DB2 entry. |
| Peak number of active pool threads | PTHWM | This field indicates the peak number of CICS tasks that have used a pool thread. |
| Maximum number of pool threads | PTLIMIT | This field indicates the current maximum number of pool threads allowed. |
| Number of times transactions reused pool threads | PTREUSE | This field indicates the number of times CICS transactions using the pool were able to reuse an already created DB2 thread. |
| Number of times threads terminated | PTTERM | This field indicates the number of terminate thread requests made to DB2 for pool threads. |
| Number of pool thread waits | PTWAIT | This field indicates the number of times all available threads in the pool were busy and a transaction had to wait for a thread to become available. |
| Protected thread purge cycle (minutes) | PURGECYCLEM | This field defines the length in minutes of the protected thread purge cycle. The range is 0 - 59. 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. |
| Protected thread purge cycle (seconds) | PURGECYCLES | This field defines the length in seconds of the protected thread purge cycle. The range is 0 - 59. If PURGECYCLEM is zero then the minimum value for PURGECYCLES is 5 seconds. See PURGECYCLEM for more information. |
| Current number of tasks using a pool thread | PXCURR | This field indicates the current number of CICS tasks that are using a pool thread. |
| Peak number of tasks using a pool thread | PXHWM | This field indicates the peak number of active pool threads. |
| Total number of tasks that used a pool thread | PXTOTAL | This field indicates the total number of completed tasks that have used a pool thread. |
| Resynchronization member | RESYNCMEMBER | This applies only if you are using group attach, and specifies the strategy that CICS adopts if outstanding units of
work are being held for the last DB2 data sharing group member to which CICS was connected.
|
| Thread reuse limit | REUSELIMIT | The maximum number of times a thread can be reused before it needs to be terminated. |
| Authorization ID used by CICS-DB2 attach | SIGNID | This field defines the authorization ID to be used by the CICS DB2 attachment facility when signing on to DB2 for pool and DB2ENTRY threads that specify AUTHTYPE(SIGN) and command threads specifying COMAUTHTYPE(CSIGN). The default is blanks which are replaced by the applid of the CICS system when the DB2CONN is installed. Note: If you specify a user ID on the SIGNID attribute, CICS performs a surrogate user check against the user ID performing the installation. Similarly, the CICS region user ID is subject to a surrogate user check during group list installation on CICS cold or initial start. |
| Standby mode action | STANDBYMODE | This field indicates action to be taken by the CICS DB2 attachment if DB2 is not active when an attempt
to start a connection is made.
|
| Attachment statistics TDQ name | STATSQUEUE | This indicates the name of the transient data queue to which statistics will be sent when the CICS DB2 attachment is shut down. |
| Current number of connections without a TCB | TCBFREE | This field indicates the current number of connections currently not associated with a TCB. |
| Maximum number of connections (TCBLIMIT) | TCBLIMIT | This field indicates the maximum number of connections (identified TCBs) that can be used to process DB2 requests. |
| Current number of tasks waiting for a connection | TCBRDYQCURR | This field indicates the current number of CICS tasks queued waiting for a DB2 connection to become available. |
| Peak number of tasks waiting for a connection | TCBRDYQHWM | This field indicates the peak number of CICS tasks queued waiting for a DB2 connection to become available. |
| Current number of connections with a TCB | TCBS | This field indicates the current number of TCBs used by the CICS-DB2 attachment facility. |
| Current number of subtask TCBs | TCURR | This field indicates the current number connections that are associated with a TCB. |
| Action following thread error | THREADERROR | This indicates the processing that is to occur following a create thread error:
|
| Maximum number of pool threads | THREADLIMIT | This field indicates the current maximum number of pool threads that the CICS DB2 attachment facility allows to be active before requests are made to wait or are rejected (subject to the THREADWAIT attribute). The default THREADLIMIT (3) is also the minimum you can specify. The maximum value must not be greater than the value specified for TCBLIMIT. |
| Number of active pool threads | THREADS | This field indicates the current number of pool threads. |
| Thread wait option | THREADWAIT | This field specifies whether or not transactions should wait for a pool thread, or be abended if the number of
active pool threads reaches the thread limit. 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:
|
| Peak number of connections with a TCB | THWM | This field indicates the peak number of active threads for this DB2 entry |
| Current maximum number of connections into DB2 | TLIMIT | This field indicates the maximum number of TCB subtasks that can be used by the CICS-DB2 attachment Facility. |