very interestingthat the swap disk had a lock on it. The swap
disk is a virtual disk in storage, right?
On 05/17/2010 02:14 PM, Eric Spencer wrote:
Dave,
That was it.
This machine had been running linux. I had stopped linux and logged it off.
vdev - 100 (root file system)
101
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.commailto:espen...@neonesoft.com
= 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
Dave,
That was it.
This machine had been running linux. I had stopped linux and logged it off.
vdev - 100 (root file system)
101 (swap)
102 (/usr)
101 had a device lock on it for some reason.
Thanks
Eric Spencer
p:512.241.7313 | f:512.343.9538
Neon Enterprise Software
files they do not have the title metadata
supplied, maybe IBM could fix that. But if your using .boo files your
probably also using the softcopy reader/Shelf Organizer which will also
show you the real title.
Eric Spencer
Sr.Software Developer
p: 512.241.7313 | m: 512.470.9807 | f: 512.343.9538
espen
I am playing with the SMAPI interface via the socket API. I am getting
the following in the log from a Check_Authorization call, can anyone
tell me what the following log entries mean or better yet where they are
documented? The socket recv call gets a len of 20 bytes then the
connection is
Thanks Dave, I'll have a look at pigiron, the parm lists certainly are
messy.
The call worked; at least the socket recv returned 20 bytes. Now that I
have confirmed that the VM side of things is set up properly I'll have a
closer look at the client.
Eric Spencer
-Original Message
