emsi
ADSM.ORG Member
Hi!
After migrating to 5.3 I found that there is a new command migrate stgpool. It seemed quite cool but I found it exhibits strange behavior: the duration arguments seems to be misinterpreted.
When I invoke:
MIGrate STGpool DISK LOwmig=0 duration=9900 w=y
(note the 9900, but any number in range from 1 to 9999 gives the same result)
It quits immediately with:
ANR0984I Process 127 for MIGRATION started in the FOREGROUND at 09:39:19 AM.
ANR2110I MIGRATE STGPOOL started as process 127.
ANR1000I Migration process 127 started for storage pool DISK manually, highMig=90, lowMig=0, duration=9900.
ANR0984I Process 128 for MIGRATION started in the FOREGROUND at 09:39:19 AM.
ANR2110I MIGRATE STGPOOL started as process 128.
ANR1000I Migration process 128 started for storage pool DISK manually, highMig=90, lowMig=0, duration=9900.
ANR4925W Migration process 127 terminated for storage pool DISK - duration exceeded.
ANR0985I Process 127 for MIGRATION running in the FOREGROUND completed with completion state SUCCESS at 09:39:19 AM.
ANR4925W Migration process 128 terminated for storage pool DISK - duration exceeded.
ANR0985I Process 128 for MIGRATION running in the FOREGROUND completed with completion state SUCCESS at 09:39:19 AM.
See the time: the start and end happens in the same second and the warning is "duration exceeded".
The storage pool DISK has MIGPRocess=2 (I'm not sure if it does matter).
I tried many things including ACCEPT DATE and nothing solves the problem.
The TSM version is 5.3.2 on Linux. Can anyone here confirm similar behavior?
After migrating to 5.3 I found that there is a new command migrate stgpool. It seemed quite cool but I found it exhibits strange behavior: the duration arguments seems to be misinterpreted.
When I invoke:
MIGrate STGpool DISK LOwmig=0 duration=9900 w=y
(note the 9900, but any number in range from 1 to 9999 gives the same result)
It quits immediately with:
ANR0984I Process 127 for MIGRATION started in the FOREGROUND at 09:39:19 AM.
ANR2110I MIGRATE STGPOOL started as process 127.
ANR1000I Migration process 127 started for storage pool DISK manually, highMig=90, lowMig=0, duration=9900.
ANR0984I Process 128 for MIGRATION started in the FOREGROUND at 09:39:19 AM.
ANR2110I MIGRATE STGPOOL started as process 128.
ANR1000I Migration process 128 started for storage pool DISK manually, highMig=90, lowMig=0, duration=9900.
ANR4925W Migration process 127 terminated for storage pool DISK - duration exceeded.
ANR0985I Process 127 for MIGRATION running in the FOREGROUND completed with completion state SUCCESS at 09:39:19 AM.
ANR4925W Migration process 128 terminated for storage pool DISK - duration exceeded.
ANR0985I Process 128 for MIGRATION running in the FOREGROUND completed with completion state SUCCESS at 09:39:19 AM.
See the time: the start and end happens in the same second and the warning is "duration exceeded".
The storage pool DISK has MIGPRocess=2 (I'm not sure if it does matter).
I tried many things including ACCEPT DATE and nothing solves the problem.
The TSM version is 5.3.2 on Linux. Can anyone here confirm similar behavior?
