Even I think there is in not problem with catalogs, It is a good solution to
design the TSO / ISPF under quite a few groups. We implemented this solution 13
years ago, using ten groups and so defining only then user alias.
For example, my gorup is USTS and my user is U0Z72B6 so my TSO files where in
the form USTS.U0Z72B6.xxxx.xxxx... With this, no more act in user catalogs when
ADD/DEL TSO users.
Of course you need some changes in our implemented CLIST/REXX to permit this,
some SMS rules probably and users must use TSO PROFILE PREFIX clause (TSO
PROFILE(USTS) in my case and some other little things, but the benefits are
good. Item more, ISPF and almost all products manage automatically this form
when detectes that PREFX and TSOUSERID does not match.
angel luis dominguez
bbva - spain
==========================================================
From: [EMAIL PROTECTED]
Date: Wed, 26 Apr 2006 11:47:25 -0400
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 ?
---------------------------------
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
----------------------------------------------------------------------
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
