While CatSync is one of the primary means used to populate the CA Repository for z/OS with metadata, it is probably not the only such tool you use.
CatSync is used only with DB2 object definitions-other facilities must be used to populate the repository with other types of metadata. This raises the important issue of how CatSync should be used with other CA Repository for z/OS tools.
Because most of the objects CatSync populates are DB2-specific, you need not be concerned with the effects of much of the CatSync-loaded metadata on the definitions of objects from other DBMSs. However, Element definitions are exceptions. ELEMENT is the entity type that is central to all the dialogs related to the physical metadata (IMS, COBOL, and so on), so the definitions CatSync imports can potentially affect the ELEMENT definitions loaded in from non-DB2 sources.
Important! Therefore, the proper coordination of CatSync with other repository facilities should be a priority of every site that wants to use the CatSync Facility.
Of course, if you keep your DB2 metadata separate from the other types of metadata using particular repository statuses, there is no issue with metadata interaction and you can forego the process of coordinating CatSync with other facilities. However, CA does not recommend this, as it permits the storage of redundant metadata.
The CA Repository for z/OS utility that loads the most ELEMENT definitions is the Copybook Import facility, so this discussion concentrates on the coordination of the Copybook Import and CatSync. Both facilities insert values into the DB2 Column Name and Element Name attributes of ELEMENTs, but CatSync searches DB2 Column Name for matches, while Copy In examines Element Name. CA recommends that you run Copybook Import before running CatSync because of the differences between the methods the two facilities use to evaluate existing ELEMENT definitions when searching for occurrences to reuse.
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |