Some long-running jobs with many add, update or delete maintenance transactions can cause a log file (LXX) to fill up. In the event the LOG reaches 100% full, or the value of the MUF Startup Option LOGSPILL “d” value is reached, the older Log file entries are “Force Spilled” to the Recovery File (RXX), and a message is issued in the MUF log:
DB00110W - FORCED SPILL JOB-jjjjjjjj NUMBER-nnnnn TSN-xxxxxxxx
When using the recommended default setting of “RXXROLLBACK YES” in the MUF Startup Options, a situation could arise where this long-running job fails and needs to rollback to undo the changes. When the rollback encounters a forced spill, a message is written to the MUF log and displayed on the console:
DB00109W - BACKOUT JOB jjjjjjjj NUMBER-nnnnn TSN-xxxxxxxx WAITING TO COMPLETE.
In this scenario, the backout process cannot complete, because all the transactions are not in the LXX, having been SPILLed previously to one or more RXX files. A COMM STATUS command will show the following for this job:
WAIT E/C DBSTXB ROLBK
Release: All releases
When this happens, you can execute the following procedure to undo all the changes for this task/jobstep.
Due to the complex nature of logging and recovery, and due to the possibility of encountering other problems in this process, this article addresses only the basic operation. If you need to process a Backward Recovery for your system, and have any question about what to do, we recommend you contact your CA Support team for assistance.
For an overview of the Recovery process, please refer to the Knowledge Base article 18722, titled “An overview of CA Datacom Forward Recovery and Backward Recovery processing, using RXX files.”
For more information about Logging and Spilling the logfile to RXX, about the Log file becoming full, about a Forced Spill and about the Recovery process, please refer to the CA Datacom documentation on techdocs.
As always, please contact CA Technologies support for CA Datacom if you have further questions.