Skip to content

Administrative Parameters that Affect an Audit

Your ChangeMan ZMF administrator can set specific global and application parameters that affect an audit. These parameters include the:

  • Audit level.

  • Installation date for processing participating packages.

  • Department number.

  • The order in which the audit auto-resolve function submits stage, recompile, and relink jobs. This order is determined by the sequence number that is assigned to Like- Source and Like-Load libraries on the application Library Types (CMNCLLT0) panel (option A.A.2 from the ChangeMan ZMF Primary Option Menu).

  • The value of the SYSLIB EXCLUDE flag that is specified for Like-Copy promotion libraries.

Although you may not have access to the administrator options that allow you to set these parameters, the following sections summarize their effects on audit. Consult your application administrator for information about the audit rules that are in force for your application. Refer to the ChangeMan ZMF Administrator’s Guide for a complete explanation of these parameters and how to set them.

Audit Level

Your package must pass an audit before you can freeze it for promotion or installation. For your package to pass an audit, the audit return code cannot exceed the value that your application administrator specifies for the audit level:

Audit Level **Meaning
0 Audit is recommended but optional.
1 Audit is required. Any return code, except abend, is acceptable.
2 Audit is required and the return code cannot exceed 12. This return code indicates that there are out-of-sync conditions in the staging libraries of the package. Any out-of-sync conditions in baseline libraries are reported as well. The package passes the audit only if the return code is not higher than 12.
3 Audit is required and the return code cannot exceed 8. This return code indicates that there are no out-of-sync conditions in the staging libraries but that there are out-of-sync conditions in the baseline libraries. The package passes the audit only if the return code is not higher than 8.
4 Audit is required and the return code cannot exceed 4. This return code indicates that there are no out-of-sync conditions in the staging or baseline libraries, but at least one component in a staging library is a duplicate (unchanged) of the corresponding baseline component. The package passes the audit only if the return code is not higher than 4.
5 Audit is required and the return code cannot exceed 0. This return code indicates that there are no out-of-sync conditions in the staging or baseline libraries. Also, there are no duplicate (unmodified) components in the staging libraries. The package passes the audit only if the return code is not higher than zero. Some components that are unknown to ChangeMan ZMF, do not have ISPF statistics, or are unparsable load modules are flagged as out of sync but are allowed to pass the audit. Examples of components that are unknown to ChangeMan ZMF include language environment subroutines which the binder automatically links into a load module.

Processing Participating Packages by Installation Date

If your site plans software changes months ahead and installs packages regularly, your global administrator should set the Process Participating Packages by Install Date parameter on the Global Parameters panel (CMNGGP03) on. If this parameter is set to on, participating packages that are scheduled for installation earlier or simultaneously with the participating package that you want to audit are included in the audit report.

In this case, staging libraries are placed in descending order by installation date in concatenation lists. The compile and link-edit job procedures use these lists. Having staging libraries in descending order ensures that the latest copybooks and called load modules are included during staging and audit.

Presumably, participating packages with installation dates later than the package you want to audit are in early development stages. If these participating packages are included in the audit, they will generate invalid out-of-sync conditions. Setting the Process Participating Packages by Install Date parameter on will exclude packages with later installation dates from the audit.

Department Number

If you want to audit participating packages with the same department as a group, your application administrator should set the Require Department parameter on the Global Parameters panel (CMNGGP02) on. This setting requires the package creator to specify a department at the time a package is created.

Complex or super packages can have participating packages with different department values. If the application administrator sets the Require Department parameter on, you can request that an audit be restricted to participating packages that have the same department at the time you submit the audit request.

Sequence Number in Library Type Definitions

The following items determine the order in which the audit auto-resolve function submits jobs:

  • The sequence number that is assigned to the Like-Source libraries that are defined for your application determines the order in which staging and recompile jobs are submitted.

  • The sequence number that is assigned to the Like-Load libraries that are defined for your application determines the order in which relink jobs are submitted.

The sequence numbers that are assigned to Like-Copy library types have no effect on the audit auto-resolve function.

Syslib exclude Field

The application administrator can set the Syslib exclude field on the application Promotion Libraries (CMNLRPM3) panel in application administration (option A.A.7 from the ChangeMan ZMF Primary Option Menu). If the value of this field is set to Y for a Like- Copy promotion library, that library is excluded from audit processing. See the ChangeMan ZMF Administrator’s Guide for more information about this field.