Catalog Synchronization Facility › Catalog Sync with a Foreign Subsystem

Catalog Sync with a Foreign Subsystem

You can use Catalog Sync to synchronize CA Repository for z/OS with DB2 catalogs located in:

• The local subsystem is the DB2 subsystem containing CA Repository for z/OS.
• A foreign subsystem is any DB2 subsystem that does not contain CA Repository for z/OS, whether it is on the same CPU or a remote CPU.

  Note: IBM refers to foreign subsystems on both local and remote CPUs as remote subsystems.

Synchronizing the repository with a foreign subsystem requires that you first set up Catalog Sync for use with the foreign subsystem. Use the following procedure.

Note: You must perform this one-time setup for each foreign subsystem you plan to synchronize with the repository.

Once you set up the foreign subsystem, you can synchronize it with the repository as often as needed, using the procedure described later in this chapter.

To set up Catalog Sync for use with a foreign subsystem

1. If the foreign subsystem is on the local CPU, go on to Step 3.
2. If the foreign subsystem is on a remote CPU, do the following:
   1. If needed, create LOADLIB and DBRMLIB data sets on the remote CPU.
   2. Copy all of the DBXCAT* members from the repository's LOADLIB and DBRMLIB data sets to libraries with the same names on the remote CPU.
   3. On the remote CPU, create a DBXPARM data set containing only one member: DBXPARM. This member should be a copy of the DBXPARM file used by the repository
3. Start the CA Repository for z/OS Installation Menu on the local CPU. For more information on accessing the Installation Menu and creating DB2 Plans and Packages, see the Installation Guide.
4. Select Installation Menu Option, Plans to display the DB2 Plans screen.

   ------------------ CA Repository for z/OS ------------
   

   ---------------------------- DB2 Plans and Packages ---------------------
   COMMAND ===>
    Prepare Packages ...
    Utility, All, or Foreign packages? ===> F (U, A, F)
   

    Set SQLID to? ===>
    BIND Plans? ===> Y (Y-yes,N-no) Auth ID of Plan? ===>
    Grant to PUBLIC? ===> N (Y-yes,N-no)
    Foreign Cat SSIDs? ===> D71A ===> D71B ===> D71C
    Foreign Cat DB2VER? ===> 7 ===> 7 ===> 7
    Edit or Submit? ===> E (E-edit,S-submit)
    Save Output? ===> N (Y-yes,N-no)
    Output Data Set ===>
   

   Enter ENTER command to continue or END command to EXIT.
   

5. Enter values in the fields on the DB2 Plans screen as follows:

1. Press Enter. CA Repository for z/OS displays the generated bind JCL.
2. Review the bind JCL and make any needed changes.
3. Save the bind JCL.
4. Press PF3 twice to exit the Installation Menu.
5. Execute the bind JCL on the foreign subsystem.

   Note: If the foreign subsystem is on a remote CPU, you may need to copy the bind JCL to that CPU and modify it before execution.

To run Catalog Sync for a foreign subsystem:

1. Using the procedure in Using Catalog Sync described earlier in this chapter, generate the Catalog Sync JCL for the foreign subsystem.

   Note: Make sure that you specified the correct foreign subsystem name in the DB2 CATALOG SUBSYSTEM? field before you press Enter to display the generated Catalog Sync JCL. If you specified the correct name, you can safely ignore the Call Attach error CA Repository for z/OS displays before displaying the generated JCL.

2. With the generated Catalog Sync JCL displayed:
   • Verify that the DBXPARM ddnames reference the correct data set.
   • Verify that the foreign subsystem's name is specified correctly in the PARM strings of the VIEW, SORT1, SORT2, and CATALOG steps.
   • Insert a null JCL line // after the CATALOG step to prevent execution of the SYNC1 and SYNC2 steps.
   • Using the format shown below, edit the SYSIN statement to specify the types and names of the objects to process.

     // SYSIN DD  *
     

     DATABASE//DBNAME
     TBSPACE//TSNAME//DBNAME
     TABLE//TBNAME//CREATOR//DBNAME
     VIEW//VWNAME//CREATOR
     DATATYPE//DTNAME//CREATOR
     For Databases
     For Table Spaces
     For Tables
     For Views
     (Database Name)
     (Table Space Name)
     (Name of Database containing Table Space)
     (Table Name)
     (Table Creator)
     (Name of Database containing Table)
     (View Name)
     (View Creator)
     For Distinct data type
     (Distinct Datatype Name)                    (Distinct Datatype Creator)
     

   Note: Long names can span multiple input lines by placing a + (plus) in position 80.

3. Save the modified Catalog Sync JCL.
4. Execute the modified Catalog Sync JCL for the foreign subsystem.

   Note: If the foreign subsystem is on a remote CPU, you may need to copy the Catalog Sync JCL to that CPU and modify it before execution.

5. If the foreign subsystem is on a remote CPU, move the DBXCATG file created by the Catalog Sync job from the remote to the local CPU (the CPU on which the repository is located).
6. Display the Catalog Sync JCL again and:
   1. Verify that the local subsystem's name is specified correctly in the PARM strings of the remaining SYNC steps.
   2. Remove the null JCL line you inserted in Step 2.
   3. Add RESTART=SYNC1 to your jobcard.
7. Save the modified Catalog Sync JCL.
8. Execute the modified Catalog Sync JCL for the local subsystem.