In a recent note, Mark Thomen said: > Date: Fri, 4 Aug 2006 14:15:01 -0700 > > > > //VSEDSN DD DSN='My Payroll file',DISP=OLD, > > // VOL=SER=SHRD01,UNIT=2314,.... > > Sorry - CATALOGUED data sets do not support lower case. Yes, you can > create funky data set names on your VTOCs, but there may be other issues > you'll have to deal with - vendor products, IBM components, etc. > So, the question becomes, why do catalog services impose syntactic restrictions beyond those of the core data management? I know part of the answer: use of the CKD facilities to search is^H^H was a rationale for the restriction to <=8-character index levels. But where's the rationale for upper case only? Can't the SEARCH KEY channel commands operate as readily on lower case as on upper?
-- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
