This should be an easy question, but the answer is eluding me.  As part of
the normal process of taking tapes from the off-site storage pool in & out
of the library, we run the command:
    CHECKIN libvol ibm3447 checklab=bar search=yes status=scratch

It works, but the catch is when there's a cleaning tape in the system.  My
understanding of the 3447 is that the library itself will grab the cleaner
and use it as needed.  The CHECKIN process, however, fails when it reaches
the cleaning tape.  (see log file below)

Should cleaning tapes have a barcode?  Is this failure normal?

-Mitch
 05/17/1999 12:11:30 ANR2017I Administrator ADMIN issued command: CHECKIN
 05/17/1999 12:11:30 ANR2017I Administrator ADMIN issued command: CHECKIN
libvol ibm3447 checklab=bar search=yes status=scratch
 05/17/1999 12:11:30 ANR0984I Process 31 for CHECKIN LIBVOLUME started in
the BACKGROUND at 12:11:30.
 05/17/1999 12:11:30 ANR8422I CHECKIN LIBVOLUME: Operation for library
IBM3447 started as process 31.
 05/17/1999 12:15:12 ANR8788W Unable to read the barcode of cartridge in
slot-id 10 in library IBM3447;  loading in drive to read label.
 05/17/1999 12:30:33 ANR8304E Time out error on drive DRIVE_B (MT5.0.0.1) in
library IBM3447.
 05/17/1999 12:30:33 ANR8912E Unable to verify the label of volume from
slot-element 10 in library IBM3447.
 05/17/1999 12:30:46 ANR8832E CHECKIN LIBVOLUME for volumes in search mode
in library IBM3447 failed.
 05/17/1999 12:30:46 ANR0985I Process 31 for CHECKIN LIBVOLUME running in
the BACKGROUND completed with completion state FAILURE at 12:30:46.

____________________________________________________________
Mitchell Ross                           mailto:mross AT psd.compucom DOT com
CompuCom Systems, Inc.
The Source for Technology Deployment Processes and Standards