Performance class data

The performance class data is described below in order of group name. The group name is always in field CMODNAME of the dictionary entry.

A user task can be represented by one or more performance class monitoring records, depending on whether the MCT event monitoring option DELIVER or the system initialization parameters MNCONV=YES or MNSYNC=YES have been selected. In the descriptions that follow, the term "user task" means "that part or whole of a transaction that is represented by a performance class record", unless the description states otherwise.

This section covers:

Performance data in group DFHCBTS

Product-Sensitive programming interface

Group DFHCBTS contains the following performance data:

200 (TYPE-C, ‘PRCSNAME’, 36 BYTES)
The name of the CICS® business transaction service (BTS) process of which the user task formed part.
201 (TYPE-C, ‘PRCSTYPE’, 8 BYTES)
The process-type of the CICS BTS process of which the user task formed part.
202 (TYPE-C, ‘PRCSID’, 52 BYTES)
The CICS-assigned identifier of the CICS BTS root activity that the user task implemented.
203 (TYPE-C, ‘ACTVTYID’, 52 BYTES)
The CICS-assigned identifier of the CICS BTS activity that the user task implemented.
204 (TYPE-C, ‘ACTVTYNM’, 16 BYTES)
The name of the CICS BTS activity that the user task implemented.
205 (TYPE-A, ‘BARSYNCT’, 4 BYTES)
The number of CICS BTS run process, or run activity, requests that the user task made in order to execute a process or activity synchronously.
206 (TYPE-A, ‘BARASYCT’, 4 BYTES)
The number of CICS BTS run process, or run activity, requests that the user task made in order to execute a process or activity asynchronously.
207 (Type-A, ‘BALKPACT’, 4 BYTES)
The number of CICS BTS link process, or link activity, requests that the user task issued.
208 (TYPE-A, ‘BADPROCT’, 4 BYTES)
The number of CICS BTS define process requests issued by the user task.
209 (TYPE-A, ‘BADACTCT’, 4 BYTES)
The number of CICS BTS define activity requests issued by the user task.
210 (TYPE-A, ‘BARSPACT’, 4 BYTES)
The number of CICS BTS reset process and reset activity requests issued by the user task.
211 (TYPE-A, ‘BASUPACT’, 4 BYTES)
The number of CICS BTS suspend process, or suspend activity, requests issued by the user task.
212 (TYPE-A, ‘BARMPACT’, 4 BYTES)
The number of CICS BTS resume process, or resume activity, requests issued by the user task.
213 (TYPE-A, ‘BADCPACT’, 4 BYTES)
The number of CICS BTS delete activity, cancel process, or cancel activity, requests issued by the user task.
214 (TYPE-A, ‘BAACQPCT’, 4 BYTES)
The number of CICS BTS acquire process, or acquire activity, requests issued by the user task.
215 (Type-A, ‘BATOTPCT’, 4 BYTES)
Total number of CICS BTS process and activity requests issued by the user task.
216 (TYPE-A, ‘BAPRDCCT’, 4 BYTES)
The number of CICS BTS delete, get, move, or put, container requests for process data containers issued by the user task.
217 (TYPE-A, ‘BAACDCCT’, 4 BYTES)
The number of CICS BTS delete, get, move, or put, container requests for current activity data containers issued by the user task.
218 (Type-A, ‘BATOTCCT’, 4 BYTES)
Total number of CICS BTS delete, get, move, or put, process container and activity container requests issued by the user task.
219 (TYPE-A, ‘BARATECT’, 4 BYTES)
The number of CICS BTS retrieve-reattach event requests issued by the user task.
220 (TYPE-A, ‘BADFIECT’, 4 BYTES)
The number of CICS BTS define-input event requests issued by the user task.
221 (TYPE-A, ‘BATIAECT’, 4 BYTES)
The number of CICS BTS DEFINE TIMER EVENT, CHECK TIMER EVENT, DELETE TIMER EVENT, and FORCE TIMER EVENT requests issued by the user task.
222 (TYPE-A, ‘BATOTECT’, 4 BYTES)
Total number of CICS BTS event-related requests issued by the user task.
End of Product-Sensitive programming interface
Start of change

Performance data in group DFHCHNL

Group DFHCHNL contains the following performance data:

Product-Sensitive programming interface
321 (TYPE-A, 'PGTOTCCT', 4 BYTES)
The number of CICS requests for channel containers issued by the user task.
322 (TYPE-A, 'PGBRWCCT', 4 BYTES)
The number of CICS browse requests for channel containers issued by the user task.
323 (TYPE-A, 'PGGETCCT', 4 BYTES)
The number of GET CONTAINER requests for channel containers issued by the user task.
324 (TYPE-A, 'PGPUTCCT', 4 BYTES)
The number of PUT CONTAINER requests for channel containers issued by the user task.
325 (TYPE-A, 'PGMOVCCT', 4 BYTES)
The number of MOVE CONTAINER requests for channel containers issued by the user task.
326 (TYPE-A, 'PGGETCDL', 4 BYTES)
The total length, in bytes, of the data in the containers of all the GET CONTAINER CHANNEL commands issued by the user task.
327 (TYPE-A, 'PGPUTCDL', 4 BYTES)
The total length, in bytes, of the data in the containers of all the PUT CONTAINER CHANNEL commands issued by the user task.
328 (TYPE-A, 'PGCRECCT', 4 BYTES)
The number of containers created by MOVE and PUT CONTAINER requests for channel containers issued by the user task.
End of Product-Sensitive programming interface
End of change

Performance data in group DFHCICS

Product-Sensitive programming interface

Group DFHCICS contains the following performance data:

005 (TYPE-T, ‘START’, 8 BYTES)
Start time of measurement interval. This is one of the following:
  • 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.
Note:
Response Time = STOP - START. For more information, see Response time.
006 (TYPE-T, ‘STOP’, 8 BYTES)
Finish time of measurement interval. This is either the time at which the user task was detached, or 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.
Note:
Response Time = STOP - START. For more information, see Response time.
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 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’, 8 BYTES)
Accumulated data for exception conditions. The 32-bit clock contains the total elapsed time for which the user waited on exception conditions. The 24-bit period count equals the number of exception conditions that have occurred for this task. For more information, see Exception class data
Note:
The performance class data field ‘exception wait time’ will be 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 syncpoint
T
Record output for a task termination.
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 will be null for those CRTE transactions which 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 MVS™ Workload Manager (WLM) service class for this transaction. This field is null if there are no transaction classification rules defined for CICS subsystems in the active MVS Workload Manager (WLM) service policy, or if the transaction was WLM-classified in another CICS region.
168 (TYPE-C, ‘RPTCLASS’, 8 bytes)
The MVS Workload Manager (WLM) report class for this transaction. This field is null if there are no transaction classification rules defined for CICS subsystems in the active MVS Workload Manager (WLM) service policy, or if the transaction was WLM-classified in another CICS region.
End of Product-Sensitive programming interface

Performance data in group DFHDATA

Product-Sensitive programming interface

Group DFHDATA contains the following performance data:

179 (TYPE-A, ‘IMSREQCT’, 4 bytes)
The number of IMS™ (DBCTL) requests issued by the user task.
180 (TYPE-A, ‘DB2REQCT’, 8 bytes)
The total number of DB2® EXEC SQL and Instrumentation Facility Interface (IFI) requests issued by the user task.
186 (TYPE-S, ‘IMSWAIT’, 8 bytes)
The elapsed time in which the user task waited for DBCTL to service the IMS requests issued by the user task.

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

Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
187 (TYPE-S, ‘DB2RDYQW’, 8 bytes)
The elapsed time in which the user task waited for a DB2 thread to become available.

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

Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
188 (TYPE-S, ‘DB2CONWT’, 8 bytes)
When CICS is connected to DB2 Version 5 or earlier, and so is not exploiting the open transaction environment, this field is the elapsed time in which the user task waited for a CICS DB2 subtask to become available. When CICS is connected to DB2 Version 6 or later, and so is using the open transaction environment, this field is the elapsed time in which the user task waited for a DB2 connection to become available for use with the user task's open TCB.

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

Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
189 (TYPE-S, ‘DB2WAIT’, 8 bytes)
When CICS is connected to DB2 Version 5 or earlier, and so is not exploiting the open transaction environment, this field is the elapsed time in which the user task waited for DB2 to service the DB2 EXEC SQL and IFI requests issued by the user task. When CICS is connected to DB2 Version 6 or later, and so is using the open transaction environment, this field does not apply and is zero. This is because in the open transaction environment, the CICS-DB2 attachment facility uses L8 mode open TCBs as the thread TCBs, rather than using specially created subtask TCBs. Any waits in DB2 that occur on a L8 mode TCB are not visible to the CICS dispatcher domain.

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

Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
End of Product-Sensitive programming interface

