The problem with putting a Linux guest to sleep, is that they tend not to wake
up so well.
Obviously, all IP communications times out.
CRON processes floods the image when it is woken.
Any database and/or logical units of work, tend to abend.
All of this was when I tried to force guests to sleep back on SLES7 on a
MP3000. My thought was, if it isn't in use, force it to sleep. We will wake
it up when necessary. My thought was to avoid the overhead in IPLing images
when they were needed and eliminate the overhead of the idling systems. There
were a lot of things we didn't know about in those days. <G>
Tom Duerbusch
THD Consulting
From:
Rick Troth <[EMAIL PROTECTED]>
To:
IBMVM@LISTSERV.UARK.EDU
Date:
04/01/2008 02:46 PM
Subject:
Re: set share to stop a guest from getting service ?
> The goal will be to put the identified guest to 'sleep' until we can
> evaluate if it is truly causing issues. ...
I think I have followed this whole thread,
and I don't seem to recall either of these suggested:
cp send cp thebadguest sleep
-or-
cp send cp thebadguest stop
If all you want to do is "hit the red button" for a period,
then issue a CP STOP command. Then CP BEGIN when you want to resume.
You could also issue a CP SLEEP with or without a time. (Usually used
with a time spec. Without a time spec, CP BEGIN or console interrupt
to wake up and resume execution.)
>From the console of that guest, with default TERM LINEND, try
#cp sleep
-or-
#cp stop
-- R; <><
Law of Cat Acceleration
A cat will accelerate at a constant rate, until he gets good and
ready to stop.
