Scribd
Upload
340 views

Out of Sync Conditions

The document describes various "Out-of-Sync" conditions that can occur during auditing in ChangeMan and provides explanations, return codes, and suggested resolutions for each condition. Conditions include components with duplicate contents, unknown relationships to ChangeMan, discrepancies between source and load modules, missing activity files, and more. Return codes typically indicate the level of severity from informational to errors. Suggested resolutions provide actions like recompiling, relinking, deleting duplicates, or staging missing components.

Uploaded by

Salai Nayagan Arunmozhi
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
340 views

Out of Sync Conditions

The document describes various "Out-of-Sync" conditions that can occur during auditing in ChangeMan and provides explanations, return codes, and suggested resolutions for each condition. Conditions include components with duplicate contents, unknown relationships to ChangeMan, discrepancies between source and load modules, missing activity files, and more. Return codes typically indicate the level of severity from informational to errors. Suggested resolutions provide actions like recompiling, relinking, deleting duplicates, or staging missing components.

Uploaded by

Salai Nayagan Arunmozhi
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Out-of-Sync Conditions

Out-OfSynch
Message

Explanation

Return
Code

Suggested
Resolution

DUPLIC! -

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
that component to drop off prematurely.

Delete the duplicate


component from the
change package.

Shows that there is a copy within a copy (an embedded


copylink). This is an informational code indicating that a
relationship exists.

No action required.

If the Audit job completes with a Cond Code of 0, SYNCH0!


errors can be ignored. Please note that the following
components will never be in ChangeMan and can be ignored
in audits.

Make the component


known to
ChangeMan by
putting the called
module into the
change package, or
if it exists in
baseline, by
rerunning
conversion
assistance to pick up
the new relationship.

No action required.

(STAGING
DUPLICATES
BASELINE)

!COPY! (EMBEDDED
COPYLINKS)

SYNCH0! (COMPONENT
UNKNOWN TO
CHANGEMAN)

IGZCBSO
IDCSACON
IGZCBSO
RHDCLENT

-----

Unknown
Unknown
Unknown
Unknown

to
to
to
to

ChangeMan
ChangeMan
ChangeMan
ChangeMan

-----

SYNCH0!
SYNCH0!
SYNCH0!
SYNCH0!

If ChangeMan has no record of this component in the


package master, and a component is calling another module
and one (or more) of the following situations exist, then
SYNCH0! results.
It may not exist in baseline, or the relationship is not found in
the impact analysis table (as read by audit), but the called or
calling module does not exist in the baseline library.
Example 1
If a source component calls a copybook, but the copybook
does not exist in baseline and the source-to-copy
relationship is not displayed in query impact (+Q.I), the
copybook is flagged.
Example 2
Similarly, a load module is flagged if it statically links (calls)
another load module (subroutine) when the called load
module does not exist in baseline, or the load-to-load
relationship does exist in query impact but the called or
calling module does not exist in baseline.
Note If a called component (copybook or load module) is
copied directly into the baseline library without going
through the change package life cycle, and conversion
assistance has not been invoked, then the called component is
also flagged.
SYNCH1! (ISPF
STATISTICS NOT
AVAILABLE)

Components that have no ISPF statistics cause a SYNCH1!


message.

Page

Out-OfSynch
Message

Explanation

Return
Code

Suggested
Resolution

SYNCH2! -

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) cause a SYNCH2! message. The final compile must
be performed prior to freeze, exactly as designated.

12

Recompile the
component using the
designated
procedure.

Load components with IDRDATA records that ChangeMan


cannot parse causes a SYNCH3! message.

No action required.

Copy or like-copy components in the staging library that have


a more current stage date than the calling source component
in the staging library cause a SYNCH4! message.

12.

Recompile the
staging version of
the source

Copy or like-copy components in staging library that have a


more current activation date than the calling source
component in the baseline library cause a SYNCH5!
message.

Recompile the
baseline version of
the source.

Components that do not have an associated corresponding


component activity file (CAF) cause a SYNCH6! message.

12

Checkout the
component again
before the staging
version of the
calling load
modules.

Called load and like-load components in the staging library


that have a more current SETSSI than the calling load
component in the staging library cause a SYNCH7! message.

12

Relink the staging


version of the
calling load.

Called load and like-load components in the staging library


that have a more current SETSSI than the calling load
component in the baseline library cause a SYNCH8!
message.

Relink the baseline


version of the
calling load.

Load and like-load components that do not have a


matching source component in the staging library cause a
SYNCH9! message.

12

Stage the source


component again.

Components that have a corresponding member in the


baseline library changed or updated since it was checked out,
cause a SYNCH10! message. To avoid this condition during
an audit, a parameter can be set at the global or application
level to check for this condition during staging.

12

Checkout the
component again
and retrofit the
changes.

Components that have been changed outside of ChangeMan


cause a SYNCH11! message because the hash token that is
created and stored within the package master during a stage
wont match the hash token that Audit calculates.

12

Verify the changes


to the component
and stage again.

(COMPILE/
DESIGNATED
PROC DIFFER)

SYNCH3! (UNPARSABLE
LOAD
COMPONENT)

SYNCH4! (CPY
PROBLEM IN
STAGING)

SYNCH5! (CPY
PROBLEM IN
BASELINE)

SYNCH6! (ACTIVITY FILE


NOT CHECKED
OUT)

SYNCH7! (CALLED
SUBROUTINE IN
STAGING)