Performance data in group DFHDEST

Product-Sensitive programming interface

Group DFHDEST contains the following performance data:

041 (TYPE-A, ‘TDGETCT’, 4 BYTES)
Number of transient data GET requests issued by the user task.
042 (TYPE-A, ‘TDPUTCT’, 4 BYTES)
Number of transient data PUT requests issued by the user task.
043 (TYPE-A, ‘TDPURCT’, 4 BYTES)
Number of transient data PURGE requests issued by the user task.
091 (TYPE-A, ‘TDTOTCT’, 4 BYTES)
Total number of transient data requests issued by the user task. This field is the sum of TDGETCT, TDPUTCT, and TDPURCT.
101 (TYPE-S, ‘TDIOWTT’, 8 BYTES)
Elapsed time in which the user waited for VSAM transient data I/O. For more information see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
End of Product-Sensitive programming interface

Performance data in group DFHDOCH

Product-Sensitive programming interface

Group DFHDOCH contains the following performance data:

226 (TYPE-A, ‘DHCRECT’, 4 bytes)
The number of document handler CREATE requests issued by the user task.
227 (TYPE-A, ‘DHINSCT’, 4 bytes)
The number of document handler INSERT requests issued by the user task.
228 (TYPE-A, ‘DHSETCT’, 4 bytes)
The number of document handler SET requests issued by the user task.
229 (TYPE-A, ‘DHRETCT’, 4 bytes)
The number of document handler RETRIEVE requests issued by the user task.
230 (TYPE-A, ‘DHTOTCT’, 4 bytes)
The total number of document handler requests issued by the user task.
240 (TYPE-A, ‘DHTOTDCL’, 4 bytes)
The total length of all documents created by the user task.
End of Product-Sensitive programming interface

Performance data in group DFHEJBS

Group DFHEJBS contains the following performance data:

311 (TYPE-C, ‘CBSRVRNM’, 4 bytes)
The CorbaServer for which this request processor instance is handling requests. Request processor transactions can be identified using byte 4 of the transaction flags, TRANFLAG (164), field.
312 (TYPE-A, ‘EJBSACCT’, 4 bytes)
The number of bean activations that have occurred in this request processor.
313 (TYPE-A, ‘EJBSPACT’, 4 bytes)
The number of bean passivations that have occurred in this request processor.
314 (TYPE-A, ‘EJBCRECT’, 4 bytes)
The number of bean creation calls that have occurred in this request processor.
315 (TYPE-A, ‘EJBREMCT’, 4 bytes)
The number of bean removal calls that have occurred in this request processor.
316 (TYPE-A, ‘EJBMTHCT’, 4 bytes)
The number of bean method calls executed in this request processor.
317 (TYPE-A, ‘EJBTOTCT’, 4 bytes)
The total for this request processor of fields 312-316.

Performance data in group DFHFEPI

Product-Sensitive programming interface

Group DFHFEPI contains the following performance data:

150 (TYPE-A,‘SZALLOCT’, 4 bytes)
Number of conversations allocated by the user task. This number is incremented for each FEPI ALLOCATE POOL or FEPI CONVERSE POOL.
151 (TYPE-A,‘SZRCVCT’, 4 bytes)
Number of FEPI RECEIVE requests made by the user task. This number is also incremented for each FEPI CONVERSE request.
152 (TYPE-A,‘SZSENDCT’, 4 bytes)
Number of FEPI SEND requests made by the user task. This number is also incremented for each FEPI CONVERSE request.
153 (TYPE-A,‘SZSTRTCT’, 4 bytes)
Number of FEPI START requests made by the user task.
154 (TYPE-A,‘SZCHROUT’, 4 bytes)
Number of characters sent through FEPI by the user task.
155 (TYPE-A,‘SZCHRIN’, 4 bytes)
Number of characters received through FEPI by the user task.
156 (TYPE-S,‘SZWAIT’, 8 bytes)
Elapsed time in which the user task waited for all FEPI services. For more information see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
157 (TYPE-A,‘SZALLCTO’, 4 bytes)
Number of times the user task timed out while waiting to allocate a conversation.
158 (TYPE-A,‘SZRCVTO’, 4 bytes)
Number of times the user task timed out while waiting to receive data.
159 (TYPE-A,‘SZTOTCT’, 4 bytes)
Total number of all FEPI API and SPI requests made by the user task.
End of Product-Sensitive programming interface

Performance data in group DFHFILE

Product-Sensitive programming interface

For a breakdown by individual file of some of the information provided in group DFHFILE, you can request transaction resource monitoring. See Transaction resource class data for details.

Group DFHFILE contains the following performance data:

036 (TYPE-A, ‘FCGETCT’, 4 BYTES)
Number of file GET requests issued by the user task.
037 (TYPE-A, ‘FCPUTCT’, 4 BYTES)
Number of file PUT requests issued by the user task.
038 (TYPE-A, ‘FCBRWCT’, 4 BYTES)
Number of file browse requests issued by the user task. This number excludes the START and END browse requests.
039 (TYPE-A, ‘FCADDCT’, 4 BYTES)
Number of file ADD requests issued by the user task.
040 (TYPE-A, ‘FCDELCT’, 4 BYTES)
Number of file DELETE requests issued by the user task.
063 (TYPE-S, ‘FCIOWTT’, 8 BYTES)
Elapsed time in which the user task waited for file I/O. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
070 (TYPE-A, ‘FCAMCT’, 4 BYTES)
Number of times the user task invoked file access-method interfaces. This number excludes requests for OPEN and CLOSE.
093 (TYPE-A, ‘FCTOTCT’, 4 BYTES)
Total number of file control requests issued by the user task. This number excludes any request for OPEN, CLOSE, ENABLE, or DISABLE of a file.

How EXEC CICS file commands correspond to file control monitoring fields is shown in Table 5.

Table 5. EXEC CICS file commands related to file control monitoring fields
EXEC CICS command Monitoring fields
READ FCGETCT and FCTOTCT
READ UPDATE FCGETCT and FCTOTCT
DELETE (after READ UPDATE) FCDELCT and FCTOTCT
DELETE (with RIDFLD) FCDELCT and FCTOTCT
REWRITE FCPUTCT and FCTOTCT
WRITE FCADDCT and FCTOTCT
STARTBR FCTOTCT
READNEXT FCBRWCT and FCTOTCT
READNEXT UPDATE FCBRWCT and FCTOTCT
READPREV FCBRWCT and FCTOTCT
READPREV UPDATE FCBRWCT and FCTOTCT
ENDBR FCTOTCT
RESETBR FCTOTCT
UNLOCK FCTOTCT
Note:
The number of STARTBR, ENDBR, RESETBR, and UNLOCK file control requests can be calculated by subtracting the file request counts, FCGETCT, FCPUTCT, FCBRWCT, FCADDCT, and FCDELCT from the total file request count, FCTOTCT.

