No only is it not obvious, so far I have been unable to find it in the 
documentation. You can specify a wait state code on the SHUTDOWN command and it 
can be anything between 1 and FFFF. I cannot find where the default is FFF. Is 
that a true system default or is it a code you have adopted for your use?


Regards,
Richard Schuh





________________________________
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf 
Of Tom Huegel
Sent: Tuesday, June 28, 2011 11:53 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SHUTTRAP

Thanks Kris, that is not obvious, but it makes sense..

On Tue, Jun 28, 2011 at 11:07 AM, Kris Buelens 
<kris.buel...@gmail.com<mailto:kris.buel...@gmail.com>> wrote:
My RxKernel has ShutTrap support.  RxServer uses WAKEUP (EXT to catch the 
interrupt.  No abends then.

And, to complete handling a shutdown signal, one is supposed to load an FFF 
wait state, not to LOGOFF.  My first attempt was to end with a LOGOFF.  But 
then our automation saw the server go logoff and started it again.  So now I 
end with the official method:
   'CP STORE PSW 000A0000 80000FFF'




2011/6/28 Raymond Noal <raymond.n...@emc.com<mailto:raymond.n...@emc.com>>
Hello Richard,

I believe the reason for your error message in using SHUTTRAP is that SHUTTRAP 
can only issue CMS commands and not CP commands. Is the message associated with 
your SHUTTRAP issuing a CP command? I had the same problem when my message was 
a CP command. As a test for SHUTTAP I issued the CMS command 'Q DISK' and it 
worked with no error message.

Hope this helps.

Raymond E. Noal

           EMC²
    where information lives

Phone: (508) 249-4076<tel:%28508%29%20249-4076>
Ext:  44076

From: The IBM z/VM Operating System 
[mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] On Behalf Of 
Schuh, Richard
Sent: Tuesday, June 28, 2011 11:59 AM
To: IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>
Subject: SHUTTRAP

I just retrieved SHUTTRAP from the download page and tried it. In my first 
simpleminded try, the results were mixed. The signal shutdown did indeed 
trigger the command included with the shuttrap command. Then I got this:

SHUTTRAP: Shutdown in 900 seconds
DMSITP143T Addressing exception occurred at 81056162 in system routine WAITRD; 
re-IPL CMS
15:07:56  * MSG FROM RSCHUH1 : DMSDIE3550I All APPC/VM and IUCV paths have been 
severed.
HCPGIR450W CP entered; disabled wait PSW 000A0000 80F3F752

There is nothing in the documentation that would lead me to believe that this 
is normal; however, the documentation consists solely of the HELP file and is 
pretty sparse in this area. I tried reassembling the module with the same 
results.

z/VM 6.1 Service Level 1002
CMS 25, Service Level 002


Regards,
Richard Schuh






--
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to