Approving ChangeMan ZMF Change Packages to PROD

You can approve ChangeMan ZMF change packages to production, the final approval for distribution and installation, through deployment tasks.

Distribute Package starts automatically when all required package approvals are received for a package that is scheduled for install at a remote site. The package is transmitted to the remote site, where package records are added to a ChangeMan ZMF P instance running there. Package staging libraries are transferred, and then the package is added to the P instance internal scheduler.

Install Package starts automatically, either when the package install date and time arrive, or when the last approval is entered, depending on the Install Job Scheduler defined for the package. If the application has production libraries that are separate from baseline libraries, current production modules are backed up and new versions are copied from package staging libraries into the production libraries. The final step of the Install process will baseline the package components and change the package status to baseline (BAS).

For detailed information on the use of ChangeMan ZMF, see the ChangeMan ZMF User's Guide.

Note: The ChangeMan ZMF install is dependent on the scheduler chosen for the change package. It will be time dependent or immediate, depending on the scheduler chosen.

To configure an approve change package to production action in a deployment task:

In the UI, point to each field for additional information.

The fields are the same as those described in Approving ChangeMan ZMF Change Packages.

Note: After you create the deployment task, if you have not linked a change package, the task appears in the list in red, and you must then associate the related change package with the deployment task.

Related Topics

Related Topics

Linking Change Packages to Deployment Tasks

Creating Change Packages