174 (TYPE-S, ‘RLSWAIT’, 8 BYTES)
Elapsed time in which the user task waited for RLS file I/O. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
175 (TYPE-S, ‘RLSCPUT’, 8 BYTES)
The RLS File Request CPU (SRB) time field (RLSCPUT) is the SRB CPU time this transaction spent processing RLS file requests. This field should be added to the transaction CPU time field (USRCPUT) when considering the measurement of the total CPU time consumed by a transaction. Also, this field cannot be considered a subset of any other single CMF field (including RLSWAIT). This is because the RLS field requests execute asynchronously under an MVS SRB which can be running in parallel with the requesting transaction. It is also possible for the SRB to complete its processing before the requesting transaction waits for the RLS file request to complete.
Note:
This clock field could contain a CPU time of zero with a count of greater than zero. This is because the CMF timing granularity is measured in 16 microsecond units and the RLS file request(s) may complete in less than that time unit.
176 (TYPE-S, 'CFDTWAIT', 8 BYTES)
Elapsed time in which the user task waited for a data table access request to the Coupling Facility Data Table server to complete. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
End of Product-Sensitive programming interface

Performance data in group DFHJOUR

Product-Sensitive programming interface

Group DFHJOUR contains the following performance data:

010 (TYPE-S, ‘JCIOWTT’, 8 BYTES)
Elapsed time for which the user task waited for journal (logstream) I/O. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
058 (TYPE-A, ‘JNLWRTCT’, 4 BYTES)
Number of journal write requests issued by the user task.
172 (TYPE-A, ‘LOGWRTCT’, 4 BYTES)
Number of CICS log stream write requests issued by the user task.
End of Product-Sensitive programming interface

Performance data in group DFHMAPP

Product-Sensitive programming interface

Group DFHMAPP contains the following performance data:

050 (TYPE-A, ‘BMSMAPCT’, 4 BYTES)
Number of BMS MAP requests issued by the user task. This field corresponds to the number of RECEIVE MAP requests that did not incur a terminal I/O, and the number of RECEIVE MAP FROM requests.
051 (TYPE-A, ‘BMSINCT’, 4 BYTES)
Number of BMS IN requests issued by the user task. This field corresponds to the number of RECEIVE MAP requests that incurred a terminal I/O.
052 (TYPE-A, ‘BMSOUTCT’, 4 BYTES)
Number of BMS OUT requests issued by the user task. This field corresponds to the number of SEND MAP requests.
090 (TYPE-A, ‘BMSTOTCT’, 4 BYTES)
Total number of BMS requests issued by the user task. This field is the sum of BMS RECEIVE MAP, RECEIVE MAP FROM, SEND MAP, SEND TEXT, and SEND CONTROL requests issued by the user task.
End of Product-Sensitive programming interface

Performance data in group DFHPROG

Product-Sensitive programming interface

Group DFHPROG contains the following performance data:

055 (TYPE-A, ‘PCLINKCT’, 4 BYTES)
Number of program LINK requests issued by the user task, including the link to the first program of the user task. This field does not include program LINK URM (user-replaceable module) requests.
056 (TYPE-A, ‘PCXCTLCT’, 4 BYTES)
Number of program XCTL requests issued by the user task.
057 (TYPE-A, ‘PCLOADCT’, 4 BYTES)
Number of program LOAD requests issued by the user task.
071 (TYPE-C, ‘PGMNAME’, 8 BYTES)
The name of the first program invoked at attach-time.

For a remote transaction:

  • If this CICS definition of the remote transaction does not specify a program name, this field contains blanks.
  • If this CICS definition of the remote transaction specifies a program name, this field contains the name of the specified program. (Note that this is not necessarily the program that is run on the remote system.)

For a dynamically-routed transaction, if the dynamic transaction routing program routes the transaction locally and specifies an alternate program name, this field contains the name of the alternate program.

For a dynamic program link (DPL) mirror transaction, this field contains the initial program name specified in the dynamic program LINK request. DPL mirror transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field.

For an ONC RPC or WEB alias transaction, this field contains the initial application program name invoked by the alias transaction. ONC RPC or WEB alias transactions can be identified using byte 1 of the transaction flags, TRANFLAG (164), field.

For an ECI over TCP/IP transaction, this field contains the name of the application program specified in the External Call Interface (ECI) request from the client application.

072 (TYPE-A, ‘PCLURMCT’, 4 BYTES)
Number of program LINK URM (user-replaceable module) requests issued by, or on behalf of, the user task.

A user-replaceable module (or user-replaceable program) is a CICS-supplied program that is always invoked at a particular point in CICS processing, as if it were part of the CICS code. You can modify the supplied program by including your own logic, or replace it with a version that you write yourself.

The CICS-supplied user-replaceable modules are:

  • bridge exit program -- DFH0CBRE, DFH0CBAE, DFHWBLT, or user specified
  • CICS-JVM interface program -- DFHJVMAT
  • distributed dynamic routing program -- DFHDSRP (or user specified)
  • document template exit program -- user specified on the DOCTEMPLATE resource definition
  • dynamic routing program -- DFHDYP (or user specified)
  • Internet Inter-ORB Protocol (IIOP) inbound request security exit program -- DFHXOPUS
  • node error program -- DFHNEP
  • program autoinstall program -- DFHPGAxX (or user specified)
  • program error program -- DFHPEP
  • terminal autoinstall program(s) -- DFHZATDX/DFHZATDY
  • terminal error program -- DFHTEP
  • transaction restart program -- DFHRTY
  • CICS-DBCTL interface status program -- DFHDBUEX
  • CICS-DB2 dynamic plan exit program -- DSNCUEXT
  • EJB Distinguished Name program -- DFHEJDNx

For detailed information on CICS user-replaceable programs, see the CICS Customization Guide.

073 (TYPE-A, ‘PCDPLCT’, 4 BYTES)
Number of distributed program link (DPL) requests issued by the user task.
113 (TYPE-C, ‘ABCODEO’, 4 BYTES)
Original abend code.
114 (TYPE-C, ‘ABCODEC’, 4 BYTES)
Current abend code.
115 (TYPE-S, ‘PCLOADTM’, 8 BYTES)
Elapsed time in which the user task waited for program library (DFHRPL) fetches. Only fetches for programs with installed program definitions or autoinstalled as a result of application requests are included in this figure. However, installed programs residing in the LPA are not included (because they do not incur a physical fetch from a library). For more information about program load time, see Clocks and time stamps, and Program load time.
Start of change286 (TYPE-A, 'PCDLCSDL', 4 BYTES)End of change
Start of changeThe total length, in bytes, of the data in the containers of all the distributed program link (DPL) requests issued with the CHANNEL option by the user task. This total includes the length of any headers to the data.End of change
Start of change287 (TYPE-A, 'PCDLCRDL', 4 BYTES)End of change
Start of changeThe total length, in bytes, of the data in the containers of all DPL RETURN CHANNEL commands issued by the user task. This total includes the length of any headers to the data.End of change
Start of change306 (TYPE-A, 'PCLNKCCT', 4 BYTES)End of change
Start of changeNumber of local program LINK requests, with the CHANNEL option, issued by the user task.
Note:
This field is a subset of the program LINK requests field, PCLINKCT (055).
End of change
Start of change307 (TYPE-A, 'PCXCLCCT', 4 BYTES)End of change
Start of changeNumber of program XCTL requests issued with the CHANNEL option by the user task.
Note:
This field is a subset of the program XCTL requests field, PCXCTLCT (056).
End of change
Start of change308 (TYPE-A, 'PCDPLCCT', 4 BYTES)End of change
Start of changeNumber of program distributed program link (DPL) requests issued with the CHANNEL option by the user task.
Note:
This field is a subset of the distributed program link requests field, PCDPLCT (073).
End of change
Start of change309 (TYPE-A, 'PCRTNCCT', 4 BYTES)End of change
Start of changeNumber of remote pseudoconversational RETURN requests, with the CHANNEL option, issued by the user task.End of change
Start of change310 (TYPE-A, 'PCRTNCDL', 4 BYTES)End of change
Start of changeThe total length, in bytes, of the data in the containers of all the remote pseudoconversational RETURN CHANNEL commands issued by the user task. This total includes the length of any headers to the data.End of change
End of Product-Sensitive programming interface

Performance data in group DFHRMI

Product-Sensitive programming interface

Group DFHRMI is present in the performance class record only if RMI=YES is specified on the DFHMCT TYPE=INITIAL macro.

Group DFHRMI contains the following performance data:

001 (TYPE-S, ‘RMITOTAL’, 8 BYTES)
The total elapsed time spent in the CICS Resource Manager Interface (RMI).

For more information, see Clocks and time stamps, and RMI elapsed and suspend time.

002 (TYPE-S, ‘RMIOTHER’, 8 BYTES)
The total elapsed time spent in the CICS RMI for resource manager requests other than DB2, DBCTL, EXEC DLI, WebSphere® MQ, CICSPlex® SM, and CICS TCP/IP socket requests.
003 (TYPE-S, ‘RMIDB2’, 8 BYTES)
The total elapsed time spent in the CICS RMI for DB2 requests.
004 (TYPE-S, ‘RMIDBCTL’, 8 BYTES)
The total elapsed time spent in the CICS RMI for DBCTL requests.
005 (TYPE-S, ‘RMIEXDLI’, 8 BYTES)
The total elapsed time spent in the CICS RMI for EXEC DLI requests.
006 (TYPE-S, ‘RMIMQM’, 8 BYTES)
The total elapsed time spent in the CICS RMI for WebSphere MQ requests.
007 (TYPE-S, ‘RMICPSM’, 8 BYTES)
The total elapsed time spent in the CICS RMI for CICSPlex SM requests.
008 (TYPE-S, ‘RMITCPIP’, 8 BYTES)
The total elapsed time spent in the CICS RMI for CICS TCP/IP socket requests.

For more information, see the RMI parameter on the DFHMCT TYPE=INITIAL macro in the CICS Resource Definition Guide.

End of Product-Sensitive programming interface

Performance data in group DFHSOCK

Product-Sensitive programming interface

Group DFHSOCK contains the following performance data:

241 (TYPE-S, ‘SOIOWTT’, 8 BYTES)
'The elapsed time in which the user task waited for inbound socket I/O. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (O14), field.
242 (TYPE-A, ‘SOBYENCT’, 4 BYTES)
The number of bytes encrypted by the secure sockets layer for the user task.
243 (TYPE-A, ‘SOBYDECT’, 4 BYTES)
The number of bytes decrypted by the secure sockets layer for the user task.
244 (TYPE-C, ‘CLIPADDR’, 16 BYTES)
The client IP address (nnn.nnn.nnn.nnn)
245 (TYPE-C, ‘TCPSRVCE’, 8 BYTES)
The TCP/IP service name which attached the user task.
246 (TYPE-A, ‘PORTNUM’, 4 BYTES)
The TCP/IP port number of the TCP/IP service which attached the user task.
289 (TYPE-A, ‘SOEXTRCT’, 4 BYTES)
The number of EXTRACT TCPIP and EXTRACT CERTIFICATE requests issued by the user task.
290 (TYPE-A,'SOCNPSCT',4 BYTES)
The total number of requests made by the user task to create a non-persistent outbound socket.
291 (TYPE-A,'SOCPSCT',4 BYTES)
The total number of requests made by the user task to create a persistent outbound socket.
292 (TYPE-A,'SONPSHWM',4 BYTES)
The peak number of non-persistent outbound sockets owned by the user task.
293 (TYPE-A,'SOPSHWM',4 BYTES)
The peak number of persistent outbound sockets owned by the user task.
294 (TYPE-A,'SORCVCT',4 BYTES)
The total number of receive requests issued for outbound sockets (persistent and non-persistent) by the user task.
295 (TYPE-A,'SOCHRIN',4 BYTES)
The total number of bytes received on outbound sockets by the user task
296 (TYPE-A,'SOSENDCT',4 BYTES)
The total number of send requests issued for outbound sockets (persistent and non-persistent) by the user task.
297 (TYPE-A,'SOCHROUT',4 BYTES)
The total number of bytes sent on outbound sockets by the user task.
298 (TYPE-A, ‘SOTOTCT’, 4 BYTES)
The total number of socket requests issued by the user task.
299 (TYPE-S, ‘SOOIOWTT ’, 8 BYTES)
The total elapsed time the user task waited on outbound sockets. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (O14), field.
301 (TYPE-A, ‘SOMSGIN1’, 4 BYTES)
The number of inbound socket RECEIVE requests issued by the user task.
302 (TYPE-A, ‘SOCHRIN1’, 4 BYTES)
The number of characters received by inbound socket RECEIVE requests issued by the user task.
303 (TYPE-A, ‘SOMSGOU1’, 4 BYTES)
The number of inbound socket SEND requests issued by the user task.
304 (TYPE-A, ‘SOCHROU1’, 4 BYTES)
The number of characters sent by inbound socket SEND requests issued by the user task.
End of Product-Sensitive programming interface

Performance data in group DFHSTOR

User storage fields in group DFHSTOR:

Product-Sensitive programming interface
033 (TYPE-A, ‘SCUSRHWM’, 4 BYTES)
Maximum amount (high-water mark) of user storage allocated to the user task below the 16MB line, in the user dynamic storage area (UDSA).
054 (TYPE-A, ‘SCUGETCT’, 4 BYTES)
Number of user-storage GETMAIN requests issued by the user task below the 16MB line, in the UDSA.
095 (TYPE-A, ‘SCUSRSTG’, 8 BYTES)
Storage occupancy of the user task below the 16MB line, in the UDSA. This measures the area under the curve of storage in use against elapsed time. For more information about storage occupancy, see Storage occupancy counts.
105 (TYPE-A, ‘SCUGETCT’, 4 BYTES)
Number of user-storage GETMAIN requests issued by the user task for storage above the 16MB line, in the extended user dynamic storage area (EUDSA).
106 (TYPE-A, ‘SCUSRHWM’, 4 BYTES)
Maximum amount (high-water mark) of user-storage allocated to the user task above the 16MB line, in the EUDSA.
107 (TYPE-A, ‘SCUSRSTG’, 8 BYTES)
Storage occupancy of the user task above the 16MB line, in the EUDSA. This measures the area under the curve of storage in use against elapsed time. For more information, see Storage occupancy counts.
116 (TYPE-A, ‘SC24CHWM’, 4 BYTES)
Maximum amount (high-water mark) of user-storage allocated to the user task below the 16MB line, in the CICS dynamic storage area (CDSA).
117 (TYPE-A, ‘SCCGETCT’, 4 BYTES)
Number of user-storage GETMAIN requests issued by the user task for storage below the 16MB line, in the CDSA.
118 (TYPE-A, ‘SC24COCC’, 8 BYTES)
Storage occupancy of the user task below the 16MB line, in the CDSA. This measures the area under the curve of storage in use against elapsed time. For more information, see Storage occupancy counts.
119 (TYPE-A, ‘SC31CHWM’, 4 BYTES)
Maximum amount (high-water mark) of user-storage allocated to the user task above the 16MB line, in the extended CICS dynamic storage area (ECDSA).
120 (TYPE-A, ‘SCCGETCT’, 4 BYTES)
Number of user-storage GETMAIN requests issued by the user task for storage above the 16MB line, in the ECDSA.
121 (TYPE-A, ‘SC31COCC’, 8 BYTES)
Storage occupancy of the user task above the 16MB line, in the ECDSA. This measures the area under the curve of storage in use against elapsed time. For more information, see Storage occupancy counts.
Table 6. User storage field id cross reference
Field UDSA EUDSA CDSA ECDSA
Getmain count 054 105 117 120
High-water-mark 033 106 116 119
Occupancy 095 107 118 121
End of Product-Sensitive programming interface

Shared storage fields in group DFHSTOR:

