David, The second step seems to be a proc over ride statement. What does the SYSUT2 DD statement look like in the COPY Proc?
I would think that if there were an issue with CA1 then you would have more than one tape dataset getting expired and scratched like this. It is more likely that the way the job ran caused the tape to be scratched. The original output from the job would be so helpful in resolving this issue. However, since you no longer have that output, I am not sure what other steps could help identify the issue. Did you run the TMS AUDIT? If so, what did it show? Lizette > > Yes, I did notice that. > > Checking the jcl the first reference to the dataset in question is > > //M4OLD DD DSN=HLQ.PUBLIC.MASTER,DISP=(OLD,PASS,CATLG), > // UNIT=ETAPE,EXPDT=99000 > > The second reference is a Icegener > > //COPY.SYSUT2 DD DSN=HLQ.PUBLIC.MASTER,DISP=(OLD,KEEP) > > One would think Expdt=99000 should have been coded here but that is not the case. > > I'm sure that you noticed but the CRTDT changed with RGWOPMSC @ 2009142 > 20.18.36.15. It went from > CRTDT=09135 EXPDT=99000 at 20.18.01.43 to CRTDT=09142 EXPDT=00000 at > 20.18.36.15. And it looks like the same job? I don't know how to read DAF > but could a step in the job (SYSUT2) opened the tape for output and > changed TMS? > Just a thought > ---------------------------------------------------------------------- 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
