I've issued the command with -barcode too, but I thought I read
somewhere that it wasn't necessary with a 3494 so I tried it without and
it worked.  Likewise, I believe the element # is not needed for a 3494
with 3590 drives.  It labels them just fine based on the bar code, it
just does them one at a time.  Also, I can do backups/archives to all 4
drives concurrently.

> -----Original Message-----
> From: Kelly J. Lipp [SMTP:lipp AT storsol DOT com]
> Sent: Tuesday, May 19, 1998 9:18 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: dsmlabel using multiple drives
>
> In my experience, I needed to include the drive,element number and I
> would
> use the -barcode qualifier too.  Since the -barcode isn't there, are
> you
> having to enter the volume label manually?  If so, this is probably
> the
> problem.
>
> Kelly Lipp
> Storage Solutions Specialists, Inc.
> lipp AT storsol DOT com
> www.storsol.com
> (719) 531-5926
>
> -----Original Message-----
> From:   Hilton Tina [SMTP:HiltonT AT TCE DOT COM]
> Sent:   Tuesday, May 19, 1998 11:42 AM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        dsmlabel using multiple drives
>
> We recently got a 3494 with 4 3590 tape drives for ADSM v2.1.5.15 on
> AIX
> 4.1.5.  When I use the dsmlabel command with all 4 drives included, I
> thought it would use them all simultaneously.  Instead it loads a tape
> in one drive, then when that tape is finished (but not ejected) it
> will
> load a tape in the next drive, then remove the ejected tape from the
> first, and on and on.  Shouldn't it use all drives concurrently, or is
> dsmlabel single-threaded?  Nothing else is happening in ADSM and I've
> even tried halting the server while the dsmlabel runs.
>
> My command is:
>
> dsmlabel -drive=/dev/rmt2 -drive=/dev/rmt3 -drive=/dev/rmt4
> -drive=/dev/rmt5 -library=/dev/lmcp0 -search -keep
>
> Any assistance would be appreciated.
>
> Tina Hilton
> Systems Consultant
> Thomson Consumer Electronics, Inc.
> Systems Software
> hiltont AT tce DOT com
> 317-587-4292