On other thing I noticed : There are no drives in use at all when I launch the 
command, so why not launch the four threads if there is no tape drive 
contention ?

Rich

-----Original Message-----
From: Richard Mochnaczewski 
Sent: Friday, February 10, 2006 9:24 AM
To: 'ADSM: Dist Stor Manager'
Subject: RE: [ADSM-L] Backup stgpool peculiarity


Hi Richard,

Thanks for the info. What's even stranger is I can launch the same type of 
process using another storage pool ( backup stgpool prd_disk prd_dr maxpr=4 ) 
and it WILL use 4 tape drives and multithread ?!?!?!?

Rich

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard Sims
Sent: Friday, February 10, 2006 9:12 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Backup stgpool peculiarity


On Feb 10, 2006, at 8:53 AM, Richard Mochnaczewski wrote:

> Why does it always default to one process instead of multiple
> sessions as I initiate ?

A question that keeps coming up...  Some prevailing factors:
The operation is node-oriented, which limits the actual number of
operating processes; and the operation is inherently limited in the
realities of serial-access media (see IBM Technote 1208545).

    Richard Sims