Skip to content

About Installation and Baseline Ripple

Package installation is a fully automated process executed by a series of batch jobs submitted by ChangeMan ZMF. The term "package installation" is used as a general term that includes two distinct processes:

  1. Production Installation - Components are copied to application production libraries after the old production versions are copied to production backup libraries. If no production libraries are defined for an application, no package components are copied. When production installation is successfully completed, the package status is changed to INS (installed)

  2. Baseline Ripple - All existing baseline versions of package components are copied over the next oldest version, and components in package libraries are copied to the level 0 baseline library. Baseline ripple is executed after package components are installed in production libraries at all sites specified in the package. When baseline ripple is successfully completed, the package status is changed to BAS (baselined)

The JCL for package installation jobs is created when a change package is frozen or when the package is approved, depending on how your administrator configures the application.

How the package installation process is initiated is determined by the Scheduler parameter chosen for your change package:

  • CMN - The first package installation job is submitted by the ChangeMan ZMF internal scheduler when it finds that the package Install Date/Time has arrived.

  • Other - The first package installation job is submitted by an external job scheduling system when it determines that the date, time, and dependencies of a job schedule are satisfied.

  • Manual - The first package installation job is submitted by ChangeMan ZMF when the last approval for the package is entered, regardless of the Install Date/Time specified in the change package information.

After the package installation process is initiated, the installation and baseline ripple jobs communicate success or failure with ChangeMan ZMF instances where the package was created and with other ZMF instances where the package is scheduled for production installation. Each successful job triggers the submission of the next batch job in the installation and baseline ripple series.