I think you have misunderstood the value of password protecting the MASTER CATALOG.
It is there to prevent you from 'accidentally' updating it. Let me give you some background.
Before VSAM, the master catalog had to be on the IPL volume and also with the VSAM MCAT,
you do not want to have individual non-system datasets cataloged in the MCAT.
The reason is that you wish to have a simple way to upgrade your MVS or try a new version of
the system by just IPLing a different pack.
By having the datasets belonging to batch application systems or individual TSO users catloged
in a user catalog you eliminate a lot of catalog synchronization by re-connecting your existing
user catalogs to the new MCAT (when you have to build a new one).
The turnkey MVS systems are already set up with usercatalogs connections for the already
existing TSO users and there are probably procedures/JOBs for creating new TSO users which
include setting up connections to usercatlogs.
By convention, TSO users use there userid as the high-level-qualifyer and batch applications have
individual HLQs. Thus you have a relatively stable set of catalog connectors to add to a recreated MCAt.
This scheme also fits well with SMS ACS routines (on more recent MVS levels) and RACF protection.
Thus normal use of the MVS system will not update the MASTER CATALOG!
Anders Edlund
