You only get one migration process for every client's data in the source
pool.  Since you only have one client on this server, that's all you'll
see.  There is no way that I've figured out to cause multiple migration
processes for one client.

One suggestion may be to set a maxsize parameter on your DASD pool, so that
some files will skip straight to tape.  This will cause a second tape drive
to be used if migration is already in use.  If you're also playing with the
resourceutilization parameter on the client (and sending more than one file
at a time), you may be able to push your tape drives a little harder.

Nick Cassimatis
nickpc AT us.ibm DOT com