Monitoring sessions and connections
The session/connection feature collects session information (functions and function timing) for DTP ( Distributed Transaction Processing) only for all session activity across LU 6.1, APPC and MRO connections.
Additionally, it collects connection usage information by activity type (see below) for all activity across LU 6.1, APPC, MRO, and TCP/IP connections.
The following table shows the data that is collected for each activity type and connection type:
Activity Type | Connection Type | Connection Data? | SessionData? | |||
|---|---|---|---|---|---|---|
LU61 | MRO | APPC | TCP/IP | |||
DBCTL | Y | Y | Y | N | Y | N |
DPL | Y | Y | Y | Y | Y | N |
DTP | Y | Y | Y | N | Y | Y |
File | Y | Y | Y | Y | Y | N |
IC | Y | Y | Y | Y | Y | N |
TD | Y | Y | Y | Y | Y | N |
TS | Y | Y | Y | Y | Y | N |
Data is maintained in the same resource entries in CMRDETL that are used for file activity, database activity, program timing, and so on, and therefore has an effect on the MAXFILE parameter.
The left parenthesis ( is used as the one-byte character identification of the session entries.
The right parenthesis ) is used as the one-byte character identification of the connection entries.
This section contains the following topics:
Related topic