can't you issue a DIRM unlock

Date: Mon, 17 May 2010 11:09:40 -0700
From: david.wak...@infocrossing.com
Subject: Re: Device locks
To: IBMVM@LISTSERV.UARK.EDU
















There is a DELETE LOCK command
that will probably rectify the situation. But the question that bothers me is:
how/why did the user lock the member?

 

David Wakser

 

Syntax:

 

>>--DELete--LOCk--.-.----------------.--dirid-.------------------------------>


                 
| '-.-fn-.--.-ft-.-'       
|                               


                 
|   '-*--' 
'-*--'         
|                               


                 
'-fn--ft--bfsid-------------'                               


               
                                                               

  
.-(--NOType---------------------.                                          


>--+-------------------------------+----------------------------------------><


  
'-(--.-TYPe------------.--.---.-'                                          


       
|        .-FIFO-. | 
'-)-'                                            


       
|-STACK--+------+-|                                                   


       
|        '-LIFO-'
|                    
                               

       
|-LIFO------------|                                                   


       
|-FIFO------------|                                                   


       
'-NOType----------'                                    
               

 

 

 





From: The IBM z/VM
Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Eric
Spencer

Sent: Monday, May 17, 2010 1:36 PM

To: IBMVM@LISTSERV.UARK.EDU

Subject: Device locks





 

I
am getting the following - 

 

dirm
for ewsauto1
get                                                       


DVHXMT1191I
Your GET request has been sent for
processing.                  


Ready;
T=0.01/0.01 13:32:10                                                 


 DVHREQ2288I
Your GET request for EWSAUTO1 at * has been
accepted.           

 DVHLOC3602E Directory entry EWSAUTO1 has active device locks
against it.    

 DVHLOC3602E
A USER lock can not be
granted.                                


 DVHREQ2289E
Your GET request for EWSAUTO1 at * has failed; with RC
=        

 DVHREQ2289E
3602.                                                          


 

 

The
user is logged off, any suggestions on commands to display what device is
locked or how to unlock it? 

 

Eric
Spencer

espen...@neon.com

 

 

 






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.


                                          
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your 
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

Reply via email to