Previous Topic Next topic Print topic


DB2 Catalog Synchronization

Use the z/OS process DB2 Catalog Synchronization to produce the sequential file containing the information needed for the load, unless the file can be produced in another manner. After a new DB2 Catalog Synchronization (client) job is created and scheduled, the sequential file is used when the job executes to load information for the cardinality for DB2 tables and the existence of a key or the existence of an image copy into the knowledge base.

The DB2 Catalog Synchronization (client) job should be executed before beginning the data subset extraction process, so that all the information is synchronized and this process can be independent of the system tables. For more information about the job, see the section DB2 Catalog Synchronization Job in the chapter Work with Jobs in the Front End Guide.

Note: For information about the structure of the output sequential files for HEADER, INTERNAL KEY, EXTERNAL KEY, and IMAGE COPY see the section DB2 Catalog Synchronization Information in the chapter Sequential Files in the Data Model Guide.

To synchronize the DB2 catalog:

  1. From the Main Menu panel, enter the following command: TSO CUINSYNC.
  2. Indicate the scope of the process by specifying the DB2 tables you need in the DB2 Owner and Table Name fields, and the name of the sequential file in the Data Set Name field.
    Note: For the DB2 Owner and Table Name fields, you can specify *ALL if you want to process all owner names or all table names.
Previous Topic Next topic Print topic