CHANGEMAN AUDIT FUNCTION:

ChangeMan

CHANGE MAN AUDIT FUNCTION:

The Change Man audit function allows you to ensure synchronization of components in an evolving package with baseline libraries and other participating packages.

Based on the package master and the impact analysis database, the audit function inspects the staging libraries of a package for out-of-synch conditions. Out-of-synch conditions could result from:

• copybooks being modified after compiling the source component that calls them

• load module being modified after the composite load component that calls themhas been link edited

• a package containing a load component that does not match its source component

Also, audit flags components of a package as out-of-synch for:

• not being active

• copied, but not staged

• a designated compile procedure was not used while staging a source component

THE AUDIT REPORT

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.

Change Management Page 1 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

According to your selected parameters and options, your auditreport 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 withincomposite 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 stagedcomponents by library type report of a simple package (SB04000086).

Change Management Page 2 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

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.

Section 1. Staged Components by Library Type

According to the library type, editable component or load module (load or like-load), the format of the report differs.

For example, the following illustration is a Stage Components by Library Type report for editable components (source code, copybooks, or JCL) report.

Change Management Page 3 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

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 LibraryType section of the audit report.

Column Name Description

Name The name of the component.

VV.MM 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

Change Management Page 4 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

time the component is processed by Change 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.

Created The date (yyyy/mm/dd) that the component was first included in the Change Man system.

Changed 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).

Size The number of lines of text data.

Init The size of the component when first created (version 01.01).

Tso-id The TSO identification of the person responsible for this component's version and modification (vv.mm).

Package The name of the participating package where the component resides.

Dept The department number field, which is filled in when a new package is created from the Package Create panel.

Linkdate For a load module, this is the link-edit date of the component in the baseline and staging libraries.

Alias-of For a load module, this field indicates that the

Change Management Page 5 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

module is an alias of a specific module.

AC For a load module, the authorization code (usually 00).

Attr For a load module, this field displays the attributes.

Setssi For a load module, a timestamp set by Change Man or extracted from a vendor module.

Section 2. Source to Copy Relationships Report

The Source to Copy Relationships report lists the copybooks called in sourcecomponents. Also, the report provides baseline information (on the left side) andstaging information (on the right side) about them. The source component name and flagged out-of-sync conditions appear in the middle of the report. All sourcecomponents in the audited package and baseline source components that call the changed copybooks appear on the report. If there is no baseline information for a component, then it is a new. If there is no staging information for a component, then it is not staged and resides in the baseline library.

Change Management Page 6 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Section 3. Load-to-Load Relationships Report

The Load-to-Load Relationships report contains the load modules called in composite load modules. Also, it provides baseline information (on the left side) and staging information (on the right side). The calling composite load module name and flagged out-of-synch conditions for the called load modules appear in the middle of the report.

This report contains all composite load modules staged in the audited package and those baseline load modules that call load modules changed in the audited package. If there is no baseline information for a load module, then it is a new. If

Change Management Page 7 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

there is no staging information for a load module, then it is not staged and resides in the baseline library.

Section 4. Legend and Summary

The Legend and Summary portion of the Audit Report provides the followinginformation:

• The level of the audit return code• The highest encountered return code• The number of encountered out-of-synch messages for each out-of-synchconditions

Change Management Page 8 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

• A message indicating whether the change package passed or failed its audit

The following illustration is an example of the Legend and Summary section of theAudit Report.

Section 5. Recommendation Summary Report

The Recommendation Summary Report section of the audit report providesrecommendations for resolving out-of-synch conditions detected in the audit package.

Change Management Page 9 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

For example, the following illustration of the Recommendation Summary sectionshows that the audit discovered SYNCH0, SYNCH1 as the out-ofsynchconditions.

Audit success or failure shows in the 'Audit Pass' line on the last page of the auditreport.

Generally, If the package does not pass the audit, you cannot be freeze it forpromotion 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

Change Management Page 10 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Note :

There may be some unknown components to Change Man components. Somecomponents might lack ISPF statistics or be unparsable load modules for which not all the audit checks can be done.

OUT-OF-SYNCH CONDITIONS

Audit detects and reports out-of-synch conditions between the components of an auditPackage, baseline components, and other components that are called in the primaryPackage components.

Each out-of-synch condition sets an appropriate return code based on its impact on theintegrity of the audited change package.

Return Codes:

Return Code Description

