Preventing abends with MainView SRM Allocation
MainView SRM Allocation attempts recovery on jobs that are abending with B37, D37, or E37 return codes (and many other out-of-space conditions).
These abend codes are associated with disk space availability and management. These codes can be found in even the most productive data-processing centers.
MainView SRM Allocation provides automatic recovery from these abend conditions, which removes a significant burden from your data center support staff. Allocation functions interact with the End-of-Volume SVC, which is a part of the z/OS operating system. Before the operating system invokes the module that produces the return codes, MainView SRM Allocation employs user-defined filtering language to decide whether to attempt recovery before the job abends.
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, MainView SRM Allocation 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 MainView SRM Allocation 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.
MainView SRM Allocation functions offer specific methods for tailoring the product to attempt recovery for user-directed abend conditions. MainView SRM Allocation will not take over your system and attempt to recover all abend conditions. After MainView SRM Allocation has been installed and tested, you need to decide which types of jobs merit a recovery attempt.
The remainder of this section describes the steps that are necessary to define your site’s recovery criteria and the associated action to take when those criteria are met.
- VSAM considerations when preventing abends with Allocation
- SMS considerations when preventing abends with Allocation
- Data striping considerations when preventing abends with Allocation
- Filter and rule list sample when preventing abends with Allocation