Do you have the venerable PDS Command? It's on the Mods Tape if you need it. It's pretty good at validating load modules, You can use
VERIFY module-name (for one module) or VERIFY : (for the entire library) PDS Command cannot generally fix a broken module, but it can quickly tell you how pervasive the problem is. . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Lim Ming Liang <[email protected]> To: [email protected] Date: 05/11/2012 08:32 PM Subject: IEW4005I FETCH FOR MODULE Failed Sent by: IBM Mainframe Discussion List <[email protected]> Hi, I had quite a few similar error messages on load modules fetching problem on a same volume; DSINIT FROM DDNAME STEPLIB FAILED BECAUSE IEWFETCH ISSUED RC 0D AND REASON 00 On the System Messages manual; IEW4005I FETCH FOR MODULE program-name FROM DDNAME ddname FAILED BECAUSE IEWFETCH ISSUED RC return-code AND REASON reason code. Explanation: Fetch for the load module failed. The possible hexadecimal return codes and hexadecimal reason codes are as follows: Return Code Error Description 00 Processing completed normally. 0B Program check. 0C Not enough storage available. Reason Code Error Description 04 No storage for DATD 08 No storage for DEB 0C No storage for IOSB 10 No storage for EXTLIST 14 No storage for module *0D ** Bad record area. *What does this Bad record area means ? Does it mean the affected volume has an hardware issue ? What utility I can used to check the volume integrity ? The load modules library is corrupted ? But I can browse the Load dataset and members without any problem. Please advise. -- Regards Lim ML ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
