Hi Marcy, We have VM:Spool, so the AUTOVSEG feature will automatically restore out SPOOL after IPL (a very, very cool feature). My problem is just formatting and allocating a few packs so there is SPOL space to restore to.
Since ICKSADSF won't load, I've actually cloned my SPOL volumes on the production system onto spindles that do PPRC replicate to the remote site, and their content has already made it "down the pipe", so I'll probably just use those spindles come up with, then I can format and allocate the spindles I intend to use locally at the remote site and discard the copies I came up on (since I don't want SPOL replicating). I'm just really curious why ICKSADSF won't load ............. -Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Monday, October 18, 2010 1:52 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: ICKSADSF Parms Well, you may want to just replicate that spool too. You can then just IPL and go format some page volumes before you bring up any workload. Saves you from recreating all the NSS's as well. The headache is probably not worth the savings. Marcy -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Michael Coffin Sent: Monday, October 18, 2010 10:22 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] ICKSADSF Parms Hi Rich, Unfortunately no, there are no running systems at the site where the DASD is (we're deploying PPRC and I chose not to replicate any system TEMP space, but I need to get the initial TEMP space set up at the remote site, should be simple but ICKSADSF won't load/run correctly, the stand alone DDR module loads and runs OK). I just tried putting CONSSYSG in the IPL PARMS of SALIPL while loading ICKSADSF per Alexander's suggestion, but that's not working either (tried CONSSYSC too). I've got a way to get the packs replicated to the remote site, but it would makes things really easy if I could just get ICKSADSF to load and run so I can allocate some PAGE/SPOL. :( -Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rich Greenberg Sent: Monday, October 18, 2010 1:15 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: ICKSADSF Parms On: Mon, Oct 18, 2010 at 12:25:31PM -0400,Michael Coffin Wrote: } I've never had an occasion to use ICKSADSF from SALIPL until now (I have a } clone of my system with NO PAGE or SPOL, so it crashes right after IPL), so } I need to allocate a couple of packs. No big deal, I'll use the handy-dandy } ICKSADSF - but whenever I try to use it the load just "stalls". I imagine } it can't find the SYSG console, what is the parm to tell it to use SYSG? } I've tried just "SYSG" and "CONS=SYSG" in the IPL PARMS but neither of those } work. Can you access any dasd belonging to the new system from a working system? Even if its not the packs you plan to use eventually, format and allocate some page and spool space and make the volser match something already in the system volume list as page/spool. Then you can IPL it and format allocate the desired pack(s) as page/spool, relabel the temp volume, and reipl. -- Rich Greenberg Sarasota, FL, USA richgr atsign panix.com + 1 941 378 2097 Eastern time. N6LRT I speak for myself & my dogs only. VM'er since CP-67 Canines: Val, Red, Shasta, Zero & Casey (At the bridge) Owner:Chinook-L Canines: Red & Cinnar (Siberians) Retired at the beach Asst Owner:Sibernet-L
