Performance data in group DFHTASK

Performance data fields in the DFHTASK group are described, including the numeric identifier, type, and size of each field.

001 (TYPE-C, 'TRAN', 4 BYTES)

Transaction identification.

004 (TYPE-C,'TTYPE',4 BYTES)

Transaction start type. The high-order bytes (0 and 1) are set as follows:

'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)

007 (TYPE-S, 'USRDISPT', 12 BYTES)

Total elapsed time during which the user task was dispatched on each CICS® TCB under which the task ran. The TCB modes managed by the CICS dispatcher are: QR, RO, CO, FO, SZ ,RP, SL, SP, SO, EP, L8, L9, S8, TP, T8, X8, X9, and D2. Be aware that, for each CICS release, new TCB modes might be added to this list, or obsolete TCB modes might be removed. For more information about dispatch time and CPU time, see Transaction dispatch time and CPU time.

008 (TYPE-S, 'USRCPUT', 12 BYTES)

Processor time for which the user task was dispatched on each CICS TCB under which the task ran. The TCB modes managed by the CICS dispatcher are: QR, RO, CO, FO, SZ, RP, SL, SP, SO, EP, L8, L9, S8, TP, T8, X8, X9, and D2. Be aware that, for each CICS release, new TCB modes might be added to this list, or obsolete TCB modes might be removed. For more information about dispatch time and CPU time, see Transaction dispatch time and CPU time.

014 (TYPE-S, 'SUSPTIME', 12 BYTES)

Total elapsed wait time for which the user task was suspended by the dispatcher. This wait time includes these values:

The elapsed time waiting for the first dispatch. This elapsed time also includes any delay incurred because of the limits set for the class of the transaction (if any) or by the system parameter MXT being reached.
The task suspend (wait) time.
The elapsed time waiting for redispatch after a suspended task has been resumed.

For more information, see Transaction wait (suspend) times.

031 (TYPE-P, 'TRANNUM', 4 BYTES)

Transaction identification number. The transaction number field is normally a 4-byte packed decimal number. However, some CICS system tasks are identified by transaction numbers that comprise special characters, as follows:

' III': System initialization task
' TCP': Terminal control

These special identifiers are placed in bytes 2 - 4. Byte 1 is a blank (X'40') before the terminal control TCP identifier, and a null value (X'00') before the others.

059 (TYPE-A, 'ICPUINCT', 4 BYTES)

Number of interval control START or INITIATE requests during the user task.

064 (TYPE-A, 'TASKFLAG', 4 BYTES)

Task error flags, a string of 32 bits used for signaling unusual conditions occurring during the user task:

Bit 0: Reserved
Bit 1: Detected an attempt either to start a user clock that was already running or to stop one that was not running
Bits 2–31: Reserved

065 (TYPE-A, 'ICSTACCT', 4 BYTES)

Total number of local interval control START requests, with the CHANNEL option, issued by the user task.

066 (TYPE-A, 'ICTOTCT', 4 BYTES)

Total number of Interval Control Start, Cancel, Delay, and Retrieve requests issued by the user task.

082 (TYPE-C, 'TRNGRPID', 28 BYTES)

The transaction group ID is assigned at transaction attach time, and can be used to correlate the transactions that CICS runs for the same incoming work request; for example, the CWXN and CWBA transactions for Web requests. This transaction group ID relationship is useful when applied to the requests that originate through the CICS Web, ECI over TCP/IP, or 3270 bridge interface, as indicated by the transaction origin in byte 4 of the transaction flags field (group name DFHTASK, field ID 164). For more information on using the transaction group ID, see Transaction tracking in the CICS Intercommunication Guide.

097 (TYPE-C, 'NETUOWPX', 20 BYTES)

Fully qualified name by which the originating system is known to the z/OS® Communications Server network. This name is assigned at attach time using either the netname derived from the TCT (when the task is attached to a local terminal) or the netname passed as part of an ISC APPC or IRC attach header. At least three padding bytes (X'00') are present at the right end of the name.

If the originating terminal is z/OS Communications Server across an ISC APPC or IRC link, the NETNAME is the networkid.LUname. If the terminal is non-z/OS Communications Server, the NETNAME is networkid.generic_applid.

