I have seen one case where each hlq was the name of a trk,1,1 catalog for that how. Not kept open by the system.
On Tue, Sep 15, 2020, 20:27 Jesse 1 Robinson <[email protected]> wrote: > I have never considered giving a single user his own ucat. You can create > multiple ucats according to function. But like users should point to the > same ucat. If you have a product that creates thousands of data sets for > its own purposes, you might consider creating a ucat just for that product. > But never for a personal userid. > > . > . > 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 <[email protected]> On Behalf > Of Charles Mills > Sent: Tuesday, September 15, 2020 4:28 PM > To: [email protected] > Subject: (External):Re: EXTERNAL EMAIL: How get a user to use his own > catalog rather than master? > > CAUTION EXTERNAL EMAIL > > 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:[email protected]] On > Behalf Of Gibney, David Allen > Sent: Tuesday, September 15, 2020 3:40 PM > To: [email protected] > 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 [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
