Richard Sims wrote:
>
> Given that the migration is to serially accessed, sequential media, I
> don't see the need for more than one major thread per migration
> stream, anyway. In such a context, I see a one-for-one
> quantification of threads and processes (where we keep in mind that a
> TSM pro
On Nov 28, 2007, at 1:11 PM, David Bronder wrote:
The question wasn't about migration _processes_, but migration
_threads_
internal to TSM. As you and Andrew both describe, there are multiple
migration _processes_ kicked off in both cases.
Given that the migration is to serially accessed, seq
PAC Brion Arnaud wrote:
>
> Your instructor should read his books again ...
The question wasn't about migration _processes_, but migration _threads_
internal to TSM. As you and Andrew both describe, there are multiple
migration _processes_ kicked off in both cases.
I hadn't heard anything about
Andrew,
Here, a snippet of the administrative command line online help "h mig
stg" :
This command creates one or more migration processes that can be
canceled
with the CANCEL PROCESS command. The number of processes is limited by
the
MIGPROCESS attribute of the storage pool definition. To disp
