IEW2747S D90C ABEND 013-18 OCCURRED WHILE PROCESSING SEQUENTIAL DATA SET WITH DDNAME SYSLIN.
IEW2230S 0414 MODULE HAS NO TEXT.
IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED.
The above messages are perfectly valid. However, what I could not believe is, there is actually a load module in the SYSLMOD dataset with the name HUH!
When I run AMBLIST on it, I get an RC of 8 and the message shown is,
Code:
AMB119I INVALID LOAD MODULE: NO CESD RECORDS FOUND ,LOAD MODULE MARKED EDITABLE
So, my question is, does IEWL still create a load module when SYSLIN does not point to a dataset? Has someone faced a similar problem? Is there a way to stop the creation of the SYSLMOD member in such cases?
(PS: I will be on a vacation for a week. So, I will not be able to respond until then.) _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
Posted: Mon Nov 08, 2004 9:34 am Post subject:
Cogito,
The easiest way to stop creating a execuetable load module from the link step is to add an additional step in there to perform a batch JCL CHECK of the link step. Since you are passing a member name that does not exist , the return code from the JCL CHECK will be 8. So you can skip the link step depending on the return code from the JCL check step.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
