On 2/6/2017 5:37 PM, Tom Conley wrote:
I must say one thing. This entire post by Gil is untrue. His
conjecture about we should have done 32 characters would have made
this project wait at least another, and possibly two releases of
z/OS. The line about deficient communication is unadulterated bull@#$%.
Indeed. And, remember the issue here is with TSO/E only. Not z/OS.
RACF, CA-ACF2, CA-TSS and z/OS subsystems already support 8-character
userids. You can define 8-character userids, use them with CICS, IMS,
DB2, etc. You can use 8-character userids with any Phoenix Software
products and I suspect the same is true for products from other ISVs as
well as much user/customer code. Ironically, you even assign an
8-character userid to the TCAS started task itself, but not to the end
users that attempt to logon to TSO/E via that TCAS. LOL!
TSO/E is the outlier. This support corrects that imbalance and makes all
well with the world again.
Any notion of extending to 32 characters would be sheer folly. That
would require changes to the three major security products, z/OS
subsystems, ISV products, customer code, etc. It would never get done.
Never, ever...
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
