Audit Report Contents
An audit report contains several sections. The number of sections and their contents depend on the types of components represented in the package or packages that are audited and the parameters you specify on the Audit Change Package (CMNAUDIT) panel when you request the audit.
An audit report can contain the following sections:
| Report Section | Description |
|---|---|
| Description of Member from Library Directory Entry | Lists package components for each application:library type. Each application:library type that is represented in the package or packages being audited has its own section. |
| History of Changes for Audited Components | Lists the history of each component of an application:library type. Each application:library type that is represented in the package or packages being audited has its own section. These report sections are generated only if you respond YES to the Include History Records prompt on the Audit Change Package panel (CMNAUDIT). |
| Copybooks Found within Source Code | Lists copybook members that source programs and other copybooks reference. Each like-copy and like-source application:library type that is represented in the package or packages being audited has its own section. |
| Static Subroutines Called within Load Members | Lists the statically link-edited subprograms that each composite load module calls. Each like-load application:library type that is represented in the package has its own section. |
| Legend and Summary Report | Shows how many occurrences of each out-of-sync condition are flagged in the audit report. |
| Recommendation Summary | Contains recommendations for fixing each out-of-sync condition. |
An example of each audit report section follows.
Note
The package audit report shown in this topic is run with these settings both selected:
-
Include history records
-
Include cross appl headings
Section Header
A header introduces each section of the audit report. The header identifies the contents of each report section and includes information such as the following:
-
Banner that identifies the ChangeMan ZMF version, the date and time that the audit report was run, and the page number.
-
Type of package being audited (simple, participating, complex/super), package name, package create date and time, and the TSO userid of the package creator.
-
The number of participating packages (for a complex or super package) and the package status.
-
The scheduled installation date (for a simple or participating package).
-
The type of component analysis information that appears in the body of this report section.
-
The application:library type of the components represented in this report section. You can control the number of application:library type lines that are printed with the value that you specify for the Include Cross Appl Headings field on the Audit Change Package (CMNAUDIT) panel. See Requesting An Audit for a description of this field.
Here’s a sample section header from an audit report:
ChangeMan(R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 15:30:05 Page 1
************************************************************************************************
* Simple Change Package ===> ACTP000081 Created 2017/11/22 at 18:43:44 by USER015 *
* Package Installation Date ===> 2018/06/06 Package Status: DEV *
* Component Analysis Type ===> Description of member from library directory entry *
* Library Appl:Libtype ===> ACTP:CPY ACTR:CPY *
...
Description of Member from Library Directory Entry
This section lists the components for each application:library type represented in the package or packages being audited. The ISPF directory entry for the library provides the information. The report section has two parts:
-
The left side of the report with the heading Baseline contains ISPF statistics about the baselined version of the components of the target application:library type. If a component was not checked out from a baseline library, the baseline information for the component is blank.
-
The right side of the report with the heading Staging contains ISPF statistics about the version of the components in the staging library associated with the component type.
The following excerpt shows the start of a sample report section that lists the components of the CPY library type for the ACTP and ACTR applications.
ChangeMan(R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 15:30:05 Page 6
****************************************************************************************************
* Simple Change Package ===> ACTP000081 Created 2017/11/22 at 18:43:44 by USER015 *
* Package Installation Date ===> 2018/06/06 Package Status: DEV *
* Component Analysis Type ===> Copybooks found within Source code *
* Source Appl:Libtype ===> ACTP:SRC ACTR:SRC *
************************************************************************************************************************************
*--------------------- B a s e l i n e ---------------------* *---------------------- S t a g i n g ----------------------*
************************************************************* *************************************************************
Copybook Source Copybook
Name VV.MM Created Changed Size Init Tso-id Name Name VV.MM Created Changed Size Init Tso-id
________ _____ __________ ________________ ____ ____ ________ ________ ________ _____ __________ ________________ ____ ____ ________
01.03 2002/05/07 2015/01/05 00:44 34 23 USER015 ACPSRCCA 02.00 2017/12/13 2017/12/13 15:17 34 34 USER015
ACPCPYCA 02.00 2002/05/07 2014/12/12 01:02 3 1 USER015
ACPCPYCB 02.00 2002/05/07 2014/12/12 01:02 3 1 USER015
ACPCPY00 02.00 2002/05/07 2014/12/12 01:02 4 1 USER015
COMCPY00 --------- Not found or unknown ------- SYNCH0!
As another example, the following excerpt shows a report section that lists the staged components of the LOD library type for the ACTP and ACTR applications.
ChangeMan(R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 15:30:05 Page 2
************************************************************************************************
*Simple Change Package ===> ACTP000081 Created 2017/11/22 at 18:43:44 by USER015 *
*Package Installation Date ===> 2018/06/06 Package Status: DEV *
*Component Analysis Type ===> Description of member from library directory entry *
*Library Appl:Libtype ===> ACTP:LOD ACTR:LOD *
************************************************************************************************************************************
*--------------------- B a s e l i n e ---------------------* *---------------------- S t a g i n g ----------------------*
************************************************************* *************************************************************
Name Size Linkdate Alias-of AC Attr Setssi Name Size Linkdate Alias-of AC Attr Setssi
________ ________ __________ ________ __ ____ ________ ________ ________ __________ ________ __ ____ ________
ACPSRCCA 00001510 2015/01/05 00 C2E2 6779D60D ACPSRCCA 00001538 2017/12/13 00 C2E2 6D013C27
CTST 00001088 2017/11/26 00 C2E2 6CEB2ED4
Refer to Audit Report Field Descriptions for a description of the fields in the Baseline and Staging sections of the report.
History of Changes for Audited Components
These report sections provide historical information about the components of each application:library type that is represented in the package or packages being audited. Here’s the start of a sample history report section for the LOD library type. It shows the packages in which the target component appears:
ChangeMan(R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 16:39:56 Page 4
**************************************************************************************
*Simple Change Package ===> ACTP000081 Created 2017/11/22 at 18:43:44 by USER015 *
*Package Installation Date ===> 2018/06/06 Package Status: DEV *
*Component Analysis Type ===> History of changes for audited components *
**************************************************************************************
*------------------ C o m p o n e n t H i s t o r y - LOD -----------------*
*******************************************************************************
Name VV.MM Changed Tso-id Package Status
________ _____ ___________________ ________ __________ ______
ACPSRCCA 01.03 2014/11/19 03:14 USER015 ACTP000001 BAS
ACPSRCCA 01.00 2015/01/05 00:45 USER015 ACTP000003 BAS
ACPSRCCA 01.00 2015/01/04 22:52 USER015 ACTP000020 BAS
ACPSRCCA 01.01 2016/01/20 20:37 USER015 ACTP000060 DEV
ACPSRCCA 01.00 2017/12/13 15:18 USER015 ACTP000081 DEV
CTST 01.00 2017/11/26 21:51 USER015 ACTP000081 DEV
...
Refer to Audit Report Field Descriptions for a description of the fields in the component history sections of the report.
Note
To display this report section, you must select field Include history records on the Audit Change Package panel (CMNAUDIT).
Copybooks Found within Source Code
This report section lists copybook members that source programs and other copybooks reference. Each like-copy and like-source application:library type that is represented in the package or packages being audited has its own section.
The report provides baseline information (on the left side) and staging information (on the right side) about each copybook member. The component name (from a like-copy or like- source library type) that references the associated copybook member appears in Source Name column in the middle of the report between the Baseline and Staging sections. Any out-of-sync conditions that are flagged for the listed components also appear in the Source Name column.
The component is new to ChangeMan ZMF if no baseline information is shown for it. If no Staging information is shown, the component resides only in the baseline library and has not been staged in the package or packages being audited.
Here’s a sample Copybooks Found within Source Code report section. The excerpt shows an audit of a simple package (ACTP000081).
Typically, you stage only those copybooks that you want to change. (That is, there is no reason to stage a copybook unless you intend to change it.) Three out-of-sync conditions are flagged in this example (SYNCH5! - cpy/hdr baseline problem).
Changeman R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 17:24:57 Page 11
*******************************************************************************************************
*Simple Change Package ===> ACTP000081 Created 2017/11/22 at 18:43:44 by USER015 *
*Package Installation Date ===> 2018/06/06 Package Status: DEV *
*Component Analysis Type ===> Copybooks found within Source code *
*Source Appl:Libtype ===> ACTP:SRS ACTR:SRS *
************************************************************************************************************************************
*--------------------- B a s e l i n e ---------------------* *---------------------- S t a g i n g ----------------------*
************************************************************* *************************************************************
Copybook Source Copybook
Name VV.MM Created Changed Size Init Tso-id Name Name VV.MM Created Changed Size Init Tso-id
________ _____ __________ ________________ ____ ____ ________ ________ ________ _____ __________ ________________ ____ ____ ________
01.02 2014/12/18 2014/12/18 02:10 23 19 USER015 ACPSRS00
ACPCPY00 02.00 2002/05/07 2014/12/12 01:02 4 1 USER015 SYNCH5! ACPCPY00 03.01 2017/12/13 2017/12/13 17:24 4 5 USER015
01.02 2014/12/18 2014/12/18 02:11 26 22 USER015 ACPSRS1B
ACPCPY00 02.00 2002/05/07 2014/12/12 01:02 4 1 USER015 SYNCH5! ACPCPY00 03.01 2017/12/13 2017/12/13 17:24 4 5 USER015
ACPCPY1B 02.00 2002/05/07 2014/12/12 01:03 4 1 USER015
ACPCPY1C 02.00 2002/05/07 2014/12/12 01:03 4 1 USER015
01.01 2014/12/18 2014/12/18 01:28 21 21 USER015 ACPSRS1C
ACPCPY00 02.00 2002/05/07 2014/12/12 01:02 4 1 USER015 SYNCH5! ACPCPY00 03.01 2017/12/13 2017/12/13 17:24 4 5 USER015
ACPCPY1C 02.00 2002/05/07 2014/12/12 01:03 4 1 USER015
Refer to Audit Report Field Descriptions for a description of the fields in the Baseline and Staging sections of the report.
Static Subroutines Called within Load Members
These report sections list all composite load modules and the statically linked subroutines that they call for each application included in the audit report. Each application:like-load library type has its own report section.
The report shows information from the Baseline library (on the left side) and information from the package Staging library (on the right side). The calling composite load module name and flagged out-of-sync conditions appear in the middle of the report under the Calling Module column.
A load module is new to ChangeMan ZMF if Staging information but no Baseline information is shown for it. If no Staging information is associated with a module, the module resides in the baseline library but has not been staged into the package.
Here’s a sample report section for Static Subroutines Called within Load Members. The following information is shown in the excerpt:
-
One composite load module named ACPSRCCA of the LOD library type for the ACTP application is shown in the report.
-
ACPSRCCA calls several statically linked subroutines. None of the subroutines have been staged from baseline into the staging library associated with package ACTP000025.
Note
The modules whose names begin with the letters CEE and IGZ identify Language Environment routines that the binder automatically links into a module. They are flagged with the SYNCH0! condition code, which means that they have not been defined to ChangeMan ZMF. You can ignore such modules for application purposes. (You can suppress SYNCH0! condition codes from audit reports with a user exit. User Exits that Affect a Package Audit
ChangeMan(R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 17:24:57 Page 12
**************************************************************************************
*Simple Change Package ===> ACTP000081 Created 2017/11/22 at 18:43:44 by USER015 *
*Package Installation Date ===> 2018/06/06 Package Status: DEV *
*Component Analysis Type ===> Static subroutines called within Load members *
*Load member Appl:Libtype ===> ACTP:LOD ACTR:LOD *
**************************************************************************************
*--------- B a s e l i n e ---------* *---------- S t a g i n g ---------- *
************************************* *************************************
Called Module Calling Called Module
Module Size Linkdate Setssi Module Module Size Linkdate Setssi
________ ________ __________ ________ ________ ________ ________ __________ ________
00001510 2015/01/05 6779D60D ACPSRCCA 00001538 2017/12/13 6D013C27
ACPSRS00 00000458 2014/12/18 67622F30
CEEARLU -- Not found or unknown SYNCH0!
CEEBETBL -- Not found or unknown SYNCH0!
CEEBINT -- Not found or unknown SYNCH0!
CEEBLLST -- Not found or unknown SYNCH0!
CEEBPIRA -- Not found or unknown SYNCH0!
CEEBPUBT -- Not found or unknown SYNCH0!
CEEBTRM -- Not found or unknown SYNCH0!
CEECPYRT -- Not found or unknown SYNCH0!
CEESG005 -- Not found or unknown SYNCH0!
CEESTART -- Not found or unknown SYNCH0!
IGZCBSO -- Not found or unknown SYNCH0
Refer to Audit Report Field Descriptions for a description of the fields in the Baseline and Staging sections of the report.
Legend and Summary Report
The Legend and Summary Report section of the audit report provides the following information:
-
The audit level that the application administrator has defined for the application (0, 1, 2, 3, 4, or 5). If you are auditing a complex package that contains components from different applications, the more restrictive audit level is used if the administrator has defined different audit levels for the applications.
-
The text description associated with the audit level that is defined.
-
A message that indicates if the package passed or failed the audit and the highest audit return code that was encountered for each package included in the audit.
-
The number of occurrences of each out-of-sync condition.
-
A message indicating whether each change package included in the audit passed or failed the audit and the highest return code issued for each package. A complex package is assigned the highest return code that is issued to its participating packages.
If you are auditing a participating package and have selected any of the following prompts on the Audit Change Package (CMNAUDIT) panel, only the audit return code for the target participating package is updated:
-
Audit Part. Pkg : 1 - as simple
-
Audit Part. Pkg : 2 - as primary
-
Update only this pkg rc
The following illustration shows a sample Legend and Summary Report section of the audit. Audit level 4 is in effect for the audit. The audit encountered the following conditions: 1 DUPLIC!, 24 SYNCH0!, 1 SYNCH4!, 7 SYNCH5!, 3 SYNCH14! and 2 SYNCH22.
ChangeMan(R) ZMF (8.1.4 - 20170707) Audit WEDNESDAY DECEMBER 13, 2017 (2017/347) 17:24:57 Page 13
Legend and Summary Report
The local level of audit chosen at this point; 4
4 - Audit is required and the return code must not exceed 4 which implies
that there are no "out-of-synch" situations within the staging libraries
nor the baseline libraries but at least one module of a staging library
is a "duplicate" of its baseline counterpart
Out-of-synch messages (hint - search for "!" marks)
DUPLIC! (Staging duplicates baseline) ===> 1
SYNCH0! (Not in scope of audit or unknown) ===> 24
SYNCH1! (Cmpnt statistics not available) ===> 0
SYNCH2! (Compile/designated proc differ) ===> 0
SYNCH3! (Unparsable load module) ===> 0
SYNCH4! (cpy/hdr staging problem) ===> 1
SYNCH5! (cpy/hdr baseline problem) ===> 7
SYNCH6! (Activity file not checked out) ===> 0
SYNCH7! (Static subcomponent stage problem) ==> 0
SYNCH8! (Static subcomponent base problem) ===> 0
SYNCH9! (Source and load discrepancy) ===> 0
SYNCH10! (Version regression problem) ===> 0
SYNCH11! (Component hash discrepancy) ===> 0
SYNCH12! (Orphan module in staging) ===> 0
SYNCH13! (Baseline/staging discrepancy) ===> 0
SYNCH14! (Components not in active status) ===> 3
SYNCH15! (Source to relationship problem) ===> 0
SYNCH16! (CPY low-date problem in baseline) ===> 0
SYNCH17! (CPY deleted problem in staging) ===> 0
SYNCH18! (LOD deleted problem in staging) ===> 0
SYNCH19! (Missing module in staging) ===> 0
SYNCH20! (Inconsistent subroutine) ===> 0
SYNCH21! (Scr/rename pkg component) ===> 0
SYNCH22! (Scratch subcmpnt is in use) ===> 2
SYNCH23! (Rename subcmpnt is in use) ===> 0
SYNCH24! (LOD low-date problem in baseline) ===> 0
SYNCH25! (LCT high-date problem in package) ===> 4
SYNCH26! (LCT -> missing executable) ===> 1
SYNCH27! (Missing LCT for executable) ===> 1
SYNCH28! (Same component in multiple ppkgs) ===> 8
Highest return code encountered ===> 12
CMN3060A - This package has failed the audit.
CMN2696I - PACKAGE ACTP000081 FAILED THE AUDIT WITH A RETURN CODE OF 12.
- The highest return code encountered for any package that was included in the audit is 12.
Recommendation Summary Report
The Recommendation Summary Report section of the audit report:
-
Identifies the out-of-sync conditions that have been flagged in the audit report.
-
Provides a brief explanation of how to correct them.
Identifies the highest return code issued for this audit report (RC=00, in this example).
Recommendation Summary Report
Listed below are some solutions to resolving out of synch situations
that can be flagged within this audit report.
DUPLIC! (Staging duplicates baseline)
Delete component from staging or change contents of staging component.
For package in BAS status, indicates no changes in baseline since pkg installed - no action required.
SYNCH0! (Not found within scope of this Audit)
The component is either unknown to ChangeMan ZMF or not found within the
criteria set for this audit. Check if component resides in an application
or package excluded from the scope of this audit.
To register an unknown component to ChangeMan ZMF stage it into a package.
SYNCH4! (cpy/hdr staging problem)
Stage source component to include copybooks/header files from the staging libraries.
SYNCH5! (cpy/hdr baseline problem)
Recompile source component from baseline to include copybooks/header files residing in the staging libraries.
SYNCH14! (Components not in active status)
Re-stage component to activate
SYNCH22! (Scratch subcmpnt is in use)
The sub-component to be scratched is in use by the indicated top-level component.
Remove the reference to the sub-component or remove the scratch request.
CMN7540I - End of job; RC = 12
If the package does not pass the audit, you cannot freeze it for approval, promotion, or installation. For the package to pass the audit, the audit return code must be consistent with the audit level set by your application administrator See Audit Level.