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.

At 08:04 AM 6/19/98 EDT, you wrote:
>My Environment is a NT 4.0 server running ADSM v3.1.1.3
>
>I am wondering has anyone had any trouble running the Audit Library command
>with a STK 9174 unit and ADSM randomly saying it cannot read the barcodes and
>have to insert multiple  tapes to read the labels.
>
>I am experiencing very random slots that ADSM Audit Library says the barcode
>can not be read on, We have swapped labels , tapes etc,,,and each time Audit
>Library is ran the Slots it says it can't read are different..
>
>Thanks for the input.
>
>John Stephens
>
>