DFHCICS owns the following performance class data fields:
- 005 (Type-T, START, 8 bytes)
- The start time (in GMT) of the measurement period. This is either:
- The time at which the task was attached, or
- The time at which data recording was most recently restarted in
support of a user event monitoring point (EMP) DELIVER option or the
monitoring options MNCONVerse, MNSYNCpoint, or MNFREQuency.
Note: - CICS PA will
always convert the start time into local time before formatting and
printing.
- The transaction response time (or measurement period) can be calculated
by subtracting the START time from the STOP time.
- 006 (Type-T, STOP, 8 bytes)
- The finish time (in GMT) of the measurement period. This is either:
- the time at which the task was detached, or
- the time at which data recording was most recently completed for
the transaction in support of a user event monitoring point (EMP)
DELIVER option or the monitoring options MNCONVerse, MNSYNCpoint,
or MNFREQuency.
Note: - CICS PA will
always convert the stop time into local time before formatting and
printing.
- The transaction response time (or measurement period) can be calculated
by subtracting the START time from the STOP time.
- 025 (Type-A, CFCAPICT, 4 bytes)
- The total number of CICS® OO
foundation class requests and Java API
for CICS (JCICS) class requests
issued by the user task. CICS does
not distinguish between the OO foundation class and JCICS class requests.
- 089 (Type-C, USERID, 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.
- 103 (Type-S, EXWTTIME, 8 bytes)
- Accumulated data for exception conditions. The timer
component of the clock contains the total elapsed time for which the
user waited on exception conditions. The period count equals the number
of exception conditions that have occurred for this task.. For more
information, see CMF exception class data fields.
Note: This
field is updated when any of the exception conditions are encountered
by the user task even when the exception class is inactive.
- 112 (Type-C, RTYPE, 4 bytes)
- The performance record type (low-order byte-3). This field indicates
the reason why a performance record has been output for the user task.
It can be one of the following values:
- C
- Record output for a terminal converse
- D
- Record output for a user EMP DELIVER request
- F
- Record output for a long-running transaction
- S
- Record output for a syncpoint
- T
- Record output for a task termination.
- 130 (Type-C, RSYSID, 4 bytes)
- The Transaction Routing Sysid RSYSID field IDentifies the connection
name (sysid) of the remote system to which the transaction was routed.
If the transaction was not routed this field is null and the initial
program name (field: PGMNAME, owner: DFHPROG, field ID: 071) will
identify the initial application program name invoked for the transaction.
See Table 1 for more
details.
This field also identifies the connection name (sysid)
of the remote system to which the transaction was routed when using
the CRTE routing transaction. However, this field is null for those
CRTE transactions which establish or cancel the transaction routing
session.
- 131 (Type-C, PERRECNT, 4 bytes)
- The total number of performance class records written by the CICS Monitoring Facility (CMF)
for this user task.
- 167 (Type-C, SRVCLASS, 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.
The transaction flags field,
TRANFLAG (owner: DFHTASK, field ID: 164) can be used to determine
if this transaction was WLM-classified in another region.
See Workload Activity report.
- 168 (Type-C, RPTCLASS, 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.
The transaction flags field,
TRANFLAG (owner: DFHTASK, field ID: 164) can be used to determine
if this transaction was WLM-classified in another region.
See Workload Activity report.
351 (Type-C, OADID, 64 bytes
The adapter identifier added to the associated data origin descriptor
by the adapter. This field is blank if the task was not started through
an adapter, or if it was started through an adapter but the adapter
did not set this value.
352 (Type-C, OADATA1, 64 bytes
The data added to the associated data origin descriptor by the
adapter. This field is blank if the task was not started through an
adapter, or if it was started through an adapter but the adapter did
not set this value.
353 (Type-C, OADATA2, 64 bytes
The data added to the associated data origin descriptor by the
adapter. This field is blank if the task was not started through an
adapter, or if it was started through an adapter but the adapter did
not set this value.
354 (Type-C, OADATA3, 64 bytes
The data added to the associated data origin descriptor by the
adapter. This field is blank if the task was not started through an
adapter, or if it was started through an adapter but the adapter did
not set this value.
- 359 (Type-C, ONETWKID, 8 bytes
- The network identifier from which this work request (transaction)
originated.
- 360 (Type-C, OAPPLID, 8 bytes)
- The APPLID of the CICS region
in which this work request (transaction) originated; (for example,
the region in which the CWXN task ran).
- 361 (Type-T, OSTART, 8 bytes)
- The time at which the originating task (for example, the CWXN
task) was started.
- 362 (Type-P, OTRANNUM, 4 bytes)
- The number of the originating task (for example, the CWXN task).
- 363 (Type-C, OTRAN, 4 bytes)
- The transaction ID (TRANSID) of the originating task (for example,
the CWXN task).
- 364 (Type-C, OUSERID, 8 bytes)
- The originating Userid-2 or Userid-1 (for example, from CWBA),
depending on the originating task.
- 365 (Type-C, OUSERCOR, 64 bytes)
- The originating user correlator.
- 366 (Type-C, OTCPSVCE, 8 bytes)
- The name of the originating TCPIPSERVICE.
- 367 (Type-A, OPORTNUM, 4 bytes)
- The port number used by the originating TCPIPSERVICE.
- 368 (Type-C, OCLIPADR, 16 bytes)
- The IP address of the originating client (or Telnet client).
- 369 (Type-A, OCLIPORT, 4 bytes)
- The TCP/IP port number of the originating client (or Telnet client).
- 370 (Type-A, OTRANFLG, 8 bytes)
- Originating transaction flags, a string of 64 bits used for signaling
transaction definition and status information:
- Byte 0
- The facility-type of the originating transaction:
- Bit 0
- None (X'80')
- Bit 1
- Terminal (X'40')
- Bit 2
- Surrogate (X'20')
- Bit 3
- Destination (X'10')
- Bit 4
- 3270 bridge (X'08')
- Bit 5
- Reserved
- Bit 6
- Reserved
- Bit 7
- Reserved
- Byte 1
- Transaction identification information:
- Bit 0
- System transaction (X'80')
- Bit 1
- Mirror transaction (X'40')
- Bit 2
- DPL mirror transaction (X'20')
- Bit 3
- ONC/RPC Alias transaction (X'10')
- Bit 4
- WEB Alias transaction (X'08')
- Bit 5
- 3270 Bridge transaction (X'04')
- Bit 6
- Reserved (X'02')
- Bit 7
- CICS BTS Run transaction
(X'01')
- Byte 2
- Reserved.
- Byte 3
- Transaction definition information:
- Bit 0
- Taskdataloc = below (x'80')
- Bit 1
- Taskdatakey = cics (x'40')
- Bit 2
- Isolate = no (x'20')
- Bit 3
- Dynamic = yes (x'10')
- Bit 4-7
- Reserved
- Byte 4
- The type of the originating transaction:
- X'01'
- None
- X'02'
- Terminal
- X'03'
- Transient data
- X'04'
- START
- X'05'
- Terminal-related START
- X'06'
- CICS business transaction
services (BTS) scheduler
- X'07'
- Transaction manager domain (XM)-run transaction
- X'08'
- 3270 bridge
- X'09'
- Socket domain
- X'0A'
- CICS Web support (CWS)
- X'0B'
- Internet Inter-ORB Protocol (IIOP)
- X'0C'
- Resource Recovery Services (RRS)
- X'0D'
- LU 6.1 session
- X'0E'
- LU 6.2 (APPC) session
- X'0F'
- MRO session
- X'10'
- External Call Interface (ECI) session
- X'11'
- IIOP domain request receiver
- X'12'
- Request stream (RZ) instore transport
- X'13'
- IP interconnectivity session
- X'14'
- Event
Byte 5
Transaction status information:- Bit 0
- This transaction is the originating transaction
- Bit 1
- Reserved
- Bit 2
- Resource Class records for this task
- Bit 3
- Identity Class records for this task
- Bit 4
- Reserved
- Bit 5
- Reserved
- Bit 6
- Task purged on an open TCB
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).
- Bit 7
- Task abnormally terminated

- Byte 6
- 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
- 371 (Type-C, OFCTYNME, 4 bytes)
- The facility name of the originating transaction. If the originating
transaction is not associated with a facility, this field is null.
The transaction facility type, if any, can be identified using byte
0 of the transaction flags, OTRANFLG (370), field.
- 372 (Type-C, OCLIPADR, 40 bytes)
- The IP address of the originating client or Telnet client.
373 (Type-C, PHNTWKID, 8 bytes
The network identifier of the CICS system of an immediately previous
task in another CICS system with which this task is associated.
374 (Type-C, PHAPPLID, 8 bytes
The APPLID of the CICS system of an immediately previous task
in another CICS region with which this task is associated.
375 (Type-T, PHSTART, 8 bytes
The start time of the immediately previous task in another CICS
system with which this task is associated.
376 (Type-P, PHTRANNO, 4 bytes
The task number of the immediately previous task in another CICS
system with which this task is associated.
377 (Type-C, PHTRAN, 4 bytes
The transaction ID (TRANSID) of the immediately previous task
in another CICS system with which this task is associated.
378 (Type-A, PHCOUNT, 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.
- 402 (Type-A, EICTOTCT, 4 bytes)
- The total number of EXEC CICS commands
issued by the user task.
- 405 (Type-A, TIASKTCT, 4 bytes)
- The number of EXEC CICS ASKTIME
commands issued by the user task.
- 406 (Type-A, TITOTCT, 4 bytes)
- The total number of EXEC CICS ASKTIME,
CONVERTTIME, and FORMATTIME commands issued by the user task.
- 408 (Type-A, BFDGSTCT, 4 bytes)
- The total number of EXEC CICS BIF
DIGEST commands issued by the user task.
- 409 (Type-A, BFTOTCT, 4 bytes)
- The total number of EXEC CICS BIF
DEEDIT and BIF DIGEST commands issued by the user task.
- 415 (Type-A, ECSIGECT, 4 bytes)
- The number of EXEC CICS SIGNAL
EVENT commands issued by the user task.
- 416 (Type-A, ECEFOPCT, 4 bytes)
- The number of event filter operations performed by the user task.
- 417 (Type-A, ECEVNTCT, 4 bytes)
- The number of events captured by the user task.
418 (Type-A, ECSEVCCT, 4 bytes)
The number of synchronous emission events captured by the user
task.