On 6/5/06, Leland Lucius <[EMAIL PROTECTED]> wrote:
be able to "flip-flop" between 2 "sysres" volumes for maintenance and backout. To do that, I'll need to move off a few things like the ckpt, spol, drct, and a few minidisks to a "shared" volume. Then, implementing maintenance is a simple matter of a full volume copy and NSS rebuilds.
Anything is possible, and certainly with z/VM... Many of us prefer to do a more phased approach like CP and CMS separate from each other and be able to run some applications with the back-level code of some program products when that turns out to be necessary. To implement maintenance you would need to fiddle with directory entries so the full switch would not happen in such a case. Unless you're doing a full re-install with each release, I think you don't want to have system data on a volume named 510RES. In shops with more than one LPAR you would need different names anyway, so I would opt for a volser based on the system name rather than the release. I suspect you will be preparing your new full pack on a second level system or another LPAR. Either you clip the volser when switching or you would need to do a global change in your directory to switch to the other full pack. And when your new release requires new or bigger mini disks you also need to manually keep these two directories up-to-date. The alternative approach that I have seen being used is to have another MAINTxxx allocated and use that to do your new installation. For implementation of the new release after testing, you need to adjust the directory links to the old MAINTxxx and make them point at the new one. -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
