The current backout process makes no distinction between newly delivered and existing components. E.g., if a package contains a new module (i.e. it was baselined for the first time with the package to be backed out), then it does not exist yet in the backup dataset for that library type. During the backout the process tries to restore the previous version of the module, regardless of whether it exists in the backup or not. The file tailoring is using ISPF table &STGLTYP.CPYTB to create the list of components.

This does not cause big issues for the copy step (IEBCOPY will simply print a warning message that the component does not exist in the dataset and continue). But if other postprocessing steps are involved, e.g. CICS NEWCOPY using CMNCICS1, then the process fails since it will try to NEWCOPY a component that no longer exists.

The ISPF table &STGLTYP.CPYTB should be extended to include the information if the component to be processed is newly added to the production dataset or an existing component is modified with a new version, since the component no longer exists after delete/restore and post-processing might not be necessary or possible anymore.