Previous Topic: Monitoring Change ActivityNext Topic: Establishing a CCDB


Change Manager Architecture

The CA Endevor/DB Change Monitor authorizes and logs updates to any IDD in an accompanying Change Control Database (CCDB). Logically, the CCDB is an extension of the dictionary. Updates to the CCDB and the dictionary being monitored are kept in synchronization through the CA Endevor/DB system software.

The Change Monitor operates as a standard CA IDMS database procedure through the subschema used to update the dictionary. The Change Monitor is “hooked” into a dictionary by mapping the CA Endevor/DB-supplied NDVRNWKA for the IDMSNWKA subschema. From this point forward all updates attempted through NDVRNWKA will be routed to the Change Monitor for logging and authorization. (Actual dictionary updates are performed by Computer Associates compilers.)

Once the Change Monitor receives control, it establishes the relationship between a dictionary and its CCDB through the DBNAME table. To achieve

monitoring, the NDVRNWKA subschema, which describes the dictionary, as well as the NDVRSUBS subschema, which defines the CCDB, are mapped to a common DBNAME. The Change Monitor supports as many CCDBs as are defined in the DBNAME table. The Change Monitor decodes the DBNAME table at system startup to determine the proper pairing of CCDBs to dictionaries.

To summarize, change monitoring is initialized by mapping the IDMSNWKA subschema to the NDVRNWKA subschema and establishing a CCDB for the database names to be monitored.

Note: CA Endevor/DB cannot be used with Data Sharing and Dictionaries managed by CA Endevor/DB cannot be shared.