Jennifer and everyone who responded:
Thank you for your help; I have talked with STK and the barcode manufacturer
and it seems STK has went back to designing there robots to read barcodes with
an additions character other than the 6 on the label.
The official label for STK DLT7000 drive systems must have a small D in the
lower let corner and be a 1703 style label.
I setup about 30 of these labels and ran and reran Audit  Library and had no
errors reading the barcodes.

Thanks again for your input.
John Stephens










Date:    Fri, 19 Jun 1998 19:16:41 -0500
From:    Jennifer Davis <jedavis AT DFW DOT NET>
Subject: Re: Audit Library trouble with barcodes

John,

ADSM makes a call to the library through the device drives and waits for
information back. If you are getting messages back that indicate that
barcodes can not be read, it is most likely the library telling ADSM this.

With this in mind, check your STK library / device driver information to
determine
if there is a mechanism with which you can test the ability to mount and
unmount
tapes from the OS --> outside of ADSM, thus forcing the library to read the
barcodes.

(For example: some IBM library's device support provide the 'tapeutil' utility
for this pupose)

I think that you will find that you have the same problem.
Force the STK libary to do a Hardware inventory --> like by opening the
door and closing it, THEN try the AUDIT LIBRARY command. Often these
conditions are clear once the library "has found it's head again".

Also, check your NT event log to ensure that you are not logging any
library errors there.

Last but not least, ensure that you have the most current microcode
installed for
the library.

Good Luck.