Freezing ChangeMan ZMF Change Packages

Freeze Package locks package information and package components to prevent further changes and to ensure that the components you install into production are the same as the components you tested. You can unfreeze, change, audit, and refreeze change packages to fix problems found in testing.

Note: Only change package-level freeze and unfreeze are supported through the default version of the plugin; component-level freeze and unfreeze, also known as selective freeze and unfreeze, are not supported.

To configure a freeze change package action in a deployment task:

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

Some of the fields are described in the following table.

Field Description Example Values
Package Name

Click the link icon to select a change package. From here, you can:

<select a change package>
Comment Enter a comment.
Note: This field is required when initiating the freeze action from Release Control because the text is used to view the freeze information in the Release Control user interface. This field is not typically required for a freeze configured in ChangeMan ZMF on z/OS.
Freeze in Dev
Environment Select each environment in which you want to execute the task. These are the environments configured in the deployment path. For example, Dev, Test, and Prod. <select Dev>
Schedule Options

For each selected environment, select the schedule option and fill out the additional fields that open based on your selection. Options include the following:

  • None
  • Specific Time
  • Opportunity Window
  • Time Window
  • Delay
  • Hold Until Released
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