On 6/6/06 1:57 AM, "Rob van der Heij" <[EMAIL PROTECTED]> wrote:
> 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. > We're definitely not to that level of expertise yet. I reckon if IBM says an RSU is good, then it RSUits me too. ;-) > 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. > Yep, second level for now and we're going for the clippage approach. Leland
