The BCS itself is just another KSDS. The code directly accessing the BCS limits itself to using 45-byte keys. That is obviously part of what would have to change. The 45-byte catalog key (44 for DSN and 1 to indicate an extension record) is not dictated by some universal law. It is merely a number chosen to correspond with the 'standard' data set name length. One option that comes to mind is to utilize the extension byte values x'F1'-x'FF' in some manner. Another is to allow longer catalog keys.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Tuesday, December 15, 2009 9:43 AM To: [email protected] Subject: Re: Could DSNAME length restriction be bypassed if catalog allowed longer ALIAS names? How do you get around the 44 byte key length restriction (for compatability) on catalogs? <snip> I'm just throwing this idea on the table, and expect either little interest or strong opposition. What if catalog support allowed ALIAS names to exceed 44 characters? </snip> ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
