Beate, I think your term 'connection' is correct. I remember searching for similar problems, in batch that was, years ago, and the result was indeed some kind of 'connection' to the catalog record, that you could net get rid of by deallocating the GDG or the GDG member. Apparently ISPF Edit knows how to do this.
I will try to recall what I found then and where, but it is a long time ago. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Beate Kawelke Sent: Thursday, July 18, 2013 12:01 To: [email protected] Subject: Re: Relative generation - how to recognize new datasets under TSO Hi Elardus, I have coded FREE=CLOSE (DALCLOSE) and also checked with DDLIST that neither the GDG nor the dataset itself are allocated after the CLOSE. DALRTDSN shows that I always get the same DSN. Best regards, Beate > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Elardus Engelbrecht > Sent: Thursday, July 18, 2013 11:54 AM > To: [email protected] > Subject: Re: [IBM-MAIN] Relative generation - how to recognize new > datasets under TSO > > Beate Kawelke wrote: > > >I've been searching for hours but did not find a solution for the > following: During a TSO session, a user specifies a dataset name. He > may use a relative generation number (e.g., "MY.DSN(0)") and he may do > this several times, each resulting in a DYNALLOC (DALMEMBR set to the > generation number). When a new generation is created during the TSO > session, any subsequent DYNALLOC will NOT get this new dataset > because, as I read in one of IBM's manuals, at the first usage of a > GDG the operating system makes some sort of "connection" to make sure > that generation 0 is always pointing to the same dataset. While this > makes a lot of sense for batch jobs, it is not what I want in the above case. > > >Is there a way to "release" / "ignore" that connection (I have looked > through the DYNALLOC parameters, but to no avail) or do I have to go > through the catalog and use my own logic to determine the correct DSN? > ISPF Edit, much to my surprise, gets it right - if I specify > generation 0, the new dataset will be found. > > Where is your FREE statements when you're finished with a generation? > AFAIK, you should ensure you have no GDG allocated before attempting > to do a [new/another] DYNALLOC. > > Groete / Greetings > Elardus Engelbrecht > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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: INFO IBM-MAIN
