Previous Topic: CA Product DCM compatibility

Next Topic: Prepare for Component Tracing

Start CAIENF

If a CAIENF procedure is to be invoked as a started task, it must be copied to a valid system procedure library. The ID associated with the ENF started task must have a valid security OMVS segment defined.

Three sample procedures are provided for CAIENF. They are ENF, ENFXMUF, and ENFIMUF.

The JCL associated with the ENF procedure contains no references to CA Datacom/AD database data sets and should be used in conjunction with the CAIENF control option, NODB. At this point 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.

If you already installed the release of CA Datacom/AD being shipped with this version of CA Common Services from a prior version of CAIENF, then you need to import this releases version of the CAIENF plan into your existing CA Datacom/AD environment. Make sure to follow the directions in Customize an Existing CA Datacom/AD for CAIENF.

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