Mark,

You don't want the wait on the update storage pool command - that command
only resets the values in the database and causes the creation of a detached
process that does the migration.  What you need to do is monitor the
detached process for completion and then trigger the next update stgpool.
That's not so easy.

Most people just estimate the amount of time it takes to do the migration
and add some fudge before setting off the next migration.  You can
periodically search the activity log for completion of the migration
process - that takes some work.  An engineer in our organization wrote a
program to synchronize all the daily functions and put it in a GUI, but that
took a lot of work.

Bill Smoldt   SSSI
Storage Solutions Specialists, Inc.
smoldt AT storsol DOT com