Getting an Endevor Natural Interface Error EINELIB8501

Products

• Endevor
• Endevor Natural Integration

Issue/Introduction

Natural programmers cannot Add new programs to EINE.  Getting the following error:

EINELIB8501   LFILE setting for EINE-MQ-FILE is not valid.

What is the issue and how to fix it?   

Environment

Release : All supported versions

Resolution

The most common cause is the Natural nucleus does not have the EINE file defined in it.

1)  Check if the EINE LFILE definitions are defined to the Natural nucleus by entering the SYSPROF command on the Natural command line.

        It will return the System Files defined to the nucleus and verify LFILE 125 and 126 are defined in the nucleus:

     NATURAL System File Assignments    
                                        
 File Name         DBID   FNR  Type    
 FUSER               ##   ###  ADABAS V8
 LFILE 125           ##   ###  ADABAS V8
 LFILE 126           ##   ###  ADABAS V8

 

2)  If the LFILEs are not defined --

     2.1)  Update the Natural nucleus and add the required NTLFILE statements

*-------------------------------------------------------------------*  
         NTLFILE 125,dbid,fnr                  EINE MSG QUEUE FILE      
         NTLFILE 126,dbid,fnr                  EINE SYSTEM FILE         
*-------------------------------------------------------------------*  

   

     2.2)  After regenerating the Natural nucleus, if using a Natural session under TSO, log off TSO and log back on.

             If running Natural under CICS, NEWCOPY the updated nucleus or shutdown and restart CICS.

 

 

3)  If the LFILEs are defined, verify that they are pointing the correct file numbers (FNR).

 

     3.1)   Check the EINE Server task and look for the SYSPROF display in CMPRT25 output.

              Verify that the Natural nucleus is pointing to the the same LFILEs that the EINE Server task is using:

File Name         DBID   FNR  Type        
File Name         DBID   FNR  Type        
File Name         DBID   FNR  Type        
FUSER               ##   ###  ADABAS V82  
LFILE 125           ##   ###  ADABAS V82  
LFILE 126           ##   ###  ADABAS V82  

 

     3.2)  If the DBID / FNR numbers are not the same, update the Natural nucleus to point to the correct DBID and file numbers and regenerate the Natural nucleus.

 

     3.3)  After regenerating the Natural nucleus, if using a Natural session under TSO, log off TSO and log back on.

             If running Natural under CICS, NEWCOPY the updated nucleus or shutdown and restart CICS.

 

     3.3)  If the DBID and FNR numbers are the same, open a Broadcom support case.