This section describes the transaction header fields in a transaction
monitoring resource record.
- MNR_ID_TRANID (Type-C, 4 bytes)
- Transaction identifier.
- MNR_ID_TERMID (Type-C, 4 bytes)
- Terminal identifier. This field is null if the task is not associated
with a terminal or session.
- MNR_ID_USERID (Type-C, 4 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.
- MNR_ID_SYTPE (Type-C, 4 bytes)
- Transaction start type. The high-order byte (0 and 1) can have
one of the following values:
- 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)
- MNR_ID_START (Type-T, 8 bytes)
- Start time of the transaction.
- MNR_ID_STOP (Type-T, 8 bytes)
- Stop time of the transaction.
- MNR_ID_TASKNO (Type-A, 4 bytes)
- The transaction identification number (the task number allocated
to the transaction at task attach).
- MNR_ID_LUNAME (Type-C, 8 bytes)
- VTAM® logical unit name
(if available) of the terminal associated with this transaction. If
the task is executing in an application-owning or file-owning region,
the LUNAME is the generic applid of the originating connection for
MRO, LUTYPE6.1, and LUTYPE6.2 (APPC). The LUNAME is blank if the originating
connection is an external CICS® interface
(EXCI).
- MNR_ID_PGMNAME (Type-C, 8 bytes)
- The name of the first program invoked at attach-time. For more
information, see the performance class data field PGMNAME (owner:
DFHPROG, field ID: 071).
- MNR_ID_UOW_PX (Type-C, 20 bytes)
- This field contains the same information as the performance class
data field NETUOWPX (owner: DFHTASK, field ID: 097).
- MNR_ID_UOW_SX (Type-C, 8 bytes)
- This field contains the same information as the performance class
data field NETUOWSX (owner: DFHTASK, field ID: 098).
- MNR_ID_TRN_FLAGS (Type-A, 8 bytes)
- Transaction flags, a string of 64 bits used for signaling transaction
definition and status information. For details, see the performance
class data field TRANFLAG (owner: DFHTASK, field ID: 164).
- MNR_ID_RSYSID (Type-C, 4 bytes)
- The name (system ID) of the remote system to which this transaction
was routed, either statically or dynamically. For more information,
see the performance class data field RSYSID (owner: DFHCICS, field
ID: 130).
- MNR_ID_FCTYNAME (Type-C, 4 bytes)
- Transaction facility name. This field is null if the transaction
is not associated with a facility. You can identify the transaction
facility type (if any) using byte 0 of the transaction flags (MNR_ID_TRN_FLAGS)
field. For details, see the performance class data field FCTYNAME
(owner: DFHTASK, field ID: 163).
- MNR_ID_RTYPE (Type-C, 4 bytes)
- Transaction resource monitoring record type (low-order byte-3).
Currently this can have only one value, T, indicating a record output
for task termination. For more information about record types, see
the performance class data field RTYPE (owner: DFHCICS, field ID:
112).
- TERMINFO (Type-A, 4 bytes)
- Terminal or session information for the task principal facility.
For more information about terminal information, see the performance
class data field TERMINFO (owner: DFHTERM, field ID: 165).
- MNR_ID_TERMCNNM (Type-C, 4 bytes)
- Terminal session connection name. If the terminal facility associated
with this transaction is a session, this field is the name of the
owning connection (system ID). For more information, see the performance
class data field TERMCNNM (owner: DFHTERM, field ID: 169).
- MNR_ID_RES_FLAGS (Type-A, 4 bytes)
- Resource flags, a string of 32 bits used for signaling resource
status information.
- Byte 0
- Resource status information:
- Bit 0
- Maximum number of files to be monitored (defined in the MCT) has
been exceeded by the transaction (X'80')
- Bit 1
- Maximum number of temporary storage queues to be monitored (defined
in the MCT) has been exceeded by the transaction (X'40')
- Bit 2
- The maximum number of distributed program link requests to be
monitored (defined in the MCT) has been exceeded by the transaction
(X'20').
- Bits 3-7
- Reserved.
- Bytes 1-3
- Reserved.
- MNR_ID_ISIPICNM (Type-C, 8 bytes)
- The name of the IPIC (IPCONN) entry of the TCP/IP service that
attached the user task. For more information, see field 305 (ISIPICNM)
in the DFHSOCK performance-class data group.
- MNR_ID_CLIPADDR (Type-C, 40 bytes)
- The IP address of the originating client or Telnet client. For
more information, see field 318 (CLIPADDR) in the DFHSOCK performance-class
data group.
- MNR_ID_ORIGIN_NETWKID (Type-C, 8 bytes)
- The network identifier from which this work request (transaction)
originated. For more information, see field 359 (ONETWKID) in the
DFHCICS performance data group.
- MNR_ID_ORIGIN_APPLID (Type-C, 8 bytes)
- The applid of the CICS region
where this work request (transaction) originated; for example, the
region in which the CWXN task ran. For more information, see field
360 (OAPPLID) in the DFHCICS performance data group.
- MNR_ID_ORIGIN_ATT_TIME (Type-T, 8 bytes)
- The time when the originating task, for example, the CWXN task,
was started. For more information, see field 361 (OSTART) in the DFHCICS
performance data group.
- MNR_ID_ORIGIN_TRANNUM (Type-P, 4 bytes)
- The number of the originating task; for example, the CWXN task.
For more information, see field 362 (OTRANNUM) in the DFHCICS performance
data group.
- MNR_ID_ORIGIN_TRANID (Type-C, 4 bytes)
- The transaction ID (TRANSID) of the originating task; for example,
the CWXN task. For more information, see field 363 (OTRAN) in the
DFHCICS performance data group.
- MNR_ID_ORIGIN_USERID (Type-C, 8 bytes)
- The originating Userid-2 or Userid-1, for example, from CWBA,
depending on the originating task. For more information, see field
364 (OUSERID) in the DFHCICS performance data group.
- MNR_ID_ORIGIN_USER_CORR (Type-C, 64 bytes)
- The originating user correlator. For more information, see field
365 (OUSERCOR) in the DFHCICS performance data group.
- MNR_ID_ORIGIN_TCPIPSERV (Type-C, 8 bytes)
- The name of the originating TCPIPSERVICE. For more information,
see field 366 (OTCPSVCE) in the DFHCICS performance data group.
- MNR_ID_ORIGIN_PORTNUM (Type-A, 4 bytes)
- The port number used by the originating TCPIPSERVICE. For more
information, see field 367 (OPORTNUM) in the DFHCICS performance data
group.
- MNR_ID_ORIGIN_CLIPADDR (Type-C, 40 bytes)
- The IP address of the originating client or Telnet client. For
more information, see field 372 (OCLIPADR) in the DFHCICS performance
data group.
- MNR_ID_ORIGIN_CLIPPORT (Type-A, 4 bytes)
- The TCP/IP port number of the originating client or Telnet client.
For more information, see field 369 (OCLIPORT) in the DFHCICS performance
data group.
- MNR_ID_ORIGIN_TRANFLAG (Type-A, 8 bytes)
- The originating transaction flags. This 64-bit string is used
for signaling transaction definition and status information. For more
information, see field 370 (OTRANFLG) in the DFHCICS performance data
group.
- MNR_ID_ORIGIN_FCTYNAME (Type-C, 8 bytes)
- The facility name of the originating transaction. If the originating
transaction is not associated with a facility, this field is null.
For more information, see field 371 (OFCTYNME) in the DFHCICS performance
data group.