Here here!!
Yes, that is right. And when you off-board (fire, terminate,
retire, etc.) a person, eventually you have to get all their data
sets (the ones with their HLQ) out of the system and finally
delete their ALIAS.
*OR *you rename their data sets/libraries, because as a systems
kind of person, they may have JOBs that never got moved to a
production library..... (sigh)
And having those REXX tools keeps one from screwing things up
when in a hurry.
My 2 Cents,
Steve Thompson
On 5/12/2023 2:49 PM, Bob Bridges wrote:
I'm a security geek now, but as most security jocks started out as system
programmers I often find it necessary to explain that I came into it from the
other side; I was a COBOL developer for 15 years. Even now I'm a programmer at
heart, and writing utilities and custom ETL stuff is what sets me on fire; I'm
pretty ignorant of the systems side. So I've occasionally studied how master
and user catalogues work, but I haven't gotten much further than understanding
that they're not the same :). When I create a TSO alias for a new user
JSCHMOE, I think what happens is that a new entry JSCHMOE is created in the
master catalogue - that's the TSO alias - which points to one of the user
catalogues via the RELATE argument. Later when I try to read
JSCHMOE.DATA.GENERAL, the system starts with the master catalogue and finds
JSCHMOE there; that points the algorithm to a user catalogue, where
JSCHMOE.DATA.GENERAL can be found.
Is that about right?, he asks uncertainly.
If I'm supposed to create a TSO alias for a new user then I suppose I need
update access to the master catalogue - if the above description is correct.
But most users don't need it. And I, given my abysmal depth of ignorance,
would be careful to write the create-alias command into a REXX and use that, so
as to be sure I don't accidentally vary the syntax and do Something Bad.
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/* Excellence is an art won by training and habituation. We do not act rightly
because we have virtue or excellence, but rather we have those because we have
acted rightly. We are what we repeatedly do. Excellence, then, is not an act
but a habit. -Aristotle */
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Steve Smith
Sent: Friday, May 12, 2023 14:36
First, allowing regular users update access to the master catalog is a good
idea... if you like risking system failure and a master catalog filled with
junk.
A good thing to start with is LISTCAT NAME CATALOG(<mastercatalog>) That will
show you what you're dealing with.
--- On Fri, May 12, 2023 at 12:13 PM Bob Bridges <robhbrid...@gmail.com> wrote:
Ah, ENT, that's what I was forgetting. Thanks, all. And I now see
that when they created my ID a few years ago, they did it without
creating a TSO alias for my ID! I don’t think I've ever seen that
done before. It means all my datasets are taking up an entry each in
the master catalogue, right? Not that I know much about catalogues.
So LISTCAT LEV lists all my datasets, but LISTCAT ENT comes up empty for me.
Steve, I wasn't sure which "both" you meant, but experimentation seems
to demonstrate that LEV gets me the DSNs and ENT gets me the alias,
and ne'er the twain shall meet no matter which content arguments I
use. Seems dumb, but ok.
----------------------------------------------------------------------
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
