The Endevor documentation explains the Catalog Synchronization Utility and how it synchronizes the element catalog with the MCF element records in two phases.
What are the phase of the Element Catalog synchronization ?
The Catalog Synchronization Utility (BC1JCSYN) synchronizes the element catalog and the MCF element records in two phases.
Here is an explanation for each phases.
PHASE 1
During the 1st phase, the utility looks at the MCFs for the environment(s) specified and checks if the elements therein are correctly entered in the Element Catalog file.
Depending on the result of this analysis, the utility issue messages:
PHASE 2
During the 2nd phase, the utility looks at the Element Catalog file and checks if the elements therein actually exist in the corresponding MCF.
Depending on the result of this analysis, the utility issue messages:
If any *MISSING *, *OLD * or *ORPHAN * messages are issued the job ends with RC 4 (assuming there are no actual error messages).
When running in validate mode (i.e. PARM=BC1PCSYNVALIDATE), RC 4 indicates that the files are out of synch and you need to re-run BC1JCSYN in UPDATE mode (i.e. PARM=BC1PCSYNUPDATE).
For further information, please read Catalog Synchronization Utility