Exception class data

Product-sensitive programming interface

Exception records are produced after each of the following conditions encountered by a transaction has been resolved:

These records are fixed format. The format of these exception records is as follows:

MNEXCDS  DSECT
EXCMNTRN DS    CL4                TRANSACTION IDENTIFICATION
EXCMNTER DS    XL4                TERMINAL IDENTIFICATION
EXCMNUSR DS    CL8                USER IDENTIFICATION
EXCMNTST DS    CL4                TRANSACTION START TYPE
EXCMNSTA DS    XL8                EXCEPTION START TIME
EXCMNSTO DS    XL8                EXCEPTION STOP TIME
EXCMNTNO DS    PL4                TRANSACTION NUMBER
EXCMNTPR DS    XL4                TRANSACTION PRIORITY
         DS    CL4                RESERVED
EXCMNLUN DS    CL8                LUNAME
         DS    CL4                RESERVED
EXCMNEXN DS    XL4                EXCEPTION NUMBER
EXCMNRTY DS    CL8                EXCEPTION RESOURCE TYPE
EXCMNRID DS    CL8                EXCEPTION RESOURCE ID
EXCMNTYP DS    XL2                EXCEPTION TYPE
EXCMNWT  EQU   X'0001'              WAIT
EXCMNBWT EQU   X'0002'              BUFFER WAIT
EXCMNSWT EQU   X'0003'              STRING WAIT
         DS    CL2                RESERVED
EXCMNTCN DS    CL8                TRANSACTION CLASS NAME
EXCMNSRV DS    CL8                SERVICE CLASS NAME
EXCMNRPT DS    CL8                REPORT CLASS NAME
EXCMNNPX DS    CL20               NETWORK UNIT_OF_WORK PREFIX
EXCMNNSX DS    XL8                NETWORK UNIT_OF_WORK SUFFIX
EXCMNTRF DS    XL8                TRANSACTION FLAGS
EXCMNFCN DS    CL4                TRANSACTION FACILITY NAME
EXCMNCPN DS    CL8                CURRENT PROGRAM NAME
EXCMNBTR DS    CL4                BRIDGE TRANSACTION ID
EXCMNURI DS    XL16               MVS/RRMS Unit of Recovery Id
EXCMNRIL DS    F                  EXCEPTION RESOURCE ID LENGTH
EXCMNRIX DS    XL256              EXCEPTION RESOURCE ID (EXTENDED)
EXCMNNID DS    CL8                NETWORK ID 
EXCMNRLU DS    CL8                REAL LUNAME 
*        END OF EXCEPTION RECORD ...
End of Product-sensitive programming interface

Exception data field descriptions

Product-sensitive programming interface
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 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)
VTAM® 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 7.
EXCMNRID (TYPE-C, 8 BYTES)
Exception resource identification. The possible values for EXCMNRID are shown in Table 7.
EXCMNTYP (TYPE-A, 2 BYTES)
Exception type. This field can be set to one of the following values:
X'0001'
Exception due to a wait (EXCMNWT)
X'0002'
Exception due to a buffer wait (EXCMNBWT)
X'0003'
Exception due to a string wait (EXCMNSWT)
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)
MVS™ 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 MVS Workload Manager (WLM) service policy, or if the transaction was WLM-classified in another CICS region.
EXCMNRPT (TYPE-C, 8 BYTES)
MVS 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 MVS 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 VTAM 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 VTAM device across an ISC APPC or IRC link, the NETNAME is the networkid.LUname. If the terminal is non-VTAM, 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-VTAM terminal originators above.

When the originator is communicating over an external CICS interface (EXCI) session, the name is a concatenation of:

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

derived from the originating system. That is, the name is a 17-byte LU name consisting of:

  • An 8-byte eye-catcher set to 'DFHEXCIU'.
  • A 1-byte field containing a period (.).
  • A 4-byte field containing the MVSID, 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 using either 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 6 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 may change during the life of the task as a result of syncpoint activity.

