All of the exception class data fields that can be produced by
the CICS® Monitoring Facility
(CMF) are described in this section.
In contrast to performance class data records whose format is described
in associated dictionary entries, exception class data records are
not defined in the dictionary record. The exception class data records
are fixed format.
The following field descriptions show the name of the exception
class data field, the type, and the size. The data type can be one
of the following:
- A - a 32- or 64- bit count
- C - a character string
- P - a packed decimal
- T - a time stamp
- EXCMNTRN (Type-C, 4 bytes)
- Transaction identification.
- EXCMNTER (Type-C, 4 bytes)
- Terminal or session 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 attach. This can also be a 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)
- Type of transaction start (Start Code or Start Type):
- TO
- The transaction was started (attached) by input of the transaction
ID from the terminal user.
- S
- Attached by automatic transaction initiation (ATI) without data.
The transaction was started (attached) by an application program using
the EXEC CICS START TRANSID('xxxx')
... API command. CICS internal
transactions such as CATR, CEJR, CESN, CQRY, CRPM, CRSQ, CSFU, CSGM,
CXRE, and CWBG are just some examples of CICS transactions that use this start type.
- SD
- Attached by automatic transaction initiation (ATI) with data.
The transaction was started (attached) by an application program using
the EXEC CICS START TRANSID('xxxx')
FROM(xxxx) ... API command. CICS internal
transactions such as CLS1 is an example of a transaction that uses
this start type.
- QD
- The transaction was started (attached) because the trigger level
of an intrapartition transient data queue was reached. If the transaction
is not associated with a terminal facility, the Transaction Facility
Name (field: FCTYNAME, owner: DFHTASK, field ID: 163) provides the
name of the transient data queue ID.
- U
- The transaction was started (attached) by a CICS internal function generally as a result
of some user request. CICS internal
transactions such as CATA, CATD, CEJR, CESC, CEX2, CFOR, CFQR, CFQS,
CFTL, CGRP, CIEP, CIOF, CIOR, CIRP, CITS, CJTR, CLQ1, CLQ2, CLS2,
COTR, COVR, CPLT, CPMI, CRSY, CSFR, CSHQ, CSNC, CSNE, CSOL, CSSY,
CSTE, CSZI, CWBA, and CWXN are just some examples of the CICS transactions that use this start type.
In addition to CICS internal
functions, transaction's that are being run under the control of the CICS Execution Diagnostic Facility
transaction, CEDF, are also started (attached) with this start type.
- TP
- Attached from terminal (TCTTE) transaction ID. The preset transaction
was started (attached) by input from the terminal user or by the previous
transaction using the EXEC CICS RETURN
TRANSID('xxxx') IMMEDIATE ... API command. The transaction ID can
be preset either from the terminal definition, from using the CRTE
routing transaction, or by the previous transaction's application
program using the EXEC CICS RETURN
TRANSID('xxxx') ... API command with or without the IMMEDIATE option
specified. Some examples of CICS transactions
which use this start type are: CESN (except when used as the initial
good morning transaction), CRTE (when invoked on the routed system),
and CSSF when invoked as part of a CRTE CANCEL (the initial CRTE transaction
which establishes the routing session uses the start type 'TO').
- SZ
- Attached by the Front End Programming Interface (FEPI). The transaction
was started (attached) as the receive program by the Front
End Programming Interface as a result of inbound data. In addition
to inbound data arriving, the receive program is also started
(attached) if the time limit set by a FEPI START command expires,
the session is lost, or anything that causes a FEPI RECEIVE command
to complete. See the CICS Front
End Programming Interface User's Guide for more information
on FEPI started tasks.
- 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 (owner: DFHCICS, field ID: 103), is a calculation
based on subtracting the start time of the exception (EXCMNSTA) from
the finish time of the exception (EXCNBSTO).
- EXCMNTNO (Type-P, 4 bytes)
- The transaction identification number.
Note: The transaction
number field is normally a 4-byte packed decimal number. However,
some CICS system tasks are
identified by special characters in this field, as follows:
- III
- for system initialization tasks
- TCP
- for
the terminal control task
These special identifiers are placed in
bytes 2 through 4. Byte 1 is blank (X'40') before the terminal
control TCP identifier, and a null value (X'00') before the
others.
- EXCMNTPR (Type-A, 4 bytes)
- The transaction priority of the task when monitoring of the task
was initialized at transaction attach.
- EXCMNLUN (Type-C, 8 bytes)
- The LUNAME field is either the VTAM® netname
(LUname) of the terminal ID (if the Access Method for the terminal
is VTAM) or the VTAM generic APPLID of the connection for the
session ID (for an EXCI connection this field is blank). The transaction's
terminal or session type can be identified from the Nature (byte 0)
field within the terminal information TERMINFO field (owner: DFHTERM,
field ID: 165). This field is null if the transaction was not associated
with a terminal or session facility.
- EXCMNEXN (Type-A, 4 bytes)
- The exception sequence number for this task.
- EXCMNRTY (Type-C, 8 bytes)
- The exception resource type. For more information, see Table 1.
- EXCMNRID (Type-C, 8 bytes)
- The exception resource identification. For more information, see Table 1.
- EXCMNTYP (Type-A, 2 bytes)
- The 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)
For more information on the exception types, see Table 1.
- EXCMNTCN (Type-C, 8 bytes)
- The transaction's transaction class name (TRANCLASS). This field
is null if the transaction is not defined in a transaction class.
- EXCMNSRV (Type-C, 8 bytes)
- The MVS™ Workload Manager
(WLM) service class 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
the transaction was WLM-classified in another CICS region.
- EXCMNRPT (Type-C, 8 bytes)
- The MVS Workload Manager
(WLM) report class 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
the transaction was WLM-classified in another CICS region.
- EXCMNNPX (Type-C, 20 bytes)
- The 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 MRO attach header. At least three
padding bytes (X'00') are present at the right end of the
name.
If the originating terminal is VTAM across an ISC APPC or IRC MRO link, the
NETNAME is the networkid.LUname. If the terminal is non-VTAM,
the NETNAME is networkid.generic_APPLID.
All originating
information is 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 hexadecimal address space ID.
For more information on the external CICS interface (EXCI), see the CICS External Interfaces Guide.
- EXCMNNSX (Type-C, 8 bytes)
- The
name by which the network unit-of-work ID is known within the originating
system. This name is assigned at transaction attach time using either
a STCK-derived token created by the originating system, or the network
unit-of-work ID passed as part of an IRC (MRO) or ISC (APPC) attach
function management header (FMH).
The first six bytes of this
field are a binary value derived from the system clock of the originating
system and which can wrap round at intervals of several months.
The
last two bytes of this field are a syncpoint sequence count. This
count might change during the life of the task as a result of syncpoint
activity.
For CICS BTS
transactions, the network unit-of-work ID is also passed to a transaction
that is invoked synchronously by an application program issuing either
a CICS BTS run ACQPROCESS synchronous
or run activity synchronous command.
Note: When using MRO or ISC,
the EXCMNNSX field can be combined with the EXCMNNPX field to uniquely
identify a task across each CICS system.
It must be combined with the EXCMNNPX because the EXCMNNSX field on
its own is unique only to the originating CICS system.
- EXCMNTRF (Type-A, 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
- Bit 5-7
- Reserved
- Byte 1
- Transaction identification information:
- Bit 0
- System transaction
- Bit 1
- Mirror transaction
- Bit 2
- DPL Mirror transaction
- Bit 4
- ONC RPC alias transaction
- Bit 4
- WEB alias transaction
- Bit 5
- 3270 Bridge transaction
- Bit 6
- Reserved
- Bit 7
- CICS BTS run transaction
(ACQPROCESS or activity) synchronous
- Byte 2
- MVS workload manager request
(transaction) completion information:
- Bit 0
- Report the total response time (begin-to-end phase) for the completed
work request (transaction)
- Bit 1
- Notify that the entire execution phase of the work request (transaction)
is complete
- Bit 2
- Notify that a subset of the execution phase of the work request
(transaction) is complete
- Bit 3-7
- Reserved
- Byte 3
- Transaction definition information:
- Bit 0
- Taskdataloc = BELOW
- Bit 1
- Taskdatakey = CICS
- Bit 2
- Isolate = NO
- Bit 3
- Dynamic = YES
- Bit 4-7
- Reserved
- Byte 4
- Transaction origin type, DFHTASK fields for
details.
- Byte 5
- Reserved
- Byte 6
- JVM status information:
- Bit 0
- JVM marked unresettable
- Bit 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
- 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 using byte 0 of the transaction flags field,
TRANFLAG (owner: DFHTASK, field ID: 164).
- EXCMNCPN (Type-C, 8 bytes)
- The name of the application program that was currently executing
when the resource shortage condition occurred as identified by the
exception record.
- EXCMNBTR (Type-C, 4 bytes)
- 3270 Bridge listener transaction identification.
- EXCMNURI (Type-C, 16 bytes)
- RRMS/MVS unit-of-recovery ID (URID).
For more general information
on the Recoverable Resource Management Services (RRMS), see the CICS External Interfaces Guide.
- EXCMNRIL (Type-A, 4 bytes)
- The length of the resource name in the exception resource identification
field, EXCMNRIX.
- EXCMNRIX (Type-C, 256 bytes)
- The exception resource identification (extended).
- EXCMNNID (Type-C, 8 bytes)
- The network ID field, NETID, is the network ID portion of the
Network Qualified Name (NQNAME) received from VTAM during bind or logon for CICS terminal resources using any VTAM LUALIAS (defined or dynamic). If the resource
has not logged on or an NQNAME was not received, then this field is
set to null.
- EXCMNRLU (Type-C, 8 bytes)
- The Real LUname (EXCMNRLU) field is the VTAM netname (LUname) of the terminal ID for CICS terminal resources using any VTAM LUALIAS (defined or dynamic).
If the resource has not logged on or an NQNAME was not received,
then this field is set to null. Also, see the field, EXCMNLUN.
Table 1 shows the values and relationships
of the exception type (EXCMNTYP), resource type (EXCMNRTY), and resource
identification (EXCMNRID) fields.
Table 1. Relationships between the exception
type, resource type, and resource identificationEXCMNTYP Exception type
|
EXCMNRTY Resource type
|
EXCMNRID Resource ID
|
Exception description |
EXCMNWT |
CFDTLRSW |
poolname |
Wait for a CF data table locking request
slot. |
EXCMNWT |
CFDTPOOL |
poolname |
Wait for a CF data table non-locking
request slot. |
EXCMNWT |
STORAGE |
CDSA |
Wait for CDSA storage |
EXCMNWT |
STORAGE |
ECDSA |
Wait for ECDSA storage |
EXCMNWT |
STORAGE |
UDSA |
Wait for UDSA storage |
EXCMNWT |
STORAGE |
EUDSA |
Wait for EUDSA 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 |
EXCMNBWT |
LSRPOOL |
filename |
Wait for a buffer associated with an
LSRPOOL |
EXCMNBWT |
TEMPSTOR |
TS Qname |
Wait for a buffer associated with DFHTEMP |
EXCMNSWT |
FILE |
filename |
Wait for a string associated with a
file |
EXCMNSWT |
LSRPOOL |
filename |
Wait for a string associated with an
LSRPOOL |
EXCMNSWT |
TEMPSTOR |
TS Qname |
Wait for a string associated with DFHTEMP |
Note: The extended resource ID field, EXCMNRIX, should be used for
analyzing the exception records for the TEMPSTOR exception resource
types because the temporary storage queue names are now 16-bytes in
length.