Use the following procedure to import object definitions from a DB2 catalog to the repository:
To synchronize a DB2 catalog
SIZE ------------------------- SYNC DB2 CATALOG -------------------
¦ NAVIGATE HELP R7SP1DEV ¦ ¦ SPECIFY CRITERIA TO SYNC SEQUENCE. ¦ ¦ SEQUENCE SEARCH CRITERIA : ¦ ¦ DB2 VERSION? ===> 8 ( 6, 7, OR 8) ¦ DB2 CATALOG SUBSYSTEM? ===> D81A ¦ SHADOW CATALOG CREATOR? ===> SYSIBM ¦ STATUS TO SYNC? ===> DBXT ¦ ELEMENT SYNC STATUS 1? ===> DBXT ¦ ELEMENT SYNC STATUS 2? ===>
¦ ELEMENT SYNC STATUS 3? ===>
¦ SYNC DEPENDENT VIEWS? ===> Y (Y-YES,N-NO)
¦ VIEWS INTO EXTENDED TEXT?===> N (Y-YES,N-NO,D-Delete Existing) ¦ QUALIFICATION LEVEL? ===> Y (N-NONE, Y-CREATOR, F-FULLY) ¦ SERVER NAME? ===> ¦ IO VALIDATE? ===> Y (Y-YES,N-NO,B-BATCH) ¦ DDL USAGE? ===> DB2 ¦ TRANSLATE "_" TO "-" ? ===> Y (Y-YES,N-NO) ¦ WORKSTATION NAME? ===> WKST01 ¦ DETACHED WORKSTATION? ===> ¦ EDIT JCL? ===> Y (Y-YES,N-NO)
*******************************************************************
|
Field |
Enter |
|---|---|
|
DB2 Version |
The DB2 version number. |
|
DB2 Catalog Subsystem |
The DB2 subsystem you are synchronizing with the repository. |
|
Shadow Catalog Creator |
The creator of a shadow catalog (if CatSync is to be performed against a shadow catalog). For more information on shadow catalogs, see Maintenance and Performance Tuning in this chapter. |
|
Status To Sync |
The repository status to use for actions performed against the repository (DELETE, INSERT, SELECT, or UPDATE). If you are synchronizing an object that is already defined in the repository, then specify the object's current status. |
|
Element Sync Status 1 |
The status CatSync should search for existing data elements. This field defaults to value specified in Status to Sync. This status is used for actions performed against the Element entity type only (DELETE, INSERT, SELECT, or UPDATE). |
|
Element Sync Status 2 |
An alternative status to search for existing elements. CatSync searches this status only if it fails to find a reusable instance in the status specified in Element Sync Status 1. |
|
Element Sync Status 3 |
A second alternative status to search for existing elements. CatSync searches this status only if it fails to find a re-usable instance in the statuses specified in Element Sync Status 1 and Element Sync Status 2. If it finds no reusable instances in this status, it inserts a new instance using the status specified in Element Sync Status 1. |
|
Sync Dependent Views |
Y-To sync all the views directly or indirectly associated with the chosen occurrences. N-To ignore all subordinate views If the current entity type is VIEW, CatSync processes only the selected views, ignoring any views or tables subordinate to the selected views. |
|
Views into Extended Text |
Y-If you want to load view CREATE statements as extended text. If you load the CREATE statement as extended test, CA Repository for z/OS generates DDL for these views using the extended text. N-If you do not want to load view CREATE statements as extended text. D-To delete existing text from the view. If you no longer want the view text stored as text, set this switch to D. |
|
Qualification Level |
Y-To process tables and views with the same name but different creators as different objects. N-To ignore creators specified in the DB2 catalog when comparing tables and views to repository definitions. F -To use the fully qualified name of the DB2 object when searching for an object in the repository. It is important that your site uses the same value consistently with every execution of the CatSync. The appendix "Functional Keys" contains a list of the functional keys (search attributes) that the catalog sync process uses to find an object in the repository. |
|
Server Name |
The DB2 location name used as the first node in a fully qualified name when qualification level is set to F. Server name is required when the qualification level is F. |
|
IO Validate |
Y-To use I/O validation when inserting or updating repository instances. N-To bypass I/O validation . You must have authority for the special CA Repository for z/OS command BLOAD.BLOAD.NOVALID to use this option. B-To use batch validation . This option results in the fastest processing times, but CA Repository for z/OS limits the number of batch validation jobs that can run at one time. For performance reasons, always set this option to N or B. |
|
DDL Usage |
DB2 |
|
Translate "_" to "-" |
Y-To have CatSync recognize dashes and spaces in the DB2 Column Name attribute as delimiters when searching for elements in the repository. CatSync searches for matching DB2 Columns Names using underscores first, then dashes, and finally spaces before it concludes there are no matching occurrences in the repository. N-To have CatSync limit its search for existing elements to those using underscores as delimiters in their DB2 Column Names. For performance reasons, we suggest this value. |
|
Workstation Name |
The name of an existing CA Repository for z/OS workstation occurrence. CatSync adds any entities it inserts as a result of the synchronization to this workstation. |
|
Detached Workstation |
The name of the workstation Catalog Sync will use The workstation contains DB2 items that were one time associated with DB2 objects that are being synced in and are no longer part of this sync process. These items potentially represent objects that were dropped from the DB2. Note: Leave this field blank if you do not want to load detached data into a workstation. |
|
Edit JCL |
Y-To have CA Repository for z/OS display the JCL for CatSync job in an ISPF edit session rather than submit it You can submit the job for the edit session by typing SUBMIT on the command line. |
SIZE ----------------TABLE LIST (USING CRITERIA)-----------------------------MAX
| CRITERIA PROFILE NAVIGATE HELP | | SEL NAME CREATOR DBNAME TSNAME | | --- ------------------- -------- --------- ------- | | _ DBX_BCA_BACHENT DBXBCA C50DEV2 BCABCAE | | _ DBX_BCA_BACHSYN DBXBCA C50DEV2 BCABSYN | | _ DBX_BCA_DIMENSN DBXBCA C50DEV2 BCADIN | | _ DBX_BCA_DOM_DON DBXBCA C50DEV2 BCADNDM | | _ DBX_BCA_DOMAIN DBXBCA C50DEV2 BCADON | | _ DBX_BCA_ENTKEY DBXBCA C50DEV2 BCAENTK | | _ DBX_BCA_TEXT DBXBCA C50DEV2 BCABTXT |
| _ DBX_BCH_ALLOWVAL DBXBCH C50DEV2 ALLOWVA |
If you are processing a foreign (non-repository) subsystem, CA Repository for z/OS displays the CatSync JCL immediately.
This JCL does not contain an object list; see Catalog Sync with a Foreign Subsystem later in this chapter.
Note: If you know before starting the CatSync process that this list of objects is too large to handle easily, you can enter the Search Criteria window immediately after the SYNCDB2 window by invoking the SYNCDB2 command with the Q parameter. For example:
OPTIONS.CATSYNC.SYNCDB2 Q.
|
Parameter |
Enter |
|---|---|
|
Debug |
Y-To instruct the job to produce CA Repository for z/OS debug statements for this step These statements aid CA Technical Support in identifying and resolving problems encountered during the CatSync process. These statements will be sent to the data set specified in the SYSPRINT file (LRECL = 80). N-To instruct the job not to include debug statements Unless CA Technical Support instructs you to do otherwise, you should always set this parameter to N (no debug statements). |
|
Columns Only |
Y-To instruct CatSync to limit scanning to subordinate tables and their column information and to ignore other dependent objects of the subordinate table (like indexes and synonyms) The table and the column definitions are all that are needed if the views that are placed on the tables are to sync successfully. |
|
Debug |
Y-To instruct the job to produce debug statements for this step N-To instruct the job not to include debug statements Unless CA Technical Support instructs you to do otherwise, you should always set this parameter to N (no debug statements). |
|
Unload FieldProc |
N-To force the CatSync to ignore DB2 Fieldproc information when scanning the catalog This will result in significant performance improvements. Unless your site uses Fieldprocs, set this option to N. |
|
Dialog |
DB2 |
|
Command |
SYNCDB2-If performing a true catalog synchronization SYNCTEST-If performing a test catalog synchronization |
|
Subsystem |
The name of the subsystem in which the repository resides |
|
Source Input |
This parameter reflects the CA Repository for z/OS process in which this step is being used In this case, the value should always be C for CatSync. This parameter is tied closely to another parameter called SOURCE TYPE, which means nothing to CatSync and should be left blank. |
|
Language |
The language format to use for new elements inserted by CatSync Valid options are: C-COBOL (to use hyphens for element values) P-PL/I (to use underscores for element values) |
|
Debug |
Y-To instruct the job to produce debug statements for this step N-To instruct the job not to include debug statements Unless CA Technical Support instructs you to do otherwise, you should always set this parameter to N (no debug statements). |
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |