Wrong Symbols table (ESYMBOLS) used by Endevor

Products

• Endevor

Issue/Introduction

Changes were made to the  ESYMBOL table source. The table was compiled and linked. The link date in the member reflects the correct date. Endevor does not pick up the changed table. It still uses the old table.

Environment

Endevor all releases

Cause

The table was put in a Linklist dataset. LLA refresh was not done after the library was updated with the changed table member.

Resolution

If the updated table was put in a library that is in the Linklist. If the library is a PDS library not PDSE.  LLA refresh may not have been issued after the update.

In summary LLA stores the location of all its members. If the library is a PDS it would point to a old member if LLA refresh is not done.

To check if this is true, run a Endevor batch job using a STEPLIB pointing to the library.

This is an example:

//STEP1   EXEC PGM=NDVRC1,PARM=C1BM3000,DYNAMNBR=1500

//STEPLIB DD DISP=SHR,DSN=<pre1>.<pre2>.CSIQAUTU  
//SYSPRINT DD SYSOUT=*                                 
//C1PRINT  DD SYSOUT=*                                 
//C1MSGS1  DD SYSOUT=*                                 
//SYSPRINT DD SYSOUT=*                                 
//SYSOUT   DD SYSOUT=*                                 
//SYSABEND DD SYSOUT=*                                 
//BSTERR DD SYSOUT=*                                   
//EN$TROPT DD SYSOUT=*                                 
//BSTIPT01 DD *                                        
  PRINT ELEMENT XXXXXX                                 
  FROM ENVIRONMENT XXXX                                
       SYSTEM      XXXX                                
       SUBSYSTEM   XXXX                                
       TYPE        XXXX                                
       STA         X                                   
  TO DDNAME C1PRINT                                    
               .  

In the above example change the Steplib to the library in the Linklist. The batch job with a steplib will bypass LLA. The above job will fail but will produce an options trace.

Check the options trace for the table data/link date. If the batch job shows the correct table then do a LLA refresh for the library.