All originating information passed as part of an ISC LUTYPE6.1 attach header has the same format as the non-z/OS Communications Server terminal originators.

When the originator is communicating over an external CICS interface (EXCI) session, the name is a concatenation of:

  'DFHEXCIU | .       |  MVS Id    |  Address Space Id (ASID)'
   8 bytes  | 1 byte  |  4 bytes   |  4 bytes

derived from the originating system. That is, the name is a 17-byte LU name consisting of these fields:

An 8-byte eye-catcher set to 'DFHEXCIU'.
A 1-byte field containing a period (.).
A 4-byte field containing the MVSID, in characters, under which the client program is running.
A 4-byte field containing the address space ID (ASID) in which the client program is running. This field contains the 4-character EBCDIC representation of the 2-byte hex address space ID.

098 (TYPE-C, 'NETUOWSX', 8 BYTES)

Name by which the network unit of work ID is known in the originating system. This name is assigned at attach time using either an STCK-derived 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 (MRO) attach header.

The first 6 bytes of this field are a binary value derived from the system clock of the originating system and which can wrap round at intervals of several months.

The last 2 bytes of this field are for the period count. These bytes can change during the life of the task as a result of sync point activity.

When using MRO or ISC, the NETUOWSX field must be combined with the NETUOWPX field (097) to uniquely identify a task, because NETUOWSX is unique only to the originating CICS system.

102 (TYPE-S, 'DISPWTT', 12 BYTES)

Elapsed time for which the user task waited for redispatch. This time is the aggregate of the wait times between each event completion and user-task redispatch.

This field does not include the elapsed time spent waiting for first dispatch. This field is a component of the task suspend time, SUSPTIME (014), field.

109 (TYPE-C, 'TRANPRI', 4 BYTES)

Transaction priority when monitoring of the task was initialized (low-order byte-3).

123 (TYPE-S, 'GNQDELAY', 12 BYTES)

The elapsed time waiting for a CICS task control global enqueue. For more information, see Clocks and time stamps.

This field is a component of the task suspend time, SUSPTIME (014), field.

124 (TYPE-C, 'BRDGTRAN', 4 BYTES)

Bridge listener transaction identifier. For CICS 3270 Bridge transactions, this field is the name of the Bridge listener transaction that attached the user task.

125 (TYPE-S, 'DSPDELAY', 12 BYTES)

The elapsed time waiting for first dispatch.

This field is a component of the task suspend time, SUSPTIME (014), field. For more information, see Clocks and time stamps.

126 (TYPE-S, 'TCLDELAY', 12 BYTES)

The elapsed time waiting for first dispatch, which was delayed because of the limits set for the transaction class of this transaction, TCLSNAME (166), being reached. For more information, see Clocks and time stamps. This field is a component of the first dispatch delay, DSPDELAY (125), field.

127 (TYPE-S, 'MXTDELAY', 12 BYTES)

The elapsed time waiting for the first dispatch, which was delayed because of the limits set by the system parameter, MXT, being reached. The field is a component of the first dispatch delay, DSPDELAY (125), field.

128 (TYPE-S, 'LMDELAY', 12 BYTES)

The elapsed time that the user task waited to acquire a lock on a resource. A user task cannot explicitly acquire a lock on a resource, but many CICS modules lock resources on behalf of user tasks using the CICS lock manager (LM) domain.

For more information about CICS lock manager, see Investigating lock manager waits.

For information about times, see Clocks and time stamps, and Transaction wait (suspend) times.

This field is a component of the task suspend time, SUSPTIME (014), field.

129 (TYPE-S, 'ENQDELAY', 12 BYTES)

The elapsed time waiting for a CICS task control local enqueue. For more information, see Clocks and time stamps. This field is a component of the task suspend time, SUSPTIME (014), field.

132 (TYPE-T, 'RMUOWID', 8 BYTES)

The identifier of the unit of work (unit of recovery) for this task. Unit of recovery values are used to synchronize recovery operations among CICS and other resource managers, such as IMS and DB2®.

163 (TYPE-C, 'FCTYNAME', 4 BYTES)

Transaction facility name. This field is null if the transaction is not associated with a facility. The transaction facility type (if any) can be identified using byte 0 of the transaction flags, TRANFLAG, (164) field.

