Checkpoint/step restart
Code Debug TSO supports Checkpoint/Step Restart using the RESTART JCL card under certain circumstances. Consider the following scenarios.
Scenario one
There is an ABEND in a multiple step job stream and the ABEND occurred in a step other than the step currently being tested. Under this scenario, both Step and Checkpoint Restarts are supported.
To use Step or Checkpoint Restarts, the session log, script, and document data sets need to be retained. Because it is not possible to know beforehand that a program will ABEND, it is your responsibility to specify retention for these data sets if you want the ability to do a Step or Checkpoint Restart. See to Log, Script, and Document Data set Screens for how to do this.
Scenario two
An ABEND has occurred in a job stream without Code Debug TSO and the user wants to use Code Debug TSO to resolve the problem. Under this scenario, Step Restart is supported if the CONVERT JCL expansion option is used. Checkpoint Restart is not supported.
To use Step Restart, the RESTART JCL card must specify a STEPNAME. The XPEDITER allocation step is then inserted into the JCL just before the step specified on the RESTART JCL card, and the RESTART JCL card is modified to point to that XPEDITER allocation STEPNAME. If the RESTART JCL card does not specify a STEPNAME, no special processing is performed (the JCL is converted as usual).
If you want to be able to use Step Restart after testing with Code Debug TSO, retain the session log, script and document data sets as described in Scenario One.