We have rolled out z/OS 2.3 to the entire Enterprise and received no problem 
reports. Some comments:

-- It may be 'typical' for a TSO user to have a RACF segment, but there is no 
overarching technical requirement unless a user needs to execute one of the few 
documented functions that explicitly require a segment. Those functions are 
typically restricted to sysprogs and other 'infrastructure' folks. So the vast 
majority of users in any shop probably do not *need* a TSOE segment.

-- Our shop has a decades old RYO security management tool that was built 
around UADS long before TSOE segments were invented. Until now (long time!) 
there has been little appetite to rewrite the tool to accommodate TSOE 
segments. So most of our users are still UADS-only.

-- Absent any problem reports, I have not delved into OA47508, but how does 
IDCAMS distinguish between a 'TSO user' who has no RACF segment and an HLQ that 
is not associated at all with any particular user? That is, HLQ XYZ001 may 
represent a TSO user or simply a (shared) high level application id. If there 
is no TSOE segment, how does IDCAMS decide what to do? 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Peter Relson
Sent: Tuesday, September 25, 2018 7:34 AM
To: [email protected]
Subject: (External):Re: TSO PREFIX, FTP and z/OS upgrade

According to doc APAR OA47508, the only case where there should be a difference 
in behavior is when there is no RACF TSO segment for this user. 

Isn't it typical for there to be such a segment?

>Is there a good reason for this incompatible change? 
yes there was/is. And that is all that I can say.

Peter Relson
z/OS Core Technology Design

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

Reply via email to