Skip to content

Rules for Backing Out Packages

The following rules and restrictions apply to package backout.

  • A package must be in BAS status at an A instance for you to back out the package at that instance.

  • A package must be in INS status at a P instance for you to back out the package at that instance.

  • You can back out a package at a P instance regardless of the status of the package at other P instances or the status of the package at the DP instance where it was created.

  • You must install and back out a package at all P instances where it was scheduled for install before you can back out a package that is installed at the DP site where it was created.

  • You cannot back out a package if the package staging libraries have been aged and physically scratched by housekeeping. You cannot back out a package if the package records have been aged and physically deleted by housekeeping.

  • You cannot back out a package at a P or DP instance if any of the package components in a production library have been overlaid by a subsequent install.

Backout and Temporary Packages

You can use package backout on an installed temporary package to remove package components that are causing a production problem. Backout will remove the members installed into the production override libraries that are concatenated ahead of your regular production libraries, and the package status will be set to BAK. You can revert your temporary package to fix a problem, or you can create a new unplanned temporary package for your changes if you need to use the unplanned approval list.

Do not use backout to remove temporary package components when they have successfully served their purpose in production override libraries. When temporary package components have successfully served their purpose, use the standard temporary package life cycle to remove the components from the override libraries and set the package status to TCC (temporary change complete).

If you cannot use a temporary package duration and the ChangeMan ZMF scheduler to automatically submit the CMN31 job to remove the package components from production override libraries, create your package with a MANUAL scheduler. The CMN31 job will be submitted with TYPRUN=HOLD when the package is installed, and you can release the job(s) manually when you want the temporary package components removed from production override libraries.