On 12/14/2009 01:08 PM, Walt Farrell wrote: > On Mon, 14 Dec 2009 08:04:23 -0600, Staller, Allan <[email protected]> > wrote: > >>From your original post: >> >> IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED >> And the FM: >> Explanation: If RACF is installed, a background job will be run using >> the minimum default user attributes. (Not the attributes of >> USER=XXXXXXX. My Italics) Either the user ID was unidentifiable, or no >> user ID was specified as a JOB card parameter, or allocation of the user >> attributes data set (SYS1.UADS) failed. >> >> >> >> This means that no userid (in the "true sense") was assigned to the >> task. T > > No, it doesn't. It means exactly what it says, that there is no *TSO* > information associated with the user; i.e., it does not have a TSO segment > nor an entry in UADS, and therefore runs with minimal TSO authorities. > > That message has nothing to do with this problem.
And lack of a TSO segment should be a normal setup for a production batch userid which should never be used for an interactive TSO session. Granted, the "PROTECTED" attribute would also prevent that abuse, but with a setup convention with two barriers you would have to commit two setup errors before the userid would be exposed to TSO hacking. -- Joel C. Ewing, Fort Smith, AR [email protected] ---------------------------------------------------------------------- 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
