IBM is already supplying the process to read the oldest or the newest with GDGORDER=LIFO or GDGORDER=FIFO. I am just asking that they allow the GDGORDER to pick up the GDG relative number where GDGORDER is specified (LIFO is the default so -1, -2 would behave the same). I am asking if GDGORDER=FIFO is specified, that it also be used with the relative gen number.
So with John's example G0001V00 - G0007V00. //GDGDD DD DISP=SHR,DSN=GDGBASE(0) = G0007V00 //GDGDD DD DISP=SHR,DSN=GDGBASE(-1) = G0006V00 //GDGDD DD DISP=SHR,DSN=GDGBASE(0),GDGORDER=FIFO = G0001V00 //GDGDD DD DISP=SHR,DSN=GDGBASE(-1),GDGORDER=FIFO = G0002V00 I did not ask for a new way to specify the Relative Gen number. So I would expect the user would need to be careful when reading oldest to youngest. Same errors should occur should a user ask for the GDGORDER=FIFO with -3 and -3 does not exist. and so on. GDGORDER only reads the base backwards. I wanted something that could target a relative GDG Number forwards or backwards. I did open a case to IBM on this, and they suggested the RFE since they liked the idea. Lizette -----Original Message----- >From: "J. P." >Sent: Jan 12, 2016 1:06 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: RFE to enhance GDGORDER in JCL > >You are asking IBM to provide a new access method to read the file(s) backward >with your request. And there is no guarantee that the actual access method >invoked by the program(s) involved will be compatible with your new backwards >access method (lets call it LBAM, shall we?). For example, the program might >be written to use BSAM (or even EXCP) while your new LBAM is only setup to >support QSAM. > >Your request is not going to end well. > >J.P. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
