Implementing CA Compliance Manager for CA Chorus for Security and Compliance Management › Implement CA Compliance Manager CA Datacom/AD Repositories › Start the CA Datacom/AD MUF for CA Compliance Manager

Start the CA Datacom/AD MUF for CA Compliance Manager

The CA Datacom/AD MUF must be executing before the CA Compliance Manager repositories can be defined.

Follow these steps:

1. Start the CMGRMUF by issuing the following console command.

   S CMGRMUF
   

   Note: If you created a MUF with a name that is different than the recommended default, CMGRMUF, use the correct MUF name in the command.

2. Verify that the CMGRMUF successfully started.

   Note: For complete information about executing the CA Datacom/AD MUF, see the CA Datacom/AD Installation Guide for z/OS.

Delete the CA Compliance Manager Repositories (If Required)

Important! Do not delete, redefine, or reload any of your existing repositories unless you are changing your implementation of CA Compliance Manager. For more information about migrating CA Compliance Manager from CA Chorus r2.5 or r3 to v4.0, see Migrating CA Chorus for Security and Compliance Management to CA Chorus v4.0.

Existing CA Compliance Manager CA Datacom/AD repositories must be deleted so that they can be redefined. The CMGRIDCD job deletes existing repositories.

Follow these steps:

1. Edit the CMGRIDCD job in CAI.CEIQJCL0.

   Modify the job to conform to your installation standards. Follow the instructions in the Notes and the Customization sections of the job to customize the job for your environment.

2. Submit the job.

   The job runs and completes.

3. Verify the output of the CMGRIDCD job.

   The existing CA Compliance Manager repositories are successfully deleted.