On 7/21/2018 10:40 AM, Charles Mills wrote:
FWIW I think there was pressure from shops with 8-character IDs elsewhere
who wanted consistency on z/OS.

Not saying it was a good idea, or a bad idea, just sayin' ...

No. It was a desire for consistency *within* z/OS. I cover this change beginning on slide 42 of my "z/OS V2R3 User Experiences" SHARE presentation. Here's a link to the slide deck for the most recent incarnation from Sacramento: http://share.confex.com/data/handout/share/130/Session_22307_handout_11384_0.pdf

In summary, eight-character userids were supported by MVS 4.2 way back in 1995. That support extended to every subsystem and environment across the stack (the BCP, RACF, JES, CICS, DB2, etc.) with one exception: TSO/E. The design of the old TSO account file -- which long predated RACF -- led to an unfortunate decision to restrict TSO userids to seven characters. After 22 years, that restriction was finally lifted in 2017 with z/OS 2.3 TSO/E.

--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/

--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to