Something similar was reported to me a few years back, when the folks involved couldn't find an explanation (It may have been the same message but I can't be sure). I found that the volume containing the Proclib had recently been made eligible for DFHSM migration and the Proclib was being migrated and recalled by DFHSM - not good. The I/O message was issued when the recall was triggered the first time the job ran and subsequently rerunning the job was successful because the Proclib was by then back on the original DASD volume. This was on z/os 1.4. Might be something worth checking - the rerunning of the job is no big issue but if this is the cause it could hurt you at IPL time one day.
Steve O. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
