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?
Regards, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Tuesday, November 17, 2015 4:06 AM To: [email protected] Subject: Fastest way to read OLDEST GDG entry I have a request to read the oldest GDG to process. But CSI is slow sometimes and better other times. 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 I tried GDGORDER on the JCL for z/OS V2.1 and it works great on the Base. But using //DDSTMT DD DISP=SHR,DSN=GDDG(0),GDGORDER=FIFO does not seem to work. Is there another process that could be used to identify the OLDEST GDG for Input and then delete that GDG? Or is there another way to handle this situation? I was going to see if the LISTC could be faster than CSI. The process should be native to z/OS and not a vendor product. Or shareware/freeware is okay. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
