Well, check into the APAR info associated with PTF 10, 11, & 12 (for
     AIX anyway...) I can't remember, I think ptf11 has fixes where such
     things like if a node is backing up going to disk and the diskpool
     reaches its HIGH limit and migration kicks in, if a node's tape is
     being used for migration and the node is still backing up rather than
     write to the same tape it will call for a scratch... and other such
     times when multiple processes associated with a node's data are
     needing to write to tape scratches will be called for....


______________________________ Reply Separator _________________________________
Subject: Tape Utilization and Collocation
Author:  ADSM-L at unix,mime/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date:    2/13/97 8:39 AM


I have collocation turned on by node in my tape storage pool.  In 1 day, I
created 3 new tapes for the same node - 2 were created by MOVE DATA commands
and 1 was created during the nightly incremental backup.  The percent utilized
for the 1st tape created was .4%, the second was 1.6% and the third was 70.2%.
I have since issued MOVE DATA commands for other nodes and a tape in filling
status was mounted and used instead of a scratch tape.  Does anyone know of
circumstances under which this multiple tape creating occurs? (the only times
these tapes were mounted on that day was when they were being created).  Any
responses will be appreciated.