164 (TYPE-A, 'TRANFLAG', 8 BYTES)

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: Transaction facility name = none (x'80')
Bit 1: Transaction facility name = terminal (x'40')
If this bit is set, FCTYNAME and TERM contain the same terminal ID.
Bit 2: Transaction facility name = surrogate (x'20')
Bit 3: Transaction facility name = destination (x'10')
Bit 4: Transaction facility name = 3270 bridge (x'08')
Bits 5–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

z/OS workload manager request (transaction) completion information:

Bit 0

Report the total response time (begin-to-end phase) for completed work request (transaction).

Bit 1

Notify that the entire execution phase of the work request is complete.

Bit 2

Notify that a subset of the execution phase of the work request is complete.

Bit 3

This transaction has been reported to the z/OS workload manager as completing abnormally because it has tried to access DB2 and a connection unavailable response has been returned. This abnormal completion occurs when all the following are true:

Bit 0 is set.
CICS is not connected to DB2.
The CICS-DB2 adapter is in standby mode (STANDBYMODE(RECONNECT) or STANDBYMODE(CONNECT) ).
CONNECTERROR(SQLCODE) is specified, causing the application to receive a -923 SQL code.

Bits 4-7

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

Transaction origin type:

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': Sockets 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': IPIC session
X'14': Event
X'15': JVMSERVER

Byte 5

Transaction status information:

Bit 0: The transaction origin
Bit 1: Reserved
Bit 2: Resource class record, or records, for this task
Bit 3: Identity class record, or 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 was purged while running on an open TCB, and its transaction timing clocks were left in an unreliable state. Because of this, the clocks are set to zero when the record is written by the CICS Monitoring Facility (CMF).
Bit 7: Task abnormally terminated

Byte 6

Transaction tracking origin data tag. For more information about how to set the transaction tracking origin data tag, see The SET_TRACKING_DATA call.

Note: The transaction tracking origin data tag can be set in the record only when it is the transaction origin. The transaction origin can be determined when bit 0 is set in the transaction status information byte 5 of the TRANFLAG field.

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

Note: Bits 2 through 6 are reset on a SYNCPOINT request when the MNSYNC=YES option is specified.

166 (TYPE-C, 'TCLSNAME', 8 BYTES)

Transaction class name. This field is null if the transaction is not in a TRANCLASS.

170 (TYPE-S, 'RMITIME', 12 BYTES)

The total elapsed time spent in the CICS Resource Manager Interface (RMI). For more information, see Clocks and time stamps, Transaction wait (suspend) times, and RMI elapsed and suspend time.

171 (TYPE-S, 'RMISUSP', 12 BYTES)

The total elapsed time that the task was suspended by the CICS dispatcher while in the CICS Resource Manager Interface (RMI). For more information, see Clocks and time stamps, Transaction wait (suspend) times, and RMI elapsed and suspend time. The field is a component of the task suspend time, SUSPTIME (014), field and also the RMITIME (170) field.

181 (TYPE-S, 'WTEXWAIT', 12 BYTES)

The elapsed time that the user task waited for one or more ECBs, passed to CICS by the user task using the EXEC CICS WAIT EXTERNAL ECBLIST command, to be posted by the MVS™ POST command. The user task can wait on one or more ECBs. If it waits on more than one, it is dispatchable as soon as one of the ECBs is posted. For more information, see Clocks and time stamps and Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

182 (TYPE-S, 'WTCEWAIT', 12 BYTES)

The elapsed time that the user task waited for one of these events:

One or more ECBs, passed to CICS by the user task using the EXEC CICS WAITCICS ECBLIST command, to be posted by the MVS POST command. The user task can wait on one or more ECBs. If it waits on more than one, it is dispatchable as soon as one of the ECBs is posted.
Completion of an event initiated by the same or by another user task. The event is usually be the posting, at the expiration time, of a timer-event control area provided in response to an EXEC CICS POST command. The EXEC CICS WAIT EVENT command provides a method of directly giving up control to some other task until the event being waited on is completed.

For more information, see Clocks and time stamps and Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

183 (TYPE-S, 'ICDELAY', 12 BYTES)

The elapsed time that the user task waited as a result of issuing one of the following commands:

