Mike, TSO cannot do a +1 (I also think ISPF 3.2 cannot do a +1 either). It can only do (0). You would have the create a specific GDG number for TSO to use for this type of process form within a CLIST/REXX. I am not sure what BPXWDYN would do for a +1 allocation.
I might recommend to FREE the DD and FREE DSN to see if TSO will see the next GDG created under (0) Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mike Schwab Sent: Thursday, July 18, 2013 9:43 AM To: [email protected] Subject: Re: Relative generation - how to recognize new datasets under TSO I think the TSO FREE would change the relative GDG number. Define a GDG. Write a small Clist. Allocates new HLQ.GDG(+1), writes a record into the dsn, FREEs it, Allocates old HLQ.GDG(+1) input to read and display the text. Probably the Allocate (+1) will error and has to Allocate (00) to read it. On Thu, Jul 18, 2013 at 11:20 AM, Paul Gilmartin <[email protected]> wrote: > On Thu, 18 Jul 2013 06:31:14 -0500, Norbert Friemel wrote: >> >>http://www-01.ibm.com/support/docview.wss?uid=isg1II08285 >> >>"Note: Dynamic allocations can turn on bit S99GDGNT to bypass >> using the table and thus always locate the current entry >> (generation 0) at the time of the allocation. This allows >> them always to know the current generation, even when this >> job (or another job), running on the same system (or a >> different system, as long as the catalog is shared between >> systems) has added generations since this job began." >> > Is this available as an option in either TSO ALLOCATE or BPXWDYN? > > -- gil > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
