Our users are very active and many produce large spool files. While all of the other packs are draining, new files could only be allocated on the one pack. Murphy tells me that more than a few files would be created there and the pack would fill up during the period I was trying to manage the SDFs.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] > Behalf Of Rob van der Heij > Sent: Monday, September 11, 2006 2:34 PM > To: [email protected] > Subject: Re: Saving a backup copy of NSSs with no tape drive > > > On 9/11/06, Schuh, Richard <[EMAIL PROTECTED]> wrote: > > > That might work in a small shop, but the only time it would > work here is immediately following an ipl, and then only if > NOAUTO is the reply to the first message. > > > > Back when > > > I was concerned about such things, I have considered to > even drain all > > > but one spool pack while build an NSS so that you keep > the entire file > > > on a single pack. > > How come? I would not be concerned to also have some other (small) > spool files on that same pack, just want to prevent the NSS spread > over multiple volumes. So I would drain the volumes once I get close > to building the segments. > > But if CP could do it right, you could have a single pack hold only > all NSS files and do a DDR copy of the pack on a running (test) system > and pick up that pack when you IPL the new system in production. > > Rob >
