I'm highly skeptical that any logon mechanism can handle the problem of the 'security folks' failing to create a catalog alias. As has been noted, you DO NOT want to give the average Joe update access to the master catalog. Recipe for disaster.
A more subtle problem is a shop convention that has users create data sets by default with an HLQ other than userid, i.e. PREFIX(xxx). Easy to obtain 'sysprefix' is some environments, tougher in others. I see this as an automated resolution to the persistent problem of failure to follow procedure. The goal is to fix more problems than you create. ;-) . . 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 Steve Beaver Sent: Tuesday, June 26, 2018 7:58 AM To: [email protected] Subject: (External):Re: ALIAS I don't mind doing an OUTTRAP, the goal is to STUPID out monkey work -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Tuesday, June 26, 2018 9:52 AM To: [email protected] Subject: Re: ALIAS On Tue, Jun 26, 2018 at 9:41 AM Steve Beaver <[email protected]> wrote: > What I'm thinking is a small REXX using &SYSUID to verify the > existence or non-existence of an ALIAS Then continue on > How about something like: /* REXX */ USERID=SYSVAR('SYSUID') "LISTCAT ENT('"USERID"') ALL" IF RC <> 0 THEN DO /* DOES NOT EXIST? */ END The above will not work correctly (false positive) if the user's ID exists as something other than an ALIAS, such as a DSN or GDG base. You could do the about inside an OUTTRAP to examine the output for further validation. I'm just too lazy. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jesse 1 Robinson > Sent: Monday, June 25, 2018 5:49 PM > To: [email protected] > Subject: Re: ALIAS > > I took OP's question about 'exit' as meaning TSO logon exit. Assigning a > catalog alias during logon would be very tricky. It would have to occur > before any process that allocates a data set with the userid as HLQ. > > Before we barrel along too much further with this, we need clarification > from OP about exactly what he needs. > > . > . > 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 Edward Finnell > Sent: Monday, June 25, 2018 3:20 PM > To: [email protected] > Subject: (External):Re: ALIAS > > There was a CLIST===> %adduser xyz005 > > > It would RACF:ADDUSER xyz005 to group xyz Define an ALIAS in CAT > USERCAT.XYZGRP AD XYZ005 to UADS and do a RACF refresh. > > Don't know where it came from > In a message dated 6/25/2018 3:43:00 PM Central Standard Time, > [email protected] writes: > > > I tend to doubt it; which catalog should it make the HLQ an alias of? -- There is no such thing as the Cloud. It is just somebody else’s computer. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
