CICS PA-specific fields

Here is a list of CICS PA-specific fields that you can use in report forms:

ALERT
For Performance Summary alert reporting, the count or percentage total of transactions at the specified alert severity (Critical, Warning, or Info) for the summary key.
APPLID
CICS generic APPLID.
APPLRECS
Number of Application records in this Network Unit-of-Work Extract record. All Cross-System Work Extract records include this field.
COMMWAIT
Total time value of the communications related fields IRWAIT, ISWAIT, SZWAIT, TCWAIT, LU61WAIT, and LU62WAIT.
DPLRECS
Number of Distributed Program Link (DPL) records in this Network Unit-of-Work Extract record. This is a subset of FUNCSHIP, the Function Shipping record count. All Cross-System Work Extract records include this field.
FILENAME
Transaction resource class data only: VSAM file name.
FUNCSHIP
Number of Function Shipping records in this Network Unit-of-Work Extract record. All Cross-System Work Extract records include this field.
IOWAIT
Total time value of the I/O wait time fields FCWAIT, JCWAIT, TDWAIT, TSWAIT.
IRESP
CICS® internal response time for the transaction. It is calculated by the difference in the Start and Stop times minus the time spent waiting on the terminal (operator think time).
JOBNAME
Jobname of the CICS system.
JVMMTIME
JVM method time, the elapsed time spent in the CICS JVM by the user task, excluding the JVM initialize and reset elapsed times. It is calculated as:

JVM elapsed time (JVMTIME) - JVM init time (JVMITIME) - JVM reset time (JVMRTIME)

MVSID
SMF system ID.
Start of changeOSLATNCYEnd of change
Start of changeLatency since start of originating transaction. It is calculated as the difference between the Start time of the current transaction and the Start time of the originating transaction.End of change
Start of changePHLATNCYEnd of change
Start of changePrevious hop latency time for the transaction. It is calculated as the difference between the Start time of the current transaction and the Start time of the previous hop transaction.End of change
RELEASE
CICS release. For example, CICS TS V4.1 is 660.
RESPONSE
CICS response time for the transaction. It is calculated as the difference between the Start and Stop times.
RMIOTIME
Elapsed time the task was suspended by the dispatcher while in the Resource Manager Interface (RMI), excluding time waiting for DB2® and IMS™. It is calculated as:

RMI suspend time (RMISUSP) - IMS wait time (IMSWAIT) - DB2 readyq wait time (DB2RDYQW) - DB2 connection wait time (DB2CONWT) - DB2 wait time (DB2WAIT)

TASKCNT
For Summary reporting only: the total number of tasks (CMF records).
TASKTCNT
For Summary reporting only: the total number of completed tasks (CMF termination records).
TOTCPU
The total task CPU time. This field is calculated as:

User CPU Time (DFHTASK S008) + RLS File Request CPU Time (DFHFILE S175)

TOTRECS
Total number of records in this Network Unit-of-Work Extract record. All Cross-System Work Extract records include this field. It is calculated as:

APPLRECS + TRANROUT + FUNCSHIP + DPLRECS

TRANROUT
Number of terminal-owning region records in this Network Unit-of-Work Extract record. All Cross-System Work Extract records include this field.
UOWID
Network unit-of-work ID: the first 6 bytes of NETUOWSX DFHTASK C098 that uniquely identifies this unit of work. This ID is assigned at attach time using either a STCK token (when the task is attached to a local terminal), or the network unit of work ID passed as part of an ISC APPC or IRC attach header. The system clock will wrap at intervals of several months.
UOWSEQ
Network unit-of-work ID sequence number: the last 2 bytes of NETUOWSX DFHTASK C098. This field is the period count, typically incremented at each syncpoint.