SYNCH8! (CALLED
SUBROUTINE IN
BASELINE)

SYNCH9! (SOURCE AND


LOAD
DISCREPANCY)

For example, if the staging library is changed outside of


ChangeMan by linking a new load component into the
staging library, the existing source component does not match
the new load component and SYNCH9! results.
SYNCH10! (VERSION
REGRESSION
PROBLEM)

SYNCH11! (COMPONENT
HASH
DISCREPANCY)

Page

Out-OfSynch
Message

Explanation

Return
Code

Suggested
Resolution

SYNCH12! -

If an unknown component is found in the staging library,


usually when a component has been copied into the staging
library outside of ChangeMan or when a compile abends, a
SYNCH12! results. If this condition is not resolved, the
component can be rippled into the baseline library.

12

Delete the
component from the
staging library.

(ORPHAN
MODULE IN
STAGING)

SYNCH13! (COMPONENT
NOT IN ACTIVE
STATUS)

Load components that have been staged into a


package as a result of recompiling a source
component from a baseline library cause a
SYNCH13! message.
Staged components that have a baseline version
which has been changed or updated since it was
staged into a change package cause a SYNCH13!
message.

12

Note: ISPF statistics must be turned on at all times for


SYNCH13! to display.

SYNCH14! (COMPONENT
NOT IN ACTIVE
STATUS)

SYNCH15! (SOURCE TO
COPY
RELATIONSHIP
PROBLEM)

If any component in the change package is not in ACTIVE


status when the audit is run, a SYNCH14! results.

12

SYNCH15! flags the following out-of-synch conditions in


source/copy relationships:

12

The contents of the called copybook(found in either


staging, promotion or baseline library) has changed since
the Source module was compiled.

A New version of the copybook has been added to the


SYSLIB search order for that source component.

The Staging LCT member has a more current activation


data than the corresponding source member.

If a load
module in
staging was
created from a
previous
recompile of a
source
component in
baseline,
recompile the
target source
from baseline
again to include
the more current
source
component in
baseline.

Checkout
the component
from baseline
and restage it, or
restage your
component.
Stage the component
or delete it from the
package.
Restage the source
component.

Page

Out-OfSynch
Message

Explanation

Return
Code

Suggested
Resolution

SYNCH16! -

SYNCH16! applies to conditions where a copy component is


staged in a package that might have a future install date. It
alerts you to a copybook residing in a package in motion
(which may or may not have gone through baseline ripple)
where the corresponding source has been installed after the
activation date of the copybook component. The SYNCH16!
function checks the copybook component for equivalent hash
tokens in staging and baseline libraries and for the lowest
creation date of the load module to the corresponding source
in the baseline library. SYNCH16! occurs only if all three of
the following criteria are met:

Recompile baseline
version of source
and rerun Audit.

12

1. Stage the missing


copybook
component to
include the
copybook referenced
by the source
program and restage
the source program.

(SOURCE TO
COPY
RELATIONSHIP
PROBLEM)

The copybook is a component in a package in motion


without the calling source component.

The activation date and time of the source component


from the baseline library has a more current activation
date and time than the copybook from staging.

The copybook has tokens from the baseline library and


the staging dataset differ.

Note If the hash tokens match and the first two criteria are
met, a DUPLIC! is the result, not a SYNCH16! message.
SYNCH17! (COPYBOOK
DELETED
PROBLEM)

SYNCH17! alerts you if one of the following two situations


occurs:
Situation 1
A new copybook is introduced to a package where the
copybook does not have a corresponding component in the
baseline library. Then the new copybook is deleted from the
package.
Situation 2
The package is going forward with a source that calls a
copybook where the copybooks source is deleted from
staging and no compile activity has occurred after the
deletion.

2. If the copybook
component is no
longer needed,
remove the included
reference to it within
the source and
restage the source.

These situations arise if you inadvertently delete the


copybook component from a package containing a source
component that references the deleted copybook.
The result is that the source referencing the deleted copybook
can no longer complete future compiles.
The copybook can be in any participating package that would
be included as part of the SYSLIB concatenation of the
compiler step based on install dates of the participating
packages.

Page

Out-OfSynch
Message

Explanation

Return
Code

Suggested
Resolution

SYNCH18! -

SYNCH18! alerts you if a new called load module that has


never been baseline rippled is staged into a package. Since
the called load module has not been baselined, it does not
have a corresponding component in the baseline library.

12

1. Restage the
missing load
component to
include it as input to
the binder for the
calling load module.

(LOAD DELETED
PROBLEM IN
STAGING)

SYNCH18! alerts you if the following situation occurs:


A new called load module, which
has never been baselined, is
introduced into a package. A
static link-edit process is
performed where the called load
module is included by a calling
module. The called load module is
deleted from the package
inadvertently.

2. If the load
component is no
longer needed,
remove the included
reference to it from
the link-edit control
cards.

This situation arises if you inadvertently delete the called


load module from the package containing the main loadmodule component that calls the deleted load module.
The result is that the calling load module (which can be run)
can no longer reference the called load module, because the
calling module cannot complete a future link-edit/bind
process.
If you are working with participating packages, the calling
and called load modules are not required to reside in the same
package for SYNCH18! to detect a condition. The called load
module can reside in any participating package that is
included as part of the SYSLIB concatenation of the linkedit/binder step based on install dates of the other
participating packages.

Page

You might also like