s Geer (607-429-3580)" [EMAIL PROTECTED]Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
12/12/2007 01:28 PM EST
Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
To
"IBMVM@LISTSERV.UARK.EDU" IBMVM@LISTSERV.UARK.EDU
cc
bcc
Su
Les,
What APAR or APARs would that be?
Jim
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Les Geer (607-429-3580)
Sent: Tuesday, December 11, 2007 5:10 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: DFSMSRM Errors in RMSMASTR
BTW, if you order
IBMVM@LISTSERV.UARK.EDU
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DFSMSRM Errors in RMSMASTR
Date: Tue, 11 Dec 2007 21:36:05 -0500
What was the category the device was assigned to in the previous
query?
Best Regards,
Les Geer
IBM z/VM and Linux Development
I have 4 tapes assigned to the category
That would be scratch0 I believe. I've been trying some stuff this
morning after reading your note. I disassociated the drive from the
scratch pool and when I re-started the RMSMASTR machine, there were no
sense errors. I was able to manually mount a tape which was volspecific.
After
PROTECTED]
Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
mailto:The%20IBM%20z/[EMAIL PROTECTED]
e
To: IBMVM@LISTSERV.UARK.EDU mailto:IBMVM@LISTSERV.UARK.EDU
Subject: Re: DFSMSRM Errors in RMSMASTR
Date: Tue, 11 Dec 2007 21:36:05 -0500
What was the category the device was assigned
My MVS counterpart, 20+ years ago, would ask me to run with a piece of
equipment on VM if it was suspect on MVS because, at that time MVS error
recovery was so much better than VM's that it was harder to tell if
there was a hardware error on something connected to MVS. It would just
recover,
The APARs which allow RMS to issue a query device without attaching
the device are VM64062 and VM64206 for RMS, and VM64157 for CP.
However, none of this service in my belief will help solve the
I/O errors you are receiving. If you associate a device with a
particular scratch pool, and there are
Dave,
What level of z/VM are you running ... your DFSMS/VM software appears to
be back level. With the current SDO for DFSMS/VM installed, a DFSMSRM
QUERY LIBRARY DEVICE command will not generate a CP ATTACH/DETACH
sequence for the device on the RMSMASTR virtual machine.
I also see the device
We're running z/VM 5.2 and DFSMS/VM that came with the SDO. Sounds like
maybe I'm behind on fixes?
-Original Message-
From: Imler, Steven J [EMAIL PROTECTED]
Reply-To: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DFSMSRM Errors
Yeah, I suppose doing a demount before mounting the tape probably
doesn't make any sense.
First, I restarted the RMSMASTR machine. Here's what it said after the
PROFILE EXEC ran:
FSMBBV3053I All DFSMS local APPC/VM resources initialized
FSMRMBLC== Diag 254 is available
TAPE 4116 ATTACHED TO
During initialization, RMS does a demount to each drive it can access.
However now that I think about this, there is a different error that
comes back which RMS intercepts indicating there is no volume
mounted. An error that is not reflected like this sense is.
I recently worked on a similar
@LISTSERV.UARK.EDU
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: DFSMSRM Errors in RMSMASTR
Date: Tue, 11 Dec 2007 18:28:02 -0500
During initialization, RMS does a demount to each drive it can access.
However now that I think about this, there is a different error that
comes back which RMS intercepts
What was the category the device was assigned to in the previous
query?
Best Regards,
Les Geer
IBM z/VM and Linux Development
I have 4 tapes assigned to the category scratch0 and 2 assigned to
volspecific:
FSMBCJ2182I SCRATCH0 VM
3592 300GB
FSMBCJ2182I SCRATCH0
13 matches
Mail list logo
