Previous Topic: Configure the CAIENF JCL for finding CA product DCMsNext Topic: Prepare for Component Tracing


Invoke CAIENF as a Started Task

Follow these steps:

  1. Copy CAIENF to a valid system procedure library. The ID associated with the CAIENF started task must have a valid security OMVS segment defined.

    Since CAIENF services multiple applications and tasks, the CAIENF dispatching priority must be greater than or equal to the highest dispatching priority of any task requesting CAIENF services.

    Note: The JCL associated with the ENF procedure contains no references to CA Datacom/AD database data sets and is used with the CAIENF control option, NODB. Now in the configuration of CAIENF, only the ENF procedure is valid to start CAIENF.

    The other two procedures ENFXMUF and ENFIMUF, are only valid after the installation of CA Datacom/AD and the configuration of CA Datacom/AD for CAIENF.

  2. (Optional). If you already installed the release of CA Datacom/AD being shipped with this version of CCS from a prior version of CAIENF, import the version of the CAIENF plan from this release into your existing CA Datacom/AD environment. Follow the directions in Customize an Existing CA Datacom/AD for CAIENF (Customize an Existing CA Datacom/AD for CAIENF, (Optional) Customize an Existing CA Datacom/AD for CAIENF).

Important! If you are currently running a lower version level of CAIENF, an IPL is necessary before bringing up CAIENF using the new libraries.

(Optional) Customize an Existing CA Datacom/AD for CAIENF

Important! Do not perform these steps until you are ready to implement the version of CAIENF for this release.

Follow these steps:

  1. Shut down the older version of CAIENF.
  2. If not already started, start DATACOM/AD external to CAIENF.
  3. IMPORT the new CAIENF plan into DATACOM/AD by editing and submitting CAW0JCL member AW1IMPRT.
  4. IPL the system.
  5. Start the new release of CAIENF.