An interval control EXEC CICS DELAY command for a specified time interval.
An interval control EXEC CICS DELAY command for a specified time of day to expire.
An interval control EXEC CICS RETRIEVE command with the WAIT option specified.

For more information, see Clocks and time stamps, and Transaction wait (suspend) times.This field is a component of the task suspend time, SUSPTIME (014), field.

184 (TYPE-S, 'GVUPWAIT', 12 BYTES)

The elapsed time that the user task waited as a result of giving up control to another task. A user task can give up control in many ways. Some examples are application programs that use one or more of the following EXEC CICS API or SPI commands:

The EXEC CICS SUSPEND command. This command causes the issuing task to give upcontrol to another task of higher or equal dispatching priority. Control is returned to this task as soon as no other task of a higher or equal priority is ready to be dispatched.
The EXEC CICS CHANGE TASK PRIORITY command. This command immediately changes the priority of the issuing task and causes the task to give up control for it to be dispatched at its new priority. The task is not redispatched until tasks of higher or equal priority, and that are also dispatchable, have been dispatched.
The EXEC CICS DELAY command with INTERVAL (0). This command causes the issuing task to give up control to another task of higher or equal dispatching priority. Control is returned to this task as soon as no other task of a higher or equal priority is ready to be dispatched.
The EXEC CICS POST command requesting notification that a specified time has expired. This command causes the issuing task to give up control so that CICS has the opportunity to post the time-event control area.
The EXEC CICS PERFORM RESETTIME command to synchronize the CICS date and time with the MVS system date and time of day.
The EXEC CICS START TRANSID command with the ATTACH option.

For more information, see Clocks and time stamps and Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

190 (TYPE-C, 'RRMSURID', 16 BYTES)

RRMS/MVS unit-of-recovery ID (URID).

191 (TYPE-S, 'RRMSWAIT', 12 BYTES)

The elapsed time in which the user task waited indoubt using resource recovery services for EXCI.

For more information, see Clocks and time stamps and Transaction wait (suspend) times.

This field is a component of the task suspend time, SUSPTIME (014), field.

192 (TYPE-S, 'RQRWAIT', 12 BYTES)

The elapsed time during which the request receiver user task CIRR (or user specified transaction ID) waited for any outstanding replies to be satisfied.

For more information, see Clocks and time stamps and Transaction wait (suspend) times.

This field is a component of the task suspend time, SUSPTIME (014), field.

193 (TYPE-S, 'RQPWAIT', 12 BYTES)

The elapsed time during which the request processor user task CIRP waited for any outstanding replies to be satisfied.

For more information, see Clocks and time stamps and Transaction wait (suspend) times.

This field is a component of the task suspend time, SUSPTIME (014), field.

194 (TYPE-C, 'OTSTID', 128 BYTES)

This field is the first 128 bytes of the Object Transaction Service (OTS) Transaction ID (TID).

195 (TYPE-S, 'RUNTRWTT', 12 BYTES)

The elapsed time in which the user task waited for completion of a transaction that ran as a result of the user task issuing a CICS BTS run process request and a run activity request synchronously.

For more information, see Clocks and time stamps and Transaction wait (suspend) times.

This field is a component of the task suspend time, SUSPTIME (014), field.

247 (TYPE-S, 'DSCHMDLY', 12 BYTES)

The elapsed time in which the user task waited for redispatch after a CICS Dispatcher change-TCB mode request was issued by or on behalf of the user task. For example, a change-TCB mode request from a CICS L8 or S8 mode TCB back to the CICS QR mode TCB might have to wait for the QR TCB because another task is currently dispatched on the QR TCB. This field is a component of the task suspend time, SUSPTIME (014), field.

249 (TYPE-S, 'QRMODDLY', 12 BYTES)

The elapsed time for which the user task waited for redispatch on the CICS QR mode TCB. This time is the aggregate of the wait times between each event completion and user-task redispatch. This field does not include the elapsed time spent waiting for the first dispatch. The QRMODDLY field is a component of the task suspend time, SUSPTIME (014), field, and also the redispatch wait, DISPWTT (102), field.

250 (TYPE-S, 'MXTOTDLY', 12 BYTES)

