In <[email protected]>, on 01/14/2011
at 11:45 PM, "Joel C. Ewing" <[email protected]> said:
>Certainly, but that wasn't the point. If you have no need to share
>the master catalog among multiple MVS images, and if you restrict
>the catalog dsn entries to dsns on release-dependent system volumes
>that will be replaced by other volsers for the new MVS release, and
>if the master catalog itself is on one of those volumes, then going
>to a new master catalog at the same time as going to a new MVS
>release is a fairly simple matter.
It's still an extra complication. If your conditions are met then
using the old master catalog is equally simple.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
