Backing Out ChangeMan ZMF Change Packages

ChangeMan ZMF has comprehensive backout management facilities. In addition to source components, the prior functioning executable components are backed up. If a backout becomes necessary, ChangeMan ZMF automatically restores these executable components to production. ChangeMan ZMF also performs all necessary DB2 Plan rebinding automatically. Because ChangeMan ZMF is package driven, it backs out all the components of a change automatically, including components that have been scratched.

When selecting a remote production site in a backout task, check that the ZMF system is configured properly for remote backout (the remote host and port specified for the selected Site Name in the Global Administration Options). Otherwise, this error is displayed during deployment: Undefined site ip address. Contact global admin

For correct Task Execution results, check the time is synchronized between the ZMF Server, ZMF Connector, and RLC server. Also check that the correct ZMF server time zone is specified in the Base Provider Configuration.

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

Create or edit a task and select the Backout action.

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: Use available items: Select change packages that have already been added. Use available configurations: Search for existing change packages or create new ones. This uses Dimensions CM Change Package Item configurations. See Associating Change Packages with Deployment Units and Creating Change Packages.	<select a change package>
Site	Select a site. If no site is selected a backout is performed on the current site (the port ID is from the provider configuration).	Onsite
Comment	A comment is required for backout
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 Test>
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