ARC0535I

Explanation
 DFSMShsm attempted to migrate the volume
with the volume serial number volser or migrate
all level 1 migration volumes, but encountered one of the following
errors:  The source migration level 2 tape volume was in use by another
task.
There was no target tape migration level 2 available.
There was no DASD migration level 2 volume available.
There was no DASD migration level 1 volume available and no DASD
migration level 2 volume available.
There was no DASD migration level 1 volume available and no tape
migration level 2 volume available.
Migration or automigration was held.
DFSMShsm was
put in emergency mode.
DFSMShsm was
being shutdown.
For the volume that is being space managed, there have been ten
I/O errors trying to read or write records in the migration control
data set (MCDS) or the offline control data set (OCDS). See previous
ARC0184I messages for the specifics of the I/O errors. Errors reading
the MCDS management control record (MCR) are not counted in this total.
See message ARC0539I or ARC0307I for more details.
In an attempt to GETMAIN storage for the buffers needed for data
movement, an error occurred. If a GETMAIN error occurs, migration
will be held. See the preceding ARC0305I or ARC0307I message for the
specific failing code.
The internal migration queue (MQ) limit is reached during space
management for the current volume. The space management for the volume
will be stopped. Nevertheless, the MDQEs, queued on MQ, will be processed.
DFSMShsm will continue to space manage other volumes.
There was an abnormal end (abend) in either the tape migration
data set installation-wide exit or the second level migration data
set installation-wide exit. Migration has been held.
The ESTAE environment could not be set up for the process of moving
data during a DFSMShsm migration
operation.
On-demand migration ended early because interval
migration (IM) started.
On-demand migration ended early because primary
space management (PSM) started.

System action
 The migration of the volume ends. DFSMShsm processing
continues.
 If there was an abend in the migrate data set installation-wide
exit, migration has been held. DFSMShsm processing continues without the
migration function.

Programmer response
  The message insert TAPE MIGRATION VOLUME IN USE is associated
with either a MIGRATE VOLUME(volser DELETEBYAGE(days))
command or a MIGRATE VOLUME (volser DELETEIFBACKEDUP(days))
command, and an ARC0560E message has not been issued. When the indicated
volume is no longer in use, reissue the volume migration command.
See message ARC0560E that was issued to the operator’s console
and the migration activity log. This message was issued for each migration
target that DFSMShsm determined
was unavailable. Also, message ARC0560E contains the appropriate programmer
response for the error condition encountered.
Release migration, if it was held. Retry the volume migration
when the correction has been made.
Issue SETSYS NOEMERGENCY, if DFSMShsm was put in EMERGENCY mode. Retry
the volume migration when the correction has been made.
Determine the cause of the I/O errors and take corrective action
on the control data set.
Stop DFSMShsm and
restart DFSMShsm with
additional storage requested.
No actions are required for MIGRATION QUEUE LIMIT REACHED. The
remainder of the volume space management will be made during the next
PSM or IM. If you need the volume space management to be performed
earlier, issue the F DFHSM,MIGRATE VOLUME(volser) command. You can
determine the internal MQ limit using the F DFHSM,DISPLAY .MGCB.+100
command.  If you wish to update this value, see the topic on "Modifying
the migration queue limit value" section in the Tuning
DFSMShsm chapter of z/OS DFSMShsm Implementation and Customization Guide.

Find the cause of the abend in the installation-wide exit. When
the cause is determined, fix and relink the exit module. Use the EXITON
parameter of the SETSYS command to reload the exit. To start the migration
function, issue the RELEASE command with the MIGRATION parameter.
Determine why the ESTAE could not be set up and take corrective
action.
No actions are required for ON-DEMAND MIGRATION
ENDED EARLY, INTERVAL MIGRATION WILL START. The remainder of the volume
space management will be made during the next on-demand migration
or during the primary space management run. 
No actions are required for ON-DEMAND MIGRATION
ENDED EARLY, PRIMARY SPACE MANAGEMENT WILL START. The remainder of
the volume space management will be made while primary space management
runs. 

 Retry the migration when the correction has been made.

Source
 DFSMShsm