John, Excellent Question:
The master catalog holds aliases in two records 1) for the absolute aliases and 2) for the Relate to the UserCat. I am researching on which one filled up. So simply adding more UCATS would take care if the second issue. But what about the first alias entry record. Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, April 26, 2006 11:57 AM To: [email protected] Subject: Re: Master Catalog maxed out w/19k Alias. > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Clark, Kevin D, > HRC-Alexandria/EDS > Sent: Wednesday, April 26, 2006 10:47 AM > To: [email protected] > Subject: Master Catalog maxed out w/19k Alias. > > Hello all, > > I have a current work around for this issue : (delete all > unused aliases > around 10k.) > > My question(s) : What if I had 19K active TSO users. Say 30,000. > > My Coworker says that we would have to reengineer our dataset naming > standards and make TSO alias another qualifier other the HLQ. > > So: DSN= TSO.TSOU002.JCL.CNTL. Would be required, instead of > TSOU002.JCL.CNTL. > > This solution would reduced my MCAT aliases of TSO users down > to 1 from 19K > by using TSO as the HLQ/ALIAS. > > Are there any sites that have more then 19,000 TSO aliases > defined on this > Listserver or has somewhat heard of a solution ? > > Kevin D. Clark I don't really understand about the "maxed out", unless you mean the number of aliases going to a single user catalog. My solution would be to use multiple user catalogs. In fact, I do that already. Our RACF ids have two portions. The first part is a group or department. The second part is a number to make the id unique. The catalog to which the RACF id points is based on the first portion or "group". -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
