CA ENF task getting CAS9340I error

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

You have upgraded to CA Common Services r14.1 S1401 from either a previous release (eg. r12.0 or r14.0) or from r14.1 0000, and you are running ENF with a Datacom/AD database. When the ENF address space starts and goes through initialization the following messages are generated and the address space terminates with a U203 abend.

CAS9217I - ENF DB initialization starting 

CAS9243I - Internal database in use

ENF:DB00133I - JOB OPEN ENF 69750 ENF STC18666

ENF:DB00135I - CONNECT TO ENF ENFX STC18666 HTSX M-14.0 I-14.0 0001

ENF:DB00101I - STARTED JOB-ENF NUMBER-69750 CXX=ENFX MUFNAME=ENFX

CAS9337I - DBC/API initialized successfully.

CAS9316E - CABMSSTA "Describe" failed - rc(-124) r/s(X'F5F1F0F0F2').

CAS9340I - PLAN CAS9ENFS.TRAN$ENF#14@1B DOES NOT EXIST .

CAS9203E - CA-ENF Initialization error - terminating

ENF:DB00239I - MUF TERMINATION, START SYSTEM ABEND

ENF:DB00289I - CXX ESTAE UPDATES STARTED

ENF:DB00289I - CXX ESTAE UPDATES COMPLETED WITH ERRORS 

ENF:DB00204I - MULTI-USER ABENDED

IEF450I ENF ENF - ABEND=S000 U0203 REASON=00000008

IEF404I ENF - ENDED

Cause:

The messages of concern are:

CAS9316E - CABMSSTA "Describe" failed - rc(-124) r/s(X'F5F1F0F0F2').

CAS9340I - PLAN CAS9ENFS.TRAN$ENF#14@1B DOES NOT EXIST .

 

The message that zeros in on the problem is the PLAN that does not exist. This is an indication that the specified PLAN was not imported into the Datacom/AD database being referenced by this ENF startup. The database that ENF references is determined by the Datacom CUSLIB that is defined in the ENF STEPLIB concatenation. The particular plan shown on the CAS9340I message was introduced with an enhancement delivered with ENF PTF RO54507.

Here are some of the PLAN names that have existed and what they are related to.

 

CAS9ENFS.TRAN$ENF -------> r14.0 base

CAS9ENFS.TRAN$ENF#14@0 --> r14.0 and PTF RO44982 (add support for Datacom v14)

CAS9ENFS.TRAN$ENF#14@1 --> r14.1 base

CAS9ENFS.TRAN$ENF#14@1B -> r14.1 and PTF RO54507 (ENF is enhanced to provide a more granular TIME field)

 

So if this was simply a matter of a missing plan the AW1IMPRT job provided in the CA Common Services CAW0JCL library could be run to import the missing plan into the database. Since we can see that the missing plan is associated with RO54507 we can refer to this PTF for any special instructions that need to be followed.

Resolution:

The following steps were provided as ACTION HOLDDATA within PTF RO54507.

 

After installing this PTF along with its co-reqs into your running ENF datasets, you must implement the PTF by DROPping

all the DATACOM/AD ENF Event related tables.

The PTF associated with this change also includes an update to the CAS9DBC module and corresponding Plan.  Therefore,          

the new Plan must also be imported.  Follow the steps below-       

                                                                   

NOTE: ENF must be down when the following procedure is performed.  

                                                                   

1.      Start the ENF related Datacom/AD MUF in its own address space.

2.      Obtain a list of ENF Event tables by submitting CAW0JCL member CASQL001.

3.      Edit CAW0JCL member CASQL004 with the list of tables obtained from the previous step to be dropped and then run job CASQL004.

4.      Import the new plan using updated CAW0JCL member AW1IMPRT. 

5.      Shutdown the MUF if you normally run an ENFIMUF.

6.      Re-start ENF with the REINIT parm (i.e. S ENF,,,REINIT) making sure that the CAIDCM DD statement is using the CAW0DCM dataset with the PTF'ed DCM modules.

       

Confirm that the same CAW0LOAD used during the Import, is being used to start ENF. At ENF start-up, ENF initialization

code will re-define the Event Related tables with the expanded time column, TIMEL.