Password protection of catalogs has not been supported for some time
now. The current AMS book says:
"Passwords are no longer honored for protecting a catalog, or data sets
contained in a catalog. If they are specified, they will be ignored and
no message will be issued. Previously, passwords were ignored only for
SMS-managed data sets. You should use z/OS Security Server RACF® or an
equivalent security package, to protect your data. Most instances of
passwords have been deleted from this publication. Passwords in keywords
such as ATTEMPTS, AUTHORIZATION, CODE, and LOCK will be ignored."
Edward Gould wrote:
On Dec 14, 2016, at 9:05 AM, Edward Gould <[email protected]> wrote:
Thirty + years ago (pre-RACF) we put update password on the mastercats.
Worked like a charm for us.
Ed
On Dec 14, 2016, at 1:16 AM, Elardus Engelbrecht
<[email protected]> wrote:
Jesse Robinson wrote:
And once you have all protections in place, remember that someone has to have
the key to master catalog. Whoever that is--including you--may occasionally get
caught by a missing alias. At every shop I've worked in, userids are defined
and managed by a non-sysprog department. If they set up a new user, especially
a new sysprog, a missing alias may be caught only after many data sets have
gone to master catalog. So it pays to check now and again even with all
recommended protections set up.
I didn’t say it was perfect solution but that it worked. BTW we used ALTER
(IDCAMS) to put the password on.
This is a quick and dirty way of doing it.
<snip>
--
John Eells
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
