Re: DD FREE=CLOSE -- when effective?
In [EMAIL PROTECTED], on 11/29/2006 at 01:04 PM, Charles Mills [EMAIL PROTECTED] said: 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. Tom is correct. 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 it's not specified in a subsequent step. In [EMAIL PROTECTED], on 11/30/2006 at 09:37 AM, Charles Mills [EMAIL PROTECTED] said: I would suggest that the following phrase may not be perfect, but it is at least closer No; it has a more serious error than the existing text. Coding FREE=CLOSE has no effect except when it is coded on all DD statements (or the only DD statement) in the last jobstep that refers to the dataset. The problem with that is that it *does* have an effect. I understand and appreciate your pointing out the other factor which I had not considered: FREE=CLOSE in any event releases the *allocation* (the DD statement has gone away) even if the ENQ is not released due to other allocations that may be in effect. Which is why your suggested text is wrong. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: DD FREE=CLOSE -- when effective?
When I asked about options to free datasets that were no longer used halfway down a very long running SMF-processing NeuMICS (and therefore SAS) job step, Ed Gould wrote: The problem I think is with SAS (design issue?) . I believe that with any other application when you get to the the end of input you would reasonably close the data set. But I am guessing that SAS does not close the input until it has completed processing . I am not familiar with MICS but perhaps it would be faster to strip out the SMF records its needs (Type xx etc). This can be done with IFSADMP or any other utility (perhaps SORT or ICETOOL with IF control cards which certainly be a lot faster). If MICS needs ALL SMF records then I would guess you are stuck. Ed, thanks for replying. As far as SAS is concerned I know that I can free allocations using either filename dd-name clear; /* when referring to non-SAS datasets */ or libname dd-name clear;/* when referring to SAS libraries */ From the discussion in this thread however it seems that deallocating the input tape dataset (which consists of only the DB2 SMF records in this case) will not buy me anything when my prime target is to free the enqueue and not to hold the dataset until all the time consuming data aggregation has been done. I'm still hoping that I get this wrong and that infact using something like //INPUTSMF DD DISP=OLD,DSN=THE.DB2.SMF.DATA MICS input processing here filename inputsmf clear;/* point A */ further MICS processing here further processing done /* point B */ would free THE.DB2.SMF.DATA (which is not being used in other steps) for other jobs. Can anybody confirm in simple words at what point in my example the dataset (which is on tape) can be used by other jobs? Is it at point A or at point B? Thanks again 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
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 -- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: [EMAIL PROTECTED] sales info: [EMAIL PROTECTED] tech support: [EMAIL PROTECTED] web: www.innovationdp.fdr.com -- 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
Re: DD FREE=CLOSE -- when effective?
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: IBM-MAIN@BAMA.UA.EDU 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
Re: DD FREE=CLOSE -- when effective?
In a recent note, Charles Mills said: Date: Fri, 1 Dec 2006 10:14:56 -0800 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. Peraps the manual is oversimplifying. I believe that technically only the active step can have any allocations, so there are no allocations to FREE in any other step. Meanwhile the initiator holds any ENQs, at least for DD statements in JCL. So I suspect that there's some communication such as Allocation tells initiator, Hey, I just FREEd dsname SUCH.AND.SUCH, so you can DEQ it! But initiator looks around and thinks, No, I can't because it's used elsewhere in JCL. Don't anthropomorphize computers -- they hate that. -- gil -- StorageTek INFORMATION made POWERFUL -- 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
What allocate means (Was RE: DD FREE=CLOSE -- when effective?)
So we use allocate(d) in at least three related but distinct senses: - The dataset is allocated to DD name XXX. - The dataset is allocated to job YYY (but to a step that is not yet running, or which has already completed, so there is no DD name to which it is allocated) - And of course, the sense of space allocation. The 5 cylinder dataset is allocated to DD XXX, but the space has not yet been allocated. This is not claimed to be some brilliant discovery on my part; I'm just prattling. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Friday, December 01, 2006 10:27 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DD FREE=CLOSE -- when effective? I believe that technically only the active step can have any allocations, so there are no allocations to FREE in any other step. -- 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
Re: DD FREE=CLOSE -- when effective?
Don't anthropomorphize computers -- they hate that. My ex used to hate that, too. Now my boys are doing it; she's complaining to them about it. Is it a guy thing? I've heard other women complain about this. When in doubt. PANIC!! -- 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
Re: DD FREE=CLOSE -- when effective?
On Wed, 29 Nov 2006 13:04:06 -0800, Charles Mills wrote: The z/OS 1.7 JCL reference says Note: Specifying FREE will not release the enqueue on the data set until the last step that requires the data set completes processing. 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. -- Tom Marchant -- 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
Re: DD FREE=CLOSE -- when effective?
Well, the code is now working and the answer is Yes, the ENQ ***is*** released. I am allocating a dataset with SVC 99 DISP=NEW and FREE=CLOSE, and writing into and the closing it. Then I am submitting a job that allocates the dataset with JCL DISP=SHR and waiting for the job to run -- and it all works as intended. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Thursday, November 30, 2006 5:54 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DD FREE=CLOSE -- when effective? 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 -- 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
Re: DD FREE=CLOSE -- when effective?
Because (as I said in the OP) the documentation for SVC 99 DALCLOSE in z/OS 1.7 Authorized Assembler Services Guide says See the description of FREE=CLOSE in z/OS MVS JCL Reference for restrictions on the FREE parameter. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Vernooy, C.P. - SPLXM Sent: Thursday, November 30, 2006 12:10 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DD FREE=CLOSE -- when effective? I am not sure what you mean with the last sentence, I think you confuse two different beasts: You quoted the JCL reference and for allocations done in JCL and the statement is 100% correct, because that is how JCL allocation works. If you dymamically allocate the datasets, you should not look in the JCL reference for the working of Dynalloc's FREE=CLOSE. -- 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
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. 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
Re: DD FREE=CLOSE -- when effective?
Ok, that part looks incorrect. Kees. Charles Mills [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Because (as I said in the OP) the documentation for SVC 99 DALCLOSE in z/OS 1.7 Authorized Assembler Services Guide says See the description of FREE=CLOSE in z/OS MVS JCL Reference for restrictions on the FREE parameter. Charles ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- 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
Re: DD FREE=CLOSE -- when effective?
On 11/30/2006 9:18 AM, Charles Mills wrote: Well, the code is now working and the answer is Yes, the ENQ ***is*** released. I am allocating a dataset with SVC 99 DISP=NEW and FREE=CLOSE, and writing into and the closing it. Then I am submitting a job that allocates the dataset with JCL DISP=SHR and waiting for the job to run -- and it all works as intended. That's because, with your use of DYNALLOC, you are running in the last jobstep that needs the data set. The case the book is documenting is: //S1 EXEC PGM=P1 //DD1 DD DSN=dsname1,DISP=SHR,FREE=CLOSE //S2 EXEC PGM=P2 //DD2 DD DSN=dsname1,DISP=SHR,FREE=CLOSE //S3 EXEC PGM=P3 //DD3 DD DSN=dsname2,DISP=SHR If P1 in step S1 CLOSEs DD1, then the data set is deallocated from S1, and P1 can not do another OPEN for DD1. However, as S2 needs dsname1, too, the ENQ is not released. If P2 in step S2 CLOSEs DD2, then the data set is deallocated from S2, and P2 can not do another OPEN for DD2. As dsname1 is not needed by any subsequent jobsteps, the ENQ is released as part of the CLOSE/FREE processing, and the data set is available to other jobs before S2 ends. Walt -- 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
Re: DD FREE=CLOSE -- when effective?
Walt, thanks. I would respectfully suggest that the JCL Ref is wrong and should be changed. Yes, in both cases, the program in question is the last step that needs the DS but that's kind of an imprecise and circular definition. I would submit that the phrase in the JCL Ref, which I quote here exactly, is wrong: Note: Specifying FREE will not release the enqueue on the data set until the last step that requires the data set completes processing. The whole point of FREE is that it releases the allocation BEFORE the completion of processing. I would suggest that the following phrase may not be perfect, but it is at least closer (and I assume IBM has wordsmiths that could make it perfect if they chose): Coding FREE=CLOSE has no effect except when it is coded on all DD statements (or the only DD statement) in the last jobstep that refers to the dataset. That fits exactly with your example below. I understand and appreciate your pointing out the other factor which I had not considered: FREE=CLOSE in any event releases the *allocation* (the DD statement has gone away) even if the ENQ is not released due to other allocations that may be in effect. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Walt Farrell Sent: Thursday, November 30, 2006 8:47 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DD FREE=CLOSE -- when effective? On 11/30/2006 9:18 AM, Charles Mills wrote: Well, the code is now working and the answer is Yes, the ENQ ***is*** released. I am allocating a dataset with SVC 99 DISP=NEW and FREE=CLOSE, and writing into and the closing it. Then I am submitting a job that allocates the dataset with JCL DISP=SHR and waiting for the job to run -- and it all works as intended. That's because, with your use of DYNALLOC, you are running in the last jobstep that needs the data set. The case the book is documenting is: //S1 EXEC PGM=P1 //DD1 DD DSN=dsname1,DISP=SHR,FREE=CLOSE //S2 EXEC PGM=P2 //DD2 DD DSN=dsname1,DISP=SHR,FREE=CLOSE //S3 EXEC PGM=P3 //DD3 DD DSN=dsname2,DISP=SHR If P1 in step S1 CLOSEs DD1, then the data set is deallocated from S1, and P1 can not do another OPEN for DD1. However, as S2 needs dsname1, too, the ENQ is not released. If P2 in step S2 CLOSEs DD2, then the data set is deallocated from S2, and P2 can not do another OPEN for DD2. As dsname1 is not needed by any subsequent jobsteps, the ENQ is released as part of the CLOSE/FREE processing, and the data set is available to other jobs before S2 ends. Walt -- 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 -- 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
Re: DD FREE=CLOSE -- when effective?
On 11/30/2006 12:38 PM, Charles Mills wrote: Walt, thanks. I would respectfully suggest that the JCL Ref is wrong and should be changed. Yes, in both cases, the program in question is the last step that needs the DS but that's kind of an imprecise and circular definition. I would submit that the phrase in the JCL Ref, which I quote here exactly, is wrong: Note: Specifying FREE will not release the enqueue on the data set until the last step that requires the data set completes processing. The whole point of FREE is that it releases the allocation BEFORE the completion of processing. I would suggest that the following phrase may not be perfect, but it is at least closer (and I assume IBM has wordsmiths that could make it perfect if they chose): Coding FREE=CLOSE has no effect except when it is coded on all DD statements (or the only DD statement) in the last jobstep that refers to the dataset. That fits exactly with your example below. I understand and appreciate your pointing out the other factor which I had not considered: FREE=CLOSE in any event releases the *allocation* (the DD statement has gone away) even if the ENQ is not released due to other allocations that may be in effect. But saying FREE=CLOSE has no effect is just wrong. It always releases the allocation, and conditionally releases the ENQ. The text you quoted is correct. It simply does not address the situation you were wanting an answer for. That does not make it incorrect, though you could argue it is incomplete as it missed an aspect that was important to you. Feel free to submit a Reader's Comment, but please keep the above in mind if you suggest a specific change. It might be better to tell them the situation they did not cover, and let them figure our how to add doc for that one. Walt -- 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
Re: DD FREE=CLOSE -- when effective?
Robert, The problem I think is with SAS (design issue?) . I believe that with any other application when you get to the the end of input you would reasonably close the data set. But I am guessing that SAS does not close the input until it has completed processing . I am not familiar with MICS but perhaps it would be faster to strip out the SMF records its needs (Type xx etc). This can be done with IFSADMP or any other utility (perhaps SORT or ICETOOL with IF control cards which certainly be a lot faster). If MICS needs ALL SMF records then I would guess you are stuck. Ed On Nov 30, 2006, at 8:24 AM, Robert Bardos wrote: 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 -- 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
DD FREE=CLOSE -- when effective?
The z/OS 1.7 JCL reference says Note: Specifying FREE will not release the enqueue on the data set until the last step that requires the data set completes processing. 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? 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? Charles Mills +1-707-291-0908 -- 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
Re: DD FREE=CLOSE -- when effective?
In a word, yes. Christopher Y. Blaicher BMC Software, Inc. Austin Development Labs (512) 340-6154 The comments made are my personal opinions. BMC Software, Inc. makes no representations or promises regarding the reliability, completeness, or accuracy of the information provided in this discussion; all readers agree not to rely on this information or take any action against BMC Software in response to this information. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Charles Mills Sent: Wednesday, November 29, 2006 3:04 PM To: IBM-MAIN@BAMA.UA.EDU Subject: DD FREE=CLOSE -- when effective? The z/OS 1.7 JCL reference says Note: Specifying FREE will not release the enqueue on the data set until the last step that requires the data set completes processing. 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? 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? Charles Mills +1-707-291-0908 -- 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 -- 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
Re: DD FREE=CLOSE -- when effective?
In a word, Thanks. That's what I assumed; nothing else would make much sense. But I wanted to ask here before I wasted any more coding effort. Gee, you'd think after 40 years they could get the documentation to say what they mean. What it says is different from what they mean. We're in a business where one bit differences matter. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Blaicher, Chris Sent: Wednesday, November 29, 2006 3:07 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: DD FREE=CLOSE -- when effective? In a word, yes. Christopher Y. Blaicher BMC Software, Inc. Austin Development Labs (512) 340-6154 The comments made are my personal opinions. BMC Software, Inc. makes no representations or promises regarding the reliability, completeness, or accuracy of the information provided in this discussion; all readers agree not to rely on this information or take any action against BMC Software in response to this information. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Charles Mills Sent: Wednesday, November 29, 2006 3:04 PM To: IBM-MAIN@BAMA.UA.EDU Subject: DD FREE=CLOSE -- when effective? The z/OS 1.7 JCL reference says Note: Specifying FREE will not release the enqueue on the data set until the last step that requires the data set completes processing. 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? -- 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
