File control open/close program exit XFCNREC
You can use XFCNREC to suppress the open failure on a non-RLS data set.
For RLS data sets, recovery is a property of the data set. Therefore it is not possible for files and their base data set to have unmatched recovery attributes. For more information about writing an XFCNREC exit program, see Administering recovery of CICS-managed resources.
Exit XFCNREC
- When invoked
- Before file open, when a mismatch is detected:
- Between the backout recovery setting for the file and its associated non-RLS data set.
- Because BWO is required but the recovery attributes indicate that no associated forward recovery file has been specified.
- Exit-specific parameters
-
- UEFILE
- Address of the 8-byte file name. If the file name is less than 8 characters in length, it will be padded with blanks.
- UEDSETN
- Address of the 44-byte base data set name. If the data set name is less than 44 characters in length, it will be padded with blanks.
- UEPFRCV
- Address of a 1-byte field containing the backout recovery setting
for the file, as specified in the FILE definition. The possible value
is:
- UEPFLOG
- Backout logging specified.
If RECOV(NONE) is specified in the FILE definition, the addressed field contains hexadecimal zeros.
This field has no meaning if the exit is driven because of a BWO mismatch.
- UEPFAIL
- Address of a 1-byte field containing the reason for the mismatch.
The possible values are:
- UEPBWOF
- A BWO mismatch
- UEPATTF
- A mismatch in the backout recovery settings
- UEPOPEN
- Address of a 1-byte field. Its default value is N. To bypass an open failure caused by a BWO mismatch, set the addressed field to Y.
- Return codes
-
- UERCNORM
- Fail open as normal.
- UERCBYP
- Bypass open failure—accept mismatch.
- XPI calls
- Must not be used.
- SPI calls
- Must not be used.
- API and SPI calls
- Must not be used.