At 21:40 +0100 on 09/18/2013, Graham Harris wrote about Re: HMIGRATE
in parallel:
I agree. What should not be hard for HSM to create multiple migration
subtasks (each with its own ML2 dataset) and have the master task pass one
dataset at a time to each subtask (ie: The subtask does the same work as is
currently done for a migrate). As each subtask finishes it asks the master
task for another dataset to migrate. That way you are migrating as many
datasets in parallel as you have subtasks allocated.
</snip>
...which is exactly what HSM provides for automatic migration, under the
control of maxmigration task setsys settings. What HSM does not provide is
such controls/parallelism for manual (HMIGRATE) migration, which is what
the OP is seemingly wanting, but no explanation as to why he wants this, as
opposed to letting HSM do what it was designed to do.
HSM auto migrate does the migration whenever it wants to not on the
"Do It NOW" basis that HMIGRATE does. Thus there is no assurance of
when a dataset will be auto migrated (only that it will eventually
occur once the migration criteria is met). HMIGRATE insures that the
migration is triggered immediately once the migration request is made.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
