It took awhile but we found the culprit. One of my coworkers ran a compress against a production file during prime time.
That process is being reviewed and appropriate changes will go into place. Thanks everyone who helped me. I thought I knew, I just wasn't sure I knew. But I knew. ;-) Lizette > >On 9/1/2010 11:51 AM, Lizette Koehler wrote: >> I am not sure where to go with this abend. So if you could give me some >> pointers, that would be great. >> >> The errors are >> >> IEW4009I FETCH FAILED FOR MODULE MYLOAD01 FROM DDNAME STEPLIB BECAUSE OF AN >> I/O ERROR. >> IEW4005I FETCH FOR MODULE MYLOAD1 FROM DDNAME STEPLIB FAILED BECAUSE >> IEWFETCH ISSUED RC 0F AND REASON 40 >> CSV031I LIBRARY ACCESS FAILED FOR MODULE MYLOAD1, RETURN CODE 24, REASON >> CODE 26080021, DDNAME STEPLIB >> >> According to the return code/reason code, it is an I/O error on the PDS in >> the STEPLIB >> >> I looked at the library that holds this module and it is good. I browsed >> the library and module under ISPF and not I/O error messages occurred. I >> also browsed several other members to ensure I did not miss an error. >> >> I have not seen a compress or Endevor job run that updated or compressed >> this file. >> >> So, I need some next steps. I think if I have the STC cycled it should be >> okay. But at this time we have not cycled. >> >> Am I going in the right direction? > >Can you cause the STC to close and re-open the dataset? > >If not, try loading the module from a batch job to see >if it is ok? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
