I agree entirely. I understand the 255 limit in the past when all we had were CVOL catalogs and a 1 byte field. ICF catalogs don't work that way. And, again, the reverse order made sense in the days of CVOL due to the way that GDGs were actually implemented in CVOLs. Again, ICF catalogs don't work that way. But I wonder what the JCL syntax would be to specify the order. Hopefully something simple.
But since GDG-ALL processing effectively creates a concatenated set of DDs, what about the limit of 255 DDs per jobstep? How to do GDG-ALL of a DSN with 1000 entries? On Fri, 2011-07-22 at 22:07 -0700, Ed Gould wrote: > John: > > I think a prime requirement is to support more than 255 GDG entries and also > a > way to call them in order they were created. > > Ed > -- John McKown Maranatha! <>< ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
