I do not know if this will help, but at CBTTAPE.ORG FILE 929 has a REXX function that could be of use.
gds = REALNAME(the.gdg.name(+1)) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Kirk Wolf Sent: Thursday, May 26, 2016 9:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Proper way to resolve existing GDG GnnnVnnn by relative reference catsearch just prints output in the order received from IGGCSI00. I have confirmed that LOCATE resolves existing relative GDG references correctly. Kirk Wolf Dovetailed Technologies http://dovetail.com On Thu, May 26, 2016 at 8:18 AM, John McKown <john.archie.mck...@gmail.com> wrote: > On Wed, May 25, 2016 at 6:37 PM, Lizette Koehler > <stars...@mindspring.com> > wrote: > > > John, > > > > Would this code account for a V01 - V99 ending in the GDG? > > And would it handle the fact that the next GDG might not be a > > G9999Vxx > but > > maybe a G0001Vxx? Remember GDG numbers at the back can wrap a > > little differently. A -1 might not be what you think it might be. > > > > I think, there is some ambiguity regarding the correct chronological > order > > in the GxxxxVxx numbers over 9000. > > > > Lizette > > > > Very good points. I don't know how catsearch works internally, so I > don't know how the output is ordered. My code assumes that the entries > are ordered correctly in that the "newest" is at the bottom (last > emitted), the "oldest" is at the top (first emitted), and each > generation is "in the proper order". The egrep stage could be changed > to accept other than V00 at the end by doing: > > egrep '^HLG\.GDG\.G[0-9]{4}V[0-9]{2}$' > > I didn't think of that because in 35 years, I have _never_ seen > anything other than V00 at the end. > > > -- > The unfacts, did we have them, are too imprecisely few to warrant our > certitude. > > Maranatha! <>< > John McKown > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
