I don't know who told you this, but it is NOT true at all.
It is very normal for ADSM to have multiple nodes on the same tape, even
with collocation on.

For instance, we have a tape library with 150 tapes available for the
primary storage pool, and 450 clients.
We set MAXSCRATCH in the storage pool to 150.
That means ADSM must put 3 clients on each tape.

This is NOT the cause of your I/O errors.

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************




> -----Original Message-----
> From: Peter Svendsen [SMTP:peter.svendsen AT ALMBRAND DOT DK]
> Sent: Tuesday, February 15, 2000 9:42 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Collocation problem
> 
> 
> Mauro
> 
> The problem is that i am running Collocation=yes, but there is still data
> from different
> notes on the same tape. And that causes the I/O error.
> 
> ADSM can not handle data from different serveres on the same tape, when
> the
> tapepool
> is defined with Collocation=yes.
> 
> I agree that if the problem is an I/O error, i should handle that problem
> first.
> 
> Peter
> 
> 
> 
> 
> 
> 
> "Mauro M. TINELLI" <Mauro.TINELLI AT ST DOT COM> - 15-02-2000 14:23:43
> 
> Besvar venligst til "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> Til:       ADSM-L AT VM.MARIST DOT EDU
> cc:         (bcc: Peter Svendsen/ABR/ALMBRAND)
> Vedrørende:    Re: Collocation problem
> 
>  << File: ATT112260.txt >>