Re: TSO and SYS1.UADS

2006-03-28 Thread Skip Robinson
You don't need UADS in your TSO PROC; probably better not to have it. Just use a Rexx like this one when you want to use the ACCOUNT command: /* REXX */ /*--- TRACE N /* Change option as needed */ /*---

Re: TSO and SYS1.UADS

2006-03-28 Thread Chris Mason
; Newsgroups: bit.listserv.ibm-main To: Sent: Tuesday, 28 March, 2006 2:33 PM Subject: Re: TSO and SYS1.UADS > In <[EMAIL PROTECTED]>, on 03/22/2006 >at 10:35 AM, Duane Weaver <[EMAIL PROTECTED]> said: > > >So my question is: How does TSO know to use SYS1.UADS? >

Re: TSO and SYS1.UADS

2006-03-28 Thread Shmuel Metz (Seymour J.)
In <[EMAIL PROTECTED]>, on 03/22/2006 at 10:35 AM, Duane Weaver <[EMAIL PROTECTED]> said: >So my question is: How does TSO know to use SYS1.UADS? Master JCL. >Does UADS need to be defined to the TSO proc? Do you want to use the ACCOUNT command? -- Shmuel (Seymour J.) Metz, SysProg a

Re: TSO and SYS1.UADS

2006-03-22 Thread Pommier, Rex R.
: 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

Re: TSO and SYS1.UADS

2006-03-22 Thread Skip Robinson
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

Re: TSO and SYS1.UADS

2006-03-22 Thread Kittendorf, Craig
Subject: Re: TSO and SYS1.UADS 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

Re: TSO and SYS1.UADS

2006-03-22 Thread Ed Finnell
In a message dated 3/22/2006 10:20:32 A.M. Central Standard Time, [EMAIL PROTECTED] writes: SYS1.UADS is user database. You can administer the users by ACCOUNT program. It is worth to have some entries in UADS for recovery in case of RACF failure. >> If the driving system was built wit

Re: TSO and SYS1.UADS

2006-03-22 Thread Walt Farrell
On 3/22/2006 10:34 AM, Duane Weaver wrote: I have a need to build a small zOS utility system. There are no plans to put our security package on this utility system. There will be no real data on this system to be concerned about. Be aware that you won't have access to any UNIX-based functio

Re: TSO and SYS1.UADS

2006-03-22 Thread Pommier, Rex R.
AM To: IBM-MAIN@BAMA.UA.EDU Subject: TSO and SYS1.UADS I have a need to build a small zOS utility system. There are no plans to put our security package on this utility system. There will be no real data on this system to be concerned about. So my question is: How does TSO know to use SYS1.UA

Re: TSO and SYS1.UADS

2006-03-22 Thread R.S.
Duane Weaver wrote: I have a need to build a small zOS utility system. There are no plans to put our security package on this utility system. There will be no real data on this system to be concerned about. So my question is: How does TSO know to use SYS1.UADS? Does UADS need to be defin

TSO and SYS1.UADS

2006-03-22 Thread Duane Weaver
I have a need to build a small zOS utility system. There are no plans to put our security package on this utility system. There will be no real data on this system to be concerned about. So my question is: How does TSO know to use SYS1.UADS? Does UADS need to be defined to the TSO proc?