Lizette, I checked the dsn is a PDS. That's why I have been honing on to type 14,15, & 17.
Lizette Koehler <[EMAIL PROTECTED]> wrote: I had a similar issue with a deleted dataset. Turned out I had to go back 3 weeks to find the job that had deleted it. I knew it was a nonvsam data set so I just scanned the 14, 15, 17, 18 records. The 60 records are needed if it is VSAM. What happened was a batch job had failed to code the JCL properly. Had a blank after the data set name and before the DISP parm. //STEPLIB DD DSN=prod.data.set.name ,DISP=SHR When this job ended the data set will be deleted as soon as the other enqueues against it were gone. This took 3 weeks (this was an IMS RESLIB data set). Next thing we knew, IMS would not come up because this file had been deleted. So, have you gone far enough back in the SMF data to find the culprit. Lizette >> >> Anybody can suggest that there is something else I could try? > >Wille - we also have a SAS job that we use to find out such information. > >Here we also check record types of 17, 18, 61, 62, 64, 65, and 66. > ---------------------------------------------------------------------- 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 --------------------------------- Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. ---------------------------------------------------------------------- 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
