This chapter describes the DB2 Catalog Synchronization Utility. The following topics are presented:
This section contains the following topics:
How Does the Catalog Synchronization Utility Work?
Specifying Synchronization Control Statements for TSDB2SY2
Estimating Virtual Storage Requirements
Using the Catalog Synchronization Utility Reports
The Catalog Synchronization Utility provides the ability to bring DB2 catalog entries up‑to‑date with CA Top Secret Option for DB2 authorizations. Because CA Top Secret Option for DB2 replaces DB2 security with authorizations kept in the Security File, CA Top Secret Option for DB2 does not update the DB2 catalog during normal processing. When changes are made to ACIDs or the CA Top Secret Option for DB2 authorizations, the catalog security information becomes obsolete for those products that rely on the catalog for reporting purposes.
To allow products to continue to use up‑to‑date DB2 catalog information, CA Top Secret Option for DB2 uses the Catalog Synchronization Utility.
The Catalog Synchronization Utility changes DB2 catalog information to reflect accesses allowed and denied under CA Top Secret Option for DB2. For information on specific exceptions, see the section “Implementation Considerations”. This utility can extract information from CA Top Secret Option for DB2, native DB2, and the CA Top Secret Recovery File, create SQL GRANT and REVOKE statements from this information, and update the DB2 catalog. The creation of these GRANT and REVOKE statements is the primary function of the Catalog Synchronization Utility. You can synchronize all or specific users and resources or only synchronize those ACIDs or authorizations that have recently changed. To execute the Catalog Synchronization Utility, you might need certain CA Top Secret, CA Top Secret Option for DB2, or native DB2 privileges. These requirements are described in the “JCL Information” section.
|
Copyright © 2011 CA Technologies.
All rights reserved.
|
|