Product-Sensitive programming interface
144 (TYPE-A, ‘SC24SGCT’, 4 BYTES)
Number of storage GETMAIN requests issued by the user task for shared storage below the 16MB line, in the CDSA or SDSA.
145 (TYPE-A, ‘SC24GSHR’, 4 BYTES)
Number of bytes of shared storage GETMAINed by the user task below the 16MB line, in the CDSA or SDSA.
146 (TYPE-A, ‘SC24FSHR’, 4 BYTES)
Number of bytes of shared storage FREEMAINed by the user task below the 16MB line, in the CDSA or SDSA.
147 (TYPE-A, ‘SC31SGCT’, 4 BYTES)
Number of storage GETMAIN requests issued by the user task for shared storage above the 16MB line, in the ECDSA or ESDSA.
148 (TYPE-A, ‘SC31GSHR’, 4 BYTES)
Number of bytes of shared storage GETMAINed by the user task above the 16MB line, in the ECDSA or ESDSA.
149 (TYPE-A, ‘SC31FSHR’, 4 BYTES)
Number of bytes of shared storage FREEMAINed by the user task above the 16MB line, in the ECDSA or ESDSA.
End of Product-Sensitive programming interface

Program storage fields in group DFHSTOR:

Product-Sensitive programming interface

For more information on program storage see Storage manager statistics.

