What are the phases of the Endevor Catalog Synchronization?

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

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 ?

Resolution

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:

1. *MISSING *
   
   If any element exists in a MCF but not in the Element Catalog file it issues a *MISSING * message.
   
   
2. SYN0003I
   
   If running in VALIDATE mode, the SYN0003I message indicates TOTAL # OF MISSING CTLG SGMTS FROM ENVIRON
   
   If running in UPDATE mode it actually adds the element to the Element Catalog file and the SYN0003I message indicates TOTAL CATALOG SEGMENTS CREATED FOR ENVIRON.
   
   *OLD *
   
   The *OLD * message means the element exists in both MCF and Element Catalog file but it hasn't been stamped to say it is in synch.
   
   
3. SYN0004I
   
   If running in VALIDATE mode the SYN0004I message indicates TOTAL # OF OLD CTLG SGMTS FOUND IN ENVIRON.
   If running in UPDATE mode the elements are synchronized and the SYN0004I message indicates
   TOTAL CATALOG SEGMENTS UPDATED FOR ENVIRON.

 

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:

1. *ORPHAN *
   
   For any element that exists in the Element Catalog file but has no corresponding MCF entry the *ORPHAN * message is issued.
   
   
2. SYN0032I
   
   If running in VALIDATE mode:
   
   
   • SYN0032I message indicates TOTAL # OF ORPHAN CTLG SGMTS IN ENVIRON.
   
   
   If running in UPDATE mode:
   
   
   • The orphans are deleted from the Element Catalog file and the
     SYN0032I message indicates TOTAL CATALOG SEGMENTS DELETED FOR ENVIRON

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

Additional Information

For further information, please read Catalog Synchronization Utility