Identity class data: Listing of data fields

The identity class data is listed in the order in which it appears in the identity class data section of a monitoring record.

All the identity class data records produced by a single CICS® run have the same format, with an identity record header followed by an identity data section for each transaction being monitored. The format of the identity class data section of a monitoring record can be mapped by the DSECT DFHMNIDS.

Header fields

These fields are the header fields in an identity class monitoring record.

MNI_ID_TRANID (TYPE-C, 4 BYTES)

Transaction identifier.

MNI_ID_TERMID (TYPE-C, 4 BYTES)

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

MNI_ID_USERID (TYPE-C, 8 BYTES)

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

MNI_ID_STYPE (TYPE-C, 4 BYTES)

Transaction start type. The high-order bytes (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 the transient data trigger level
"U ": Attached by a user request
"TP": Attached from a terminal TCTTE transaction ID
"SZ": Attached by the Front End Programming Interface (FEPI)

MNI_ID_START (TYPE-T, 8 BYTES)

Start time of the transaction.

MNI_ID_STOP (TYPE-T, 8 BYTES)

Stop time of the transaction.

MNI_ID_TASKNO (TYPE-A, 4 BYTES)

The transaction identification number (the task number allocated to the transaction at task attach).

MNI_ID_LUNAME (TYPE-C, 8 BYTES)

z/OS® Communications Server logical unit name (if available) of the terminal associated with this transaction. If the task is running 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).

MNI_ID_PGMNAME (TYPE-C, 8 BYTES)

The name of the first program called at attach-time. For more information, see field 071 (PGMNAME) in the DFHPROG performance data group.

MNI_ID_UOW_PX (TYPE-C, 20 BYTES)

This field contains the same information as the performance class data field NETUOWPX. See NETUOWPX, in group DFHTASK for details.

MNI_ID_UOW_SX (TYPE-C, 8 BYTES)

This field contains the same information as the performance class data field NETUOWSX. See NETUOWSX, in group DFHTASK for details.

MNI_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 field 130 (RSYSID) in the DFHCICS performance data group.

MNI_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 field 164 (TRANFLAG) in the DFHTASK performance data group.

MNI_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 field 163 (FCTYNAME) in the DFHTASK performance data group.

MNI_ID_RTYPE (TYPE-C, 4 BYTES)

Transaction resource monitoring record type (low-order byte 3). Currently this record type can have only one value, T, indicating a record produced for task termination. For more information about record types, see field 112 (RTYPE) the DFHCICS performance data group.

MNI_ID_TERMINFO (TYPE-A, 4 BYTES)

Terminal or session information for the task principal facility. For more information about terminal information, see field 165 (TERMINFO) in the DFHTERM performance data group.

MNI_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 field 169 (TERMCNNM) in the DFHTERM performance data group.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_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.

MNI_PHD_NETWKID (TYPE-C, 8 BYTES)

The network identifier of the CICS system of an immediately previous task in another CICS system with which this task is associated. For more information, see field 373 (PHNTWKID) in the DFHCICS performance data group.

MNI_PHD_APPLID (TYPE-C, 8 BYTES)

The APPLID from previous hop data. This is the APPLID of the CICS system of a previous task in another CICS system with which this task is associated. For more information, see field 374 (PHAPPLID) in the DFHCICS performance data group.

MNI_PHD_ATTACH_TIME (TYPE-T, 8 BYTES)

The start time of the immediately previous task in another CICS system with which this task is associated. For more information, see field 375 (PHSTART) in the DFHCICS performance data group.

MNI_PHD_TRANNO (TYPE-P, 4 BYTES)

The task number of the immediately previous task in another CICS system with which this task is associated. For more information, see field 376 (PHTRANNO) in the DFHCICS performance data group.

MNI_PHD_TRANID (TYPE-C, 4 BYTES

The transaction ID (TRANSID) of the immediately previous task in another CICS system with which this task is associated. For more information, see field 377 (PHTRAN) in the DFHCICS performance data group.

MNI_PHD_COUNT (TYPE-A, 4 BYTES)

The number of times there has been a request from one CICS system to another CICS system to initiate a task with which this task is associated. For more information, see field 378 (PHCOUNT) in the DFHCICS performance data group.

MNI_PTD_ATTACH_TIME (TYPE-T, 8 BYTES)

The start time of the immediately previous or parent task in the same CICS system with which this task is associated. For more information, see field 480 (PTSTART) in the DFHCICS performance data group.

MNI_PTD_TRANNUM (TYPE-P, 4 BYTES)

The task number of the immediately previous or parent task in the same CICS system with which this task is associated. For more information, see field 481 (PTTRANNO) in the DFHCICS performance data group.

MNI_PTD_TRANID (TYPE-C, 4 BYTES)

The transaction ID (TRANSID) of the immediately previous or parent task in the same CICS system with which this task is associated. For more information, see field 482 (PTTRAN) in the DFHCICS performance data group.

MNI_PTD_COUNT (TYPE-A, 4 BYTES)

The number of times there has been a request from one task to initiate another task in the same CICS system with which this task is associated, such as by a RUN TRANSID or START command. For more information, see field 483 (PTCOUNT) in the DFHCICS performance data group.

Data entry fields

Each identity record consists of an identity record header, an identity record identification section, and two identity data entries (an entry for the distinguished name and an entry for the realm). Each identity data entry consists of an entry identifier field, an entry length field, and a variable length entry field.

MNI_ENTRY_IDENT: Data entry identifier.
MNI_ENTRY_LENGTH: Length of the data entry that is specified by the data entry identifier.
MNI_ENTRY_FIELD: Data entry field.

Table 1. Identity record data entry fields
Data entry identifier decimal (hexadecimal)	Data entry length	Format	Description
1 (1)	1 - 246	UTF-8	A distinguished name, which uniquely identifies the user.
2 (2)	1 - 255	UTF-8	A realm, which identifies the set of resources to which the authentication information requested (that is, the user ID and password) applies.