Re: Device locks

2010-05-18 Thread Eric Spencer
No, it was a real mini disk formated as SWAP From: The IBM z/VM Operating System [ib...@listserv.uark.edu] On Behalf Of Dave Jones [d...@vsoft-software.com] Sent: Monday, May 17, 2010 3:55 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Device locks That's

Device locks

2010-05-17 Thread Eric Spencer
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

Re: Device locks

2010-05-17 Thread Wakser, David
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

Re: Device locks

2010-05-17 Thread clifford jackson
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

Re: Device locks

2010-05-17 Thread Wakser, David
Sorry, I made an error - I showed you the SFS DLETE LOCK - not the DIRMAINT UNLOCK. My error. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of clifford jackson Sent: Monday, May 17, 2010 2:19 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Device locks can't

Re: Device locks

2010-05-17 Thread Eric Spencer
= 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

Re: Device locks

2010-05-17 Thread Dave Jones
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

Re: Device locks

2010-05-17 Thread Eric Spencer
LLC. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dave Jones Sent: Monday, May 17, 2010 1:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Device locks Eric, you need to find out what virtual address in the directory entry

Re: Device locks

2010-05-17 Thread Kris Buelens
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

Re: Device locks

2010-05-17 Thread Dave Jones
, May 17, 2010 1:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Device locks Eric, you need to find out what virtual address in the directory entry is locked and then use the DIRM FOR EWSAUTO1 UNOCKvaddr command. DJ On 05/17/2010 01:25 PM, Eric Spencer wrote: I tried that first (DIRM

Re: Device locks

2010-05-17 Thread Schuh, Richard
...@listserv.uark.edu] On Behalf Of Dave Jones Sent: Monday, May 17, 2010 1:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Device locks Eric, you need to find out what virtual address in the directory entry is locked and then use the DIRM FOR EWSAUTO1 UNOCKvaddr command. DJ On 05/17