Preventing abends with StopX37/II
For a sequential data set to be multivolume, the data set must already be cataloged. If a job uses all 16 extents that are available to a sequential data set, StopX37/II functions can dynamically allocate and add new volumes to the data set’s catalog entry. The sequential data set then becomes a multivolume data set.
Your data center might not want StopX37/II to attempt recovery for all B37, D37, E37, or other errors. The decision to attempt recovery for a particular job can be based on many considerations, including job name, job class, account number, data set name, IBM RACF group, and so on.
By using a full screen ISPF interface, you can specify filtering criteria to select which jobs will be recovered. After a job has been selected, you can use the ISPF interface to apply a rule list to the job to determine the specific parameters of the recovery action to be taken.
A complete audit trail is provided by way of the JOBLOG/SYSLOG and SMF data sets. Batch reporting utilities are provided to scan SMF data for statistics about recovery attempts and actions that were taken.
StopX37/II functions offer specific methods for tailoring the product to attempt recovery for user-directed abend conditions. StopX37/II will not take over your system and attempt to recover all abend conditions. After StopX37/II has been installed and tested, you need to decide which types of jobs merit a recovery attempt.
For information about the steps that are necessary to define your site’s recovery criteria and the associated action to take when those criteria are met, see: