Event Notification Facility › Operation › Replace a DCM

Replace a DCM

Sometimes a DCM must be replaced. The DCM replacement may include a definition of a new event or a change to the definition of an event. When CAIENF is recording events to the database, the database table associated with the changed event must be deleted. Instructions are provided along with the new DCM PTF having a ++HOLD status.

Important! Before you submit any jobs to replace a DCM, consider the following:

• A CA Datacom/AD Multi-User Facility (MUF) must be running on the system where the JCL associated with the procedure will execute.
• A CA Datacom/AD MUF can execute in its own address space or under the CAIENF address space.
• To customize CA Datacom/AD for CAIENF or resolve CA Datacom/AD for CAIENF customization issues, the CA Datacom/AD MUF must be running with its own address space and CAIENF must be down or started in a separate address space from the CA Datacom/AD MUF with the control option NODB

To utilize the new DCM

1. Reference the new DCM in the CAIENF startup JCL under DD statement CAIDCM.

   Important! If you are running CAIENF with control option NODB, Stop and Restart CAIENF to pick up the new module or proceed to the next step to delete the Database definitions for the old DCM.

2. Prepare batch jobs CASQL004 and CADB001 located in the CAW0JCL data set by editing and specifying a job card and the appropriate Datacom execution libraries in the Set JCL statements.

   CASQL004 must have the name of the specific table to be deleted in the SQL Drop Table statement.

   Optionally, CAS9DCMR utility can be used to generate the DROP TABLE statements. For more information on CAS9DCMR - DCM MAPPER, see the Reference Guide.

3. Shutdown CAIENF with the STOP ENF operation command.

   Important! If you are running CAIENF with an internal CA Datacom/AD MUF, after CAIENF is down, you must start the CA Datacom/AD MUF in its own address space before submitting the job that deletes the old DCM's database definitions.

4. Submit CASQL004.

   If successful you may restart CAIENF. When CAIENF is restarted, it will dynamically create the new DCM's database definitions.

5. If the CASQL004 batch job completes in error, the database has CAIENF table information remaining in its internal cache. Submit batch job CADB001 to ready the database for another Drop Table.
6. After CADB001 completes, resubmit job CASQL004 and restart CAIENF.

Note: For more details, see the CAIENF Batch Database Query and Administration Appendix.