On Wed, 24 Nov 2010 09:27:55 -0600, Arthur Gutowski <[email protected]> wrote:
>It looks like a non-starter. I don't see any support for VOLUME specification in >the BPXPRMxx MOUNT statement, the TSO/E nor Unix command, nor in >automount. Without that, I can't see how it makes my cloning process any >easier. I still have to maintain unique DSNames for my maintenance FS'. >Hence, a rename is still required during a clone, even if all our systems take >advantage of it for IPL volumes. All it seems to buy me is I can take &SYSR1. >out of the FILESYSTEM parm of the MOUNT statements. BFD. > >If I missed something, I'll be receptive to some illumination. > Right. Even when I was using HFS and had the root on my 1 & only IPL volume, the maintenance version didn't live on the maintenance sysres because it had to have a different name to mount it at the service mount point in order to apply maintenance. It then was logically copied to the IPL volume in the cloning process after the full volume copy. Going way back to pre OS/390 2.6 support for non-SMS HFS, being on a separate volume and cataloged was an HFS requirement anyway. So until you can mount an uncataloged HFS or zFS, the maintenance version will always need to have a different name, regardless of indirect cataloging of the run-time version. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- 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
