Descriptions of the performance data fields in the DFHCICS
group, including the numeric identifer, type, and size of each field.
- 005 (TYPE-T, 'START', 8 BYTES)
- Start time of measurement interval, which is one of the following
times:
- The time at which the user task was attached.
- The time at which data recording was most recently reset in support
of the MCT user event monitoring point DELIVER option or the monitoring
options MNCONV, MNSYNC, or FREQUENCY.
For more information, see Clocks and time stamps.
- 006 (TYPE-T, 'STOP', 8 BYTES)
- Finish time of measurement interval, which is one of the following
times:
- The time at which the user task was detached.
- the time at which data recording was completed in support of the
MCT user event monitoring point DELIVER option or the monitoring options
MNCONV, MNSYNC, or FREQUENCY.
For more information, see Clocks and time stamps.
- 025 (TYPE-A, 'CFCAPICT', 4 BYTES)
- Number of CICS® OO foundation class requests, including
the Java™ API for CICS (JCICS)
classes, issued by the user task.
- 089 (TYPE-C, 'USERID', 8 BYTES)
- User identification at task creation. This identification 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.
- 103 (TYPE-S, 'EXWTTIME', 12 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
on exception conditions, see Exception class data: Listing of data fields. For more information
on clocks, see Clocks and time stamps.
Note: The
performance class data field 'EXWTTIME' is updated when exception
conditions are encountered even when the exception class is inactive.
- 112 (TYPE-C, 'RTYPE', 4 BYTES)
- Performance record type (low-order byte-3):
- 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 sync point
- T
- Record output for the end of a task.
- 130 (TYPE-C, 'RSYSID', 4 BYTES)
- The name (SYSID) of the remote system to which this transaction
was routed either statically or dynamically.
This field also includes
the connection name (SYSID) of the remote system to which this transaction
was routed when using the CRTE routing transaction. The field is null
for those CRTE transactions that establish or cancel the transaction
routing session.
Note: If the transaction was not routed or was
routed locally, this field is set to null. Also see the program name
(field 71).
- 131 (TYPE-A, 'PERRECNT', 4 BYTES)
- The number of performance class records written by the CICS Monitoring
Facility (CMF) for the user task.
- 167 (TYPE-C, 'SRVCLASS', 8 BYTES)
- The z/OS Workload Manager (WLM) service class for this
transaction. This field is null if no transaction classification rules
are defined for CICS subsystems in the active z/OS Workload
Manager (WLM) service policy, or if the transaction was WLM-classified
in another CICS region.
- 168 (TYPE-C, 'RPTCLASS', 8 BYTES)
- The z/OS Workload Manager (WLM) report class for this
transaction. This field is null if no transaction classification rules
are defined for CICS subsystems in the active z/OS Workload
Manager (WLM) service policy, or if the transaction was WLM-classified
in another CICS region.
- 351 (TYPE-C, 'OADID', 64 BYTES)
- The adapter identifier added to the origin data by the adapter.
This field is blank if the task was not started by using an adapter,
or if it was and the adapter did not set this value.
- 352 (TYPE-C, 'OADATA1', 64 BYTES)
- The data added to the origin data by the adapter. This field is
blank if the task was not started by using an adapter, or if it was
and the adapter did not set this value.
- 353 (TYPE-C, 'OADATA2', 64 BYTES)
- The data added to the origin data by using the adapter. This field
is blank if the task was not started by using an adapter, or if it
was and the adapter did not set this value.
- 354 (TYPE-C, 'OADATA3', 64 BYTES)
- The data added to the origin data by the adapter. This field is
blank if the task was not started by using an adapter, or if it was
and 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.
- 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
- 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')
- Bits 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
- Reserved.
- 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', 8 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 originating 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 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. See Previous hop data characteristics for more information
about previous hop data.
- 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.
- 449 (TYPE-A, 'MPPRTXCD', 4 BYTES)
- Number of policy rule thresholds that this task has exceeded.
This field is all nulls (0x00 bytes) if no thresholds have been exceeded
or if the task has no policy rules applied to it.