Have you just upgraded to Cobol 5.1 and now Endevor message: C1G0259E NO ESD RECORD FOUND IN DATASET SPECIFIED
search cancel

Have you just upgraded to Cobol 5.1 and now Endevor message: C1G0259E NO ESD RECORD FOUND IN DATASET SPECIFIED

book

Article ID: 28444

calendar_today

Updated On:

Products

Endevor Endevor Natural Integration Endevor - ECLIPSE Plugin Endevor - Enterprise Workbench CA 2E

Issue/Introduction

Upgrading to COBOL 5.1 and now received the C1G0259E NO ESD RECORD FOUND IN DATASET

Resolution

If you have just upgraded to Cobol 5.1 and are receiving the message :

C1G0259E NO ESD RECORD FOUND IN DATASET SPECIFIED

When attempting to do a footprint=create on the file being created in the //SYSLIN DD statement of the compile step please look at the DCB statement.

Example of JCL that will fail;

 

//SYSLIN   DD  DSN=&&SYSLIN,DISP=(,PASS,DELETE),
 //             UNIT=SYSDA,SPACE=(TRK,(3,5),RLSE),
 //             DCB=BLKSIZE=3120,
 //             MONITOR=&MONITOR,
 //             FOOTPRNT=CREATE      
Example that will work;
//SYSLIN   DD  DSN=&&SYSLIN,DISP=(,PASS,DELETE),
//             UNIT=SYSDA,SPACE=(TRK,(3,5),RLSE),
//             DCB=(RECFM=FB,LRECL=80,BLKSIZE=0,DSORG=PS),
//             MONITOR=&MONITOR,
//             FOOTPRNT=CREATE

 

The difference is in the DCB statements, the one that fails does not have the LRECL defined and due to an IBM problem the LRECL will be defined the same as the BLKSIZE which will cause Endevor to be unable to footprint it.

The quick solution is to update your processor as shown in the second example. The longer term solution is too contact IBM for the solution to have the temporary built with an LRECL of 80 in the compile step.