Note:
When using MRO or ISC, 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:
Byte 0
Transaction facility identification
Bit 0
Transaction facility name = none
Bit 1
Transaction facility name = terminal
Bit 2
Transaction facility name = surrogate
Bit 3
Transaction facility name = destination
Bit 4
Transaction facility name = 3270 bridge
Bits 5-7
Reserved
Byte 1
Transaction identification information
Bit 0
System transaction
Bit 1
Mirror transaction
Bit 2
DPL mirror transaction
Bit 3
ONC RPC alias transaction
Bit 4
WEB alias transaction
Bit 5
3270 bridge transaction
Bit 6
Reserved
Bit 7
CICS BTS Run transaction
Byte 2
MVS Workload Manager request (transaction) completion information
Bit 0
Report the total response time (begin-to-end phase) for completed work request (transaction)
Bit 1
Notify that the entire execution phase of the work request is complete
Bit 2
Notify that a subset of the execution phase of the work request is complete
Bits 3-7
Reserved
Byte 3
Transaction definition information
Bit 0
Taskdataloc = below
Bit 1
Taskdatakey = cics
Bit 2
Isolate = no
Bit 3
Dynamic = yes
Bits 4- 7
Reserved
Byte 4
Transaction origin type
Byte 5
Transaction status information
Bits 0-5
Reserved
Bit 6
Task purged on an open TCB
Bit 7
Task abnormally terminated
Note:
If bit 6 is set, the task has been purged while running on an open TCB, and its transaction timing clocks have been left in an unreliable state. Because of this, the clocks will be set to zero when the record is written by the CICS Monitoring Facility (CMF).
Byte 6
JVM information
Bit 0
JVM marked unresettable
Bits 1-7
Reserved
Byte 7
Recovery manager information
Bit 0
Indoubt wait = no
Bit 1
Indoubt action = commit
Bit 2
Recovery manager - UOW resolved with indoubt action
Bit 3
Recovery manager - shunt
Bit 4
Recovery manager - unshunt
Bit 5
Recovery manager - indoubt failure
Bit 6
Recovery manager - resource owner failure
Bit 7
Reserved
Note:
Bits 2 through 6 will be reset on a SYNCPOINT request when the MSYNC=YES option is specified.
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 VTAM. If it is a VTAM resource and the network qualified name has not yet been received, NETID is 8 blanks. In all other cases it is nulls.
EXCMNRLU (TYPE-C, 8 BYTES)
Real network name if a network qualified name has been received from VTAM. In all other cases this field will be the same as LUNAME (field id 111). For non-VTAM resources it is nulls.

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

Table 7. Possible values of EXCMNTYP, EXCMNRTY, and EXCMNRID The relationship between exception type, resource type, and resource identification.
EXCMNTYP Exception type EXCMNRTY Resource type EXCMNRID Resource ID MEANING
EXCMNWT
‘CFDTLRSW’
poolname
Wait for CF data tables locking request slot
EXCMNWT
‘CFDTPOOL’
poolname
Wait for CF data tables non-locking request slot
EXCMNWT
‘STORAGE’
‘UDSA’
Wait for UDSA storage
EXCMNWT
‘STORAGE’
‘EUDSA’
Wait for EUDSA storage
EXCMNWT
‘STORAGE’
‘CDSA’
Wait for CDSA storage
EXCMNWT
‘STORAGE’
‘ECDSA’
Wait for ECDSA storage
EXCMNWT
‘STORAGE’
‘SDSA’
Wait for SDSA storage
EXCMNWT
‘STORAGE’
‘ESDSA’
Wait for ESDSA storage
EXCMNWT
‘STORAGE’
‘RDSA’
Wait for RDSA storage
EXCMNWT
‘STORAGE’
‘ERDSA’
Wait for ERDSA storage
EXCMNWT
‘TEMPSTOR’
TS Qname
Wait for temporary storage
EXCMNSWT
‘FILE’
filename
Wait for string associated with file
EXCMNSWT
‘LSRPOOL’
filename
Wait for string associated with LSRPOOL
EXCMNSWT
‘TEMPSTOR"
TS Qname
Wait for string associated with DFHTEMP
EXCMNBWT
‘LSRPOOL’
LSRPOOL
Wait for buffer associated with LSRPOOL
EXCMNBWT
‘TEMPSTOR’
TS Qname
Wait for buffer associated with DFHTEMP
End of Product-sensitive programming interface

Related tasks
Controlling CICS monitoring
Processing CICS monitoring facility output

Related concepts
The CICS monitoring facility
The classes of monitoring data: Overview
Event monitoring points
The monitoring control table (MCT)

Related reference
Interpreting CICS monitoring
Notes on the performance data
Performance class data
Transaction resource class data
[[ Contents Previous Page | Next Page Index ]]