How to Define CA Datacom/AD for Use with CAIENF

Document ID : KB000021321
Last Modified Date : 14/02/2018
Show Technical Document Details


Beginning with release 12.0 of CA Common Services, CAIENF requires CA Datacom/AD to define the ENF database if CA's scheduling products are recording events. See details in this Knowledge Document for the steps required to understand and be successful in creating this new database structure.

NOTE:  The 12.0 release of Common Services is out of support and CA Datacom/AD 12.0 will go out of support in June 2016.  A more current knowledge document, "How to Define CA Datacom/AD 14.0 Multi-User Facility (MUF) for use with CAIENF 14.1" is available.  This document can be found at the following url:


Environment:  z/OS



Before we discuss how to define a CA Datacom/AD for use with CAIENF (ENF), let's discuss why CA decided to change the database configuration. Beginning with release 12.0 of Common Services, the database used previously by ENF, CA-Universe, was replaced by CA Datacom/AD for the following reasons:

  • CA Universe was a very old database that was only being used by ENF, in fact the CA-Universe functionally was stabilized in the early 90's and support was ended in the late 90's.

  • There was no tracing available to assist in debugging any problems that might arise. Therefore, the only fix to any CA-Universe problem was to rebuild it.

  • CA Datacom/AD provides the following for use with CAIENF:

    • Ability to use SQL to query the database

    • Good recoverability and availability

    • zIIP eligible