Note:
If a task loads the same program several times, the fields in this group might not reflect the true high-water mark of program storage used by the task. The fields are incremented each time the LOAD command is issued, but if the program has already been loaded by the task, the existing copy of the program is used, meaning that only one copy of the program actually exists in storage. Because of this, for tasks that repeatedly load the same program, the data in the fields PCSTGHWM, PC24BHWM, PC31RHWM, PC31AHWM, PC31CHWM, PC24CHWM, PC24SHWM, PC31SHWM and PC24RHWM should be used with caution.
087 (TYPE-A, ‘PCSTGHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task both above and below the 16MB line.
108 (TYPE-A, ‘PC24BHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task below the 16MB line. This field is a subset of PCSTGHWM (field id 087) that resides below the 16MB line.
122 (TYPE-A, ‘PC31RHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task above the 16MB line, in the extended read-only dynamic storage area (ERDSA). This field is a subset of PC31AHWM (field id 139) that resides in the ERDSA.
139 (TYPE-A, ‘PC31AHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task above the 16MB line. This field is a subset of PCSTGHWM (field id 087) that resides above the 16MB line.
142 (TYPE-A, ‘PC31CHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task above the 16MB line, in the extended CICS dynamic storage area (ECDSA). This field is a subset of PC31AHWM (139) that resides in the ECDSA.
143 (TYPE-A, ‘PC24CHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task below the 16MB line, in the CICS dynamic storage area (CDSA). This field is a subset of PC24BHWM (108) that resides in the CDSA.
160 (TYPE-A, ‘PC24SHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task below the 16MB line, in the shared dynamic storage area (SDSA). This field is a subset of PC24BHWM (108) that resides in the SDSA.
161 (TYPE-A, ‘PC31SHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task above the 16MB line, in the extended shared dynamic storage area (ESDSA). This field is a subset of PC31AHWM (139) that resides in the ESDSA.
162 (TYPE-A, ‘PC24RHWM’, 4 BYTES)
Maximum amount (high-water mark) of program storage in use by the user task below the 16MB line, in the read-only dynamic storage area (RDSA). This field is a subset of PC24BHWM (108) that resides in the RDSA.
End of Product-Sensitive programming interface

Performance data in group DFHSYNC

Product-Sensitive programming interface

Group DFHSYNC contains the following performance data:

060 (TYPE-A, ‘SPSYNCCT’, 4 BYTES)
Number of SYNCPOINT requests issued during the user task.

Notes:
  1. A SYNCPOINT is implicitly issued as part of the task-detach processing.
  2. A SYNCPOINT is issued at PSB termination for DBCTL.
173 (TYPE-S, ‘SYNCTIME’, 8 BYTES)
Total elapsed time for which the user task was dispatched and was processing Syncpoint requests.
177 (TYPE-S, 'SRVSYWTT', 8 BYTES)
Total elapsed time in which the user task waited for syncpoint or resynchronization processing using the Coupling Facility data tables server to complete.
Note:
This field is a component of the task suspend time, SUSPTIME (O14), field.
196 (TYPE-S, 'SYNCDLY', 8 BYTES)
The elapsed time in which the user task waited for a syncpoint request to be issued by it's parent transaction. The user task was executing as a result of the parent task issuing a CICS BTS run-process or run-activity request to execute a process or activity synchronously. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
199 (TYPE-S,'OTSINDWT',8 BYTES)
The elapsed time in which the user task was dispatched and/or suspended indoubt whilst processing a syncpoint for an Object Transaction Service (OTS) syncpoint request. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014) field.
End of Product-Sensitive programming interface

Performance data in group DFHTASK

Product-Sensitive programming interface

Group DFHTASK contains the following performance data:

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 to:
"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’, 8 BYTES)
Total elapsed time during which the user task was dispatched on each CICS TCB under which the task executed. This can include all TCB modes managed by the CICS dispatcher: QR, RO, CO, FO, SZ ,RP, SL, Start of changeSP,End of change SO, J8, J9, L8, Start of changeL9, End of change S8, Start of changeX8, X9, End of change JM and D2. Start of changeBe 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.End of change
008 (TYPE-S, ‘USRCPUT’, 8 BYTES)
Processor time for which the user task was dispatched on each CICS TCB under which the task executed. This can include all TCB modes managed by the CICS dispatcher: QR, RO, CO, FO, SZ, RP, SL, Start of changeSP,End of change SO, J8, J9, L8, Start of changeL9, End of change S8, Start of changeX8, X9, End of change JM and D2. Start of changeBe 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.End of change
014 (TYPE-S, ‘SUSPTIME’, 8 BYTES)
Total elapsed wait time for which the user task was suspended by the dispatcher. This includes:
  • The elapsed time waiting for the 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.
  • The task suspend (wait) time.
  • The elapsed time waiting for redispatch after a suspended task has been resumed.
For more information, see Wait (suspend) times.
031 (TYPE-P, ‘TRANNUM’, 4 BYTES)
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 character ‘transaction numbers’, as follows:
  • ‘ III’ for system initialization task
  • ‘ TCP’ for terminal control.

These special identifiers are placed in bytes 2 through 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
Start of change065 (TYPE-A, 'ICSTACCT', 4 BYTES)End of change
Start of changeTotal number of local interval control START requests, with the CHANNEL option, issued by the user task.End of change
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 executes 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, IIOP, ECI over TCP/IP, 3270 bridge interface, or EJB logical server, as indicated by the transaction origin in Byte 4 of the transaction flags field (group name DFHTASK, field ID 164).
097 (TYPE-C, ‘NETUOWPX’, 20 BYTES)
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 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 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 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 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 within 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 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 for the period count. These may change during the life of the task as a result of syncpoint activity.

Note:
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’, 8 BYTES)
Elapsed time for which the user task waited for redispatch. This is the aggregate of the wait times between each event completion and user-task redispatch.
Note:
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’, 8 BYTES)
The elapsed time waiting for a CICS task control global enqueue. For more information, see Clocks and time stamps.
Note:
This field is a subset 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 which attached the user task.
125 (TYPE-S, ‘DSPDELAY’, 8 BYTES)
The elapsed time waiting for first dispatch.
Note:
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’, 8 BYTES)
The elapsed time waiting for first dispatch which was delayed because of the limits set for this transaction’s transaction class, TCLSNAME (166), being reached. For more information, see Clocks and time stamps.
Note:
This field is a subset of the first dispatch delay, DSPDELAY (125), field.
127 (TYPE-S, ‘MXTDELAY’, 8 BYTES)
The elapsed time waiting for first dispatch which was delayed because of the limits set by the system parameter, MXT, being reached.
Note:
The field is a subset of the first dispatch delay, DSPDELAY (125), field.
128 (TYPE-S, ‘LMDELAY’, 8 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 the CICS Problem Determination Guide.

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

Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
129 (TYPE-S, ‘ENQDELAY’, 8 BYTES)
The elapsed time waiting for a CICS task control local enqueue. For more information, see Clocks and time stamps.
Note:
This field is a subset of the task suspend time, SUSPTIME (014), field.
Start of change132 (TYPE-T, ‘RMUOWID’, 8 BYTES)End of change
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
Transaction facility identification
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
MVS 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
Bits 3-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:
Start of change
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
End of change
Byte 5
Transaction status information
Bits 0-5
Reserved
Bit 6
Task purged on an open TCB
Bit 7
Task abnormally terminated
Note:
If bit 6 is set, the task has been purged while running on an open TCB, and its transaction timing clocks have been left in an unreliable state. Because of this, the clocks will be set to zero when the record is written by the CICS Monitoring Facility (CMF).
Byte 6
JVM information
Bit 0
JVM marked unresettable
Bits 1-7
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
Note:
Bits 2 through 6 will be 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’, 8 BYTES)
The total elapsed time spent in the CICS Resource Manager Interface (RMI). For more information, see Clocks and time stamps, and Wait (suspend) times, and Figure 8.
171 (TYPE-S, ‘RMISUSP’, 8 BYTES)
The total elapsed time the task was suspended by the CICS dispatcher while in the CICS Resource Manager Interface (RMI). For more information, see Clocks and time stamps, and Wait (suspend) times, and Figure 8.
Note:
The field is a subset of the task suspend time, SUSPTIME (014), field and also the RMITIME (170) field.
181 (TYPE-S, ‘WTEXWAIT’, 8 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 MVS POSTed. 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 Wait (suspend) times.
Note:
This field is a component of the task suspend time, (SUSPTIME) (014), field.
182 (TYPE-S, ‘WTCEWAIT’, 8 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, 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 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 Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
183 (TYPE-S, ‘ICDELAY’, 8 BYTES)
The elapsed time 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 Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
184 (TYPE-S, ‘GVUPWAIT’, 8 BYTES)
The elapsed time 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 EXEC 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 Clocks and time stamps, and Wait (suspend) times.
Note:
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’, 8 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 Wait (suspend) times.

Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
192 (TYPE-S, 'RQRWAIT', 8 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 Wait (suspend) times.

Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
193 (TYPE-S, 'RQPWAIT', 8 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 Wait (suspend) times.

Note:
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’, 8 BYTES)
The elapsed time in which the user task waited for completion of a transaction that executed as a result of the user task issuing a CICS BTS run process, or run activity, request to execute a process, or activity, synchronously.

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

Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
Start of change247 (TYPE-S, 'DSCHMDLY', 8 BYTES)End of change
Start of changeThe 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.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
End of change
249 (TYPE-S, ‘QRMODDLY’, 8 BYTES)
The elapsed time for which the user task waited for redispatch on the CICS QR TCB. This is the aggregate of the wait times between each event completion. and user-task redispatch.
Note:
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’, 8 BYTES)
The elapsed time in which the user task waited to obtain a CICS open TCB, because the region had reached the limit set by the system parameter, MAXOPENTCBS. This applies to L8 Start of changeand L9 End of changemode open TCBs only. L8 Start of changeand L9 End of changemode open TCBs are used by Start of changeOPENAPI application programs, or End of change task-related user exit programs that have been enabled with the OPENAPI option, Start of change for example, End of change the CICS DB2 adaptor, when CICS connects to DB2 Version 6 or later.

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

Note:
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 J8, J9, L8, Start of changeL9,End of change S8, Start of changeX8 and X9End of change) that have been concurrently allocated to the user task.
253 (TYPE-S, ‘JVMTIME’, 8 BYTES)
The total elapsed time spent in the JVM by the user task. See JVM elapsed time and suspend time for more details.
254 (TYPE-S, ‘JVMSUSP’, 8 BYTES)
The elapsed time the user task was suspended by the CICS dispatcher while running in the JVM.
Note:
This field is a subset of the task suspend time, SUSPTIME (014), field.
255 (TYPE-S, ‘QRDISPT’, 8 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’, 8 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’, 8 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 the ONC/RPC or CICS Web Interface Feature is installed and active.
  • Start of changeSO, SL, Start of changeand SPEnd of change 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).End of change
  • D2 is used only in CICS Transaction Server for z/OS®, Version 2 Release 2 or later, when CICS is connected to DB2 Version 6 or later, to terminate DB2 protected threads.
  • JM is used for the master JVM when the shared class cache is in use.
For more information, see Clocks and time stamps.
258 (TYPE-S, ‘MSCPUT’, 8 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’, 8 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 invokes Start of change an OPENAPI application program defined with EXECKEY=CICS, or End of change a task-related user exit program that has been enabled with the OPENAPI option Start of change for example, End of change the CICS DB2 adaptor, when CICS connects to DB2 Version 6 or later, it is allocated and uses a CICS L8 mode TCB. Start of change (An L8 mode TCB can also be allocated if the OPENAPI program is defined with EXECKEY=USER, but the storage protection facility is inactive.) End of change Once a task has been allocated an L8 mode TCB, that same TCB remains associated with the task until the transaction is Start of changedetached. End of change For more information on this field, see Clocks and time stamps.
260 (TYPE-S, ‘J8CPUT’, 8 BYTES)
The processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS J8 mode TCB. When a transaction invokes a Java program defined with EXECKEY=CICS, that requires a JVM in CICS key, it is allocated and uses a CICS J8 mode TCB. (A J8 mode TCB can also be allocated if the Java program is defined with EXECKEY=USER, but the storage protection facility is inactive.) Once a task has been allocated a J8 mode TCB, that same TCB remains associated with the task until the Java program completes. For more information, see Clocks and time stamps.
261 (TYPE-S, ‘S8CPUT’, 8 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 is using the secure sockets layer (SSL) during client certificate negotiation. Start of changeThe S8 mode TCB remains associated with the same task for the life of the SSL request.End of change For more information, see Clocks and time stamps.
262 (TYPE-S,'KY8DISPT',8 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 invokes Start of change an OPENAPI application program defined with EXECKEY=CICS, or End of change a task-related user exit program that has been enabled with the OPENAPI option. (This includes, for example, the CICS DB2 adaptor, when CICS connects to DB2 Version 6 or later.) The TCB remains associated with the task until the transaction is detached.
  • A J8 mode TCB is allocated when a transaction invokes a Java program defined with EXECKEY=CICS, that requires a JVM in CICS key. (A J8 mode TCB can also be allocated if the Java program is defined with EXECKEY=USER, but the storage protection facility is inactive.) The TCB remains associated with the task until the Java program completes.
  • An S8 mode TCB is allocated when a transaction is using the secure sockets layer (SSL) during client certificate negotiation. Start of changeThe S8 mode TCB remains associated with the same task for the life of the SSL request.End of change
  • Start of changeAn X8 mode TCB is allocated when a transaction invokes 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.End of change
Note:
This field is a component of the task dispatch time field, USRDISPT (field id 007 in group DFHTASK).
263 (TYPE-S,'KY8CPUT',8 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).
Note:
This field is a component of the task CPU time field, USRCPUT (field id 008 in group DFHTASK).
264 (TYPE-S, ‘KY9DISPT’, 8 BYTES)
The total elapsed time during which the user task was dispatched by the CICS dispatcher on a CICS Key 9 mode TCB:
  • A J9 mode TCB is allocated 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.
  • Start of changeAn L9 mode TCB is allocated when a transaction invokes an OPENAPI application program defined with EXECKEY=USER. The TCB remains associated with the task until the transaction is detached.End of change
  • Start of changeAn X9 mode TCB is allocated 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.End of change
Note:
This field is a component of the task dispatch time field, USRDISPT (field id 007 in group DFHTASK).
265 (TYPE-S, ‘KY9CPUT’, 8 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).
Note:
This field is a component of the task CPU time field, USRCPUT (field id 008 in group DFHTASK).
Start of change266 (TYPE-S, ‘L9CPUT’, 8 BYTES)End of change
Start of changeThe 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.) Once a task has been allocated an L9 mode TCB, that same TCB remains associated with the task until the transaction is detached.
Note:
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).
End of change
267 (TYPE-S, ‘J9CPUT’, 8 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.) Once 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’, 8 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. Java Applications in CICS has more information about how CICS manages TCB mismatch waits for these transactions.
269 (TYPE-S, ‘RODISPT’, 8 BYTES)
The 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 other functions.
Note:
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’, 8 BYTES)
The processor 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 other functions.
Note:
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).
Start of change271 (TYPE-S, ‘X8CPUT’, 8 BYTES)End of change
Start of changeThe processor time during which the user task was dispatched by the CICS dispatcher domain on a CICS X8 mode TCB. When a transaction invokes 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.) Once 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 (field id 008 in group DFHTASK), and the task key 8 CPU time field, KY8CPUT (field id 263 in group DFHTASK).
End of change
Start of change272 (TYPE-S, ‘X9CPUT’, 8 BYTES)End of change
Start of changeThe processor time during which the user task was dispatched by the CICS dispatcher domain on a 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, 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.) Once 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 (field id 008 in group DFHTASK), and the task key 9 CPU time field, KY9CPUT (field id 265 in group DFHTASK).
End of change
273 (TYPE-S, 'JVMITIME', 8 BYTES)
The elapsed time spent initializing the JVM environment. For more information, see Clocks and time stamps, and JVM elapsed time and suspend time.
275 (TYPE-S, 'JVMRTIME', 8 BYTES)
The elapsed time spent resetting the JVM environment to its initial state. For more information, see Clocks and time stamps.
277 (TYPE-S, ‘MAXJTDLY’, 8 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 Wait (suspend) times.

Note:
This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field id: 014).
279 (TYPE-S, ‘DSMMSCWT’, 8 BYTES)
The elapsed time which the user task spent waiting because no TCB pwas available, and none could be created because of MVS storage constraints. For more information about MVS storage constraints, see Dealing with warnings about MVS storage constraints.
Note:
This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field id: 014).
Start of change281 (TYPE-S, 'MAXSTDLY', 8 BYTES)End of change
Start of changeThe 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 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 Wait (suspend) times.
Note:
This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field id: 014).
End of change
Start of change282 (TYPE-S, ‘MAXXTDLY’, 8 BYTES)End of change
Start of changeThe elapsed time in which the user task waited to obtain a CICS XP 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 and C++ programs that were compiled with the XPLINK option. For more information, see Wait (suspend) times.
Note:
This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field id: 014).
End of change
285 (TYPE-S, ‘PTPWAIT’, 8 BYTES)
The elapsed time in which the user task waited for the 3270 bridge partner transaction to complete. For more information, see Wait (suspend) times.
Note:
This field is a component of the task suspend time field, SUSPTIME (group name: DFHTASK, field id: 014).
Start of change345 (TYPE-A, 'ICSTACDL', 4 BYTES)End of change
Start of changeTotal 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.End of change
Start of change346 (TYPE-A, 'ICSTRCCT', 4 BYTES)End of change
Start of changeTotal number of interval control START CHANNEL requests, to be executed on remote systems, issued by the user task.End of change
Start of change347 (TYPE-A, 'ICSTRCDL', 4 BYTES)End of change
Start of changeTotal 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.End of change
End of Product-Sensitive programming interface

