There doesn't appear to be a way to easily get around the 8 character dataset name (HLQ or node) limitation. It's a design scheme built into the heart of MVS that we all have to live with.
However, to extend the life of your numbering scheme ... Have you considered changing the numbering scheme from "decimal only" to either hexadecimal (allow 0...9 and A...F) or even something I call "Base36" (allow 0...9 and uppercase A...Z)? You'll get many more valid "numbers" to fit in a 6-char. field. All you need (That's easy for me to say ... :-) is to change the routine which determines the next number to use. Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of David McCrina Sent: Tuesday, November 09, 2010 4:12 AM To: [email protected] Subject: 8 character dataset nodes The discussion about the 7 character TSO ID limitation brings up something else I have wondered about. Why are TSO dataset nodes limited to 8 characters? We have a sequential number that is used as one node of dataset names with a two character prefix - xxnnnnnn, the assigned number is fast approaching 1 million so we are going to have to re-think the naming convention. What is the technical limitation of 8 character nodes? ---------------------------------------------------------------------- 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
