Recovering from a CICS system failure

Through the remote VSAM access services of 

AR/CTL

, a batch application program can use a VSAM data set owned by a CICS region. If CICS fails while sharing a VSAM data set with a batch program, CICS considers the batch program to be an in-flight transaction. At emergency restart, CICS performs dynamic transaction backout for all changes made by the batch program since the last checkpoint (syncpoint) or since the beginning of the job step, whichever is later.

If emergency restart fails, you may be able to recover the data set with RPCV. If you run an RPCV UPDATE BACKOUT, be sure to include in-flight transactions. If you run an RPCV forward file recovery, be sure to exclude in-flight transactions.

Warning

A data integrity exposure may result if you set the Access Level option to 2 in the data set option (FCB) member for a shared VSAM data set and a batch job updates that data set while it requires CICS recovery. The CICS recovery may overlay the updates made by the batch job. You can prevent this exposure by setting the Access Level option to 3.

Related topic

Handling-system-problems


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*