Thanks, but colocation is not on (nor was there any other
activity going on during the migration).

Pat

>  Check to see that Collocation is not enabled for that STg pool, if
>  collocation is set for 'yes' then during migration when the data from
>  another client is set to migrate to your stgpool it will need to mount
>  another tape to keep that data together .
>
>  Regards,
>  John Stephens
>
>  ***************************************************************************
>
>  Date:    Tue, 6 Oct 1998 11:52:21 -0400
>  From:    Pat Wilson <paw AT NORTHSTAR.DARTMOUTH DOT EDU>
>  Subject: stgpool migration starts 2nd scratch tape?
>
>
>
>  Hmm.  Why would ADSM start a 2nd tape (during a normal stgpool
>  migration) when the (first) tape it's been writing to is still
>  present and enabled?  In the following log, we first write to D0012 a
>  couple of times, then dismount it, and then _remount_ it (in the other
>  drive), but also mount a new scratch volume (D0013) and decide to write to
>  that.
>
>  Is there some parameter I should be setting?  I'd expected everything to
>  write on one tape (only 17GB of data, and we've got 35GB DLT tapes).  D0012
>  is now 41% full, still R/W access, and in the "filling" state.
>
>  Thanks.
>
>  Pat Wilson
>  paw AT dartmouth DOT edu
>  ----------------------------------------------------------------
>  The information transmitted is intended only for the person or entity to
>  which it is addressed and may contain confidential and/or privileged
>  material.  Any review, retransmission, dissemination or other use of, or
>  taking of any action in reliance upon, this information by persons or
>  entities other than the intended recipient is prohibited.   If you received
>  this in error, please contact the sender and delete the material from any
>  computer.