IBM Support

DFSMShsm: ARC0560E MIGRATION LIMITED: NO MIGRATION LEVEL 1

How To


Summary

During HSM space management on volume VOL123, migration to a Level 1 (ML1) volume failed. The system issued message ARC0560E MIGRATION LIMITED: NO LEVEL 1 MIGRATION VOLUME AVAILABLE, indicating that no suitable ML1 volume was available for dataset migration. Further investigation revealed that the failure was due to a VTOC index space issue on the target ML1 volume.

Objective

To identify the root cause of the ARC0560E message and resolve the migration failure by verifying and correcting VTOC index limitations on the target ML1 volume.

Environment

z/OS 

Steps

1. Review HSM Messages

The following messages were observed during space management:

ARC0522I SPACE MANAGEMENT STARTING ON VOLUME VOL123(SMS)

ARC0523I SPACE MANAGEMENT ENDED ON VOLUME VOL123  

ARC0560E MIGRATION LIMITED: NO MIGRATION LEVEL 1 VOLUME AVAILABLE  

ARC0559I MIGRATION LEVEL 1 WILL NOT BE TARGETED UNTIL A SUITABLE VOLUME IS AVAILABLE  

2. Analyze PDA Output

  • HSM attempted to migrate dataset 'dsname' from VOL123 to ML1 volume ML1234.
  • Migration failed with ARC1244I, indicating a VTOC issue on the target volume.
  • Allocation error ARC0503E was issued with: RETURN CODE=0004, REASON CODE=4708

3. Interpret Reason Code 4708

According to IBM documentation, Reason Code 4708 means:

  • The VTOC index lacked space for a new entry, or
  • There were insufficient DSCBs to allocate the dataset.

IBM z/OS DYNALLOC Reason Codes

https://www.ibm.com/docs/en/zos/latest?topic=codes-interpreting-error-reason-from-dynalloc

4. Run LISTVTOC to Confirm VTOC Index Status

Use the following JCL to list VTOC and index details:

//STEP01  EXEC PGM=IEHLIST
//SYSPRINT DD SYSOUT=*
//DD1      DD UNIT=3390,DISP=SHR,VOL=SER=VOL123   << replace with actual volser
//SYSIN    DD *
  LISTVTOC DUMP,VOL=3390=VOL123
  LISTVTOC FORMAT,VOL=3390=VOL123
  LISTVTOC FORMAT,INDEXDSN=SYS1.VTOCIX.VOL123,VOL=3390=volser
/* 

Sample Output: LISTVTOC INDEX Summary showing only 3 VIRs left:

VTOC INDEX DATA SET ANALYSIS FOR SYS1.VTOCIX.VOL001

TOTAL VIRs:        120
ALLOCATED VIRs:    117
UNALLOCATED VIRs:    3

5. Resolve by Expanding the VTOC Index

To correct the issue, the VTOC index was expanded using the following command:

REFORMAT UNIT(0F5B) VERIFY(VOL123) EXTINDEX(45) EXTVTOC(225)

This increased the available VIRs, allowing HSM to resume Level 1 migration successfully.  See technote for more information.

How do I increase the size of my VTOC and/or VTOCIX?

https://www.ibm.com/support/pages/how-do-i-increase-size-my-vtoc-andor-vtocix

Document Location

Worldwide

Operating System

z/OS:All operating systems listed

[{"Type":"MASTER","Line of Business":{"code":"LOB56","label":"Z HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG90","label":"z\/OS"},"ARM Category":[{"code":"a8m0z0000000AHoAAM","label":"DFSMS-\u003EHSM-\u003EMigration"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.10.0;1.11.0;1.12.0;1.9.0;2.1.0;2.2.0;2.3.0;2.4.0;2.5.0;3.1.0;3.2.0"}]

Document Information

Modified date:
30 July 2025

UID

ibm17240942

Page Feedback