Endevor failing to allocate the type sequence table during initialization

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

At the start of an Endevor batch run, the following messages may show up in the C1MSGS1 report

 

B1TS003S  TYPE SEQUENCE FILE ALLOCATION FAILED, RC=000C (HEX)
C1G0055E  DATASET UPRFX.UQUAL.PARMLIB - ALLOCATION FAILURE
B1TS011E  TYPE SEQUENCE TABLE HAS ERRORS ON DSN=UPRFX.UQUAL.PARMLIB MBR=GLBLTYPE
B1TS012E  TYPE SEQUENCE PROCESSING IS NOW DISABLED.
 

 

 

Cause

During initialization, Endevor fails to allocate the member that contains the type sequence definition, which is defined in the C1DEFLTS table parameters:

• PARMLIB - Name of the library containing the member
• TYPESEQMBR - Name of the member

The messages show the names coded in the C1DEFLTS table. In the above example, it is meaningful that UPRFX.UQUAL.PARMLIB and GLBLTYPE are the names contained in the factory-default table shipped with the product

Resolution

Ensure that the job is loading the correct C1DEFLTS table.

• The table must be assembled and cataloged in the CSIQAUTU library
• The JCL has to allocate the right CSIQAUTU library in STEPLIB DD
• An ENUXSITE user exit might be instructing Endevor to load a module other than C1DEFLTS
• The factory-default ENUXSITE reacts to the presence of ddname EN$DFTxx causing Endevor to load module C1DEFLxx

To see the C1DEFLTS table being used, take an Endevor options report by adding the following DD to the JCL (at the step that runs program NDVRC1)

//EN$TROPT DD SYSOUT=*,SPIN=NO

The options report shows the module name and the assembly date of the table which may help to understand where it comes from.