The following sections describe the steps you need to take to successfully define CA Datacom/AD for use with CAIENF:

  1. Do you require a CA Datacom/AD database for CAIENF?

    1. Run CAS9DB LIST DB(*) DETAIL command in every LPAR that is running Common Services r11. See sample JCL below:

      //DBIN DD *

    2. Find the Defined CA-ENF Events. See the section of the report output and look for nn Records written. See example below:

      jobinit - Batch JOB/Started Task/TSO Session Initiations
      35 Records written
      Options(A,R,P), Retention (1)

      If no records have been written, you are likely not recording events, and there is no
    3. following ENF modify command on every LPAR that is running CA Common Services 11.0. See sample command below:

      /f enf,event

      Look for CAS9280I and CAS9282I messages and for the *RECORD* or *SELECT* entry in the CAS9280I message. See the following examples:

      CAS9282I - 00000001 EVENTS HAVE OCCURRED

      CAS9282I - 00000043 EVENTS HAVE OCCURRED

    4. If events are NOT being recorded, you'll see a message like the following:

      CAS9280I - Event(JOBINIT ) Status(*Active*) Norecord

    5. If you determine that you are NOT recording events, you need not continue with this checklist as CA Datacom/AD is not required for this configuration.

    6. If you ARE recording events, continue to the next section, Determine Size Requirements.

  2. Determine Size Requirements

    1. Before customizing Datacom/AD database for ENF, you must first determine the size requirements for the ENF database (ENF700) and for the ENF Index (IXX700).

    2. Run batch job CAS9DB LIST DB(*) DETAIL Report in every LPAR that is running CAIENF to obtain the total number of events being recorded. See an example of the LIST DB JCL in the previous section with examples of the output.

    3. Total the number of all Records written for all events and follow the formula documented in CA Common Services for z/OS Installation Guide to determine the size of these datasets. The totals for each CAIENF system can vary, therefore, the size requirements can vary as well.

    4. You will use these totals for executing job AW1ID001 discussed below, in Step 4 Customize CA Datacom/AD for CAIENF, Phase 3.

    5. As an alternative to running the CAS9DB DETAIL Report, you may use 500 cylinders for IXX700 and 1500 cylinders for ENF700 datasets as a starting point and monitor usage for a representative work cycle and then run the following DBUTLTY job with the SYSIN:


      Review the MAX % Full field to see the high water mark which delineates how full the data base and Index (IXX) area got in the represented run cycle time. Then you can adjust the size at the next IPL/maintenance opportunity. Please note that this recommended starting point is a high estimate which is a better alternative to having space issues with the ENF data and index areas.

  3. Install Datacom/AD MUF for Use with ENF

    1. If you are already running a CA product that requires CA Datacom/AD, verify that you are running Version 14.0. Review your currently running Datacom/AD started task and do a find on message DB00215I, see example below:

      DB00215I - CA Datacom/DB r14 at service pack: SP0

      If you find that you are running a supported level of Datacom/AD according to the CA Common Services documentation, then you can use the same SMP/E resources that already exist. If you want or need to create a separate SMP/E environment, refer to the CA Datacom/AD Installation Guide.

    2. CAIENF requires a separate CA Datacom/AD MUF instance separate from the MUF running to support other products such as CA Jobtrac and CA Scheduler.

    3. In preparation for these steps, review the CA Datacom/AD r12.0 README PTF RI16369, and apply PTFs RO22750 and RO37053 which provide replacement members for the jobs that follow.

    4. Run the following CA Datacom/AD jobs to define the Multi-User Facility (MUF) for use with ENF. Refer to the CA Datacom/AD Installation Guide for more information on these jobs.

    5. AXCUS00 - Copies the installation JCL from your existing CA Datacom/AD r12.0 SMP/E CAAXSAMP members to the INSTJCL members.

      • AXCUS01 - Performs CA Datacom product custom assemblies and links. This job creates a new CUSLIB, CUSMAC, CUSPROC for use by ENF. Do NOT use the same libraries and PROCs as you have with other environments running CA Datacom/AD.

        DBDATIN1 :
        MUF enflpar ,99,NO

        DBSIDPR :
        DBSYSID X
        CONSOLE=5, X
        DELAY68=2, X
        DELAY85=1, X
        enflpar ), X

        : The CONNECT_ALLOW_PRIORITY =(LOCAL), specifies only local access, so the TOGROUP=ADXGRP01 is ignored.

      • AD12SVCL - If you are not currently running a MUF where you are implementing CAIENF you need to execute this member.

      • AXNEW01 - Adds the JCLLIB members.

      • AXNEW02 - Initializes and loads the CXX, LXX, FXX, and CA Datacom/AD databases.

      • AXNEW03 - Starts the CA Datacom/AD MUF.

      • AXNEW03B - Populates the Dataquery database.

      • AXNEW04 - Backs up the CA Datacom/AD v12.0 databases.

      • AXNEW05 - Shuts down the CA Datacom/AD MUF.

  4. Customize CA Datacom/AD for CAIENF

    • Run AD12STRT to bring up the CA Datacom/AD MUF.

    • Modify and run job AW1ID001 provided by ENF.

      Phase 1 - Creates the Datacom/AD Datadictionary definitions for the ENF database, which is defined with DBID 700.
      Phase 2 - Catalogs these definitions to the Datacom/AD CXX (Directory).
      Phase 3 - Defines the ENF Datacom/AD datasets, initializes them and loads them.
      Phase 4 - Imports the ENF PLAN definitions for use with the CA Datacom SQL component.

  5. Run AD12STOP to shutdown the customized MUF.

  6. Update the CAIENF ENFPARM member to define an internal MUF or IMUF. Running the ENFPARM member as-is defaults to using an external MUF (i.e., XMUF).

  7. Update the appropriate startup procedure depending on whether you will be running either an internal MUF or and external MUF:

    1. ENFIMUF - Use JCL in this member to run ENF as an internal MUF inside the ENF address space.

    2. ENFXMUF - Use JCL in this member to run ENF as an external MUF which runs in its own address space external to ENF

  8. Start or Restart ENF

    • If you have defined an IMUF, starting the ENF will bring up CA Datacom/AD at startup.

    • If you have defined an external MUF, you must first start Datacom/AD before starting ENF. Use AD12STRT as a model.

    • NOTE: An IPL is required to start a new release of ENF if the previous release was already active since the last IPL.