We sometime get this with a broke tape or a tape that is write locked. We usually check them out and look at them. If they look good we log their number and check them back in. We log the number to see if it happens to them again. If so we get rid of them.
Just my 2 cents worth. -- Phillip Ford Senior Software Specialist Corporate Computer Center Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 2:17 AM To: [EMAIL PROTECTED] Subject: Re: q libv showed 'private' STATUS but blank LAST_USE All you have to do is issue an update libvolume [lib] [volume] status=scratch. If it is not in use TSM will change it to scratch. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -----Original Message----- From: Joel Fuhrman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 8:53 PM To: [EMAIL PROTECTED] Subject: Re: q libv showed 'private' STATUS but blank LAST_USE Check the tape out and then back in with a status=scratch. On Wed, 5 Jun 2002, Chuck Lam wrote: > TSM 4.1.4 running in AIX 4.3.3 > > After I came back from the Memorial weekend, I noticed > a bunch of tapes with 'private' Status but blank > Last_Use when I did a 'q libv'. 'q vol volume_name' > on these tapes returned with 'NO MATCH'. There were > problems with one of the tape drives over that weekend > and a lot of tapes were marked as 'UNAVAILABLE' by > TSM, but I was able to make them work again by > modifying the access=readwrite. However, I cannot > even 'q volume' this bunch of tapes, since TSM seemed > to lose track of them. > > Can anyone help me with this problem? > > TIA > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > *************************************************************** This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.