Performance data in group DFHTEMP

Product-Sensitive programming interface

For a breakdown by individual temporary storage queue of the information provided in group DFHTEMP, you can request transaction resource monitoring.

See Transaction resource class data for details.

Group DFHTEMP contains the following performance data:

011 (TYPE-S, ‘TSIOWTT’, 8 BYTES)
Elapsed time for which the user task waited for VSAM temporary storage I/O. For more information see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
044 (TYPE-A, ‘TSGETCT’, 4 BYTES)
Number of temporary-storage GET requests issued by the user task.
046 (TYPE-A, ‘TSPUTACT’, 4 BYTES)
Number of PUT requests to auxiliary temporary storage issued by the user task.
047 (TYPE-A, ‘TSPUTMCT’, 4 BYTES)
Number of PUT requests to main temporary storage issued by the user task.
092 (TYPE-A, ‘TSTOTCT’, 4 BYTES)
Total number of temporary storage requests issued by the user task. This field is the sum of the temporary storage READQ (TSGETCT), WRITEQ AUX (TSPUTACT), WRITEQ MAIN (TSPUTMCT), and DELETEQ requests issued by the user task.
178 (TYPE-S, ‘TSSHWAIT’, 8 BYTES)
Elapsed time that the user task waited for an asynchronous shared temporary storage request to a temporary storage data server to complete. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
End of Product-Sensitive programming interface

Performance data in group DFHTERM

Product-Sensitive programming interface

Group DFHTERM contains the following performance data:

002 (TYPE-C, ‘TERM’, 4 BYTES)
Terminal or session identification. This field is null if the task is not associated with a terminal or session.
009 (TYPE-S, ‘TCIOWTT’, 8 BYTES)
Elapsed time for which the user task waited for input from the terminal operator, after issuing a RECEIVE request. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
034 (TYPE-A, ‘TCMSGIN1’, 4 BYTES)
Number of messages received from the task’s principal terminal facility, including LUTYPE6.1 and LUTYPE6.2 (APPC) but not MRO (IRC).
035 (TYPE-A, ‘TCMSGOU1’, 4 BYTES)
Number of messages sent to the task’s principal terminal facility, including LUTYPE6.1 and LUTYPE6.2 (APPC) but not MRO (IRC).
067 (TYPE-A, ‘TCMSGIN2’, 4 BYTES)
Number of messages received from the LUTYPE6.1 alternate terminal facilities by the user task.
068 (TYPE-A, ‘TCMSGOU2’, 4 BYTES)
Number of messages sent to the LUTYPE6.1 alternate terminal facilities by the user task.
069 (TYPE-A, ‘TCALLOCT’, 4 BYTES)
Number of TCTTE ALLOCATE requests issued by the user task for LUTYPE6.2 (APPC), LUTYPE6.1, and IRC sessions.
083 (TYPE-A, ‘TCCHRIN1’, 4 BYTES)
Number of characters received from the task’s principal terminal facility, including LUTYPE6.1 and LUTYPE6.2 (APPC) but not MRO (IRC).
084 (TYPE-A, ‘TCCHROU1’, 4 BYTES)
Number of characters sent to the task’s principal terminal facility, including LUTYPE6.1 and LUTYPE6.2 (APPC) but not MRO (IRC).
085 (TYPE-A, ‘TCCHRIN2’, 4 BYTES)
Number of characters received from the LUTYPE6.1 alternate terminal facilities by the user task. (Not applicable to ISC APPC.)
086 (TYPE-A, ‘TCCHROU2’, 4 BYTES)
Number of characters sent to the LUTYPE6.1 alternate terminal facilities by the user task. (Not applicable to ISC APPC.)
100 (TYPE-S, ‘IRIOWTT’, 8 BYTES)
Elapsed time for which the user task waited for control at this end of an MRO link. For more information, see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
111 (TYPE-C, ‘LUNAME’, 8 BYTES)
VTAM logical unit name (if available) of the terminal associated with this transaction. If the task is executing in an application-owning or file-owning region, the LUNAME is the generic applid of the originating connection for MRO, LUTYPE6.1, and LUTYPE6.2 (APPC). The LUNAME is blank if the originating connection is an external CICS interface (EXCI).
133 (TYPE-S, ‘LU61WTT’, 8 BYTES)
The elapsed time for which the user task waited for I/O on a LUTYPE6.1 connection or session. This time also includes the waits incurred for conversations across LUTYPE6.1 connections, but not the waits incurred due to LUTYPE6.1 syncpoint flows. For more information see Clocks and time stamps, and Wait (suspend) times.
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
134 (TYPE-S, ‘LU62WTT’, 8 BYTES)
The elapsed time for which the user task waited for I/O on a LUTYPE6.2 (APPC) connection or session. This time also includes the waits incurred for conversations across LUTYPE6.2 (APPC) connections, but not the waits incurred due to LUTYPE6.2 (APPC) syncpoint flows. For more information, see Clocks and time stamps, and Wait (suspend) times
Note:
This field is a component of the task suspend time, SUSPTIME (014), field.
135 (TYPE-A, ‘TCM62IN2’, 4 BYTES)
Number of messages received from the alternate facility by the user task for LUTYPE6.2 (APPC) sessions.
136 (TYPE-A, ‘TCM62OU2’, 4 BYTES)
Number of messages sent to the alternate facility by the user task for LUTYPE6.2 (APPC) sessions.
137 (TYPE-A, ‘TCC62IN2’, 4 BYTES)
Number of characters received from the alternate facility by the user task for LUTYPE6.2 (APPC) sessions.
138 (TYPE-A, ‘TCC62OU2’, 4 BYTES)
Number of characters sent to the alternate facility by the user task for LUTYPE6.2 (APPC) sessions.
165 (TYPE-A, ‘TERMINFO’, 4 BYTES)
Terminal or session information for this task’s principal facility as identified in the ‘TERM’ field id 002. This field is null if the task is not associated with a terminal or session facility.
Byte 0
Identifies whether this task is associated with a terminal or session. This field can be set to one of the following values:
X'00'
None
X'01'
Terminal
X'02'
Session
Byte 1
If the principal facility for this task is a session (Byte 0 = x'02'), this field identifies the session type. This field can be set to one of the following values:
X'00'
None
X'01'
IRC
X'02'
IRC XM
X'03'
IRC XCF
X'04'
LU61
X'05'
LU62 Single
X'06'
LU62 Parallel
Byte 2
Identifies the access method defined for the terminal id or session id in field TERM. This field can be set to one of the following values:
X'00'
None
X'01'
VTAM
Start of changeX'02'End of change
Start of changeBTAM (no longer supported)End of change
X'03'
BSAM
Start of changeX'04'End of change
Start of changeTCAM/DCB (supported for remote terminals only)End of change
Start of changeX'05'End of change
Start of changeTCAM/ACB (no longer supported)End of change
X'06'
BGAM
X'07'
CONSOLE
Byte 3
Identifies the terminal or session type for the terminal id or session id in TERM.

  • See RDO Typeterm

