Rick - I love your suggestion - THANK YOU Lionel B. Dyck, Consultant/Specialist
Enterprise Platform Services, Mainframe Engineering
KP-IT Enterprise Engineering
925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED]
AIM: lbdyck | Yahoo IM: lbdyck
Kaiser Service Credo: "Our cause is health. Our passion is service. We're
here to make lives better."
I never guess. It is a capital mistake to theorize before one has data.
Insensibly one begins to twist facts to suit theories, instead of theories
to suit facts.
- Sir Arthur Conan Doyle
NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail,
you are prohibited from sharing, copying, or otherwise using or disclosing
its contents. If you have received this e-mail in error, please notify the
sender immediately by reply e-mail and permanently delete this e-mail and
any attachments without reading, forwarding or saving them. Thank you.
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; <><
<<image/gif>>
