The successful completion could be due to the device finally completing or 
timing out the I/O, CP's MITIME (Missing Interrupt handler) timeout value 
for that device, CP's timebomb cleanup (15 minute default, see 
"DISCONNECT_TIMEOUT" value in "SYSTEM CONFIG"), good fortune, aligned 
planets, or something else entirely.

The CP command "HALT" is good to know when a real device is causing some 
problems.  But I've see that fail to work the first time it is issued. 
Hence, the pasted "REHALT EXEC", below...

Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.

/* Prolog; See Epilog for additional information ********************
 * Exec Name     - REHALT   EXEC                                    *
 * Unit Support  - OSS/VM                                           *
 * Status        - Version 1, Release 1.0                           *
 ********************************************************************/

   address 'COMMAND'
   parse source xos xct xfn xft xfm xcmd xenvir .
   parse upper arg parms 1 operands '(' options ')' parmrest

   Signal ON Syntax
   Signal ON NoValue
/* Signal ON ERROR */

   /* Expected replies, all rc=0 ...
    Halt initiated to tape nnnn
    Halt was not initiated to tape nnnn because the device as not active
   */
    parse var operands rdev .
    If operands='' | operands='?' then Signal Explain

    parse var options limit .
    If limit='' then limit=50

    Do ix=1 to limit /* until word2='INITIATED' */
      'PIPE LITERAL +0.25 | DELAY'
       parse upper value diag(08,'CP HALT' rdev) with reply '15'x ,
                                                 1 . word2 . '15'x .
    End
    say reply '('ix 'tries)'
    If word2='INITIATED' then Call Exit 0
                         else Call Exit 36


/********************************************************************/
/*                   Sub-Routines below this point                  */
/********************************************************************/

Exit:
   parse arg exitrc .
   If verify(exitrc,'-0123456789')=0 then Exit exitrc
                                     else Exit 999999

Syntax:
   say '+++ Syntax error routine entered in:' xfn xft xfm
   say '+++ from line:' sigl', which reads:'
   say '+++'sourceline(sigl)
Call Exit 20


NoValue:
   say '+++ NoValue error routine entered in:' xfn xft xfm
   say '+++ from line:' sigl', which reads:'
   say '+++'sourceline(sigl)
   say '+++ Variable with no value is:' condition('Description')
Call Exit 24


Explain:
say 'REHALT can be used to get a stubborn device (usually tape) offline'
say 'when a single HALT does not stop it - sometimes due to MISSING'
say 'INTERRUPT.'
say
say 'Syntax:'
say '                                +-( 50----------------------+    '
say '>--REHALT--rdev-----------------+---------------------------+--><'
say '                                +-( max numer of retries )--+ -  '
Call Exit 0
/* Epilog ***********************************************************
 * Dependencies  - VM/SP 3 or higher.                               *
 *               - e.g. LISTFILE, COPYFILE, etc.                    *
 * Program Lang. - CMS REXX                                         *
 * Date Written  - 20040405                                         *
 * Author        - Michael R. Walter                                *
 * Changed | By  | Description of Change                            *
 * --------+-----+------------------------------------------------- *
 * yyyymmdd  iii -                                                  *
 *                                                                  *
 ********************************************************************/



"Wandschneider, Scott" <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
10/12/2009 01:36 PM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: LOGOFF/FORCE pending






The hung User completed its logoff before I could issue the HALT.  It was 
hung for about 30-35 minutes before completing. 
 
Thank you,
 
Scott
 
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Imler, Steven J
Sent: Monday, October 12, 2009 1:31 PM
To: [email protected]
Subject: Re: LOGOFF/FORCE pending
 
Issue a CP HALT to the REAL device ...
 
JR (Steven) Imler
CA 
Senior Sustaining Engineer
Tel: +1-703-708-3479
[email protected]
 
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Wandschneider, Scott
Sent: Monday, October 12, 2009 02:19 PM
To: [email protected]
Subject: LOGOFF/FORCE pending
 
I have a LOGOFF/FORCE pending situation and I know which device is hung. 
Any ideas on how to clear the device so the force may complete? 
 
Thank you,
Scott R Wandschneider
Senior Systems Programmer|| Infocrossing, a Wipro Company || 11707 Miracle 
Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223  || 
:: [email protected] **Think Green  - Please print 
responsibly**
 
Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 
it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 
dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 
in error, please immediately return it to the sender and delete it from 
your system. Thank you. 
Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 
it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 
dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 
in error, please immediately return it to the sender and delete it from 
your system. Thank you. 




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