Close, but I am not willing to grant you a cigar. If all, or even most, have 
the same Signalled by id, then either a "signal shutdown all" was done or a 
program did multiple "signal shutdown user userid" commands in rapid sequence.

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Raymond Noal
> Sent: Tuesday, June 28, 2011 3:38 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: SHUTTRAP
> 
> Richard,
> 
> You can use the CP command - 'Q SIGNALS' to make your 
> determinations, as in - 
> 
> q signals                                                  
>                                         Signalled  Timeout  
> Userid        Signal    Signal Status   By         Remaining
> LN192209      SHUTDOWN  Enabled         -          -        
> VMSERVR       SHUTDOWN  Enabled         -          -        
> VMSERVU       SHUTDOWN  Enabled         -          -        
> VMSERVS       SHUTDOWN  Enabled         -          -        
> 
> Happy parsing!!
> 
> Raymond E. Noal
> 
>            EMC²
>     where information lives
> 
> Phone: (508) 249-4076
> Ext:  44076
> 
> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Schuh, Richard
> Sent: Tuesday, June 28, 2011 6:22 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: SHUTTRAP
> 
> Given the lack of direction, I suppose that you can do almost 
> anything, so long as you are consistent. There is no right or 
> wrong, so logging off will work so long as the watchdog 
> machine does not bring logged off users back on. Is there any 
> way for a user to determine if it is being targeted alone, by 
> a "signal shutdown user userid" or is included in a "signal 
> shutdown all"? I suspect not, but I can see where that might 
> be useful at times. Also, CP does notice when a user who has 
> requested the shutdown signal logs off and cancels the 
> request, does it not? It must because a virtual machine can 
> log off at any time, regardless of the shutdown signal, and 
> CP has to handle it correctly. Does CP disallow new logons 
> when it receives  "signal shutdown all" command?
> 
> Regards,
> Richard Schuh 
> 
>  
> 
> > -----Original Message-----
> > From: The IBM z/VM Operating System
> > [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alan Altmark
> > Sent: Tuesday, June 28, 2011 1:56 PM
> > To: IBMVM@LISTSERV.UARK.EDU
> > Subject: Re: SHUTTRAP
> > 
> > On Tuesday, 06/28/2011 at 03:10 EDT, "Schuh, Richard" 
> > <rsc...@visa.com>
> > wrote:
> > > 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?
> > 
> > You will not find any published information on the mechanism.
> > 
> > I *observe* that if you SIGNAL SHUTDOWN to a 2nd level VM, it will 
> > load wait state FFF and the SIGNAL SHUTDOWN command gives a 
> > "successful termination" message.
> > 
> > Draw your own conclusions.
> > 
> > Alan Altmark
> > 
> > Senior Managing z/VM and Linux Consultant IBM System Lab 
> Services and 
> > Training ibm.com/systems/services/labservices
> > office: 607.429.3323
> > mobile; 607.321.7556
> > alan_altm...@us.ibm.com
> > IBM Endicott
> > 
> 

Reply via email to