开云体育I truly do understand why I would want to protect the master catalog, I just do not understand and need to correct the fact that the MCAT password would fine with a batch mode job that does an update to the MCAT, prompts me and accepts the password, but in an interactive TSO session, I get prompted for the MCAT password but it will not accept it.?? ? There is some difference on my system as built, that is causing this issue, but there are no logs that I can find or a specific error message to provide additional info (that I know of), TSO simply won’t accept the password, while batch job processing does, the only difference is that batch is on the local console session instead of a VTAM user session, but that should not make a difference. ? It for sure would be easier for me to use a TK system rather than my “do it yourself” version.??? Jay Mosley has spent considerable errort on his excellent instructions and I think him very much.?? I do not believe I would be able to learn as much without building this as I have. ? I do not really require security at all, as I am the only user but it still should work.? And an unresolved error, regardless if I need that function or not, is kinda unacceptable to me and will bother me until I know how to resolve it. ? Thanks, Dave ? From:
<[email protected]> on behalf of "andersedlund via groups.io" <andersedlund@...> ? 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 |
