Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
ERROR - NO ESD ENTRIES, EXECUTION IMPOSSIBLE while linkedit

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
Ashishpanpaliya

New User


Joined: 13 Oct 2017
Posts: 26
Location: India

PostPosted: Thu Jun 21, 2018 8:57 pm    Post subject: ERROR - NO ESD ENTRIES, EXECUTION IMPOSSIBLE while linkedit
Reply with quote

Hi ,

We have installed vanilla zD&T(IBM zOS cloud mainframe instance) on open stack.

I have written very simple cobol batch program to run it.

I am able to compile successfully but getting an error while doing linkedit.
I am using option 'Batch' available on ISPF for this which generate job to do compile and link edit.

Here is linkedit job
Code:
//LINK   EXEC  PGM=HEWLF064,REGION=2048K,COND=(12,LE),
// PARM=()
//SYSPRINT DD  SYSOUT=(*)
//SYSLIN   DD  DSN=ADCDA.SAMPLE.PDS1(CICSPGM),
//   DISP=SHR
//OBJECT   DD  DSN=ADCDA.SAMPLE.OBJ,
//   DISP=SHR
//SYSLIB   DD  DSN=ADCDA.SAMPLE.LOAD,
//   DISP=SHR
//SYSLMOD  DD  DSN=ADCDA.SAMPLE.LOAD(CICSPGM),
//             DISP=SHR,DCB=(BLKSIZE=3072)
//SYSUT1   DD  UNIT=SYSDA,SPACE=(CYL,(2,2)),DISP=NEW

copying sysprint message from jcl

Code:
DFSMS/MVS LINKAGE EDITOR   09:01:58  THU  JUN 21, 2018
JOB ADCDAABC   STEP LINK
INVOCATION PARAMETERS -   NONE
ACTUAL SIZE=(317440,79872)
OUTPUT DATA SET ADCDA.SAMPLE.LOAD IS ON VOLUME A3SYS1
IEW0302      CBL  AWO
IEW0302           IDENTIFICATION   DIVISION.
IEW0302           PROGRAM-ID.      CICSPGM.
IEW0302           AUTHOR.          Ashish Panpaliya.
IEW0302           DATE-WRITTEN.    15/06/18.
IEW0302           DATE-COMPILED
IEW0302          *************************************************************
IEW0302          * Sample  Program
IEW0302          *************************************************************
IEW0302           ENVIRONMENT DIVISION.
IEW0302           DATA DIVISION.
IEW0302           WORKING-STORAGE                                 SECTIO
IEW0302           PROCEDURE DIVISION.
IEW0302           PROG-CONTROL                   SECTION.
IEW0302               DISPLAY 'First Program'.
IEW0302               EXIT.
IEW0302               STOP RUN.
IEW0123
 
                                             DIAGNOSTIC MESSAGE DIRECTORY
   IEW0302 ERROR - INVALID STATEMENT -- SCAN TERMINATED.
   IEW0123 ERROR - NO ESD ENTRIES, EXECUTION IMPOSSIBLE.


Edited by moderator to remove excessive blank lines and to use the code tags.
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8391
Location: Dubuque, Iowa, USA

PostPosted: Thu Jun 21, 2018 9:34 pm    Post subject: Reply to: ERROR - NO ESD ENTRIES, EXECUTION IMPOSSIBLE while linkedit
Reply with quote

You have managed to create a long post with almost no usable information in it.

First, learn to use the Code tag for computer output -- it preserves spacing and frequently spacing indicates where the issue is.

Second, you say
Quote:
I am able to compile successfully but getting an error while doing linkedit.
without stating precisely what "compile successfully" means -- did it get a 0 step condition code? did it get a 4 step condition code? did it get some other step condition code? did it generate output in ADCDA.SAMPLE.OBJ?

Third, the IEW0123 error message implies that either ADCDA.SAMPLE.OBJ is empty, or that it has no ESD entries (that is, it is not a good object module that can be used to generate a load module). Either way, this indicates that your compile was not as successful as you think.

Fourth, have you used the ISPF batch compile option successfully in the past? If not, why not try a compile process that you have used successfully in the past rather than going with something new?

Fifth, your posted JCL is suspect. LKED primary input is from SYSLIN, which you pointed to your SOURCE code instead of your OBJECT code (which probably explains the IEW0123 error message). //OBJECT is not a DD statement that the linkage editor / binder will use unless you have an INCLUDE OBJECT(........) in your SYSIN to the linkage editor / binder. SYSLMOD, SYSPRINT, SYSUT1 are all mandatory DD statements while SYSLIB is an optional DD statement, as is SYSIN.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 664
Location: The Universe

PostPosted: Thu Jun 21, 2018 9:46 pm    Post subject:
Reply with quote

  • You must compile the source program. The input to the Linkage Editor in the DD statement with DD name SYSLIN is the contents of the data set specified by the DD statement with DD name SYSLIN in the compiler JCL. It is not the source program.
  • The no esd message is the Linkage Editor telling you there was no valid object input.
  • Why are you using the Linkage Editor? It was replaced by the Binder more than 20 years ago! The Binder is faster, it does not have some silly restrictions the Linkage Editor has, and it may produce a load module that may load a tiny bit faster than the load module produced by the Linkage Editor.
