Effect of retained lock override on CICS
VSAM records the use of the option to override retained locks, so that it can notify a CICS® region when the region next opens the data set. Because data could have been altered by the non-RLS batch job, the results of CICS performing any recovery (on UOWs that were in a backout-failed or indoubt-failed state at the time of the batch job) are unpredictable. In this situation, therefore, the default CICS action is not to back out any updates that were outstanding at the time that locks were overridden, and to write diagnostic information about each backout ignored to the CSFL transient data queue.
The XFCBOVER global user exit is provided to enable you, for each
UOW log record for which backout is being ignored, to:
- Write application-related diagnostics to supplement those provided by CICS
- To perform application-related recovery actions
- To reverse the default by requesting that the backout should be carried out after all. This option is required for the case where the batch job is known not to corrupt data integrity (for example, because it only inserts records).
- When invoked
- Whenever CICS is about to ignore a UOW log record that is due to be backed out, because the lock that protected the updated record could have been overridden by a non-RLS batch program.
- Exit-specific parameters
-
- UEPOLOGR
- Address of the file control portion of a shunted log record that represents an update to a data set for which retained locks may have been overridden. The file control portion of the log record can be mapped using the DSECT DFHFCLGD.
- UEPODSN
- Address of a 44-byte area of storage containing the name of the data set whose locks were overridden.
- Return codes
-
- UERCNORM
- Do not perform the backout of this log record. Any updates performed by the batch run should take precedence.
- UERCBCKO
- Perform the backout. It is known that the actions of the batch job could not have affected this update.
- XPI calls
- All can be used, but subject to the same caution as for API and SPI calls.
- API and SPI calls
- Although this exit is allowed to issue API and SPI calls, you
should be very careful about which commands you use because the exit
is invoked during file backout, which is part of syncpoint phase 2.
It is recommended that you restrict EXEC CICS commands to inquiries, and avoid commands that update CICS resources, because the resources may themselves be in a state of recovery. In particular, the following restrictions apply:
- Do not issue any recoverable operations.
- Do not use operations that access systems or resource owners external to this CICS, even if the target resource is non-recoverable.
- Do not disable or close files, because this could cause further error conditions.
- It is possible for this exit to be invoked under a different transaction environment from that under which the updates that are being backed out were originally made. If your exit program wants to perform any actions (such as writing a message to the terminal) that require it to be running under the original transaction environment, it must first check the value returned in the RE_ATTACHED_TRANSACTION parameter of a transaction manager INQUIRE_TRANSACTION XPI call.