> > > > > >Am I correct in assuming that does not mean what it > says; that what it > >should say is something like "Coding FREE=CLOSE has no > effect except when > it > >is coded in the last jobstep that refers to the dataset"? > > > > No. It means what it says. The ENQ is not released, > but the data set is > freed. This is useful in the case of SYSOUT, allowing > JESx to print it > immediately. I'm not sure, but I think it will cause > the tape drive to be > unloaded also. >
May I add to this with a real life example? We are running MICS jobs reading some 20 to 30 tapes sequentially from DDname INPUTSMF. The input process itself is taking about two hours. In the very same step the data are being processed further, this "processing further" taking another three to six hours. Since there are other jobs/applications that want to input the same data, I thought (erroneously as I learned from the discussion) that by adding FREE=CLOSE to the DD statement the dataset(s) would be available to those other jobs as soon as DDname INPUTSMF is closed. Would this be my own design, I'd consider splitting up the step in two pieces but it's MICS and I'm still in the learning phase (wonder whether that will change anytime soon ...) so this idea is not applicable. What options do I have? (environment is JES3 with z/OS 1.7) TIA Robert Bardos Ansys AG, Zürich, Switzerland ---------------------------------------------------------------------- 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
