Skip to content

Installing a Release

Packages attached to a release are distributed when all release approvals are entered and the release status is changed to APR.

Each package attached to a release is installed according to the package Scheduler and Install Date/Time.

  • If the package scheduler is MANUAL, the package installation process is initiated immediately after the final release approval is entered.

  • If the package scheduler is CMN, the package is inserted into the ChangeMan ZMF scheduler, and the package installation process is initiated by the scheduler when the specified install date/time arrives.

  • If the package scheduler is OTHER, the CMN17 job is submitted after the last release approval is entered, and that job enters the first package install job into your external job scheduler.

Although release components are installed on a package-by-package basis, the components are copied from final release area libraries rather than from package staging libraries.

When a release package is installed successfully at a production instance, the package status is there is changed to INS. When all release packages are successfully installed at a production instance, the release status there is changed to BAS.

When a release package is installed successfully at all production instances, and the baseline ripple at the development is successful, the package status in the development instance is changed to BAS.

When all packages attached to a release are baselined successfully in the development instance, the release status in the development instance is changed to BAS.

CMNRMRLF                Release List            Release Reverted
Command ===>                                    Scroll ===> CSR

    Release Sta Install  Work request   Dept Aud    Creator Pkgs
    FIN6410 BAS 20160328 WR 9010        FINANCE     USER015 00001
    FIN6430 BAS 20160328 WR 9030        FINANCE     USER015 00003
******************************* Bottom of data *******************************