Where you can add your own code
At emergency restart, you can add your own code in post-initialization programs that you nominate in the program list table.
About this task
You might want to include the following function in global
user exit programs that run during an emergency restart:
- Process file control log records containing the details of file updates that are backed out
- Deal with the backing-out of additions to data set types that do not support deletion (VSAM ESDS and BDAM), by flagging the records as logically deleted
- Handle file error conditions that arise during transaction backout
- Process user recovery records (in the XRCINPT exit of the user log record recovery program during emergency restart)
- Deal with the case of a non-RLS batch program having overridden RLS retained locks (this should not occur often, if at all)
You can use the following exits:
- XRCINIT—started at the beginning and end of the user log record recovery program
- XRCINPT—started whenever a user log record is read from the system log
- XFCBFAIL—file backout failure exit
- XFCLDEL—file logical delete exit
- XFCBOVER—file backout non-RLS override exit
- XFCBOUT—file backout exit
You can use any of these exits to add your own processing if you do not want the default action, but do not set the UERCPURG return code for these exits because the exit tasks cannot be purged. Use the following procedure to use these exits at emergency restart.
Procedure
- Enable the exits in PLT programs in the first part of PLT processing.
- Specify the exits on the system initialization parameter, TBEXITS. This takes the form TBEXITS=( name1,name2,name3,name4,name5,name6 ), where name1, name2, name3, name4, name5 , and name6 are the names of your global user exit programs for the XRCINIT, XRCINPT, XFCBFAIL, XFCLDEL, XFCBOVER, XFCBOUT exit points.