0 No out-of-synch conditions were found in your package. No useraction is required.

4 Some out-of-synch conditions were found, but the conditions arevery minor and are usually informational. Typically, no user actionis required.

8 Some out-of-synch conditions were found, and the conditions mustbe reviewed and possibly corrected.These out-of-synch conditions are SYNCH5, SYNCH8, andSYNCH16. User action is required prior to freezing the package.

12 Some out-of-synch conditions were found, and the conditions mustbe reviewed and corrected.All out-of-synch conditions are affected, except SYNCH0,SYNCH5, SYNCH8, and SYNCH16. User action is required priorto freezing the package

This section describes the out-of-synch condition messages you can receive duringyour audit and gives the corresponding return code for each message.

Change Management Page 11 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

DUPLIC! (Staging duplicates baseline)

Components that, after a line by line compare, show no difference between staging and baseline libraries cause this condition. At baseline ripple, this causes older versions of hat component to drop off prematurely.

Return Code Description

4 Delete the duplicate component from the change package or change the contents of the staged component.

! COPY! (Embedded copybooks)

Shows that there is a copy within a copy (an embedded copylink). This is an informational code indicating that a relationship exists.

Return Code Description

0 No action required.

SYNCH0! (Component unknown to Change Man)

If Change Man has no record of this component in the package master, and theComponent is calling another module and one (or more) of the following situationsexist, then SYNCH0! results:

Change Management Page 12 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

• The component does not exist in the baseline library

• The source-to-copy or load-to-load relationship does not exist in the ImpactAnalysis table.

• The relationship is found but the called or calling component does not exist in thebaseline library

Return Code Description

0 Ignore if the component resides in another participating packageexcluded from this audit due to installation date. If the component exists in the baseline library, run the Conversion Assistance to select new relationships.

SYNCH1! (ISPF statistics not available)

A component has no ISPF statistics. Therefore, some audit checks cannot beperformed for this component.

Return Code Description

0 Create or reset the ISPF statistics for the component.

SYNCH2! (Compile/designated procedure differ)

Change Management Page 13 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Source or like-source components in which the final compile was done without using the designated compile procedure (including designated compile options, link options, or user options)

Return Code Description

12 Recompile the component using the designated procedure.

SYNCH3! (Unparsable load module)

A load component whose IDRDATA records cannot be parsed and interpreted correctly.Therefore, some audit checks cannot be performed for the component.

Return Code Description

0 Check the load module, it might be corrupted. Also, stage, relink, or recompile the corresponding source component.

SYNCH4! (CPY problem in staging)

A copybook has been staged after the staging of the source component that calls the copybook. Therefore, the source has been compiled with a previous version of the copybook.

An updated staged copybook may be nested in another copybook called in the source copybook.

Change Management Page 14 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Return Code Description

12 Stage the source component to include the update copybook staging libraries. Alternatively, set the Auto-Resolve option to YES and resubmit the audit.

SYNCH5! (CPY high date problem in baseline)

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 Description

8 Recompile the source component from the baseline to includecopybooks residing in the staging libraries.

SYNCH6! (Activity file not checked out)

The component activity file (CAF) of a component has not been checked out, while the component has been staged.

Return Code Description

12 Check out and stage the associated activity file for the component.

Change Management Page 15 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

SYNCH7! (Called subroutine in staging)

After staging the composite load module that calls a specific load module, you have staged that load module. Therefore, an out-of-synch condition is present because a previous version of the called module is link-edited to the calling module.

Return Code Description

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.

SYNCH8! (Called subroutine in baseline)

When you stage a load module, all composite load modules that are not staged andcalled the staged load module become out-of-synch because a previous version of thesubroutine is link-edited with these load modules.

An updated staged subroutine may be link-edited in another load module called by thebaseline composite load module.

Return Code Description

8 Relink the calling load module from baseline to include the called load module in the staging libraries.

SYNCH9! (Source and load discrepancy)

Change Management Page 16 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

A source component and a corresponding load module in the staging libraries do notmatch. For example, when the load module is link-edited into the staging library,outside of Change Man, it replaces the load module from the staging of the sourcecomponent and creates a source and load module discrepancy.

Return Code Description

12 Stage the source component to create a new load module

SYNCH10! (Version regression problem)

You have checked out a component to more than one change package. At the time ofthe 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 theprevious baseline and not to the newly baseline version.

To avoid version regression due to concurrent development, you must merge changesin the new baseline version with the changes in the staged component.

