Mark Yuhas wrote:
If one browses SYS1.UADS, one will notice that each member name/TSO User
ID has been suffixed with the character '0'. Since the maximum length
of the member name is 8 bytes and since ACCOUNT adds a '0' to TSO User
ID, the maximum length of a TSO User ID is 7.
At least, this is what I have gleaned over the years.
The first UADS member for a user ID is suffixed with zero. If
there are more, they are suffixed with 1, 2, 3, etc. All those
that exist are used to retrieve information about a given ID. If
you are still using UADS (why?), then the block size you choose
affects how much "stuff" (a technical term, meaning PROCs, etc.,
IIRC) can be defined for a particular ID before another member is
created in UADS. This historical design is one reason behind the
7-character length limit for TSO/E user IDs.
There is (or at least was at one time) a topic in one of the
TSO/E books that talks about choosing a reasonable block size for
UADS given how much "stuff" you define for each ID on the average
so that additional members are minimized without wasting space.
(If you're still using UADS, it's probably better to read about
what you need to do to convert all but a very small number of
recovery IDs to use RACF for TSO/E user ID definition instead. ;-)
The above is also why UADS' block size is modeled from your
existing UADS in ServerPac. We didn't want to choose an
arbitrary block size for anyone who was (a) still using UADS and
(b) had troubled to optimize its block size.
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[EMAIL PROTECTED]
----------------------------------------------------------------------
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