The elapsed time in which the user task waited to obtain a CICS L8 or L9 mode open TCB, because the region had reached the limit set by CICS for these TCBs. L8 and L9 mode open TCBs are used by OPENAPI application programs or by task-related user exit programs that have been enabled with the OPENAPI option, for example, the CICS-DB2 adapter, when CICS connects to DB2 Version 6 or later and the CICS-MQ adapter, when CICS connects to Websphere MQ Version 6 or later.

For more information, see Clocks and time stamps and Transaction wait (suspend) times.

This field is a component of the task suspend time, SUSPTIME (014), field.

251 (TYPE-A, 'TCBATTCT', 4 BYTES)

The number of CICS TCBs attached by or on behalf of the user task.

252 (TYPE-A, 'DSTCBHWM', 4 BYTES)

The peak number of CICS open TCBs (in TCB modes L8, L9, S8, T8, X8, and X9) that have been concurrently allocated to the user task.

253 (TYPE-S, 'JVMTIME', 12 BYTES)

The total elapsed time spent in the JVM by the user task. For more information, see JVM elapsed time, suspend time, and cleanup time.

254 (TYPE-S, 'JVMSUSP', 12 BYTES)

The elapsed time for which the user task was suspended by the CICS dispatcher while running in the JVM. For more information, see JVM elapsed time, suspend time, and cleanup time. This field is a component of the task suspend time, SUSPTIME (014), field.

255 (TYPE-S, 'QRDISPT', 12 BYTES)

The elapsed time for which the user task was dispatched on the CICS QR TCB. For more information, see Clocks and time stamps.

256 (TYPE-S, 'QRCPUT', 12 BYTES)

The processor time for which the user task was dispatched on the CICS QR TCB. For more information, see Clocks and time stamps.

257 (TYPE-S, 'MSDISPT', 12 BYTES)

Elapsed time for which the user task was dispatched on each CICS TCB. The CICS TCB modes are used as follows:

RO and FO are always used.
CO is used if SUBTSKS=1 is specified as a system initialization parameter.
SZ is used if FEPI is active.
RP is used if ONC/RPC is installed and active.
SL, SO, and SP are used if TCPIP=YES is specified as a system initialization parameter. Mode SL is used by the CICS support for TCP/IP (TCP/IP Service) Listener system transaction CSOL. Mode SO is used to process the CICS support for TCP/IP socket requests issued by or on behalf of the user task. Mode SP is the CICS support for TCP/IP sockets IPT task (Initial Pthread TCB) and also owns all the SSL pthreads (S8 TCBs).
D2 is used to stop DB2 protected threads.
EP is used for event processing.
CICS creates a TP mode TCB for every JVMSERVER resource definition that is installed and enabled. The TP TCB owns the IPT task (Initial Process Thread TCB), the Language Environment® enclave, the JVM, the THRD TCB pool, and the T8 TCBs for that JVM server.

For more information, see Clocks and time stamps.

258 (TYPE-S, 'MSCPUT', 12 BYTES)

The processor time for which the user task was dispatched on each CICS TCB. The usage of each CICS TCB is shown in the description for field MSDISPT (field ID 257 in group DFHTASK). For more information, see Clocks and time stamps.

