MIGRATION HELD, {NO MIGRATION LEVEL 1 VOLUME AVAILABLE |
NO MIGRATION LEVEL 1 VOLUME AND NO TAPE MIGRATION VOLUME AVAILABLE
| NO TAPE MIGRATION VOLUME AVAILABLE}, {ABEND IN INSTALLATION-WIDE
EXIT | ESTAE SET UP FOR DATA MOVEMENT FAILED}
Explanation
If an abend in an installation-wide
exit occurred or if the ESTAE setup failed, space management was held. During
migration processing, DFSMShsm detected that the required target
migration volumes were not available for migration to continue to
run. The required target migration volume types are listed below:
- Migration level 1 DASD and migration level 2 tapes, if either
of the following is true:
- The storage management subsystem (SMS) is installed.
- The data set migration exit (ARCMDEXT) is active in the system.
- Migration level 1 DASD, if all of the following are true:
- SMS is not installed on the system.
- The data set migration exit (ARCMDEXT) is not active in the system.
- The DFSMShsm tape
migration environment is not direct-to-tape.
- Migration level 1 DASD, if all of the following are true:
- SMS is installed on the system.
- The SMS management class definitions do not direct any SMS-managed
data set to level 2 tape.
- The data set migration exit (ARCMDEXT) is not active in the system.
- The DFSMShsm tape
migration environment is not direct-to-tape.
- Migration level 2 tape, if all of the following are true:
- SMS is not installed on the system.
- The DFSMShsm tape
migration environment is direct-to-tape.
System action
The migration was held; DFSMShsm processing continues.
Programmer response
If an abend in an installation
exit occurred, see message ARC0004I to identify the exit and abend
code. Bring this abend to the attention of a Storage Administrator.
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. After the failure has
been corrected, issue the RELEASE MIGRATION command and retry the
request. If the ESTAE setup for data movement failed, search problem
reporting databases for a fix for the problem. If no fix exists, contact
the IBM® Support Center.