Skip to content

Requesting An Audit

You request an audit by filling in the information on the Audit Change Package (CMNAUDIT) panel and submitting the audit job. Your response to prompts on this panel determine the focus and scope of the audit.

Take the following steps to request an audit and generate an audit report:

  1. Select option 1 Build from the Primary Option Menu.

  2. Select option 7 Audit from the Build Options menu (CMNBUILD). The Audit Change Package panel (CMNAUDIT) is displayed.

CMNAUDIT                Audit Change Package
Command ===> __________________________________________

Package . . . . . . . . ACTP000081
Audit part. pkg . . . . (1-As simple,2-As primary,3-By Department)
Autoresolve parms . . . __________________________________________

Enter "/" to select option
__ Audit staging libraries only
/  Include history records
__ Format report for printing
__ Specify application              __ User variables
__ Suppress batch messages  
/  Include cross appl headings      __ Print top line only
__ Lock package                     __ Reset lock
__ Auto resolve
__ Update only this pkg rc
Job statement information:
//          CLASS=A,
//          NOTIFY=USER015,
//      MSGCLASS=X

Fields on this panel are:

Field Description
Command TRACE. Write diagnostic information to SYSPRINT DD at job step AD000.
Package The package that you want to audit (a simple package, a complex or super package, or a participating package).
Audit part. pkg The value of this field can be set only if the Package identifies a participating package. This field value affects the scope of the audit as follows:
**1- As Simple
Audit the specified participating package as a simple package. Only the staging and baseline libraries associated with this package are considered in the audit. If you select this, you must not select the Update Only this Pkg rc field.
2 - As Primary**
Audit the libraries of all participating packages in the audit, but reports out-of-sync conditions only in the target participating package and updates the audit return code for only the target participating package. The text Primary Package Processing appears in the header of each section of the audit report to indicate that you have requested that the target participating package be audited as a primary package.
3 - By Department**
Exclude the participating packages that have a department number that differs from the department number of the target participating package.
Autoresolve parms Fully qualified data set name for an optional file that contains audit auto resolve runtime parameters that are intended to provide the most efficient process for resolving out-of-synch conditions. The administrator may force the use of a standard data set with a ZMF exit program. See Auto Resolve Runtime Parameters.
Audit staging libraries only This field indicates whether you want to check for out-of-sync conditions in the package’s staging libraries only or in the staging and baseline libraries. If audit is required for your package before freeze, then it must be a full audit of staging and baseline libraries.
If not selected, then audit will check for out-of-sync conditions in both the staging and baseline libraries.
Select this with a / for audit to check for out-of-sync conditions only in the staging libraries. This option will automatically be enforced if the package being audited is attached to an ERO release.
Include history records This field allows you to include or exclude component history information in the audit report. Component history shows other packages that contain the staged component and may be helpful in resolving out-of-sync conditions.
If not selected then the audit will not display component history information when generating the audit report.
elect this with a / to extract component history for each staged component and display it in the audit report.
Format report for printing This field enables you to customize the appearance of the audit report:
If not selected, then the audit report will be formatted for browsing. The text starts in column one and blank lines separate the header and sections of the audit report.
Select this to format the audit report for printing. The first character is an ASA printer spacing control character that controls the vertical printer motion.
Specify application If not selected, then do not change the mix of applications that will be included in the audit by default. The applications included by default depend on the type of package being audited, and are as follows:
Only the application associated with a simple package or with a participating package that is being audited as a simple or primary package (1 - As simple or 2 - As primary).
The applications associated with all participating packages if the package being audited is a:
Complex or super package.
Participating package that is not being audited as a simple or primary package.
If selected then ChangeMan ZMF will bring up the Application Scope Selection List panel (CMNAUDAP) to select additional applications whose libraries you want to include in the audit. See Performing a Cross-Application Audit for a description of this panel.
User Variables Enter '/' to specify user variables V01 through V10 on panel CMNUSV1 to pass information to skeleton file tailoring.
Suppress batch message Select to suppress the SEND message normally broadcast at the completion of the batch audit job that tells you whether your package passed or failed the audit.
Include cross appl headings If numerous application:libtype combinations share the same baseline library, this field enables you to specify the number of application:libtype combinations that are printed in the heading of an audit report section.
Select to list all appl:libtype combinations. Up to six appl:libtype combinations are printed on each line.
If not selected, then suppress all appl:libtype combinations.
Also select "Print top line only" to print only the first line of appl:libtype combinations.
For example, if the same baseline library is shared among 300 applications, then selecting this cross application headings field prints 50 lines of appl:libtype combinations in the heading of a report section. This field enables you to control the number of heading lines that are printed if a large number of appl:libtype lines are undesirable.
Lock package Select this to lock the package during audit to prevent users from acting on the package until the audit completes. For complex, super and participating packages, other participating packages being audited are also locked.
Reset lock Select this option to unlock a package that remains locked for audit when a previous audit job did not complete. For complex or super packages, all participating packages are unlocked. For other packages, only the requested package is unlocked. Note: When you select the Reset Lock field and press Enter, audit is not submitted. The package(s) will be unlocked and you will remain on the panel, and the field is cleared so that you may continue.
Auto resolve Normally audit will only report out-of-sync conditions but does not attempt to resolve them. Select this field to not only report out-of- sync conditions, but also to automatically submit restage, recompile and relink jobs to resolve SYNCH2, SYNCH4, SYNCH5, SYNCH7, SYNCH8, SYNCH9, SYNCH16, and SYNCH24 conditions.. See Using Audit Auto Resolve.
Update only this pkg rc Normally audit will update the return code for all participating packages that are included in the audit. If the Package is a complex or super package, the return code for the target package is also updated and is set to the highest return code issued for the participating packages. If you select this field then the audit will only update the return code for this package.
Job statement information These JOB statements are used when you press Enter to submit the audit job. Verify this information before you submit the job.