Sei sulla pagina 1di 5

Out-of-Sync Conditions

Out-Of- Explanation Return Suggested


Synch Code Resolution
Message
DUPLIC! - Components that, after a line by line compare, show no 4 Delete the duplicate
(STAGING difference between staging and baseline libraries cause this component from the
DUPLICATES condition. At baseline ripple, this causes older versions of change package.
BASELINE) that component to drop off prematurely.

!COPY! - Shows that there is a copy within a copy (an embedded 0 No action required.
(EMBEDDED copylink). This is an informational code indicating that a
COPYLINKS) relationship exists.

SYNCH0! - If the Audit job completes with a Cond Code of 0, SYNCH0! 0 Make the component
(COMPONENT errors can be ignored. Please note that the following known to
UNKNOWN TO components will never be in ChangeMan and can be ignored ChangeMan by
CHANGEMAN) in audits. putting the called
module into the
IGZCBSO -- Unknown to ChangeMan -- SYNCH0! change package, or
IDCSACON -- Unknown to ChangeMan -- SYNCH0! if it exists in
IGZCBSO -- Unknown to ChangeMan -- SYNCH0! baseline, by
RHDCLENT -- Unknown to ChangeMan -- SYNCH0!
rerunning
conversion
assistance to pick up
If ChangeMan has no record of this component in the the new relationship.
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! - Components that have no ISPF statistics cause a SYNCH1! 0 No action required.
(ISPF message.
STATISTICS NOT
AVAILABLE)
Out-Of- Explanation Return Suggested
Synch Code Resolution
Message
SYNCH2! - Source or like-source components in which the final compile 12 Recompile the
(COMPILE/ was done without using the designated compile procedure component using the
DESIGNATED (including designated compile options, link options, or user designated
PROC DIFFER) options) cause a SYNCH2! message. The final compile must procedure.
be performed prior to freeze, exactly as designated.

SYNCH3! - Load components with IDRDATA records that ChangeMan 0 No action required.
(UNPARSABLE cannot parse causes a SYNCH3! message.
LOAD
COMPONENT)

SYNCH4! - Copy or like-copy components in the staging library that have 12. Recompile the
(CPY a more current stage date than the calling source component staging version of
PROBLEM IN in the staging library cause a SYNCH4! message. the source
STAGING)

SYNCH5! - Copy or like-copy components in staging library that have a 8 Recompile the
(CPY more current activation date than the calling source baseline version of
PROBLEM IN component in the baseline library cause a SYNCH5! the source.
BASELINE) message.

SYNCH6! - Components that do not have an associated corresponding 12 Checkout the


(ACTIVITY FILE component activity file (CAF) cause a SYNCH6! message. component again
NOT CHECKED before the staging
OUT) version of the
calling load
modules.

SYNCH7! - Called load and like-load components in the staging library 12 Relink the staging
(CALLED that have a more current SETSSI than the calling load version of the
SUBROUTINE IN component in the staging library cause a SYNCH7! message. calling load.
STAGING)

SYNCH8! - Called load and like-load components in the staging library 8 Relink the baseline
(CALLED that have a more current SETSSI than the calling load version of the
SUBROUTINE IN component in the baseline library cause a SYNCH8! calling load.
BASELINE) message.

SYNCH9! - Load and like-load components that do not have a 12 Stage the source
(SOURCE AND matching source component in the staging library cause a component again.
LOAD SYNCH9! message.
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! - Components that have a corresponding member in the 12 Checkout the


(VERSION baseline library changed or updated since it was checked out, component again
REGRESSION cause a SYNCH10! message. To avoid this condition during and retrofit the
PROBLEM) an audit, a parameter can be set at the global or application changes.
level to check for this condition during staging.

SYNCH11! - Components that have been changed outside of ChangeMan 12 Verify the changes
(COMPONENT cause a SYNCH11! message because the hash token that is to the component
HASH created and stored within the package master during a stage and stage again.
DISCREPANCY) won’t match the hash token that Audit calculates.
Out-Of- Explanation Return Suggested
Synch Code Resolution
Message

SYNCH12! - If an unknown component is found in the staging library, 12 Delete the


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

SYNCH13! - • Load components that have been staged into a 12 • If a load


(COMPONENT package as a result of recompiling a source module in
NOT IN ACTIVE component from a baseline library cause a staging was
STATUS) SYNCH13! message. created from a
• Staged components that have a baseline version previous
which has been changed or updated since it was recompile of a
staged into a change package cause a SYNCH13! source
message. component in
baseline,
Note: ISPF statistics must be turned on at all times for recompile the
SYNCH13! to display. 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.
SYNCH14! - If any component in the change package is not in ACTIVE 12 Stage the component
(COMPONENT status when the audit is run, a SYNCH14! results. or delete it from the
NOT IN ACTIVE package.
STATUS)

SYNCH15! - SYNCH15! flags the following out-of-synch conditions in 12 Restage the source
(SOURCE TO source/copy relationships: component.
COPY
RELATIONSHIP • The contents of the called copybook(found in either
PROBLEM) 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.
Out-Of- Explanation Return Suggested
Synch Code Resolution
Message
SYNCH16! - SYNCH16! applies to conditions where a copy component is 8 Recompile baseline
(SOURCE TO staged in a package that might have a future install date. It version of source
COPY alerts you to a copybook residing in a package in motion and rerun Audit.
RELATIONSHIP (which may or may not have gone through baseline ripple)
PROBLEM)
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:

• 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! - SYNCH17! alerts you if one of the following two situations 12 1. Stage the missing
(COPYBOOK occurs: copybook
DELETED component to
PROBLEM) Situation 1 include the
copybook referenced
A new copybook is introduced to a package where the by the source
copybook does not have a corresponding component in the program and restage
baseline library. Then the new copybook is deleted from the the source program.
package.
2. If the copybook
Situation 2 component is no
longer needed,
The package is going forward with a source that calls a
remove the included
copybook where the copybook’s source is deleted from
reference to it within
staging and no compile activity has occurred after the
the source and
deletion.
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.
Out-Of- Explanation Return Suggested
Synch Code Resolution
Message
SYNCH18! - SYNCH18! alerts you if a new called load module that has 12 1. Restage the
(LOAD DELETED never been baseline rippled is staged into a package. Since missing load
PROBLEM IN the called load module has not been baselined, it does not component to
STAGING) have a corresponding component in the baseline library. include it as input to
the binder for the
SYNCH18! alerts you if the following situation occurs: calling load module.

A new called load module, which 2. If the load


has never been baselined, is component is no
introduced into a package. A longer needed,
static link-edit process is remove the included
performed where the called load reference to it from
module is included by a calling the link-edit control
module. The called load module is cards.
deleted from the package
inadvertently.

This situation arises if you inadvertently delete the called


load module from the package containing the main load-
module 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 link-
edit/binder step based on install dates of the other
participating packages.