You may have to press enter once twice on the 3270 integrated console to obtain
the CLEAR SCREEN TO CONTINUE message.
The CP Planning and Administration book has:
If you only need to override the console that CP will use as the system
operator console during CP initialization, specify a load parameter of
CONSxxxx. For example:
Specify CONSSYSG to use the integrated 3270 console on the IBM Hardware
Management Console (HMC)
Specify CONSSYSC to use the operating system messages panel on the HMC
Specify CONSxxxx to cause CP to use the 3270 at address xxxx.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Michael Coffin
Sent: Monday, October 18, 2010 11:51 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: EXTERNAL: Re: ICKSADSF Parms
Just to prove to myself that my ICKSADSF MODULE wasn't corrupt, I cloned my
RES pack on our local production system and IPL'd it second level. I
selected ICKSADSF to load, left the IPL PARMS blank, and pressed PF10. I
instantly got the expected CLEAR SCREEN TO CONTINUE (or words to that
effect) message in the lower right corner of the 3270 screen. So I'm sure
the ICKSADSF MODULE is good, I'm just not giving it the right parms to point
it to SYSG on my HMC. :(
So far I have tried:
CONS=SYSG
SYSG
CONSSYSG
CONSSYSC
CONSSCLP
And I've left the parms blank as well. None of these have worked. :(
-Mike
-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Michael Coffin
Sent: Monday, October 18, 2010 1:22 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: 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