For a list of the typeterm definitions, see the CICS Application Programming Reference.

169 (TYPE-C, ‘TERMCNNM’, 4 BYTES)
Terminal session connection name. If the terminal facility associated with this transaction is a session, this field is the name of the owning connection (sysid).

A terminal facility can be identified as a session by using byte 0 of the terminal information, TERMINFO (165), field. If the value is x'02' the terminal facility is a session.

197 (TYPE-C, ‘NETID’, 8 BYTES)
NETID if a network qualified name has been received from VTAM. If it is a VTAM resource and the network qualified name has not yet been received, NETID is 8 blanks. In all other cases it is nulls.
198 TYPE-C, 'RLUNAME', 8 BYTES
Real network name if a network qualified name has been received from VTAM. In all other cases this field will be the same as LUNAME (field id 111). For non-VTAM resources it is nulls.
End of Product-Sensitive programming interface

Performance data in group DFHWEBB

Product-Sensitive programming interface

Group DFHWEBB contains the following performance data:

224 (TYPE-A, ‘WBREADCT’, 4 BYTES)
The number of CICS Web support READ HTTPHEADER and FORMFIELD requests issued by the user task.
225 (TYPE-A, ‘WBWRITCT’, 4 BYTES)
The number of CICS Web support WRITE HTTPHEADER requests issued by the user task.
231 (TYPE-A, ‘WBRCVCT’, 4 BYTES)
The number of CICS Web interface RECEIVE requests issued by the user task.
232 (TYPE-A, ‘WBCHRIN’, 4 BYTES)
The number of bytes received by the CICS Web interface RECEIVE requests issued by the user task.
233 (TYPE-A, ‘WBSENDCT’, 4 BYTES)
The number of CICS Web interface SEND requests issued by the user task.
234 (TYPE-A, ‘WBCHROUT’, 4 BYTES)
The number of bytes sent by the CICS Web interface SEND requests issued by the user task.
235 (TYPE-A, ‘WBTOTWCT’, 4 BYTES)
The total number of CICS Web interface requests issued by the user task.
236 (TYPE-A, ‘WBREPRCT’, 4 BYTES)
The number of reads from the repository in temporary storage issued by the user task.
237 (TYPE-A, ‘WBREPWCT’, 4 BYTES)
The number of writes to the repository in temporary storage issued by the user task.
238 (TYPE-A, ‘WBEXTRCT’, 4 BYTES)
The number of CICS Web support EXTRACT requests issued by the user task.
239 (TYPE-A, ‘WBBRWCT’, 4 BYTES)
The number of CICS Web support BROWSE HTTPHEADER and FORMFIELD requests (STARTBROWSE, READNEXT, and ENDBROWSE) issued by the user task.
Start of change331 (TYPE-A, ‘WBREDOCT’, 4 BYTES)End of change
Start of changeThe number of CICS Web support READ HTTPHEADER requests issued by the user task when CICS is an HTTP client.End of change
Start of change332 (TYPE-A, ‘WBWRTOCT’, 4 BYTES)End of change
Start of changeThe number of CICS Web support WRITE HTTPHEADER requests issued by the user task when CICS is an HTTP client.End of change
Start of change333 (TYPE-A, ‘WBRCVIN1’, 4 BYTES)End of change
Start of changeThe number of CICS Web support RECEIVE and CONVERSE requests issued by the user task when CICS is an HTTP client.End of change
Start of change334 (TYPE-A, ‘WBCHRIN1’, 4 BYTES)End of change
Start of changeThe number of bytes received by the CICS Web support RECEIVE and CONVERSE requests issued by the user task when CICS is an HTTP client. This includes the HTTP headers for the response.End of change
Start of change335 (TYPE-A, ‘WBSNDOU1’, 4 BYTES)End of change
Start of changeThe number of CICS Web support SEND and CONVERSE requests issued by the user task when CICS is an HTTP client.End of change
Start of change336 (TYPE-A, ‘WBCHROU1’, 4 BYTES)End of change
Start of changeThe number of bytes sent by the CICS Web support SEND and CONVERSE requests issued by the user task when CICS is an HTTP client. This includes the HTTP headers for the request.End of change
Start of change337 (TYPE-A, ‘WBPARSCT’, 4 BYTES)End of change
Start of changeThe number of CICS Web support PARSE URL requests issued by the user task.End of change
Start of change338 (TYPE-A, ‘WBBRWOCT’, 4 BYTES)End of change
Start of changeThe number of CICS Web support BROWSE HTTPHEADER requests (STARTBROWSE, READNEXT, and ENDBROWSE) issued by the user task when CICS is an HTTP client.End of change
Start of change340 (TYPE-A, ‘WBIWBSCT’, 4 BYTES)End of change
Start of changeThe number of CICS INVOKE WEBSERVICE requests issued by the user task.End of change
Start of change341 (TYPE-A, ‘WBREPRDL’, 4 BYTES)End of change
Start of changeThe total length, in bytes, of the data read from the repository in temporary storage by the user task.End of change
Start of change342 (TYPE-A, ‘WBREPWDL’, 4 BYTES)End of change
Start of changeThe total length, in bytes, of the data written to the repository in temporary storage by the user task.End of change
Note:
When requests are made using the WEB CONVERSE command, this increments both the Send and Receive request counts (WBSNDOU1 and WBRCVIN1) and the counts of characters sent and received (WBCHRIN1 and WBCHROU1).
End of Product-Sensitive programming interface

Related tasks
Controlling CICS monitoring
Processing CICS monitoring facility output

Related concepts
The CICS monitoring facility
The classes of monitoring data: Overview
Event monitoring points
The monitoring control table (MCT)

Related reference
Interpreting CICS monitoring
Notes on the performance data
Exception class data
Transaction resource class data
[[ Contents Previous Page | Next Page Index ]]