ChangeMan ZMF Plugin → Using the ChangeMan ZMF Plugin → Configuring Tasks for ChangeMan ZMF Change Packages

Configuring Tasks for ChangeMan ZMF Change Packages

After the ChangeMan ZMF Actions plugin configuration has been added or updated as needed, you can set up a set of ordered deployment tasks to complete the set of ChangeMan ZMF actions needed to deploy through the environments.

To add a ChangeMan ZMF deployment task, use the ChangeMan ZMF Actions configuration. Typically, to use the ChangeMan ZMF Actions configuration, in the Deployment Tasks tab, do the following:

  1. Click Edit Deployment Tasks.
  2. Click the + icon to add a task.
  3. Select the ChangeMan ZMF Actions configuration.
  4. In the resulting form, select an action.

    Details for each action are described in subsequent topics. Before continuing to the details of each action, you should read the following topics:

Deployment Task Order

Example Task List

Example Tasks If Testing Fails

Available Actions

Deployment Task Order

The order in which you set up the deployment tasks is very important for ChangeMan ZMF actions. The actions you can perform are determined by your ChangeMan ZMF implementation's rules, and actions that you can perform for each environment depend on what makes sense for that environment. You must be very familiar with your implementation of ChangeMan ZMF and use the same order of actions as you would use if you were entering ChangeMan ZMF commands in ISPF or running batch jobs to achieve the same result.

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

Example Task List

An example set of ChangeMan ZMF deployment tasks is as follows and shown in the subsequent figure.

  1. audit
  2. promote to dev
  3. approve test
  4. promote in test
  5. approve for prod

Example Tasks If Testing Fails

All active deployment tasks you add are executed; they are not conditionally executed. Therefore, if you need to reject and revert based on a failure, you'll need to activate or create additional deployment tasks at the time they are needed and inactivate any tasks in the list that should no longer be executed.
Tip: To inactivate a deployment task, edit the deployment tasks and beside the task, click an active environment name icon to gray it out. This inactivates it for that environment.

The positive path is shown in the preceding example. For other actions, such as reject, revert, and so on, you must set up tasks as needed. For example, if "promote in test" was successful but testing failed when QA tested the z/OS application changes that the ChangeMan ZMF change package contained, other deployment tasks must be set up to get the environment back to the condition necessary to continue the release testing. That may be to reject it, revert the environment back to how it was before, or whatever the release process you follow for z/OS requires.

The deployment tasks that need to be set up depend on the promotion rule set for the application. If the promotion rule is set to “4”, then the following tasks must be created and executed in the same environment where the package was last promoted.

Here are steps:

  1. Fail the deployment task
  2. Return it back to construction
  3. Create a demote from dev task
  4. Create a revert task
  5. Start the deployment to execute the demotion and revert deployment tasks
  6. Fix the code
  7. Re-execute the audit and promote to dev task

See Promotion and Demotion Rules.

Tip: You can set up template tasks ahead of time and copy them in at run time if they are needed.

Available Actions

See the following topics for details on the ChangeMan ZMF actions available to select in deployment tasks:

Copyright © 2012–2017 Serena Software, Inc. All rights reserved.