Files: Resource statistics - requests information

File requests information statistics provide information about the requests made against files.

The following eight items are service request statistics. They do not tell you directly how many I/O accesses are being carried out for each transaction (a single-transaction measurement is required for this). Nevertheless, by regularly totaling the service requests against individual data sets, they can enable you to anticipate data set problems when I/O activity increases.

They list the number of service requests processed against the data set. These are dependent on the type of requests that are allowed on the data set.

Table 1. Files: Resource statistics - requests information
DFHSTUP name	Field name	Description
File name	A17FNAM	is the name you specified in: The DEFINE FILE command of resource definition online (for BDAM files only) The TYPE=FILE, FILE operand of the DFHFCT macro. Reset characteristic: not reset
GET requests	A17DSRD	is the number of GET requests attempted against this file. Reset characteristic: reset to zero
GET upd requests	A17DSGU	is the number of GET UPDATE requests attempted against this file. Reset characteristic: reset to zero
Browse requests	A17DSBR	is the number of GETNEXT and GETPREV requests attempted against this file. Reset characteristic: reset to zero
Update requests	A17DSWRU	is the number of PUT UPDATE requests attempted against this file. Reset characteristic: reset to zero
Add requests	A17DSWRA	is the number of PUT requests attempted against this file. Reset characteristic: reset to zero
Delete requests	A17DSDEL	is the number of DELETE requests attempted against this file. Reset characteristic: reset to zero
Brws upd requests	A17DSBRU	is the number of browse READNEXT UPDATE and READPREV UPDATE requests issued against this file. Note that this field is only applicable to RLS accessed files. Reset characteristic: reset to zero
VSAM EXCP requests
–Data	A17DSXCP	A value is printed if the file has been opened and used as a VSAM KSDS during the CICS® run, even if the file is not being used as a KSDS at the time of taking statistics. See notes 1, 2 and 3.
–Index	A17DSIXP	See notes 1, 2 and 3. Reset characteristic: reset to zero
RLS req timeouts	A17RLSWT	is the number of RLS requests made to this file that were not serviced in the specified time limit, and therefore the requests were terminated. Reset characteristic: reset to zero
Not in DFHSTUP report	A17_FILE_DEFINE_SOURCE	The name of the CSD group that contains to this resource. Reset characteristic: not reset
Not in DFHSTUP report	A17_FILE_CHANGE_TIME	The time stamp (STCK) in local time of CSD record change. Reset characteristic: not reset
Not in DFHSTUP report	A17_FILE_CHANGE_USERID	The user ID that ran the change agent. Reset characteristic: not reset
Not in DFHSTUP report	A17_FILE_CHANGE_AGENT	The agent that made the last change. Reset characteristic: not reset
Not in DFHSTUP report	A17_FILE_INSTALL_AGENT	The agent that installed the resource. Reset characteristic: not reset
Not in DFHSTUP report	A17_FILE_INSTALL_TIME	The time stamp (STCK) in local time when the resource was installed. Reset characteristic: not reset
Not in DFHSTUP report	A17_FILE_INSTALL_USERID	The user ID that installed the resource. Reset characteristic: not reset
Notes: The “VSAM EXCP requests” fields indicate the number of I/O operations on the file for data and index records respectively. Also, note the following points: The values printed for both items relate to the file. If dynamic allocation has been used to change the physical data sets associated with a file, the value shown is an accumulation for all the data sets. Take care when using these values for files participating in data set name sharing, because VSAM maintains only one count of EXCPs for all access method control blocks (ACBs) thus connected. In this situation, the value reported against each file represents the total accesses for all sharing ACBs during the period for which the file was open. Therefore, if all files in the data set name sharing group were open for the same period, each file would have the same EXCP values reported against it, which would be the total for all the files in the group. When the count of EXCPs rises above x'80000000', the count is no longer reliable, and you should consider redefining the file. For RLS, this value is a count of the number of calls to the system buffer manager. It includes calls that result in either a coupling facility cache access or an I/O. The EXCP count for RLS files is the count of all EXCPs for all tasks accessing the RLS file within that CICS region. It should be noted as stated in note 2, EXCP counts are stored in the file's corresponding ACB within that CICS region.