You probably want to pipe the output of SHOW SLOTS into a file, and then
examine that file carefully. The output can be voluminous, but it can be
very useful, so do it.
You can also run the lbtest utility. Call IBM TSM Support for detailed
instructions, because it's an extremely powerful and useful program with
a not-too-friendly user interface. However, with lbtest you're talking
directly to the device driver, without TSM getting in between. Another
program whose output you want to somehow save in a file for more
contemplative examination. I save lbtest output via my SSH client.
Roger Deschner University of Illinois at Chicago rogerd AT uic DOT edu
======I have not lost my mind -- it is backed up on tape somewhere.=====
On Wed, 12 Oct 2011, Jerry Michalak wrote:
>try show slots <library_name> in TSM to see the library info.
Jerry Michalak
jerry_gjm AT yahoo DOT com
________________________________
From: "Moyer, Joni M" <joni.moyer AT HIGHMARK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Sent: Wednesday, October 12, 2011 12:57 PM
Subject: Re: [ADSM-L] Label volumes in a scsi library?
Hi,
I've tried to do this and I'm now getting the following errors:
10/06/11 12:50:34 ANR0609I LABEL LIBVOLUME started as process 33588.
(SESSION: 58343, PROCESS: 33588)
10/06/11 12:50:46 ANR2017I Administrator LIDZR8V issued command: QUERY
PROCESS (SESSION: 58344)
10/06/11 12:50:47 ANR8300E I/O error on library NAS_QI6000 (OP=00006C03,
CC=207, KEY=05, ASC=21, ASCQ=01, SENSE=70.00.05.00.00.00-
.00.0A.00.00.00.00.21.01.00.CF.00.06., Description=Device
is not in a state capable of performing request). Refer
to Appendix C in the 'Messages' manual for recommended
action. (SESSION: 58343, PROCESS: 33588)
10/06/11 12:50:48 ANR8942E Could not move volume Q00000 from slot-element
4096 to slot-element 65535. (SESSION: 58343, PROCESS:
33588)
10/06/11 12:50:48 ANR8802E LABEL LIBVOLUME process 33588 for library
NAS_QI6000 failed. (SESSION: 58343, PROCESS: 33588)
10/06/11 12:50:48 ANR0985I Process 33588 for LABEL LIBVOLUME running in the
BACKGROUND completed with completion state FAILURE at
It seems like it doesn't want to move the volume to a drive to label it, but
I'm having issues trying to figure out what that error message means from
Appendix C.
How do I tell where those slot elements are? It appears as if something is
still not working correctly, but I'm trying to figure out if this is a set up
issue? Or if it's something else entirely.
I defined a scsi library as follows for my nas partition which the drives are
zoned from the library to the datamovers and I have the library & path and
drives & paths defined within TSM:
Library Name: NAS_QI6000
Library Type: SCSI
ACS Id:
Private Category:
Scratch Category:
WORM Scratch Category:
External Manager:
Shared: No
LanFree:
ObeyMountRetention:
Primary Library Manager:
WWN:
Serial Number: QUANTUM273100111_LL2
AutoLabel: No
Reset Drives: No
Relabel Scratch:
Source Name: TSMPROD3
Source Type: SERVER
Destination Name: NAS_QI6000
Destination Type: LIBRARY
Library:
Node Name:
Device: /dev/lb0
External Manager:
LUN:
Initiator: 0
Directory:
On-Line: Yes
If anyone has any suggestions/ideas as to what I might be doing wrong I'd
really appreciate the help. Thanks!!!!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
James Choate
Sent: Friday, October 07, 2011 9:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Label volumes in a scsi library?
How did tape Q00000 get into the library? Did you manually load a batch of
tapes in this library without checking them in thru the bulk I/O?
If that is the case, you can just checkin the tapes.
You can try:
Check in volumes that are already labeled:
checkin libvolume NAS_QI6000 search=yes status=scratch checklabel=barcode
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Moyer, Joni M
Sent: Thursday, October 06, 2011 8:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Label volumes in a scsi library?
Hi Everyone,
I was trying to label a volume in a scsi library and I used the label libvol
command to try and label Q00000 in the library NAS_QI6000 and it is failing.
The tape is already physically in a slot in the library, so could someone
please explain how I am to label tapes within this library on TSM?
Any help is greatly appreciated!!!!
Date/Time Message
-------------------- ----------------------------------------------------------
10/06/11 10:24:59 ANR0984I Process 33581 for LABEL LIBVOLUME started in the
BACKGROUND at 10:24:59. (SESSION: 58024, PROCESS: 33581)
10/06/11 10:24:59 ANR8799I LABEL LIBVOLUME: Operation for library NAS_QI6000
started as process 33581. (SESSION: 58024, PROCESS:
33581)
10/06/11 10:24:59 ANR0609I LABEL LIBVOLUME started as process 33581.
(SESSION: 58024, PROCESS: 33581)
10/06/11 10:25:10 ANR8323I 006: Insert ANY volume Q00000 R/W into entry/exit
port of library NAS_QI6000 within 60 minute(s); issue
'REPLY' along with the request ID when ready. (SESSION:
58024, PROCESS: 33581)
10/06/11 10:26:45 ANR2017I Administrator LIDZR8V issued command: QUERY
ACTLOG search="process: 33581" (SESSION: 58028)
10/06/11 10:32:21 ANR2017I Administrator LIDZR8V issued command: QUERY
ACTLOG search="process: 33581" (SESSION: 58031)
10/06/11 10:32:30 ANR8385E All entry/exit ports of library NAS_QI6000 are
empty. (SESSION: 58024, PROCESS: 33581)
10/06/11 10:32:30 ANR8802E LABEL LIBVOLUME process 33581 for library
NAS_QI6000 failed. (SESSION: 58024, PROCESS: 33581)
10/06/11 10:32:30 ANR0985I Process 33581 for LABEL LIBVOLUME running in the
BACKGROUND completed with completion state FAILURE at
10:32:30. (SESSION: 58024, PROCESS: 33581)
________________________________
This e-mail and any attachments to it are confidential and are intended solely
for use of the individual or entity to whom they are addressed. If you have
received this e-mail in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this e-mail without the author's prior permission.
The views expressed in this e-mail message do not necessarily represent the
views of Highmark Inc., its subsidiaries, or affiliates.
>
|
