On Tue, Nov 17, 2015 at 7:49 AM, Greg Shirey <wgshi...@benekeith.com> wrote:
> Why does the process need to delete the oldest GDG after it reads it? > Won't the oldest one be deleted when the next +1 GDG is created? > Not necessarily. That only happens if the number of GDGs which are "rolled in" are at the limit. It might be interesting to understand _exactly_ what the OP is trying to accomplish by reading in the "oldest" GDG and exactly how said generations are being created. I don't know why the OP says that IGGCSI00 is "slow". I may, when I feel better, look at writing a C program which uses IGGCSI00 to do "something or other" like this. Another thought, from way out in left field, is to create a SUBSYS=, say called LGDG, which would do exactly what the OP wants. Something like: //SYSUT1 DD SUBSYS=(LGDG,'gdg.base.name') which looks up "gdg.base.name" and then allocates the generation (SVC 99) with the lowest generation number. Of course, this does not allow the deletion of said GDG. But that could possibly be done with other options. > > Regards, > Greg Shirey > Ben E. Keith Company > -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
