There is a file on one of DIRMAINT's disks that tells what is locked. At my former customer, I wrote some REXX code to check in this file for locks that were held too long. If longer than -maybe a week- I sent an email to the person creating the lock and to the systems programmers. I can dig up that code, but the mail generation is not part of it, that was done by the code interpreting these REXX code snippets, all of this was the "TSLA" measure and warning system.
When a logoff of the locked user helps, it means that someone used DIRMAINT to move/change/clean a minidisk of that user. DATAMOVE then wants exclusive access to the MDISK to perform its task, and until that succeeds the user and this minidisk are locked. 2010/5/17 Dave Jones <d...@vsoft-software.com> > Eric, > > you need to find out what virtual address in the directory entry is locked > and then use the DIRM FOR EWSAUTO1 UNOCK <vaddr> command. > > DJ > > > On 05/17/2010 01:25 PM, Eric Spencer wrote: > >> I tried that first (DIRM FOR ... unlock). it doesn't appear to be "that >> kind" of lock. >> >> DVHREQ2288I Your UNLOCK request for EWSAUTO1 at * has been accepted. >> DVHLOC3601E Directory entry EWSAUTO1 is already unlocked. >> DVHREQ2289E Your UNLOCK request for EWSAUTO1 at * has failed; with RC >> DVHREQ2289E = 3601. >> >> >> Eric Spencer >> p:512.241.7313 | f:512.343.9538 >> Neon Enterprise Software LLC. >> >> >> >> >> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On >> Behalf Of clifford jackson >> Sent: Monday, May 17, 2010 1:19 PM >> To: IBMVM@LISTSERV.UARK.EDU >> Subject: Re: Device locks >> >> 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<mailto:espen...@neonesoft.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. See how.< >> http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2 >> > >> >> > -- > Dave Jones > V/Soft > www.vsoft-software.com > Houston, TX > 281.578.7544 > -- Kris Buelens, IBM Belgium, VM customer support
