- 001 (Type-C, TRAN, 4 bytes)
- Transaction identification.
- 004 (Type-C, TTYPE, 4 bytes)
- Type of transaction start (Start Code or Start Type):
- TO
- The transaction was started (attached) by input of the transaction
ID from the terminal user.
- S
- Attached by automatic transaction initiation (ATI) without data.
The transaction was started (attached) by an application program using
the EXEC CICS® START TRANSID('xxxx')
... API command. CICS internal
transactions such as CATR, CEJR, CESN, CQRY, CRPM, CRSQ, CSFU, CSGM,
CXRE, and CWBG are just some examples of CICS transactions that use this start type.
- SD
- Attached by automatic transaction initiation (ATI) with data.
The transaction was started (attached) by an application program using
the EXEC CICS START TRANSID('xxxx')
FROM(xxxx) ... API command. CICS internal
transactions such as CLS1 is an example of a transaction that uses
this start type.
- QD
- The transaction was started (attached) because the trigger level
of an intrapartition transient data queue was reached. If the transaction
is not associated with a terminal facility, the Transaction Facility
Name (field: FCTYNAME, owner: DFHTASK, field ID: 163) provides the
name of the transient data queue ID.
- U
- The transaction was started (attached) by a CICS internal function generally as a result
of some user request. CICS internal
transactions such as CATA, CATD, CEJR, CESC, CEX2, CFOR, CFQR, CFQS,
CFTL, CGRP, CIEP, CIOF, CIOR, CIRP, CITS, CJTR, CLQ1, CLQ2, CLS2,
COTR, COVR, CPLT, CPMI, CRSY, CSFR, CSHQ, CSNC, CSNE, CSOL, CSSY,
CSTE, CSZI, CWBA, and CWXN are just some examples of the CICS transactions that use this start type.
In addition to CICS internal
functions, transaction's that are being run under the control of the CICS Execution Diagnostic Facility
transaction, CEDF, are also started (attached) with this start type.
- TP
- Attached from terminal (TCTTE) transaction ID. The preset transaction
was started (attached) by input from the terminal user or by the previous
transaction using the EXEC CICS RETURN
TRANSID('xxxx') IMMEDIATE ... API command. The transaction ID can
be preset either from the terminal definition, from using the CRTE
routing transaction, or by the previous transaction's application
program using the EXEC CICS RETURN
TRANSID('xxxx') ... API command with or without the IMMEDIATE option
specified. Some examples of CICS transactions
which use this start type are: CESN (except when used as the initial
good morning transaction), CRTE (when invoked on the routed system),
and CSSF when invoked as part of a 'CRTE CANCEL' (the initial CRTE
transaction which establishes the routing session uses the start type
'TO').
- SZ
- Attached by the Front End Programming Interface (FEPI). The transaction
was started (attached) as the receive program by the Front
End Programming Interface as a result of inbound data. In addition
to inbound data arriving, the receive program is also started
(attached) if the time limit set by a FEPI START command expires,
the session is lost, or anything that causes a FEPI RECEIVE command
to complete. See the CICS Front
End Programming Interface User's Guide for more information
on FEPI started tasks.
- 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, J8, J9, L8, L9, S8, TP, T8, X8, X9, JM, 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.
- 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, J8, J9, L8, L9, S8, TP, T8, X8, X9, JM, 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.
- 014 (Type-S, SUSPTIME, 12 bytes)
- The total elapsed suspend (wait) time for which the user task
was suspended by the CICS dispatcher
domain. This includes:
- The task suspend (wait) time.
- The elapsed time that the transaction waited for its first dispatch.
This also includes any delay incurred because of the limits set for
this transaction's transaction class (if any) or by the system parameter
MXT being reached by this transaction.
- The elapsed time waiting for redispatch after a suspended task
has been resumed.
For more information, see Transaction suspend (wait) time.
- 031 (Type-P, TRANNUM, 4 bytes)
- The transaction identification number.
Note: The transaction
number field is normally a 4-byte packed decimal number. However,
some CICS system tasks are
identified by special characters in this field as follows:
- III
- for system initialization tasks
- TCP
- for
the terminal control task
These special identifiers are placed in
bytes 2 through 4. Byte 1 is blank (X'40') before the terminal
control TCP identifier, and a null value (X'00') before the
others.
- 059 (Type-A, ICPUINCT, 4 bytes)
- The number of Interval Control START requests issued by 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
- The CICS Monitoring Facility
(CMF) detected an attempt 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)
- The total number of local interval control START requests, with
the CHANNEL option, issued by the user task.
- 066 (Type-A, ICTOTCT, 4 bytes)
- The total number of Interval Control Start, Cancel, Delay, and
Retrieve requests issued by the user task.
Note: The number of interval
control Cancel, Delay, and Retrieve requests can be calculated by
subtracting the interval control request count ICPUINCT from the total
interval control request count, ICTOTCT.
- 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 particularly useful when applied
to the requests that originate through the CICS Web support (CWS), IIOP, ECI over TCP/IP,
or the 3270 bridge interface, as indicated by the transaction origin
in byte 4 of the transaction flags field (owner: DFHTASK, field ID:
164). See below for more details on the transaction origin type.
For
more information, see Correlating performance class data and
the Transaction Group report.
- 097 (Type-C, NETUOWPX, 20 bytes)
- The fully qualified name by which the originating system is known
to the VTAM® network. This name
is assigned at attach time using either the netname derived from the
terminal (when the task is attached to a local terminal), or the netname
passed as part of an IRC (MRO) or ISC (APPC) attach header. At least
three padding bytes (X'00') are present at the right end
of the name.
If the originating terminal is VTAM across an ISC APPC or IRC link, the NETNAME
is the networkid.LUname. If the terminal is non-VTAM, the NETNAME
is networkid.generic_APPLID.
All originating information
is passed as part of an ISC LUTYPE6.1 attach header has the same format
as the non-VTAM terminal originators above.
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:
- An 8-byte eye-catcher set to 'DFHEXCIU'.
- A 1-byte field containing a period '.'.
- A 4-byte field containing the MVS™ ID,
in characters, under which the client program is running.
- A 4-byte field containing the address space ID (AS ID) in which
the client program is running. This field contains the 4-character
EBCDIC representation of the 2-byte hexadecimal address space ID.
For more information on the external CICS interface (EXCI), see the CICS External Interfaces Guide.
Note: That
it is possible for transactions that are attached without a terminal
or session facility to be given the same network unit-of-work netname
in the format of networkid.generic_APPLID.
For more
information, see Correlating performance class data and the Cross-System Work report.
- 098 (Type-C, NETUOWSX, 8 bytes)
- The
name by which the network unit-of-work ID is known within the originating
system. This name is assigned at transaction attach time using either
a STCK-derived token created by the originating system, or the network
unit-of-work ID passed as part of an IRC (MRO) or ISC (APPC) attach
function management header (FMH).
The first six 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 two bytes of this field are a syncpoint sequence count. This
count might change during the life of the task as a result of syncpoint
activity.
For CICS Business
Transaction Services (BTS) transactions, the network unit-of-work
ID is also passed to a transaction that is invoked synchronously by
an application program issuing either a CICS BTS
run ACQPROCESS synchronous or run activity synchronous command.
Note: When
using MRO or ISC, the NETUOWSX field can be combined with the NETUOWPX
field (field ID: 097) to uniquely identify a task across each CICS system. It must be combined
with the NETUOWPX because the NETUOWSX field on its own is unique
only to the originating CICS system.
For
more information, see Correlating performance class data and Cross-System Work report.
- 102 (Type-S, DISPWTT, 12 bytes)
- The elapsed time for which the user task waited for redispatch
by the CICS dispatcher domain.
This is the aggregate of the wait times between each wait event completion
and the user task being redispatched by the CICS dispatcher domain.
Note: - This field does not include the elapsed time spent waiting for
the first dispatch.
- This field is a component of the task suspend time field, SUSPTIME
(owner: DFHTASK, field ID: 014).
- 109 (Type-C, TRANPRI, 4 bytes)
- The transaction priority of the task when monitoring of the task
was initialized at transaction attach.
- 123 (Type-S, GNQDELAY, 12 bytes)
- The elapsed time in which the user task waited for a CICS task control global enqueue.
For more
information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 124 (Type-C, BRDGTRAN, 4 bytes)
- For those transactions that are attached by the CICS 3270 Bridge interface, this field contains
the name of the bridge listener transaction that invoked the transaction.
A bridge transaction can be identified using byte 1 of the transaction
flags field, TRANFLAG (owner: DFHTASK, field ID: 164).
- 125 (Type-S, DSPDELAY, 12 bytes)
- The elapsed time in which the user task waited for the first dispatch
by the CICS dispatcher domain.
Note: This field is a component of the task suspend time field, SUSPTIME
(owner: DFHTASK, field ID: 014).
- 126 (Type-S, TCLDELAY, 12 bytes)
- The elapsed time in which the user task waited for first dispatch
which was delayed because of the limits set for this transaction's
transaction class. The name of the transaction class for this transaction
can be found in the TCLSNAME field, (owner: DFHTASK, field ID: 166).
For more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014) and the first dispatch delay time field, DSPDELAY
(owner: DFHTASK, field ID: 125).
- 127 (Type-S, MXTDELAY, 12 bytes)
- The elapsed time in which the user task waited for first dispatch
which was delayed because of the limits set by the MXT system parameter
being reached.
For more information, see Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID:
014) and the first dispatch delay time field, DSPDELAY (owner: DFHTASK,
field ID: 125).
- 128 (Type-S, LMDELAY, 12 bytes)
- The elapsed time in which 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, see Transaction timing fields.
For
more information about the CICS lock
manager, see the CICS Problem
Determination Guide.
Note: This field is a component of
the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).
- 129 (Type-S, ENQDELAY, 12 bytes)
- The elapsed time in which the user task waited for a CICS task control local enqueue. For more information,
see Transaction timing fields
Note: This field is a
component of the task suspend time field, SUSPTIME (owner: DFHTASK,
field ID: 014).
- 132 (Type-T, RMUOWID, 8 bytes)
- The identifier of the local unit of work (unit of recovery) for
this task. The local unit-of-recovery values are used to synchronize
recovery operations amongst CICS systems
and other resource managers, such as IMS™ (DBCTL)
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 field,
TRANFLAG (owner: DFHTASK, field ID: 164).
- 164 (Type-A, TRANFLAG, 8 bytes)
- Transaction flags, a string of 64 bits used for signaling transaction
definition and status information:
- Byte 0
- Transaction facility identification. The field identifies the
type of resource that is the transaction's principal facility and
can have one of the following values:
- Bit 0
- Transaction facility name = none
- Bit 1
- Transaction facility name = terminal
- Bit 2
- Transaction facility name = surrogate
- Bit 3
- Transaction facility name = destination
- Bit 4
- Transaction facility name = 3270 bridge
- Bit 5-7
- Reserved
- Byte 1
- Transaction identification information:
- Bit 0
- System transaction
- Bit 1
- Mirror transaction
- Bit 2
- Distributed Program Link (DPL) mirror transaction
- Bit 3
- ONC RPC alias transaction
- Bit 4
- WEB alias transaction
- Bit 5
- 3270 bridge transaction
- Bit 6
- Reserved
- Bit 7
- CICS BTS run transaction
(ACQPROCESS or activity) synchronous
- Byte 2
- z/OS® workload manager request
(transaction) completion information:
- Bit 0
- Report the total response time (begin-to-end phase) for the completed
work request (transaction)
- Bit 1
- Notify that the entire execution phase of the work request (transaction)
is complete
- Bit 2
- Notify that a subset of the execution phase of the work request
(transaction) 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
- Bit 1
- Taskdatakey = CICS
- Bit 2
- Isolate = NO
- Bit 3
- Dynamic = YES
- Bit 4-7
- Reserved
- Byte 4
- Transaction origin type:
- X'01'
- None
- X'02'
- Terminal
- X'03'
- Transient data
- X'04'
- Start
- X'05'
- Terminal 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'
- II domain Request Receiver
- X'12'
- Request stream (RZ) Instore Transport
- X'13'
- IPIC session
- X'14'
- Event
- X'15'
- JVMSERVER
- Byte 5
- 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
- Bit 7
- Task abnormally terminated
Note: If bit 6 is set, the task was 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).
- Byte 6
- CICS TS V3.2 and later:
Reserved.
CICS TS V3.1 and
earlier:
JVM status information:
- Bit 0
- JVM marked unresettable
- Bit 1-7
- Reserved
- Byte 7
- Recovery manager status 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)
- The transaction's transaction class name (TRANCLASS). If the transaction
was delayed because of the limits set for the transaction class, the
elapsed time that the transaction waited can be found in the TCLDELAY
field, (owner: DFHTASK, field ID: 126).
The transaction class
name field is null if the transaction is not defined in a transaction
class.
- 170 (Type-S, RMITIME, 12 bytes)
- The total elapsed time the user task spent in the CICS Resource Manager Interface (RMI) for all
the resource managers invoked by the user task, including DB2, IMS (DBCTL), WebSphere® MQ, CICS Sockets, and so on.
For information
on the related fields for DB2 and IMS (DBCTL), see DFHDATA fields.
For more information,
see RMI elapsed and suspend time.
Refer
also to DFHRMI fields for information
that can provide additional insight into understanding and interpreting CICS Resource Manager Interface
(RMI) performance problems.
- 171 (Type-S, RMISUSP, 12 bytes)
- The elapsed time during which the user task was suspended by the CICS dispatcher domain whilst in
the CICS Resource Manager Interface
(RMI).
For more information, see RMI elapsed and suspend time and Transaction timing fields.
For information on the related
fields for DB2 and IMS (DBCTL), see DFHDATA fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 181 (Type-S, WTEXWAIT, 12 bytes)
- The elapsed time 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 MVS POSTed.
The user task can wait on one or more ECBs. If it waits on more than
one, the user task becomes dispatchable as soon as one of the ECBs
is posted.
For more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 182 (Type-S, WTCEWAIT, 12 bytes)
- The elapsed time the user task waited for:
- One or more ECBs, passed to CICS by
the user task using the EXEC CICS WAITCICS
ECBLIST command, to be MVS POSTed.
The user task can wait on one or more ECBs. If it waits on more than
one, the user task becomes dispatchable as soon as one of the ECBs
is posted.
- Completion of an event initiated by the same or by another task.
The event would normally 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 Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 183 (Type-S, ICDELAY, 12 bytes)
- The elapsed time that the user task waited as a result of issuing
either:
- An interval control EXEC CICS DELAY
command for a specified time interval, or
- An interval control EXEC CICS DELAY
command for a specified time of day to expire, or
- An interval control EXEC CICS RETRIEVE
command with the WAIT option specified.
For more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 184 (Type-S, GVUPWAIT, 12 bytes)
- The elapsed time in which 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:
- Using the EXEC CICS SUSPEND
command. This command causes the issuing task to relinquish 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.
- Using 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 in order
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.
- Using the EXEC CICS DELAY
command with INTERVAL(0). This command causes the issuing task to
relinquish 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.
- Using the EXEC CICS POST
command requesting notification that a specified time has expired.
This command causes the issuing task to relinquish control to give CICS the opportunity to post the
time-event control area.
- Using the CICS CICS PERFORM RESETTIME command
to synchronize the CICS date
and time with the MVS system
date and time of day.
- Using the EXEC CICS START
TRANSID command with the ATTACH option.
For more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 190 (Type-C, RRMSURID, 16 bytes)
- The RRMS/MVS Unit-of-Recovery Id (URID).
For more general
information on the Recoverable Resource Management Services (RRMS),
see the CICS External
Interfaces Guide.
- 191 (Type-S, RRMSWAIT, 12 bytes)
- The elapsed time in which the user task waited indoubt using the MVS resource recovery services (RRS)
for transactional EXCI.
For more information, see Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID:
014).
- 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 Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (group name: DFHTASK, field
ID: 014).
- 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 Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (group
name: DFHTASK, field ID: 014).
- 194 (Type-C, OTSTID, 128 bytes)
- The OTS TID is the Object Transaction Service Transaction ID.
It can be used to correlate all the transactions that are part of
the same Object Transaction.
- 195 (Type-S, RUNTRWTT, 12 bytes)
- The elapsed time in which the user task waited for completion
of a transaction that run as a result of the user task issuing a CICS BTS run ACQPROCESS or run
activity request to run a process or activity synchronously.
For
more information, see Correlating performance class data and Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID:
014).
- 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. Ideally the number of CICS dispatcher change-TCB modes
should be kept to a minimum. See the section on the Open transaction environment for more additional information.
For
more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 249 (Type-S, QRMODDLY, 12 bytes)
- The elapsed time in which the user task waited for redispatch
on the CICS QR mode TCB. This
is an aggregate of the wait times between each wait event completion
and the user task being redispatched by the CICS dispatcher domain on the QR mode TCB.
See the section on the Open transaction environment for
additional information.
This field is a subset of the wait for
redispatch field, DISPWTT (owner: DFHTASK, field ID: 102).
For
more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time field, SUSPTIME (owner:
DFHTASK, field ID: 014).
- 250 (Type-S, MAXOTDLY, 12 bytes)
- The elapsed time in which the user task waited to obtain a CICS open mode TCB because the CICS system had reached the limit
set by the system parameter, MAXOPENTCBS.
This applies to L8 mode
open TCBs only. L8 mode open TCBs are used by task-related
user exits that are enabled with the OPENAPI option. This includes
the CICS DB2 adaptor when CICS connects
to DB2 Version 6 or later.
See the section on the Open transaction environment for
more general information.
For more information, see Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID:
014).
- 251 (Type-A, TCBATTCT, 4 bytes)
- The number of CICS dispatcher
domain TCB attaches issued by or on behalf of the user task. See the
section on the Open transaction environment for additional
information.
- 252 (Type-A, DSTCBHWM, 4 bytes)
- The peak number of CICS open
TCBs (in TCB modes J8, J9, 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 that the user task spent in the CICS Java Virtual
Machine (JVM).
For more information, see JVM elapsed and suspend time.
- 254 (Type-S, JVMSUSP, 12 bytes)
- The elapsed time during which the user task was suspended by the CICS dispatcher domain while running
in the CICS Java Virtual Machine (JVM).
For more information,
see JVM elapsed and suspend time and Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID:
014).
- 255 (Type-S, QRDISPT, 12 bytes)
- The total elapsed time during which the user task was dispatched
by the CICS dispatcher domain
on the CICS QR mode TCB.
Note: This
field is a component of the total task dispatch time field, USRDISPT
(owner: DFHTASK, field ID: 007).
- 256 (Type-S, QRCPUT, 12 bytes)
- The total processor (CPU) time during which the user task was
dispatched by the CICS dispatcher
domain on the CICS QR mode
TCB.
Note: This field is a component of the total task CPU time field,
USRCPUT (owner: DFHTASK, field ID: 008).
- 257 (Type-S, MSDISPT, 12 bytes)
- The total elapsed time during which the user task was dispatched
by the CICS dispatcher domain
on each CICS TCB, mode RO,
CO, FO, SZ, RP, SL, SO, SP, D2 and JM. Note that:
Note: This field is a component of the total task dispatch time
field, USRDISPT (owner: DFHTASK, field ID: 007).
- 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).
Note: This field is a component
of the total task CPU time field, USRCPUT (owner: DFHTASK, field ID:
008).
- 259 (Type-S, L8CPUT, 12 bytes)
- The processor (CPU) time during which the user task was dispatched
by the CICS dispatcher domain
on a CICS L8 mode TCB.
A
transaction is allocated and uses a CICS L8
mode TCB when it invokes a task-related user exit program that has
been enabled with the OPENAPI option. This includes the CICS DB2 adaptor
when CICS connects to DB2 Version 6 or later. However,
when a task has been allocated an L8 mode TCB, that same TCB will
remain associated with the task until the transaction is detached.
For
more information on the CICS open
transaction environment (OTE), see the CICS Application Programming Guide
For
more information on the DB2 accounting
and monitoring, see the CICS DB2 Guide.
Note: This
field is a component of the total task CPU time field, USRCPUT (owner:
DFHTASK, field ID: 008) and the task key 8 CPU time field, KY8CPUT
(owner: DFHTASK, field ID: 263). See the section on the
Open transaction environment for more information.
- 260 (Type-S, J8CPUT, 12 bytes)
- The processor (CPU) time during which the user task was dispatched
by the CICS dispatcher domain
on a CICS J8 mode TCB. A transaction
is allocated and use a CICS J8
mode TCB each time the transaction invokes a CICS Java Virtual
Machine (JVM) application program. However, when a task has been allocated
a J8 mode TCB, that same TCB will remain associated with the task
until the transaction is detached.
Note: This field is a component
of the total task CPU time field, USRCPUT (owner: DFHTASK, field ID:
008) and the task key 8 CPU time field, KY8CPUT (owner: DFHTASK, field
ID: 263).
- 261 (Type-S, S8CPUT, 12 bytes)
- The processor (CPU) 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 is using the secure sockets layer (SSL) during client
certification negotiation. The S8 mode TCB remains associated with
the same task for the life of the SSL request.
Note: This field is
a component of the total task CPU time field, USRCPUT (owner: DFHTASK,
field ID: 008) and the task key 8 CPU time field, KY8CPUT (owner:
DFHTASK, field ID: 263).
- 262 (Type-S, KY8DISPT, 12 bytes)
- The total elapsed time during which the user task was dispatched
by the CICS dispatcher domain
on a CICS Key 8 mode TCB. A
transaction is allocated and dispatched on a:
- CICS H8 mode TCB when it
invokes an HPJ-compiled Java application
program that has been defined to use Java hot-pooling.
- CICS J8 mode TCB each time
the transaction invokes a Java application
program that has been defined with JVM(YES). However, when a task
has been allocated a J8 mode TCB, that same TCB will remain associated
with the task until the transaction is detached. See the section
on the Open transaction environment for more information.
- CICS L8 mode TCB when it
invokes a task-related user exit program that has with the OPENAPI
option.
This includes the CICS DB2 adaptor when CICS connects to DB2 Version
6 or later. However, when a task has been allocated an L8 mode TCB,
that same TCB will remain associated with the task until the transaction
is detached.
For more general information on the CICS open transaction environment (OTE), see
the CICS Application
Programming Guide.
- CICS S8 mode TCB when it
is using the secure sockets layer (SSL) during client certification
negotiation. The S8 mode TCB will remain associated with the same
task until the secure socket close which normally occurs during task
detach processing.
- CICS T8 mode
when it 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.
- CICS X8 mode
TCB when a transaction invokes a C or C++ application program compiled
with the XPLINK option on, and that is defined with EXECKEY=CICS.
The TCB remains associated with the task until the program ends.
Note: This field is a component of the total task dispatch time
field, USRDISPT (owner: DFHTASK, field ID: 007).
- 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).
Note: This
field is a component of the total task CPU time field, USRCPUT (owner:
DFHTASK, field ID: 008).
- 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. A transaction
is allocated and dispatched on a:
- CICS J9 mode TCB when a
transaction invokes a Java program
defined with EXECKEY=USER, that requires a JVM in user key. (If the
storage protection facility is inactive, the transaction is allocated
a J8 mode TCB instead of a J9 mode TCB.) The TCB remains associated
with the task until the Java program
completes.
- CICS L9 mode
TCB when a transaction invokes an OPENAPI application program defined
with EXECKEY=USER. The TCB remains associated with the task until
the transaction is detached.
- CICS X9 mode
TCB when a transaction invokes 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.
Note: This field is a component of the task dispatch time field,
USRDISPT (owner: DFHTASK, field ID: 007).
- 265 (Type-S, KY9CPUT, 12 bytes)
- The total processor (CPU) time during which the user task was
dispatched by the CICS dispatcher
on a CICS Key 9 mode TCB. A
transaction is allocated and dispatched on a:
- CICS J9 mode TCB when a
transaction invokes a Java program
defined with EXECKEY=USER, that requires a JVM in user key. (If the
storage protection facility is inactive, the transaction is allocated
a J8 mode TCB instead of a J9 mode TCB.) The TCB remains associated
with the task until the Java program
completes.
- CICS L9 mode
TCB when a transaction invokes an OPENAPI application program defined
with EXECKEY=USER. The TCB remains associated with the task until
the transaction is detached.
- CICS X9 mode
TCB when a transaction invokes 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.
Note: This field is a component of the total task CPU time field,
USRCPUT (owner: DFHTASK, field ID: 008).
- 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 invokes an OPENAPI application program 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.
For more information on the CICS open
transaction environment (OTE), see the CICS Application Programming Guide.
Note: This
field is a component of the total task CPU time field, USRCPUT (owner:
DFHTASK, field ID: 008).
- 267 (Type-S, J9CPUT, 12 bytes)
- The processor time during which the user task was dispatched by
the CICS dispatcher domain
on a CICS J9 mode TCB. When
a transaction invokes a Java program
defined with EXECKEY=USER, that requires a JVM in user key, it is
allocated and uses a CICS J9
mode TCB. (If the storage protection facility is inactive, a J8 mode
TCB is used instead of a J9 mode TCB.) When a task has been allocated
a J9 mode TCB, that same TCB remains associated with the task until
the Java program completes.
- 268 (Type-S, DSTCBMWT, 12 bytes)
- The elapsed time which the user task spent in TCB mismatch waits,
that is, waiting because there was no TCB available matching the request,
but there was at least one non-matching free TCB. For transactions
that invoke a Java program to
run in a JVM, this shows the time spent waiting for a TCB of the correct
mode (J8 or J9) and JVM profile. See Java Application Development for CICS: Base Services and CORBA Client Support for
more information about how CICS manages
TCB mismatch waits for these transactions.
- 269 (Type-S, RODISPT, 12 bytes)
- The total elapsed time during which the user task was dispatched
by the CICS dispatcher on the CICS RO mode TCB. The CICS RO mode TCB is used for opening and closing CICS data sets, loading programs,
issuing RACF calls, and so
on.
Note: This field is a component of the total task dispatch time
field, USRDISPT (owner: DFHTASK, field ID: 007) and the task miscellaneous
TCB dispatch time field MSDISPT (owner: DFHTASK, field ID: 257).
- 270 (Type-S, ROCPUT, 12 bytes)
- The total processor (CPU) time during which the user task was
dispatched by the CICS dispatcher
on the CICS RO mode TCB. The CICS RO mode TCB is used for opening
and closing CICS data sets,
loading programs, issuing RACF calls,
and so on.
Note: This field is a component of the total task CPU
time field USRCPUT (owner: DFHTASK, field ID: 008) and the task miscellaneous
TCB CPU time field MSCPUT (owner: DFHTASK, field ID: 258).
- 271 (Type-S, X8CPUT, 12 bytes)
- The processor (CPU) time during which the user task was dispatched
by the CICS dispatcher domain
on a CICS X8 mode TCB. A transaction
is allocated and use a CICS X8
mode TCB each time the transaction invokes a C or C++ application
program that has been compiled with the XPLINK flag turned on and
that is defined with EXECKEY=CICS. (An X8 mode TCB can also be allocated
if the program is defined with EXECKEY=USER, but the storage protection
facility is inactive.) When a task has been allocated an X8 mode TCB,
that same TCB remains associated with the task until the program completes.
Note: This
field is a component of the total task CPU time field USRCPUT (owner:
DFHTASK, field ID: 008) and the task key 8 CPU time field KY8CPUT
(owner: DFHTASK, field ID: 263).
- 272 (Type-S, X9CPUT, 12 bytes)
- The processor (CPU) time during which the user task was dispatched
by the CICS dispatcher domain
on a CICS X9 mode TCB. A transaction
is allocated and use a CICS X9
mode TCB each time the transaction invokes a C or C++ application
program that has been compiled with the XPLINK flag turned on, 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.) When a task has been allocated an X9 mode TCB, that
same TCB remains associated with the task until the program completes.
Note: This
field is a component of the total task CPU time field USRCPUT (owner:
DFHTASK, field ID: 008) and the task key 9 CPU time field KY9CPUT
(owner: DFHTASK, field ID: 265).
- 273 (Type-S, JVMITIME, 12 bytes)
- The elapsed time the user task spent initializing the CICS Java Virtual
Machine (JVM) environment.
For more information, see JVM elapsed and suspend time.
Note: This field is a component
of the task JVM elapsed time field JVMTIME (owner: DFHTASK, field
ID: 253).
- 275 (Type-S, JVMRTIME, 12 bytes)
- The elapsed time the user task spent resetting or destroying the CICS Java Virtual
Machine (JVM) environment. If the reset fails, the JVM is marked un-resettable
and the JVM is terminated.
For more information, see JVM elapsed and suspend time.
Note: This field is a component
of the task JVM elapsed time field JVMTIME (owner: DFHTASK, field
ID: 253).
- 277 (Type-S, MAXJTDLY, 12 bytes)
- The elapsed time in which the user task waited to obtain a CICS JVM TCB (J8 or
J9 mode), because the CICS system
had reached the limit set by the system parameter, MAXJVMTCBS. The
J8 and J9 mode open TCBs are used exclusively
by Java programs defined with
JVM(YES).
For more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time (field: SUSPTIME, owner:
DFHTASK, field ID: 014).
- 278 (Type-S, MAXHTDLY, 12 bytes)
- The elapsed time in which the user task waited to obtain a CICS Hot-Pooling TCB (H8 mode),
because the CICS system had
reached the limit set by the system parameter, MAXHPTCBS. The H8 mode
open TCBs are used exclusively by HPJ-compiled Java programs defined with HOTPOOL(YES). This field is not available in CICS Transaction Server for z/OS Version 3.1 or later.
For more
information, see Transaction timing fields.
Note: This
field is a component of the task suspend time (field: SUSPTIME, owner:
DFHTASK, field ID: 014).
- 279 (Type-S, DSMMSCWT, 12 bytes)
- The elapsed time which the user task spent waiting because no
TCB was available, and none could be created because of MVS storage constraints.
Note: This field is
a component of the task suspend time (field: SUSPTIME, owner: DFHTASK,
field ID: 014).
- 281 (Type-S, MAXSTDLY, 12 bytes)
- The elapsed time in which the user task waited to obtain a CICS SSL TCB (S8 mode), because
the CICS system had reached
the limit set by the system 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 timing fields.
Note: This field is a component
of the task suspend time (field: SUSPTIME, owner: DFHTASK, field ID:
014).
- 282 (Type-S, MAXXTDLY, 12 bytes)
- The elapsed time in which the user task waited to obtain a CICS XPLink TCB (X8 or X9 mode),
because the CICS system had
reached the limit set by the system parameter, MAXXPTCBS. The X8
and X9 mode open TCBs are used exclusively by C or C++ programs compiled
with the XPLINK flag turned on. For more information, see Transaction timing fields.
Note: This field is a component
of the task suspend time (field: SUSPTIME, owner: DFHTASK, field ID:
014).
- 283 (Type-S, MAXTTDLY, 12 bytes)
- The elapsed time in 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 1024 for each CICS region and each JVM server
in a CICS region can have up
to 256 threads.
- 285 (Type-S, PTPWAIT, 12 bytes)
- The elapsed time in which the user task waited for the 3270 bridge
partner transaction to complete. For more information on the CICS 3270 Bridge, see the CICS External Interfaces Guide.
For
more information, see Transaction timing fields.
Note: This
field is a component of the task suspend time (field: SUSPTIME, owner:
DFHTASK, field ID: 014).
- 345 (Type-A, ICSTACDL, 4 bytes)
- The total length, in bytes, of the data in the containers of all
the locally-run interval control START requests, with the CHANNEL
option, issued by the user task. This total includes the length of
any headers to the data.
- 346 (Type-A, ICSTRCCT, 4 bytes)
- The number of interval control START requests, with the CHANNEL
option, to be run on remote systems issued by the user task.
- 347 (Type-A, ICSTRCDL, 4 bytes)
- The total length, in bytes, of the data in the containers of all
the remotely-run interval control START requests, with the CHANNEL
option, issued by the user task. This total includes the length of
any headers to the data.
- 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.
Note: 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.
Note: This field is a component
of the task suspend time field, SUSPTIME (group name: DFHTASK, field
ID: 014).