Exception class data: listing of data fields

Exception records are fixed format. The format of the exception data section of a monitoring record can be mapped by the DSECT MNEXCDS.

EXCMNTRN (TYPE-C, 4 BYTES)

Transaction identification.

EXCMNTER (TYPE-C, 4 BYTES)

Terminal identification. This field is null if the task is not associated with a terminal or session.

EXCMNUSR (TYPE-C, 8 BYTES)

User identification at task creation. This identifier can also be the remote user identifier for a task created as the result of receiving an ATTACH request across an MRO or APPC link with attach-time security enabled.

EXCMNTST (TYPE-C, 4 BYTES)

Transaction start type. The low-order byte (0 and 1) is set to:

"TO"

Attached from terminal input

"S"

Attached by automatic transaction initiation (ATI) without data

"SD"

Attached by automatic transaction initiation (ATI) with data

"QD"

Attached by transient data trigger level

"U "

Attached by user request

"TP"

Attached from terminal TCTTE transaction ID

"SZ"

Attached by Front End Programming Interface (FEPI)

EXCMNSTA (TYPE-T, 8 BYTES)

Start time of the exception.

EXCMNSTO (TYPE-T, 8 BYTES)

Finish time of the exception.

Note: The performance class exception wait time field, EXWTTIME (103), is a calculation based on subtracting the start time of the exception (EXCMNSTA) from the finish time of the exception (EXCMNSTO).

EXCMNTNO (TYPE-P, 4 BYTES)

Transaction identification number.

EXCMNTPR (TYPE-C, 4 BYTES)

Transaction priority when monitoring was initialized for the task (low-order byte).

EXCMNLUN (TYPE-C, 4 BYTES)

z/OS® Communications Server logical unit name (if available) of the terminal associated with this transaction. This field is nulls if the task is not associated with a terminal.

EXCMNEXN (TYPE-A, 4 BYTES)

Exception sequence number for this task.

EXCMNRTY (TYPE-C, 8 BYTES)

Exception resource type. The possible values for EXCMNRTY are shown in Table 1.

EXCMNRID (TYPE-C, 8 BYTES)

Exception resource identification. The possible values for EXCMNRID are shown in Table 1.

EXCMNTYP (TYPE-A, 2 BYTES)

Exception type. This field can be set to one of the following values:

X'0001'

Exception because of a wait (EXCMNWT)

X'0002'

Exception because of a buffer wait (EXCMNBWT)

X'0003'

Exception because of a string wait (EXCMNSWT)

X'0004'

Exception because a policy rule has triggered (EXCMNPOL)

EXCMNTCN (TYPE-C, 8 BYTES)

Transaction class name. This field is null if the transaction is not in a transaction class.

EXCMNSRV (TYPE-C, 8 BYTES)

z/OS Workload Manager Service Class name for this transaction. This field is null if there are no transaction classification rules defined for CICS® subsystems in the active z/OS Workload Manager (WLM) service policy, or if the transaction was WLM-classified in another CICS region.

EXCMNRPT (TYPE-C, 8 BYTES)

z/OS Workload Manager Report Class name for this transaction. This field is null if there are no transaction classification rules defined for CICS subsystems in the active z/OS Workload Manager (WLM) service policy, or if the transaction was WLM-classified in another CICS region.

EXCMNNPX (TYPE-C, 20 BYTES)

Fully qualified name by which the originating system is known to the z/OS Communications Server network. This name is assigned at attach time using either the NETNAME derived from the TCT (when the task is attached to a local terminal), or the NETNAME passed as part of an ISC APPC or IRC attach header. At least three passing bytes (X'00') are present at the right end of the name.

If the originating terminal is a z/OS Communications Server device across an ISC APPC or IRC link, the NETNAME is the networkid.LUname. If the terminal is not a z/OS Communications Server device, the NETNAME is networkid.generic_applid.

All originating information passed as part of an ISC LUTYPE6.1 attach header has the same format as the non-z/OS Communications Server terminal originators.

When the originator is communicating over an external CICS interface (EXCI) session, the name is a concatenation of the following information that is derived from the originating system:

  'DFHEXCIU  |  .       |   MVS Id   |   Address space Id (ASID)'
   8 bytes   |  1 byte  |   4 bytes  |   4 bytes

That is, the name is a 17-byte LU name that consists of the following:

• An 8-byte eye-catcher set to 'DFHEXCIU'.
• A 1-byte field containing a period (.).
• A 4-byte field containing the MVS™ ID, in characters, under which the client program is running.
• A 4-byte field containing the address space ID (ASID) in which the client program is running. This field contains the 4-character EBCDIC representation of the 2-byte hex address space ID.

EXCMNNSX (TYPE-C, 8 BYTES)

Name by which the unit of work is known within the originating system. This last name is assigned at attach time, either by using an STCK-derived token (when the task is attached to a local terminal), or the unit of work ID is passed as part of an ISC APPC or IRC attach header.

The first six bytes of this field are a binary value derived from the clock of the originating system and wrapping round at intervals of several months. The last two bytes of this field are for the period count. These bytes can change during the life of the task as a result of syncpoint activity.

Note: When MRO or ISC is used, the EXCMNNSX field must be combined with the EXCMNNPX field to uniquely identify a task, because the EXCMNNSX field is unique only to the originating CICS system.

EXCMNTRF (TYPE-C, 8 BYTES)

Transaction flags; a string of 64 bits used for signaling transaction definition and status information. For details, see field 164 (TRANFLAG) in performance data group DFHTASK.

EXCMNFCN (TYPE-C, 4 BYTES)

Transaction facility name. This field is null if the transaction is not associated with a facility. The transaction facility type (if any) can be identified by using byte 0 of the transaction flags field, EXCMNTRF.

EXCMNCPN (TYPE-C, 8 BYTES)

The name of the currently running program for this user task when the exception condition occurred.

EXCMNBTR (TYPE-C, 4 BYTES)

3270 Bridge transaction identification.

EXCMNURI (TYPE-C, 16 BYTES)

RRMS/MVS unit-of-recovery ID (URID).

EXCMNRIL (TYPE-A, 4 BYTES)

Exception resource ID length.

EXCMNRIX (TYPE-C, 256 BYTES)

Exception resource ID (extended).

EXCMNNID (TYPE-C, 8 BYTES)

NETID if a network qualified name has been received from z/OS Communications Server. For a z/OS Communications Server resource when the network qualified name has not yet been received, NETID is eight blanks. In all other cases, this field is nulls.

EXCMNRLU (TYPE-C, 8 BYTES)

Real network name if a network qualified name has been received from z/OS Communications Server. In all other cases, this field is the same as LUNAME (field id 111). For non-z/OS Communications Server resources, this field is nulls.

The following table shows the value and relationships of the fields EXCMNTYP, EXCMNRTY, and EXCMNRID.