Installing the S213 Abend Exit

S213 Abend Exit › F1-DSCB Not Found S213 Abend Exit (IFG0EX0A Exit) › Installing the S213 Abend Exit

Installing the S213 Abend Exit

Installing the S213 exit requires an IPL. Perform the following procedure to install the S213 abend exit.

To install the S213 abend exit

If you installed module IFG0EX0A into your LPALIB from a release of CA Disk prior to Release 7.1, remove it as follows.
1. Assemble and link member IFG0EX0A, contained in the CA Disk installation library, into your SYS1.LPALIB.
2. If you also have DFHSM and want CA Disk and DFHSM to auto-restore data sets, use the IFG0EX0A supplied by DFHSM.
If you did not install module IFG0EX0A into your LPALIB from a release of CA Disk prior to Release 7.1, continue here.
Sample JCL is provided in the installation library member USERMOD7.
After completing the relink, run the following JCL to verify your changes.
```
//LIST     EXEC PGM=AMBLIST
//SYSPRINT  DD  SYSOUT=*
//SYSLIB    DD  DISP=SHR,DSN=SYS1.LPALIB
//SYSIN     DD  *
    LISTLOAD MEMBER=(IFG0EX0A)
```
Make sure that the correct version of IFG0EX0A has been link-edited. If DFHSM is not installed, the IFG0EX0A CSECT in module IFG0EX0A should consist of only two instructions:
```
SR 15,15
BR 14.
```
IPL your system with either the CLPA or MLPA option. The auto-restore function is now active. If MLPA is used, be sure to add the proper entry to SYS1.PARMLIB member IEALPAxx and specify it during the IPL.

Note: When changing modules that reside in LPA, it can be common practice to link the new version into a linklist library other than SYS1.LPALIB, and then use the MLPA ability to test the new module. If all testing goes well, you might use IEBCOPY to copy and replace the old version in SYS1.LPALIB, and then schedule an IPL with a CLPA. This all works, but only if you specify the entire alias names as well as the true member name in the SELECT MEMBER=(...list...) statement for IEBCOPY. Omitting the alias names can cause the IPL with CLPA to fail with unpredictable symptoms.

If archived data sets are cataloged to the CA Disk pseudo-volume, they can be restored by the catalog management hook to any one of a pool of volumes. If the data set is recataloged to a real volume, only the S213 exit of OPEN will be invoked and the restored data set has to go back to that specific volume. The real volume to which archived data sets are recataloged can be thought of as a common staging volume for auto-restores. The volume can be monitored for activity and easily managed to ensure enough space to handle the restores.

If the S213 exit is installed, the following restrictions apply:

The IFG0EX0A exit does not get invoked for VSAM data sets, and therefore they must be restored manually.
The data set must be restored to the same volume to which the 213 was invoked. If sufficient free space does not exist on the volume, the restore fails and the originating task terminates with a system 213 abend.
The IFG0EX0A exit is not entered from TSO and ISPF functions.