Back to top
View user's profile Send private message
Ashishpanpaliya

New User


Joined: 13 Oct 2017
Posts: 26
Location: India

PostPosted: Thu Jun 21, 2018 11:13 pm    Post subject:
Reply with quote

Hi Robert,

Quote:
without stating precisely what "compile successfully" means -- did it get a 0 step condition code? did it get a 4 step condition code? did it get some other step condition code? did it generate output in ADCDA.SAMPLE.OBJ?

Yes, I got the maxcc zero on compilation job and object code is created.
Quote:
Third, the IEW0123 error message implies that either ADCDA.SAMPLE.OBJ is empty, or that it has no ESD entries (that is, it is not a good object module that can be used to generate a load module). Either way, this indicates that your compile was not as successful as you think.

Member is created but not sure how to verify wheteher object module good or not.
Quote:
Fourth, have you used the ISPF batch compile option successfully in the past? If not, why not try a compile process that you have used successfully in the past rather than going with something new?

as I said this a new zOS instance were setup and we are doing POC to proof that it can be use as alternative to current development process.
Quote:
You must compile the source program. The input to the Linkage Editor in the DD statement with DD name SYSLIN is the contents of the data set specified by the DD statement with DD name SYSLIN in the compiler JCL. It is not the source program.

I tried doing this and an got below error. copying snippet of error.
Also, tried to use Binder but its too failing.
Code:
IEW0222

IEW0222                 {           {          u                               \
IEW0222
IEW0222
IEW0123
IEW0143
                                             DIAGNOSTIC MESSAGE DIRECTORY
   IEW0222 ERROR - CARD PRINTED CONTAINS INVALID INPUT FROM OBJECT MODULE.
   IEW0123 ERROR - NO ESD ENTRIES, EXECUTION IMPOSSIBLE.
   IEW0143 ERROR - NO TEXT.

Error while using Binder option
Code:
IEW2456E 9207 SYMBOL CEESTART UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL CEEBETBL UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXBST3 UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXPRS UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXCMSG UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXDSP UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXTREC UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXRT1 UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL CEESG004 UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL IGZXBS61 UNRESOLVED.  MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8391
Location: Dubuque, Iowa, USA

PostPosted: Thu Jun 21, 2018 11:49 pm    Post subject:
Reply with quote

Quote:
Member is created but not sure how to verify wheteher object module good or not.
Browse it -- it contains 80-byte records starting with record identifiers (such as ESD, RLD, TXT).

The IEW0222 / IEW0123 / IEW0143 messages again indicate that you are not generating and using the object deck correctly. Run your compile again with the options LIST,DECK,NODLL,MAP to verify that you are generating an object deck. And browse the object deck to make sure that it has data in 80-byte records. If you have appropriate access on your system, you could run this job:
Code:
//JOBNAME JOB ...
//             EXEC     PGM=AMBLIST
//SYSPRINT     DD       SYSOUT=A
//OBJMOD       DD       DISP=SHR,DSN=ADCDA.SAMPLE.OBJ
//SYSIN        DD       *
    LISTOBJ         DDN=OBJMOD,
        TITLE=('OBJECT MODULE LISTING FOR MYJOB',25)
/*
If you don't have compile option DECK (or OBJECT) specified, you may well get a zero step condition code on the COBOL compile, but you won't get an object deck generated and hence you will NEVER be able to link (or execute) the module.

When you do your linkage edit / bind, you will need //SYSLIB DD DISP=SHR,DSN=CEE.SCEELKED (or whatever the LE linkage library is called on your system). The unresolved references are because you need to include LE modules and there's no source for them in your JCL.

Are you really sure you belong on this forum? The types of issues you are having indicate you may do better on Beginners and Students Forum as it is more oriented to people with the kinds of questions you have asked.
Back to top
View user's profile Send private message
Ashishpanpaliya

New User


Joined: 13 Oct 2017
Posts: 26
Location: India

PostPosted: Fri Jun 22, 2018 8:22 pm    Post subject:
Reply with quote

I created the loadlib as Library(PDSE) data type and job ran fine.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 664
Location: The Universe

PostPosted: Fri Jun 22, 2018 9:10 pm    Post subject:
Reply with quote

Thank you for letting us know.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Error while trying to open an AIX in ... amitc23 CICS 4 Tue Sep 04, 2018 12:15 pm
No new posts Error while initiation CICS program f... Ashishpanpaliya CICS 3 Mon Jul 16, 2018 5:12 pm
No new posts BAMAD file IO Error m1985nehal CICS 1 Fri May 25, 2018 11:51 am
No new posts DB2 Sql Error code -204 rohit_naidu DB2 5 Fri May 18, 2018 4:40 pm
No new posts Trap the jcl error message or maxcc i... ankita agarwal CLIST & REXX 5 Fri May 18, 2018 2:08 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us