Before and during the execution of the Move Volume utility, you
should minimize or quiesce the following types of system activity,
which might interfere with the utility:
- Any activity involving reading from the
source volume. Or, if the source volume is an optical volume any activity
involving reading from the volume on the opposite
side of the optical disk. If read activity on the source volume cannot
be quiesced, investigate using the UPD=N option on the CBRINIT statement
in the IEFSSNxx member of PARMLIB during initial program
load (IPL). This will avoid conflicting updates to the objects'
directory entries.
- Any activity involving inserting, selecting,
updating, or deleting operations on the OAM DB2 object directory
table for the storage group.
System activity includes, but is not limited to the following:
- Scheduled or operator-initiated OSMC storage group management
cycles involving the:
- Storage group that contains the source volume when moving objects
from a primary volume.
- Storage groups that contain objects that have a backup copy on
the source volume when moving objects from a backup optical volume.
- Operator-initiated invocations of the Move Volume utility for
other volumes requiring the same OAM DB2 object directory tables.
- Operator-initiated invocations of the Volume Recovery utility
for other volumes requiring the same OAM DB2 object directory tables.
- Operator-initiated Tape Recycle commands affecting volumes requiring
the same OAM DB2 object directory tables.
- Applications using the OSREQ interface to read data from or write
data to the storage groups referenced by the Move Volume utility,
or both.
Failure to minimize or quiesce this type of system activity might
cause operations in the other system activities to complete unsuccessfully
(for example, due to the unavailability of the source volume during
the execution of the utility) or might interfere with the operation
of the utility (for example, causing contention in the DB2 databases
required for the utility to operate).