Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
!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.
Example 1
Example 2
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.
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.
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
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.
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 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.