Previous Topic: Configure DCM StatementsNext Topic: Handling ENF Database Full Conditions


Replace a DCM

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

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

Follow these steps:

  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 statement 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.

  3. Shut down CAIENF with the STOP ENF operation command.

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

  4. Submit CASQL004.

    If successful, restart CAIENF. When CAIENF is restarted, it dynamically creates the DCM 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.