Yes, Walt wisely points out that "no effect" is too severe, and yes, I went ahead and wrote the software and it works as intended. Another job can allocate the dataset I created with FREE=CLOSE while the creating program is still running.
My thinking now is that the note in the manual is simply superfluous. Of course FREE=CLOSE only frees up that one allocation, not every allocation in every step. At most the note should say something like what I just said in the previous sentence. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Black Sent: Friday, December 01, 2006 7:51 AM To: [email protected] Subject: Re: DD FREE=CLOSE -- when effective? > > 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 effect? FREE=CLOSE deallocates the dataset; if on tape, it frees the tape drive. It may not DEQ the dataset. > > > I am actually interested in using SVC 99 allocate with the FREE text unit > (whose documentation refers in turn to the restriction above). Am I correct > in assuming that (barring some other allocation of the dataset) that coding > this text unit will cause the dataset ENQ to be released when the dataset is > closed? If you had no other ENQ for the same dataset name in the job, then the ENQ will be released when the FREE=CLOSE is executed ---------------------------------------------------------------------- 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
