File control EXEC interface SPI exits XFCAREQ and XFCAREQC
The XFCAREQ exit allows you to intercept a file control system programming interface (SPI) request before any action has been taken on it by file control. The XFCAREQC exit allows you to intercept the response after a file control SPI request has completed.
The file control SPI requests intercepted are:
- EXEC CICS INQUIRE FILE
- EXEC CICS SET FILE
Using XFCAREQ, you can:
- Analyze the SPI parameter list (function, keywords, argument values, and responses)
- Modify any input parameter before execution of the request
- Prevent execution of a request and set appropriate responses.
Using XFCAREQC, you can:
- Analyze the SPI parameter list
- Modify any output parameter value and set responses after execution.
You can also:
- Pass data between your XFCAREQ and XFCAREQC exit programs when they are invoked for the same request.
- Pass data between your file control exit programs when they are invoked within the same task. You can pass data between successive invocations of XFCAREQ and XFCAREQC and also between invocations of other EXEC-enabled user exits.
If you make changes to file states (that is, if you open, close, enable,
or disable a file) it is possible that exits in the file state change program
(XFCSREQ and XFCSREQC) could modify situations set up by XFCAREQ. Therefore
you must consider the order in which the exits are invoked. If all four exits
are enabled, the order of invocation is as follows:
- For the SET FILE command:
- XFCAREQ
- XFCSREQ
- XFCSREQC
- XFCAREQC
- For the INQUIRE FILE command:
- XFCAREQ
- XFCAREQC