DFHFILE fields

For a break down by individual file of some of the DFHFILE information, you can request transaction resource monitoring. See CMF transaction resource class data fields for details.

DFHFILE owns the following performance class data fields:

036 (Type-A, FCGETCT, 4 bytes)
The number of file control GET requests issued by the user task.
037 (Type-A, FCPUTCT, 4 bytes)
The number of file control PUT requests issued by the user task.
038 (Type-A, FCBRWCT, 4 bytes)
The number of file control BROWSE requests issued by the user task.
039 (Type-A, FCADDCT, 4 bytes)
The number of file control ADD requests issued by the user task.
040 (Type-A, FCDELCT, 4 bytes)
The number of file control DELETE requests issued by the user task.
063 (Type-S, FCIOWTT, 8 bytes)
The elapsed time in which the user task waited for non-RLS file I/O.

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).
070 (Type-A, FCAMCT, 4 bytes)
The number of times the user task invoked file access-method interfaces. This number excludes requests for file OPEN and CLOSE.
093 (Type-A, FCTOTCT, 4 bytes)
The 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 the EXEC CICS® file API commands correspond to the file control monitoring fields is shown in Table 1.

Table 1. EXEC CICS file commands related to the file control monitoring fields
EXEC CICS file 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 control request count, FCTOTCT.
174 (Type-S, RLSWAIT, 8 bytes)
The elapsed time in which the user task waited for RLS file I/O.

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

However, this field cannot be considered a subset of any other single CMF field (including RLSWAIT). This is because the RLS file requests run 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 requests might complete in less than that time unit.
176 (Type-S, CFDTWAIT, 8 bytes)
The 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 Transaction timing fields.

See the CICS System Definition Guide for more information on the CICS data servers.

Note: This field is a component of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID: 014).