259 (TYPE-S, 'L8CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS L8 mode TCB. When a transaction starts an OPENAPI application program defined with EXECKEY=CICS, or a task-related user exit program that has been enabled with the OPENAPI option, CICS allocates a CICS L8 mode TCB to the task. (An L8 mode TCB can also be allocated if the OPENAPI program is defined with EXECKEY=USER, but the storage protection facility is inactive.) After a task has been allocated an L8 mode TCB, that same TCB remains associated with the task until the transaction is detached. For more information on this field, see Clocks and time stamps.

261 (TYPE-S, 'S8CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS S8 mode TCB. A transaction is allocated a CICS S8 mode TCB when it uses the secure sockets layer (SSL) during client certificate negotiation. The S8 mode TCB remains associated with the same task for the life of the SSL request. For more information, see Clocks and time stamps.

262 (TYPE-S, 'KY8DISPT', 12 BYTES)

The total elapsed time during which the user task was dispatched by the CICS dispatcher on a CICS Key 8 mode TCB:

An L8 mode TCB is allocated when a transaction calls an OPENAPI application program defined with EXECKEY=CICS or a task-related user exit program that has been enabled with the OPENAPI option. The TCB remains associated with the task until the transaction is detached.
An S8 mode TCB is allocated when a transaction is using the secure sockets layer (SSL) during client certificate negotiation. The S8 mode TCB remains associated with the same task for the life of the SSL request.
A T8 mode TCB is allocated when a transaction is using a JVM server to perform multithreaded processing. When a thread is allocated a T8 mode TCB, that same TCB remains associated with the thread until the processing completes.
An X8 mode TCB is allocated when a transaction calls a C or C++ program that was compiled with the XPLINK option and that is defined with EXECKEY=CICS. The TCB remains associated with the task until the program ends.

This field is a component of the task dispatch time field, USRDISPT (field ID 007 in group DFHTASK).

263 (TYPE-S, 'KY8CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher on a CICS Key 8 mode TCB. The usage of the CICS Key 8 mode TCBs is shown in the description for field KY8DISPT (field ID 262 in group DFHTASK). This field is a component of the task CPU time field, USRCPUT (field ID 008 in group DFHTASK).

264 (TYPE-S, 'KY9DISPT', 12 BYTES)

The total elapsed time during which the user task was dispatched by the CICS dispatcher on a CICS Key 9 mode TCB:

An L9 mode TCB is allocated when a transaction calls an OPENAPI application program defined with EXECKEY=USER. The TCB remains associated with the task until the transaction is detached.
An X9 mode TCB is allocated when a transaction calls a C or C++ program that was compiled with the XPLINK option and that is defined with EXECKEY=USER. The TCB remains associated with the task until the program ends.

This field is a component of the task dispatch time field, USRDISPT (field ID 007 in group DFHTASK).

265 (TYPE-S, 'KY9CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher on a CICS Key 9 mode TCB. The usage of the CICS Key 9 mode TCBs is shown in the description for field KY9DISPT (field ID 264 in group DFHTASK). This field is a component of the task CPU time field, USRCPUT (field ID 008 in group DFHTASK).

266 (TYPE-S, 'L9CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS L9 mode TCB. When a transaction calls an OPENAPI application program that is defined with EXECKEY=USER it is allocated and uses a CICS L9 mode TCB. If the storage protection facility is inactive, an L8 mode TCB is used instead of an L9 mode TCB. When a task has been allocated an L9 mode TCB, that same TCB remains associated with the task until the transaction is detached. This field is a component of the total task CPU time field, USRCPUT (field ID 008 in group DFHTASK), and the task key 9 CPU time field, KY9CPUT (field ID 265 in group DFHTASK).

268 (TYPE-S, 'DSTCBMWT', 12 BYTES)

The elapsed time that the user task spent in TCB mismatch waits; that is, waiting because no available TCB matched the request, but at least one non matching TCB was free.

269 (TYPE-S, 'RODISPT', 12 BYTES)

The elapsed time during which the user task was dispatched by the CICS dispatcher on the CICS RO mode TCB. The RO TCB is used for loading programs, unless the command to load the program (EXEC CICS LOAD, XCTL, or LINK) is issued by an application that is currently running on an open TCB. In that situation, the open TCB is used to load the program instead of the RO TCB. The CICS RO mode TCB is also used for opening and closing CICS data sets, issuing RACF® calls, and similar tasks. This field is a component of the task dispatch time field, USRDISPT (group name: DFHTASK, field ID: 007) and the task miscellaneous TCB dispatch time field, MSDISPT (group name: DFHTASK, field ID: 257).

270 (TYPE-S, 'ROCPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher on the CICS RO mode TCB. The RO TCB is used for loading programs, unless the command to load the program (EXEC CICS LOAD, XCTL, or LINK) is issued by an application that is currently running on an open TCB. In that situation, the open TCB is used to load the program instead of the RO TCB. The CICS RO mode TCB is also used for opening and closing CICS data sets, issuing RACF calls, and similar tasks. This field is a component of the task CPU time field, USRCPUT (group name: DFHTASK, field ID: 008) and the task miscellaneous TCB CPU time field, MSCPUT (group name: DFHTASK, field ID: 258).

271 (TYPE-S, 'X8CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS X8 mode TCB. When a transaction calls a C or C++ program that was compiled with the XPLINK option, and that is defined with EXECKEY=CICS, it is allocated and uses a CICS X8 mode TCB. An X8 mode TCB can also be allocated if the program is defined with EXECKEY=USER, but the storage protection facility is inactive. After a task has been allocated an X8 mode TCB, that same TCB remains associated with the task until the program completes. This field is a component of the total task CPU time field, USRCPUT (field ID 008 in group DFHTASK), and the task key 8 CPU time field, KY8CPUT (field ID 263 in group DFHTASK).

272 (TYPE-S, 'X9CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS X9 mode TCB. When a transaction calls a C or C++ program that was compiled with the XPLINK option, and that is defined with EXECKEY=USER, it is allocated and uses a CICS X9 mode TCB. (If the storage protection facility is inactive, an X8 mode TCB is used instead of an X9 mode TCB.) After a task has been allocated an X9 mode TCB, that same TCB remains associated with the task until the program completes. This field is a component of the total task CPU time field, USRCPUT (field ID 008 in group DFHTASK), and the task key 9 CPU time field, KY9CPUT (field ID 265 in group DFHTASK).

273 (TYPE-S, 'JVMITIME', 12 BYTES)

The elapsed time spent initializing the JVM environment. For more information, see Clocks and time stamps.

275 (TYPE-S, 'JVMRTIME', 12 BYTES)

Reserved field, returns zero.

279 (TYPE-S, 'DSMMSCWT', 12 BYTES)

The elapsed time that the user task spent waiting because no TCB was available and a TCB was not created because of MVS storage constraints. This field is a component of the task suspend time, SUSPTIME (014), field.

281 (TYPE-S, 'MAXSTDLY', 12 BYTES)

The elapsed time for which the user task waited to obtain a CICS SSL TCB (S8 mode), because the CICS system reached the limit set by the system initialization parameter MAXSSLTCBS. The S8 mode open TCBs are used exclusively by secure sockets layer (SSL) pthread requests issued by or on behalf of a user task. For more information, see Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

282 (TYPE-S, 'MAXXTDLY', 12 BYTES)

The elapsed time for which the user task waited to obtain a CICS XP TCB (X8 or X9 mode), because the CICS system reached the limit set by CICS for these types of TCB. The X8 and X9 mode open TCBs are used exclusively by C and C++ programs that were compiled with the XPLINK option. For more information, see Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

283 (TYPE-S, 'MAXTTDLY', 12 BYTES)

The elapsed time for which the user task waited to obtain a T8 TCB, because the CICS system reached the limit of available threads. The T8 mode open TCBs are used by a JVM server to perform multithreaded processing. Each T8 TCB runs under one thread. The thread limit is 2000 for each CICS region and each JVM server in a CICS region can have up to 256 threads. For more information, see Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

285 (TYPE-S, 'PTPWAIT', 12 BYTES)

The elapsed time for which the user task waited for the 3270 bridge partner transaction to complete. For more information, see Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

345 (TYPE-A, 'ICSTACDL', 4 BYTES)

Total length, in bytes, of the data in the containers of all the locally executed START CHANNEL requests issued by the user task. This total includes the length of any headers to the data.

346 (TYPE-A, 'ICSTRCCT', 4 BYTES)

Total number of interval control START CHANNEL requests, to be run on remote systems, issued by the user task.

347 (TYPE-A, 'ICSTRCDL', 4 BYTES)

Total length, in bytes, of the data in the containers of all the remotely executed START CHANNEL requests issued by the user task. This total includes the length of any headers to the data.

348 (TYPE-S, 'ROMODDLY', 12 BYTES)

The elapsed time for which the user task waited for redispatch on the CICS RO TCB. This time is the aggregate of the wait times between each event completion and user-task redispatch. The ROMODDLY field is a component of the task suspend time, SUSPTIME (014), field, and also the redispatch wait, DISPWTT (102), field.

349 (TYPE-S, 'SOMODDLY', 12 BYTES)

The elapsed time for which the user task waited for redispatch on the CICS SO TCB. This time is the aggregate of the wait times between each event completion and user-task redispatch. The SOMODDLY field is a component of the task suspend time, SUSPTIME (014), field, and also the redispatch wait, DISPWTT (102), field.

400 (TYPE-S, 'T8CPUT', 12 BYTES)

The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS T8 mode TCB. T8 mode TCBs are used by a JVM server to perform multithreaded processing. When a thread is allocated a T8 mode TCB, that same TCB remains associated with the thread until the processing completes. This field is a component of the total task CPU time field, USRCPUT (field ID 008 in group DFHTASK), and the task key 8 CPU time field, KY8CPUT (field ID 263 in group DFHTASK).

401 (TYPE-S, 'JVMTHDWT', 12 BYTES)

The elapsed time that the user task waited to obtain a JVM server thread because the CICS system had reached the thread limit for a JVM server in the CICS region. This field is a component of the task suspend time, SUSPTIME (014), field. This does not apply to Liberty JVM servers.

429 (TYPE-S, 'DSAPTHWT', 12 BYTES

The dispatcher allocated pthread wait time. This is the time that the transaction had to wait for a Liberty pthread to be allocated during links to Liberty programs. For more information, see Clocks and time stamps and Transaction wait (suspend) times. This field is a component of the task suspend time, SUSPTIME (014), field.

430 (TYPE-C, 'CECMCHTP', 4 BYTES)

The CEC machine type, in EBCDIC, for the physical hardware environment where the CICS region is running. CEC (central electronics complex) is a commonly used synonym for CPC (central processing complex).

431 (TYPE-C, 'CECMDLID', 16 BYTES)

The CEC model number, in EBCDIC, for the physical hardware environment where the CICS region is running.

433 (TYPE-A, 'MAXTASKS', 4 BYTES)

The MXT or MAXTASKS value, expressed as a number of tasks, for the CICS region at the time the user task was attached.

434 (TYPE-A, 'CURTASKS', 4 BYTES)

The current number of active user transactions in the system at the time the user task was attached.

436 (TYPE-S, 'CPUTONCP', 12 BYTES)

The total task processor time on a standard processor for which the user task was dispatched on each CICS TCB under which the task ran.

This field is a component of the task CPU time field, USRCPUT (field ID 008 in group DFHTASK). To calculate the task processor time that was spent on a specialty processor (zIIP or zAAP), subtract the time recorded in the CPUTONCP field from the time recorded in the USRCPUT field.

Note: The times shown in the CPUTONCP and OFFLCPUT fields are only available when running on a system that supports the Extract CPU Time instruction service that is available on IBM® z9® or later hardware. For z/OS, Version 1 Release 13, the PTF for APAR OA38409 must also be applied.

437 (TYPE-S, 'OFFLCPUT', 12 BYTES)

The total task processor time that was spent on a standard processor but was eligible for offload to a specialty processor (zIIP or zAAP).

This field is a component of the task CPU time field, USRCPUT (field ID 008 in group DFHTASK), and also a component of the standard CPU time field, CPUTONCP (field ID 436 in group DFHTASK). To calculate the task processor time spent on a standard processor that was not eligible for offload to a specialty processor, subtract the time recorded in the OFFLCPUT field from the time recorded in the CPUTONCP field.

Note: The times shown in the CPUTONCP and OFFLCPUT fields are only available when running on a system that supports the Extract CPU Time instruction service that is available on IBM z9 or later hardware. For z/OS, Version 1 Release 13, the PTF for APAR OA38409 must also be applied.

451 (TYPE-C, 'ACAPPLNM', 64 BYTES)

The 64-character name of the application in the application context data.

452 (TYPE-C, 'ACPLATNM', 64 BYTES)

The 64-character name of the platform in the application context data.

453 (TYPE-A, 'ACMAJVER', 4 BYTES)

The major version of the application in the application context data, expressed as a 4-byte binary value.

454 (TYPE-A, 'ACMINVER', 4 BYTES)

The minor version of the application in the application context data, expressed as a 4-byte binary value.

455 (TYPE-A, 'ACMICVER', 4 BYTES)

The micro version of the application in the application context data, expressed as a 4-byte binary value.

456 (TYPE-C, 'ACOPERNM', 64 BYTES)

The 64-character name of the operation in the application context data.

For a description of TCB modes, see TCB statistics.