Conference decwet::networker

382.0. "TL812 and Barcode Labels" by NQOS01::rdodial_port16.32.81.16.in-addr.arpa::ATKINS (atkinss@mail.dec.com) Tue Feb 04 1997 18:57

I have a Alpha 4100 running NT 3.51 and NSR 4.3 connected to a TL812.

(A) When I set the AutoChanger Option to Match Volumes and Bar code Labels I 
could not get the Labels process to work. It grabs a tape from Slot 1 and 
tells me the tape is unlabled in the message window. Then it gives me a 
message that says Slot 1 is emtpy, leaving the tape in the //dev0. 

When I changed the Match Bar Code Labels back to "no" I was able to label the 
volumes.

I could have hosed up everything because I cheated and loaded all the tapes by 
hand. 

I ran the following command from the DOS prompt after I loaded the tapes.

NSRJB -H

and it said that contents may have changed (I expected it would) and I needed 
to issue the NSRJB -IE command. So I did that and went back to the GUI where 
it said all the Volumes were unlabeled.

I then tried to Label the Volumes in slots 1-46 with the Match set to 
"YES", and the Label Field said "Bar Code Label"

I got the same results in (A) above.

When I changed Match Bar Code Labels back to "NO" I was able to label the 
tapes with the default label (system.name.domain.com.001).

The Tape in slot 1 has a Bar Code label of ALF501, slot 2 ALF502, through Slot 
46 with a label of ALF546.

Any Ideas.

Thanks,
Steve
Atkinss@mail.dec.com

Also, If I'm correct the Juke Box Firmware numbers the Slots from Left to 
Right, top to Bottom. Legato NSR numbers the Slots from Top to Bottom, Left to 
Right.  I say this becuase if you have the Juke Box set for AutoLoad and feed 
it tapes it loads them in in Juke Box Order. 


Juke Box       Legato NSR

 1  2  3       1  17  33
 4  5  6       2  18  34
 7  8  9       3  19  35
 .  .  .       .   .   .
 .  .  .       .   .   .
 .  .  .       .   .   .
 46 47 48      16  32 48

Is there a easy way to make these match.

This is a duplicate of an IPMT.  A patched
nsrjb was made for this.  If it is not in
the list of patches, it should be soon. 

See note 56.2 (just posted) for the location of this patch.

Wes