Les,
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 re-associating the drive to the scratch0 pool, I once again got
the errors on initialization of RMSMASTR.
Which APAR(s) should I be applying to bring DFSMS/VM current?
Thanks,
Dave
-----Original Message-----
From: Les Geer (607-429-3580) <[EMAIL PROTECTED]>
Reply-To: The IBM z/VM Operating System <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 scratch0 and 2 assigned to
>volspecific:
>
>FSMBCJ2182I SCRATCH0 VM0000
>3592 300GB
>FSMBCJ2182I SCRATCH0 VM0001
>3592 300GB
>FSMBCJ2182I SCRATCH0 VM0002
>3592 300GB
>FSMBCJ2182I SCRATCH0 VM0003
>3592 300GB
>FSMBCJ2182I VOLSPECIFIC VM0004
>3592 300GB
>FSMBCJ2182I VOLSPECIFIC VM0005
>3592 300GB
>
>
>
Dave Keeton
Systems Programmer
Enterprise Systems
Oregon State Data Center
(503) 373-0832
email: [EMAIL PROTECTED]
