CA ENF task getting CAS9340I error

Document ID : KB000004862
Last Modified Date : 28/03/2019
Show Technical Document Details
Issue:

Running ENF with a Datacom/AD database to record event activity. 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


Note: The event name displayed with the CAS9316E message may or may not be CABMSSTA.

Cause:

The CAS9304I message zeros in on the problem. 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 defined in the ENF STEPLIB concatenation. The ENF plan name may change at new release levels or introduced with an enhancement related PTF.

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)
  • CAS9ENFS.TRAN$ENF#15@0 ---> r15.0 base


Note: The introduction of a new ENF plan name would be identified via a PTF's ++HOLD information or within new release documentation. 

Resolution:
Import the new/missing ENF plan into the Datacom/AD database defined for ENF.

Method #1 - Running ENFIMUF (Datacom/AD MUF running within ENF address space)
  1. Start the ENF related Datacom/AD MUF in its own address space
    • Datacom provides a job a job in the INSTJCL library (eg. AD14STRT, AD15STRT)
    • Customize this job with the same Datacom libraries currently defined to ENF
  2. Import the new plan using updated CAW0JCL member AW1IMPRT
    • Be sure to define the same CUSLIB and CAAXLOAD libraries
    • Verify plan name on //SYSIN DD statement
    • Verify plan name in member referenced by //TRANSF DD
  3. Shutdown the Datacom/AD MUF 
  4. Start ENF

Method #2 - Running ENFXMUF (Datacom/AD MUF running enternal from ENF address space)
  1. Import the new plan using updated CAW0JCL member AW1IMPRT
    • Be sure to define the same CUSLIB and CAAXLOAD libraries as are defined in the Datacom/AD MUF running for ENF
    • Verify plan name on //SYSIN DD statement
    • Verify plan name in member referenced by //TRANSF DD
  2. Start ENF
Additional Information:

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

After installing RO54507 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 and importing a new plan. 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.

       

Note: Ensure the same CAW0LOAD used during the Import, is being used to start ENF. During the initial startup of ENF, the initialization code will re-define all Event Related tables with the expanded time column, TIMEL.