Les Geer [EMAIL PROTECTED] wrote :-
A 3140 reason code does mean 'device is not available'. Typically
though this is not an RMS problem. The quickest way to find out would
be query the drive, and if 'FREE', then try attaching the drive outside
of RMS to see if that is successful.
: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf
Of Colin Allinson
Sent: Tuesday, February 26, 2008 03:36 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DFSMS/RMS question
Les Geer [EMAIL PROTECTED] wrote :-
A 3140
There are several reasons why a 3140 could be returned.
1) The device is not 'free' when RMS queries it. You already have
shown this is not the case.
2) There is a code problem in RMS. As JR indicated, apply the latest
RMS service starting with UM32029
3) 'Device not available' was returned
We have been using DFSMS/RMS on VM for a long time. At the weekend we had
an issue which, I suspect, has happened before but not been identified.
We have 16 drives per VTS shared between 6 VM systems (VMTAPE STAM)
handles the sharing of the drives.
Yesterday, on only one of these drives, I was
: DFSMS/RMS question
We have been using DFSMS/RMS on VM for a long time. At the weekend we
had an issue which, I suspect, has happened before but not been identified.
We have 16 drives per VTS shared between 6 VM systems (VMTAPE STAM)
handles the sharing
Technical Manager - VM Systems Support
Operating Systems Services
Amadeus Data Processing GmbH
T: +49 (0)8122 43 4975
F: +49 (0)8122 43 3260
[EMAIL PROTECTED]
www.amadeus.com
Imler, Steven J [EMAIL PROTECTED]
To
IBMVM@LISTSERV.UARK.EDU
cc
bcc
Subject
Re: DFSMS/RMS question
Imler, Steven J [EMAIL
A 3140 reason code does mean 'device is not available'. Typically
though this is not an RMS problem. The quickest way to find out would
be query the drive, and if 'FREE', then try attaching the drive outside
of RMS to see if that is successful. Generally there is a reason why
RMS could not
