General request processing
All file requests, whatever the request and whatever the file access
method, follow the same general sequence of steps:
- User exit XFCREQ is called.
- The request is converted from EXEC parameter list form to FCFR interface form.
- If this is the first file access request by the transaction, a FRAB is obtained and its address stored in Recovery Manager's FC Token. The FRAB provides the anchor for file request state for this transaction.
- If this is the first request to this file by the transaction, a FLAB is obtained and the file control table entry is located. If the file is remote or an explicit SYSID has been specified on the request, the FLAB is marked with a remote indicator. If this is not the first request to the file, then the FLAB is located that repressents accesses made to the file by this transaction.
- If this is the first, or only, request of a request sequence, a FRTE is obtained. If this is not the first request in a request sequence, the FRTE that represents the sequence is located. rather than being function shipped.
- If the request is to a local file, and if resource security is active, the security check is made, unless a check has already been made within the current UOW for this file.
- If the request is to a local file and the file is not already open, it is opened and its access method dependent attributes are saved in its file control table entry.
- The SERVREQ attributes of the file are checked.
- For READ and browse requests, SET storage is released or obtained, as necesssary.
- The access method specific request processor is called as follows:
- DFHFCVS for non-RLS VSAM files
- DFHFCRS for RLS VSAM files
- DFHFCBD for BDAM files
- DFHFCDR for coupling facility data tables
- DFHFCDTS for user-maintained data tables
- DFHFCDTS for non-update requests to CICS maintained data tables
- DFHFCVS for update requests to CICS maintained data tables
- DFHFCRF for requests that are to be shipped to a remote region
- CICS has checked whether the file is defined as local or remote.
If it is remote, the request is function-shipped to the file-owning
region, where CICS processes the request as if it had originated locally.
There is an exception for CICS-maintained and user-maintained data tables, for which non-update requests are treated as local rather than being function shipped.
Note that RLS support and coupling facility data tables support both provided shared access within a parallel sysplex without the use of function shipping. Files which use either of these types of sharing will be defined as local on all systems which want to share the data set (in the case of RLS support) or data table (CFDT support).
- SET storage is obtained for BDAM files or below the line READ requests.
- The FRTE is released if the request sequence has ended and the file is closed if a close is pending, this FRTE is the last user and the FLAB indicates that the file can be closed.
- The FCFR responsed are converted to EXEC parameter list responses. In particular, the EIBRCODE and RESP2 values are constructed.
- User exit XFCREQC is called.