The audit report that you generate depends on the parameters and options that you select on the Audit Change Man panel For each library type, the audit report provides information about each component in the baseline and staging libraries, their corresponding ISPF statistics, and out-ofsynch conditions. According to your selected parameters and options, your audit Change Management Page 1 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
report may contain one or all of the following reports (section) each beginning with a report header: Staged component by library type (editable components and load module) Source-to-copy relationship (copybooks members within source code) Load-to-load relationship (statically link-edited called subroutines within composite load modules)
Component history Also, the audit report ends with the following summary reports: Legend and Summary of flagged out-of-synch conditions Recommendation Summary REPORT HEADER
Each report (section), with the exception of the summary sections, contains a header that provides the version of Change Man at your site. Also, the report contains the generated date and time, the package level, the package ID, the installation date of the package, status of the package, department number of the requested package, and component analysis type or report type. For example, the following illustration is a sample of a report header of a staged components by library type report of a simple package (SB04000086).
Change Management
Page 2 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
REPORT BODY
The body of the report displays a section for each component library type associated with the package. The components appear with its ISPF statistics in the baseline (on the left side of the body), and the staging libraries for checkup and comparison appear on the right side.
Change Management
Page 3 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
NOTES Out-of-synch conditions are displayed between the baseline and staging areas. Also, the following illustration contains information for load modules (LOD and like- LOD library types). The following table describes the fields of the Staged Components by Library Type section of the audit report. Column Name Name VV.MM Description The name of the component. The version and modification number for the component following the IBM standards (mm starts at 01, increments to 99; vv starts at 01, increments to 99, and recycles to 01). The first time the component is processed by Change Page 4 of 22
Change Management
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Man the vv.mm is 01.01. Each successive stage request (within the same change package) increments the mm portion (for example, 01.02, 01.03). The next package using the component causes the vv portion to be incremented (02.01). If an existing library is added to Change Man the vv.mm is not reset. The date (yyyy/mm/dd) that the component was first included in the Change Man system. The date (yyyy/mm/dd) of the most recent change to the component residing in current production (on the staging side of the report this would be the most recent staged date). The number of lines of text data. The size of the component when first created (version 01.01). The TSO identification of the person responsible for this component's version and modification (vv.mm). The name of the participating package where the component resides. The department number field, which is filled in when a new package is created from the Package Create panel. For a load module, this is the link-edit date of the component in the baseline and staging libraries. For a load module, this field indicates that the module is an alias of a specific module. Page 5 of 22
Created Changed
Package Dept
Linkdate Alias-of
Change Management
ChangeMan
CHANGEMAN AUDIT FUNCTION:
AC
For a load module, the authorization code (usually 00). For a load module, this field displays the attributes. For a load module, a timestamp set by Change Man or extracted from a vendor module.
Attr Setssi
Change Management
Page 6 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Change Management
Page 8 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
The following illustration is an example of the Legend and Summary section of the Audit Report.
Change Management
Page 9 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Audit success or failure shows in the 'Audit Pass' line on the last page of the audit report. Generally, If the package does not pass the audit, you cannot be freeze it for promotion or installation. For the package to pass the audit, the audit return code should correspond to the audit level set by your application administrator i.e 4 Note : There may be some unknown components to Change Man components. Some components might lack ISPF statistics or be unparsable load modules for which not all the audit checks can be done.
Change Management
Page 10 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
OUT-OF-SYNCH CONDITIONS
Audit detects and reports out-of-synch conditions between the components of an audit Package, baseline components, and other components that are called in the primary Package components. Each out-of-synch condition sets an appropriate return code based on its impact on the integrity of the audited change package.
Return Codes:
Return Code 0 4 8 Description No out-of-synch conditions were found in your package. No user action is required. Some out-of-synch conditions were found, but the conditions are very minor and are usually informational. Typically, no user action is required. Some out-of-synch conditions were found, and the conditions must be reviewed and possibly corrected. These out-of-synch conditions are SYNCH5, SYNCH8, and SYNCH16. User action is required prior to freezing the package. Some out-of-synch conditions were found, and the conditions must be reviewed and corrected. All out-of-synch conditions are affected, except SYNCH0, SYNCH5, SYNCH8, and SYNCH16. User action is required prior to freezing the package
12
This section describes the out-of-synch condition messages you can receive during your audit and gives the corresponding return code for each message.
Change Management
Page 11 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Return Code
Description Delete the duplicate component from the change package or change the contents of the staged component.
Return Code
Description
No action required.
Change Management
Page 12 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Return Code 0
Description Ignore if the component resides in another participating package excluded from this audit due to installation date. If the component exists in the baseline library, run the Conversion Assistance to select new relationships.
Return Code
Description
Return Code
Description
Change Management
Page 13 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
12
Return Code
Description
Check the load module, it might be corrupted. Also, stage, relink, or recompile the corresponding source component.
Return Code 12
Description Stage the source component to include the update copybook staging libraries. Alternatively, set the Auto-Resolve option to YES and resubmit the audit.
ChangeMan
CHANGEMAN AUDIT FUNCTION:
When a copybook is staged, source components that are not staged and called the copybook receive outof-synch condition because they are compiled with a previous versions of the copybook. An updated staged copybook may be nested in another copybook called in the baseline source component.
Return Code 8
Description Recompile the source component from the baseline to include copybooks residing in the staging libraries.
Return Code
Description
12
Check out and stage the associated activity file for the component.
Return Code
Description
Change Management
Page 15 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
12
Relink the calling load module to include the called load module in the staging libraries. Alternatively, set the Auto-Resolve option to YES and re-submit the audit.
Return Code 8
Description Relink the calling load module from baseline to include the called load module in the staging libraries.
Return Code 12
ChangeMan
CHANGEMAN AUDIT FUNCTION:
You have checked out a component to more than one change package. At the time of the audit of the other packages, one of the packages has been installed. Therefore, current changes to the component are invalid, because the changes were made to the previous baseline and not to the newly baseline version. To avoid version regression due to concurrent development, you must merge changes in the new baseline version with the changes in the staged component.
Return Code 12
Description Copy the staged component to a development library. Check out component from baseline to obtain the latest version. Apply your changes to the latest version and stage the component.
Return Code
Description
12
Change Management
Page 17 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Return Code 12
Return Code 12
Description Check out the most current component from the baseline, apply changes, and stage the component. If a load module in the staging library has been created by recompiling a source component from the baseline, recompile the source component from the baseline again to obtain the most current version.
Return Code
Description
Change Management
Page 18 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
12
Return Code
Description
12
Re-stage the source component to obtain the current COPY or LCT relationship. Alternatively, set the Auto-Resolve option to YES and resubmit the audit.
Change Management
Page 19 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
changed. Therefore, the source-to-copybook relationship is out-of-synch. A Synch16! also applies to conditions where a source component is recompiled from baseline into a package. It alerts the user to a recompiled source component residing in a package in motion where a copybook included from the previous recompile originated from baseline, and the corresponding copybook was installed from another package after the recompile date of the source. The conditions are as follows: There is a recompiled component in a package in motion and the included copybook does not reside in the staging library of the same package. The copybook resides in baseline. The activation date and time of the included copybook from the baseline library has a more current date and time than the recompile date and time of the corresponding source. The copybook hash token from baseline and the copybook hash token stored in the package master for the included copybook at the time of the last recompile are different.
Return Code 8
Description Recompile the source component from baseline to include the copybooks residing in the staging libraries
Change Management
Page 20 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
Return Code 12
Description Stage the missing called copybook and re-stage the source component. If the copybook is no longer needed, remove any reference to it from the source component, and re-stage the source component. If the copybook is no longer needed, and the source was recompiled from baseline,and at least one other copybook has to be included from any staging libraries,recompile the source from baseline to include the baseline version of the deleted copybook. If the copybook is no longer needed, and the source was recompiled from baseline,and there are no other copybooks to be included from any staging libraries, and there are no compile or link-edit attributes changes, delete the recompile source from the package.
Return Code 12
Description Stage the missing called load module in the composite load module, and relink the composite load module. If the called load module is no longer needed, remove any reference from the link-
Change Management
Page 21 of 22
ChangeMan
CHANGEMAN AUDIT FUNCTION:
edit control cards, and the source and re-stage the composite load module.
Change Management
Page 22 of 22