Uh, so that the Wait State could get a parking space closer to the door?
Is it Friday yet?
Mike Walter
----- Original Message -----
From: "Jim Bohnsack" [EMAIL PROTECTED]
Sent: 12/05/2007 01:02 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: How to create a CP Disabled Wait State?
In "glancing" at the subject line, my first thought was "why would
anyone (other than maybe a developer in Endicott) want to create a CP
Disabled Wait"?
Jim
Kris Buelens wrote:
------=_Part_2456_31291049.1196879405992
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On can use the CP STORE command.
Here an extract of my RxServer code as response to a Signal Shutdown:
if shutdown='SHUTDOWN' then 'CP STORE PSW 000A0000 80000FFF'
2007/12/5, Dave Keeton <[EMAIL PROTECTED]>:
I'm working through Appendix E in the DirMaint Tailoring and Admin guide
(SC24-6135-01) and I'm not sure how to complete one of the steps. I'm on
step 9, "Test DirMaint's automatic restart and recovery" and I'm not sure
how to "Create a CP disabled wait state".
How does one go about creating this condition? I've encountered it before;
I see it when a Linux guest is shutdown and the guest is still logged on. I
don't know how to force this condition. Any help would be greatly
appreciated.
Thanks in advance,
Dave Keeton
Oregon State Data Center
--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.
