Thanks Mike

________________________________

From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Walter
Sent: Tuesday, October 07, 2008 6:26 PM
To: [email protected]
Subject: Re: Need some help with REXX EXEC



Larry, 

He is using CP SIGNAL, hence the HCPSIG... messages he's trying to wait
for. 
That's easy to overlook when we only see part of the code. 


Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or policies of Hewitt Associates. 





"Davis, Larry" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <[email protected]> 

10/07/2008 04:24 PM 
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected] 
cc
Subject
Re: Need some help with REXX EXEC

        




If you use the signal facility the Linux image will shutdown and VM will
wait for it to shutdown prior to completing VM's own shutdown process. 
  
Larry 


________________________________

From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Martin, Terry R. (CMS/CTR) (CTR)
Sent: Tuesday, October 07, 2008 4:41 PM
To: [email protected]
Subject: Need some help with REXX EXEC

Hi 
  
I am trying to write a REXX exec to shutdown my z/Linux guests. I am
having trouble figuring out a couple of things: 
  
  'MAKEBUF'                                                             
   RC = 0                                                               
 DO FOREVER;               /* WILL GET MESSAGES UNTIL GUEST DOWN */     
 'WAKEUP (IUCVMSG QUIET'                /* MESSAGE HAS ARRIVED */       
                                                                        
  PARSE PULL MSG                  /*    GET RETURNED MESSAGE*/         
 /* PARSE VAR MSG TYPE F1 F2 MSGID F3 GUEST REST */                     
                                                                        
  IF RC = 6 THEN                                                       
 /*IF RC = 5 & TYPE = '*CP', */                                         
 /*  & (MSGID = 'HCPSIG2113I'| MSGID = 'HCPSIG2112I') THEN */           
    DO                                                                 
     IF FUNCTION = 'SHUTDOWN' THEN         
  
First, I am not seeing the Shutdown message coming back to the BUFFER
(MAKEBUF). I would like to parse the message to make sure it is the
message I am looking for. I did a QUEUED on the BUFFER and there was
nothing on the STACK. Any ideas why or even if this message should/is
not coming back to the BUFFER? 
  
Second, After I receive the HCPSIG2112I message that says the guest has
been shutdown, and I check and it has, but instead of dropping into the
code it just sits there in RUNNING and I need to hit the ENTER key to
get going again. Is there something I need or can do to simulate the
ENTER KEY. 
  
Note: All of the code is not shown here! 
  
  
                              
Thank You, 
  
Terry Martin 
Lockheed Martin - Information Technology 
z/OS & z/VM Systems - Performance and Tuning 
Cell - 443 632-4191 
Work - 410 786-0386 
[EMAIL PROTECTED] <mailto:[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. E-mails 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 e-mail. 

Reply via email to