S213-04 abends involving ELIB libraries during Endevor package actions including package ship

Products

• Endevor

Issue/Introduction

A S213-04 abend can occur when doing package actions:

• RESET package
• COMMIT package
• DELETE package
• BACKOUT/BACKIN package
• Package Ship

The abend arises when:

• The package was defined with backout enabled
• One of the output datasets was a PDS or PDS/E when the package was executed
• Between the package execution and the failing action, the dataset (which is the one flagged by the abend) was converted into an ELIB

 

Environment

• All supported Releases
• Endevor 
• Package Ship 

Cause

Package backout is not supported with ELIB libraries. This is because the creation and handling of backout members is done using MVS macros that only work with PDS or PDS/E

If a PDS or PDS/E containing backout members is copied to ELIB, Endevor is not aware of the change and the abend arises when it tries to blindly use the MVS macros on the ELIB dataset 

Resolution

To allow the package actions to proceed, you may either copy back the ELIB to PDS(E) or remove the references to the ELIB from the package.

To remove the references to the ELIB, run the Endevor job BC1JRPKG with the following DD statement allocated:

//EN$BKOUT DD DUMMY

The presence of EN$BKOUT DD triggers the following processing:

• Each and every output dataset mentioned in the package backout records is checked for existence and to see whether it is an ELIB.
• Each particular dataset is checked only once for better performance
• All backout records naming a dataset which is either not found or found to be an ELIB are removed from the package dataset