Thanks for the correction. Like I said, it's been eons since I had to deal with this situation.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Skip Robinson Sent: Wednesday, March 22, 2006 4:14 PM To: [email protected] Subject: Re: TSO and SYS1.UADS Search is the other way around: look first in RACF; if not found, look in UADS. This simplifies conversion to RACF. Just add a TSOE segment and test. If there's a problem, delete the TSOE segment and you're back to UADS. You never have to touch UADS if you choose to leave it as is. . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List <[email protected]> wrote on 03/22/2006 08:26:21 AM: > I'll give it a shot. I don't know if it is needed in both places, but > I have SYS1.UADS defined in the master JCL to DD SYSUADS and in the > TSO proc under DD SYSUADS as well. I believe - tho it's been eons > since I've looked at it - that TSO actually looks in UADS first and if > the userid isn't there, it goes to RACF to get the account > information. > > I'm sure somebody will correct me if I'm wrong here <g> > > Rex <snip> ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