Return Code Description

12 Copy the staged component to a development library. Check out component from baseline to obtain the latest version. Apply yourchanges to the latest version and stage the component.

SYNCH11! (Component hash discrepancy)

A components was staged, then edited or replaced in the staging library outside ofChange Man.

Change Management Page 17 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Return Code Description

12 Stage the component again.

SYNCH12! (Orphan module in staging)

Outside of Change Man, a component is copied into the staging library. Although thecomponent is in the baseline library and its relationships are recorded in the ImpactAnalysis table, it is not treated as a component in the staging library. Also, whenstaging a source component, the compile job abends and no load module is staged.Therefore, the source component is an orphan module.

Return Code Description

12 Delete the component from the staging library.

SYNCH13! (Baseline/staging discrepancy)

Based on the ISPF statistics of the baseline and staging libraries, an editable stagedcomponent has an earlier last modified date than its corresponding baselinecomponent. Therefore, the staged component is out-of-synch with the baseline library.

For load modules, the SETSSI of the staged and baseline components are compared and if the staged SETSSI is less than the baseline SETSSI, then the load module is flagged.

Return Code Description

Change Management Page 18 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

12 Check out the most current component from the baseline, applychanges, and stage the component.

If a load module in the staging library has been created by recompiling asource component from the baseline, recompile the source componentfrom the baseline again to obtain the most current version.

SYNCH14! (Component not in active status)

A component in the package is not in active status.

Return Code Description

12 To activate the component, re-stage it.

SYNCH15! (Source to copy relationship problem)

After a source component, which calls the contents of a copybook, was staged, thecontent of the copybook was changed. These conditions resulted in a out-of-synchcondition for the source component with the called copybook. Possible scenarios forthis condition follow:

• The copybook might have been included from the baseline, staging, or promotionlibraries based on the SYSLIB search for the source component compile job.

• The contents of the called copybook (found in either staging, promotion orbaseline library) has changed since the Source module was compiled.

• A new version of the copybook has been added to the SYSLIB search order forthat source component.

The Staging LCT member has a more current activation date than the correspondingsource member.

Change Management Page 19 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Return Code Description

12 Re-stage the source component to obtain the current COPY or LCTrelationship. Alternatively, set the Auto-Resolve option to YES and resubmit the audit.

SYNCH16! (CPY low-date problem in baseline)

The last modified date of a source component in baseline is after the last recompiledate or after a called copybook was last modified in staging library. A copybook waschanged in a package, which does not contain the source component that calls it. Thesource component has been baselined in another package after the copybook has beenchanged. Therefore, the source-to-copybook relationship is out-of-synch.

A Synch16! also applies to conditions where a source component is recompiled frombaseline into a package. It alerts the user to a recompiled source component residing ina package in motion where a copybook included from the previous recompileoriginated from baseline, and the corresponding copybook was installed from anotherpackage after the recompile date of the source. The conditions are as follows:

• There is a recompiled component in a package in motion and the includedcopybook does not reside in the staging library of the same package. Thecopybook resides in baseline.

• The activation date and time of the included copybook from the baseline libraryhas a more current date and time than the recompile date and time of thecorresponding source.

• The copybook hash token from baseline and the copybook hash token stored inthe package master for the included copybook at the time of the last recompile aredifferent.

Change Management Page 20 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

Return Code Description

8 Recompile the source component from baseline to include thecopybooks residing in the staging libraries

SYNCH17! (Copybook deleted problem in staging)

A new unknown to Change Man copybook is staged into a package, and a sourcecomponent that calls the unknown is also staged in the same package or a participatingpackage. When the copybook is deleted, changes are not made to the sourcecomponent to remove any reference to the copybook.

A baselined copybook is changed and staged, then deleted from the package but thesource that calls it is not re-staged or recompiled.

Return Code Description

12 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 deletedcopybook.

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 thepackage.

Change Management Page 21 of 22

CHANGEMAN AUDIT FUNCTION:

ChangeMan

SYNCH18! (Load deleted problem in staging)

A new unknown to Change Man load module is staged into a package, and acomposite load module that calls it is also staged in the same package or aparticipating package. When the load module is deleted, changes are not made to thesource and link-edit control cards for the composite load module to remove anyreference to the load module.

Return Code Description

12 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-edit control cards, and the source and re-stage the composite load module.

Change Management Page 22 of 22