CAIENF initialization may produce the following error: DB02406I PXX END - invalid table name?

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

PROBLEM:

At CAIENF initialization,the  the following error messages are received:


ENF:DB00903I - OPENED, BASE - 15
ENF:DB00903I - OPENED, BASE - 700
ENF:DB02405I - PXX START ENF 61150 02(052) OPEN -700-
ENF: DB02406I PXX END - invalid table name


ENVIRONMENT:

z/OS, CA COMMON SERVICES 14.1, DATACOM 14.0, CA WORKLOAD AUTOMATION ESP R11.4 


CAUSE:

CA Workload Automation is being used as the scheduling package and no ENF Database (CA Datacom MUF) is necessary.


RESOLUTION: 

As a bit of background. Prior to Common Services r12.0, the ENF database was required regardless of the need for event recording.  This was due to the fact that the DCM definitions were stored in the database itself.  However, beginning with Common Services r12.0, this requirement was eliminated.

  • The DCM definitions and other ENF settings were moved to a PDS member of the CAIOPTN (r12.0) or CAW0OPTN (v14.0/r14.1) dataset
  • The legacy ENF database was eliminated and replaced by a Datacom MUF.

The two factors above allowed the use of the database to become optional.  However, many customers who upgrade from a release prior to Common Services r12.0 define the database due to the legacy requirement.

Additionally, not all CA Scheduling packages require event recording.  Products such as CA Scheduler, CA Jobtrac, and CA-7 are CA Products which may require event recording.  However there are also some that do not require it.  Therefore it is important for CA Support to know which CA Product is in use at your site and you should be prepared to provide this information.

In this case, however, CA Workload Automation ESP is being used as the scheduling package and no ENF Database (CA Datacom MUF) is necessary.
With this in mind, the CAW0PROC member ENF can be used.  This member does not reference the Datacom database at all.  You also need to use the following ENF parms:

  • NODB
  • RECORD(NO)
  • ARCHIVE parm is not needed if recording is not taking place.
    • comment out the statement itself
    • code ARCHIVE(OFF)

With the above  ENF parms in place, none of the before mentioned DATACOM messages will  be produced.

This is because a Datacom database will no longer be used.

ADDITIONAL INFORMATION: 

Additional information about the use and setup of the ENF database and the necessary parms can be found in the CA Common Services r14.1 Reference Guide.