Use one command for each user:
DEF ALIAS(NAME('foo') RELATE(' existing catalog'))
DEF ALIAS(NAME('bar') RELATE(' existing catalog'))
DEF ALIAS(NAME('baz') RELATE(' existing catalog'))
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Charles Mills <charl...@mcn.org>
Sent: Tuesday, September 15, 2020 7:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EXTERNAL EMAIL: How get a user to use his own catalog rather than
master?
Well geez, now you tell me, after I have it all working. :-)
I followed @John McKown's instructions: DEF ALIAS(NAME('NEWUSER') RELATE('name
of existing user high level catalog'))
1. How would I decide whether to give the user his or her own catalog? I would
guess I do *not* need one. There will be a handful of very specialized userids
with zero or nearly zero long-term cataloged datasets.
2. What would the above command look like if NEWUS01 through NEWUS20 were all
going to share the same user catalog?
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gibney, David Allen
Sent: Tuesday, September 15, 2020 3:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EXTERNAL EMAIL: How get a user to use his own catalog rather than
master?
It is a bit of an overkill for each individual user to have their own catalog 😊
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
