Yikes. What happens if "lots of GDG's" goes beyond the limit for the GDG? Lost data? How much data are we talking about here? Maybe just a new GDG by day, and keep modding onto it? Can the data be sorted down so that you can process oldest first?
_________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Tuesday, November 17, 2015 8:55 AM To: [email protected] Subject: Re: Fastest way to read OLDEST GDG entry So the intent is to create lots of GDGs throughout the day. Then the process needs to read the oldest GDG, process it, delete it, move on to the next oldest GDG. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Bill Ashton > Sent: Tuesday, November 17, 2015 5:21 AM > To: [email protected] > Subject: Re: Fastest way to read OLDEST GDG entry > > If the intention is to just delete the oldest generation, why not run > IEBGENER of a dummy file to create the new +1, and this will make the oldest > generation fall off. > Then you could run a job to delete the (0) generation. > > On Tue, Nov 17, 2015 at 6:26 AM, Elardus Engelbrecht < > [email protected]> wrote: > > > Lizette Koehler wrote: > > > > >I have a request to read the oldest GDG to process. > > > > I believe someone asked at SHARE, but my memory has been rolled out > > ala GDG... grrrrr.... > > > > Something like these: > > > > MY.GDG(LATEST) (same as (0) ) > > MY.GDG(OLDEST) > > MY.GDG(LATEST-7) > > MY.GDG(LATEST+1) (for creation of a new version of GDDG?) > > > > I tried this before posting on a GDG of 5 with JCL DD MY.GDG(-6). > > Only got a JCL error as documented... > > > > >But CSI is slow sometimes and better other times. > > > > Limiting the scope of CSI searches could speed things up, unless you > > want to do a big search. > > > > >So here is the basic request File lands as a GDG often The process > > >needs to read the oldest GDG and then delete it. > > >GDGs must be read in correct order for time/date processing > > > > >Or is there another way to handle this situation? I was going to > > >see if > > the LISTC could be faster than CSI. > > > > LISTC could be faster. Just use the First ASSOCIATIONS in GDG BASE output. > > > > But then wraparound of version numbers could be a problem. > > > > Groete / Greetings > > Elardus Engelbrecht > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
