ARC0560E

Explanation
 During a volume migration (from a DFSMShsm-managed
volume or from a migration volume), level 1 to level 2 migration,
or data set migration, DFSMShsm failed to migrate a data set. The
migration failed because of a lack of available space in the hierarchy
or because some condition occurred making it impossible (or inadvisable)
to continue migrating to a certain level in the hierarchy. Migration
to migration level 1 may be inhibited if there is no space remaining
in the VTOC or VTOC index on the volumes that are defined.
 The
EXCESSIVE I/O ERRORS and ABEND IN TAPE INSTALLATION-WIDE EXIT conditions
occurred while trying to migrate a data set to tape.
 EXCESSIVE
I/O ERRORS means either  Five I/O errors occurred while reading the management control
record (MCR).
Ten I/O errors occurred while accessing records other than the
MCR in either the migration control data set (MCDS) or offline control
data set (OCDS), or both.

 A tape migration volume is considered not available if
one of the following conditions is true:  An attempt was made to migrate a data set to a tape migration
level 2 volume, and either the operator responded to the mount request
with a NO, or the timer to mount a tape expired. A new tape volume
was selected and again the operator could not mount the tape.
There have been ten I/O errors trying to read or write records
in MCDS or the OCDS. See previous ARC0184I messages for the specifics
of the I/O errors. Errors reading the MCDS MCR are not counted in
this total.
When DFSMShsm is
in a tape migration environment (SETSYS TAPEMIGRATION(DIRECT)) or
(SETSYS TAPEMIGRATION(ML2TAPE)), MCR is checked after the migration
of each data set is complete to see if a recall task needs a tape
that is allocated to a migration task. When DFSMShsm is in a multiprocessing
unit environment, the DASD copy of the MCR needs to be checked. There
have been five errors in the read of the MCR record. An ARC0184I message
is issued each time the read failed.
The tape data set installation-wide exit (ARCTDEXT) abnormally
ended (abended).

 No migration level 1 volume is considered available if
one of the following conditions is true:  No migration level 1 volume has been ADDVOLed to DFSMShsm.
The space between the full volume and the high threshold of the
selected migration volume is too small for a small data set, but not
for a small data set packing data set. The migration failed because
sufficient space was not available on the migration volumes. The failure
occurred on two consecutive attempts, and the migration (level 1)
volumes were space checked between attempts.

System action
 The particular migration request failed. DFSMShsm issues
either an ARC12nnx message (for data set command
migration) or an associated ARC0734I message (for volume migration),
giving specific reasons for the failure.
 DFSMShsm continues migrating
data for those cases where other target levels can still be used.
 If
the NO TAPE MIGRATION VOLUME AVAILABLE, EXCESSIVE I/O ERRORS, or ABEND
IN TAPE INSTALLATION-WIDE EXIT condition occurred, DFSMShsm stops trying to migrate
to tape.
 Until a RELEASE MIGRATION or RELEASE AUTOMIGRATION
or RELEASE ALL command is issued, DFSMShsm will not attempt to migrate any
data set that would require using the indicated hierarchy level as
a target.
 Note: If DFSMShsm was migrating a volume (as the
result of a MIGRATE command, FREEVOL command, interval migration or
automatic primary space management), or was processing the automatic
secondary space management when the condition occurred, some of the
data sets on the volume may still migrate successfully.

Operator response
 When the original problem is corrected (or
if migration can continue without exit ARCTDEXT being active):  Delete the ARC0560E message from the console.  If the message identifier is not available, issue the DISPLAY
R,I command to get the ID.
To delete the message, issue the following command using the message
identifier id obtained from the above DISPLAY R,I
command.  CONTROL C,I,id

Issue the RELEASE MIGRATION command to allow DFSMShsm to attempt using the
indicated level and device category.

 Note: There may be more than one such message on the console
if a problem with one hierarchy level was not resolved before DFSMShsm encountered
a problem with another level in the hierarchy.

Programmer response
  For NO LEVEL 1 MIGRATION SPACE AVAILABLE, if there is free space
on ML2, then FREEVOL some ML1 volume(s) to level 2, to clear some
space on level 1. Otherwise, have at least one level 1 volume ADDVOLed.
 Reorganize the index, if it is full, and reissue the ADDVOL command
to add the migration level 1 volume.

For NO LEVEL 1 MIGRATION VOLUME AVAILABLE, have at least one level
1 volume ADDVOLed.
For NO DASD LEVEL 2 MIGRATION VOLUME AVAILABLE, have at least
one level 2 volume ADDVOLed.
For NO TAPE MIGRATION VOLUME AVAILABLE OR TAPE ALLOCATION
ERROR, determine why no tape is made available to DFSMShsm and have at least one
tape available, or fix the allocation problem.
For EXCESSIVE I/O ERRORS, analyze the most recent ARC0184I error
messages against the MCDS and OCDS to determine the specific problem
needing correction.
For ABEND IN TAPE INSTALLATION-WIDE EXIT, issue the SETSYS EXITOFF
command to inactivate the migration-tape data set installation-wide
exit (ARCTDEXT).  If migration can proceed without ARCTDEXT being
active, migration can be released before the exit is corrected.
  The
ARCTDEXT module should be examined to determine the reason for the
abend; when corrected, the exit can be relinked and the SETSYS EXITON
command used to reactivate the exit.

 When the original problem has been corrected, issue the
RELEASE MIGRATION command to allow DFSMShsm to attempt using the indicated
level and device category.
 If an ADDVOL command is issued for
the unavailable volume type while a volume migration is in progress,
data sets will be directed to the volume just added without requiring
a RELEASE MIGRATION command.

Source
 DFSMShsm