Install CA Datacom/AD › Customize CA Datacom/AD for Event Management

Customize CA Datacom/AD for Event Management

The following steps are optional for Event Management.

If you decide to use Calendars or Message Actions with Event Management, you must have CA Datacom/AD installed and perform these steps.

Calendars and Message Actions are typically not required for sites using CA OPS/MVS Event Management and Automation interfacing with Event Management, but may be helpful for sites that are not using CA OPS/MVS Event Management and Automation to process events.

After completing the CA Datacom/AD installation, you will have two CA Datacom/AD load libraries, CAAXLOAD, CUSLIB and a parameter library, CUSMAC. These libraries are required to complete the CA Datacom/AD setup for Event Management.

If you have a DATACOM/TR repository used for release 3.0 of Event Management, you may want to extract the table information from the old repository and load the information into the new DATACOM/AD repository. For information on the optional steps to extract and load your existing table information, see the latter portion of the following procedure.

To customize the CA Datacom/AD for Event Management

1. Update MUF DATAPOOL parameter.

   Change the CA Datacom/AD startup and tuning parameter member for the MUF by altering the DATAPOOL buffers.

   Depending upon how you are running the MUF, refer to the CAIENF or CA Datacom/AD MUF startup procedure JCL SYSIN DD statement to determine the data set and member name containing the startup and tuning parameters.

   Change

   DATAPOOL    8K,2000,16K,2        DATA BUFFER SIZE,# OF BUFFERS
   

   to

   DATAPOOL    12K,2000,16K,2       DATA BUFFER SIZE,# OF BUFFERS
   

2. Start or Recycle CA Datacom/AD.

   Note: Before performing the following steps, the CA Datacom/AD MUF must be active with the previous changes in effect.

3. Create DB Definitions.

   Modify and Submit CNSMJCL member D5IRTV01.

4. Verify Definitions and Initialize Database.

   Modify and Submit CNSMJCL member D5IRTV02.

5. Define the SQL tables.

   Modify and Submit CNSMJCL member D5IRTV03.

   Note: If the D5IRTV jobs in steps 3, 4, and 5 do not complete successfully, see Resolve CA Datacom/AD for Event Management Customization Issues.

6. (Optional) If you are a previous CA Datacom/TR user (from CA Common Services r11) and would like to migrate your CA Datacom/TR data to CA Datacom/AD, perform this step. In past releases, Event Management maintained message action records and calendars in the CA Datacom/TR database.
   • With EM 3.0 Datacom R9 active, produce a CA Datacom/AD utility report of the Event Management database using CNSMJCL member D5IDBUTL.
   • Using the Datacom R9 utility report, update CNSMJCL member D5IDBEXT with the three character TABLE NAME for each OCCURRENCE of the Event Management Table Names shown in the JCL member D5IDBEXT.

     Example - Datacom utility report:

     TABLE NAME - C27          
     OCCURRENCE - CADB-OPRA_CTL
     

     Change JCL member D5IDBEXT:

     EXTRACT AREA=EM0,DBID=1011,DDNAME=DDOCTL,TABLE=C27, CADB-OPRA-CTL BLKSIZE=10236
     

   • Extract Datacom/TR data for migration to CA Datacom/AD.

     Modify and Submit CNSMJCL Member D5IDBEXT.

   • Load extracted Datacom/TR Data into CA Datacom/AD.

     Modify and submit CNSMJCL member D5IDBLD to load the extracted data into CA Datacom/AD.

     Restart CA Datacom/AD if currently started.

7. Confirm your Event Management Profile.

   During the Common Services Installation step (Create the Event Management Profile) entries were made pertaining to CA Datacom/AD.

   Ensure that the /cai/nsmem/PROFILE file is edited to specify CA_OPR_ZOSDB=Y.

   This allows the usage of Calendars and Message Actions with Event Management. If you did not know the CA Datacom/AD data set names or data set high level qualifier at the time of the installation, you can edit the /cai/nsmem/PROFILE file directly with this information now. Refer back to the installation step for information on how to edit this file.

   The STEPLIB environment variable in /cai/nsmem/PROFILE must point to the correct CA Datacom/AD libraries.

   If you are migrating from a CA Datacom/TR or creating a new CA Datacom/AD database, make sure the STEPLIB variable points to the correct CAAXLOAD and CUSLIB data sets.

   Once the /cai/nsmem/PROFILE file updates are complete, rerun CNSMJCL member D5II0065. This ensures that any information required for the use of the CA Datacom/AD databases is updated in the proper Event Management component scripts.

   If you optionally updated the system /etc/profile file to have the EM environment variables set when a user logs on, you will have to rerun script fwsetup to reflect the CA Datacom/AD libraries in the STEPLIB variable. For more information, see section Run the Event Management Post-Installation Script.

8. Start MUF.

   The CA Datacom/AD MUF can run in its own address space or under the CAIENF address space.

   If you are using Calendars or Message Actions, you should initialize the MUF before the Event Management components start. If the MUF is not initialized, expect startup error messages. The caiopr daemon starts without the MUF running, but the Calendar daemon does not.

9. Start Event Management Daemons.

   You can access your new database by starting the Event Management Daemons using CNSMPROC member NSMEMSTR.