David--That's exactly what you cannot do with DCSSBKUP/.RSAV is copy
NSS's. That's one of the two major short comings with those utilities
with the other being, IMHO, the fact that the restored DCSS's do not
retain the original spool file time/date stamp.
I suspect, tho, that you really just
do a FORCE start on the new system.
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Romanowski, John (OFT)
Sent: Tuesday, September 26, 2006 3:23 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Can't copy a spool pack?
While the host is running I
ka, James (GTI)
Sent: Tuesday, September 26, 2006 3:28 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Can't copy a spool pack?
You need to copy the CHECKPOINT and/or the WARM START areas too. You
will more than likely have to do a FORCE start on the new system.
-Original Message-
Fro
:23 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Can't copy a spool pack?
While the host is running I copied the host VM5.2's single SPOOL pack to
the single spool pack of my guest VM5.2 system, wanting to give the
guest a copy of the host's NSS's and other System Data Files (SDF)
While the host is running I copied the host VM5.2's single SPOOL pack to
the single spool pack of my guest VM5.2 system, wanting to give the
guest a copy of the host's NSS's and other System Data Files (SDF).
When I IPL-ed the guest it reported no spool files; it had no NSS's.
I did the copy 3 ti
