Previous Topic: Customize an Existing CA Datacom/AD for CAIENFNext Topic: Customize CA Datacom/AD for Event Management


Resolve CA Datacom/AD for CAIENF Customization Issues

There can be instances where problems are encountered customizing CA Datacom/AD for CAIENF. For example, a data set name or space allocation can be specified incorrectly or the CAIENF database installation CAW0JCL member AW1ID001 receives an error.

In many cases, the CAIENF database installation CAW0JCL member AW1ID001 can be resubmitted after resolving the issue that caused the error by editing the JCL to begin at the job step encountering the error.

However in some cases, it can be more desirable to delete a partially or completely installed CAIENF database.

Follow these steps:

  1. See CA Datacom/AD MUF Considerations in Customize CA Datacom/AD for CAIENF before you start this procedure.
  2. Submit CAW0JCL member AW1AD001 to obtain a list of existing CAIENF database tables.

    If no rows are found, proceed to step 4 to delete the CAIENF database.

  3. Edit and execute CAW0JCL member CASQL004 to drop all CAIENF tables.

    This step is only required if the listing for job AW1AD001 indicated that rows were found.

    The EVENT tables are dynamically installed at CAIENF startup when the RECORD(YES) ENFPARM control option has been specified.

    Important! Never drop an EVENT table while CAIENF is actively recording events. For more information, see CA Datacom/AD MUF Considerations in Customize CA Datacom/AD for CAIENF.

    Note: The DROP TABLE statement renders the table obsolete. This action removes all versions and statuses of the table from the data dictionary databases, deletes the Directory definition, and deletes the data.

    If CASQL004 returns an error, execute CAW0JCL member CADB001 to close all CAIENF tables then resubmit CASQL004.

    Note: An error is returned if the database table information remained cached by the CA Datacom/AD address space.

  4. Edit and submit CAW0JCL member CADB003 to delete the CAIENF database definitions from CA Datacom/AD.

    Important! Drop all the CAIENF tables before deleting the CAIENF database.

    Note: If the CAIENF database was partially installed, one or more database components could not exist and CADB003 indicates errors for the missing components. You can safely ignore such errors.

  5. Edit and submit CAW0JCL member CADB004 to delete the CA Datacom/AD directory definitions for CAIENF.

    Only run this job when the step to define and initialize the CA Datacom/AD CAIENF database data sets found in CAW0JCL member AW1ID001 successfully initialized and updated the Datacom/AD CXX file with the CAIENF ENF0700 and IX0700 data set information.

  6. Edit and submit CAW0JCL member CADB005 to delete the CAIENF database data sets.

    This job only runs when the step to define and initialize the CA Datacom/AD CAIENF database data sets found in CAW0JCL member AW1ID001 successfully allocated the CAIENF ENF0700 and IXX0700 data sets.

  7. Re-install the CAIENF database using CAW0JCL member AW1ID001.

Customize a New CA Datacom/AD for CAIENF

Follow these steps:

  1. Modify and submit member, AW1ID001 to install the CAIENF database definitions into CA Datacom/AD and allocate the CAIENF database data sets.

    Note: If AW1ID001 does not complete successfully, see Resolve CA Datacom/AD for CAIENF Customization Issues.

    If you are upgrading from CA Common Services r11, to obtain the total number of events count, your current running CCS CAIENF r11 can be used to help. Run the CAS9DB LIST DETAIL report shortly before your ARCHIVE (BACKUP) time, preferably the day after your three busiest days of the week. The LIST DETAIL report provides the total number of records that are currently recorded for each event type on the CAIENF r11 database. You can then simply add them up. Here is the CAS9DB LIST DETAIL JCL:

    //CAS9DB   EXEC PGM=CAS9DB,REGION=4M
    //DBOUT    DD SYSOUT=*
    //DBIN     DD *
      LIST DB(*) DETAIL
     /*
    

    Make sure CAIENF r11 is up and running to use the above JCL as is.

  2. Update the CAIENF procedure.

    CAW0PROC contains three CAIENF procedures; ENF, ENFXMUF, and ENFIMUF. Select the procedure that applies to the requirements for your site.

    ENF - Use the JCL found in this procedure to not record events or install CA Datacom/AD.

    ENFXMUF - Use the JCL found in this procedure to record events. CA Datacom/AD is installed and the MUF is external (runs in its own address space) to CAIENF.

    ENFIMUF - Use the JCL found in this procedure to record events. CA Datacom/AD is installed and the MUF is internal (runs under the CAIENF address space) to CAIENF.

    For ENFXMUF and ENFIMUF:

  3. Start or Restart CAIENF.

    CAIENF dynamically creates the EVENT tables to record events and CAIENF system tables to record miscellaneous supportive data.

    The EVENT tables are created when CAIENF initializes with RECORD(YES) specified.

    If RECORD(YES) is specified and the DATACOM/AD MUF is not available, CAIENF will shut down.