The only way to solve this problem is to move all drives to first frame
and make sure there are no empty drive elements!
The way Networker currently works is that it takes the first and last
element number that drives are reported in and based on this calculates
to total number of drives.
There should be no REAL problem moving the drives in all frames to  be
consecutive starting with the first one except the time needed... (a few
work hours for the technician). Any words of "wisdom" by the vendor that
this will slow down the jukebox can be practically dismissed due to the
fact that taking a tape from the third frame to a drive in the first
frame will only be marginally longer that doing that in the same frame.
The exact timing are described in the jukebox documentation.
The only other possibility would be for Legato to rewrite the way they
handle jukebox elements in their implementation of the SJI standard.
I am not aware if the standard itself has the way this should be handled
defined.
I know that other backup software products do not suffer from the empty
elements (TXX,Vxxxxxx,...).
Itzik

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Gerardo Gomez
> Sent: Wednesday, May 04, 2005 20:46
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] ibm 3584 vs networker
> 
> Greetengs,
> 
> I am installing an IBM 3584. I have the same problem 
> described in this entry. I have three module library. In 
> first module I have 5 LTO drives and in second module other 5 
> LTO drives. As you descrived, sjirelem and jbconfig command 
> shows 17 drives, forcing us to define 7 dummy devices for 
> first module.
> 
> Have you ever solve this problem?
> It is posible configure the IBM 3584 to NOT show those NON 
> existing devices?
> 
> C:\>sjirelem [email protected]
> Element Data for [email protected], Element Type DATA TRANSPORT:
>         Elem[001]: pres_val=1 med_pres=0 med_side=0
>         Elem[002]: pres_val=1 med_pres=0 med_side=0
>         Elem[003]: pres_val=1 med_pres=0 med_side=0
>         Elem[004]: pres_val=1 med_pres=0 med_side=0
>         Elem[005]: pres_val=1 med_pres=0 med_side=0
>         Elem[006]: pres_val=0 med_pres=0 med_side=0
>         Elem[007]: pres_val=0 med_pres=0 med_side=0
>         Elem[008]: pres_val=0 med_pres=0 med_side=0
>         Elem[009]: pres_val=0 med_pres=0 med_side=0
>         Elem[010]: pres_val=0 med_pres=0 med_side=0
>         Elem[011]: pres_val=0 med_pres=0 med_side=0
>         Elem[012]: pres_val=0 med_pres=0 med_side=0
>         Elem[013]: pres_val=1 med_pres=0 med_side=0
>         Elem[014]: pres_val=1 med_pres=0 med_side=0
>         Elem[015]: pres_val=1 med_pres=0 med_side=0
>         Elem[016]: pres_val=1 med_pres=0 med_side=0
>         Elem[017]: pres_val=1 med_pres=0 med_side=0
> 
> 
> Regards,
> Gerardo.
> 
> --
> Note: To sign off this list, send a "signoff networker" 
> command via email to listserv AT listserv.temple DOT edu or visit 
> the list's Web site at 
> http://listserv.temple.edu/archives/networker.html where you 
> can also view and post messages to the list. Questions 
> regarding this list should be sent to stan AT temple DOT edu 
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> 

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=