Process symptoms indicate migration errors
You might be faced with process symptoms that point to migration as the cause for errors.
Migration does not run for sequential media storage pool
If migration does not run for sequential media storage pools, issue the QUERY STGPOOL stgpoolName F=D command.
Migration
from sequential media storage pools calculates the Pct. Util
as
the number of volumes in use for the storage pool, relative to the
total number of volumes that can be used for that storage pool. Similarly,
it calculates the Pct. Migr
as the number of volumes with data
that can be migrated, in use for the storage pool, relative to the
total number of volumes that can be used for that storage pool. Because
it might be considering unused scratch volumes in this calculation,
there might not appear to be sufficient data that can be migrated
in the storage pool to require migration processing.
Migration uses only one process
Issue the QUERY STGPOOL stgpoolName F=D and QUERY OCCUPANCY * * STGPOOL= stgpoolName command.
- The Migration Processes setting for the storage pool is set to one or is not defined (blank). If true, issue the UPDATE STGPOOL stgpoolName MIGPROCESS=n command, where n is the number of processes to use for migrating from this pool. Note that this value must be less than or equal to the number of drives (mount limit) for the NEXT storage pool where migration is storing data.
- If the QUERY OCCUPANCY command only reports a single client node and file space in this storage pool, migration can only run a single process even if the Migration Processes setting for the storage pool is greater than one. Migration processing is partitioning data, based on client node and file space. For migration to run with multiple processes, data for more than one client node needs to be available in that storage pool.