ChangeMan ZMF Plugin → Using the ChangeMan ZMF Plugin → Configuring Tasks for ChangeMan ZMF Change Packages → Auditing ChangeMan ZMF Change Packages
Package Audit detects problems that will occur in production if you install your package now in its current condition. Audit detects synchronization problems in relationships between components in your change package and synchronization problems between package components, components in participating packages, components in promotion, and baseline components. Each ChangeMan ZMF application is defined with Audit Level, which dictates the audit level which must be passed before the ChangeMan ZMF change package can be frozen and continue through the lifecycle.
To configure an audit 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: 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> |
Applications | Select additional applications if necessary;
by default the change package will be audited within the scope of its own
application.
Note: This is the equivalent of setting the SPECIFY APPLICATION
SCOPE option to YES in
ChangeMan ZMF
in the AUDIT CHANGE PACKAGE screen and subsequently selecting applications.
|
<select applications> |
Comment | Enter a comment.
Note: This field is required when initiating the audit action
from
Release Control
because the text is used to view the audit information in the
Release Control
user interface. This field is not typically required for an audit configured in
ChangeMan ZMF
on z/OS.
|
Audit 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:
|
Copyright © 2012–2017 Serena Software, Inc. All rights reserved.