Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace z/OS
Categories DFSMS HSM
Created by Guest
Created on Apr 7, 2023

Improve HSM messaging around ML1 data set migration failures

During ML1 migration, HSM selects a volume by examining the space available but it does not consider the fragmentation index for the volumes. In cases where there are many volumes (especially EAV's) with a lot of space available in the overall pool of volumes but HSM fails to migrate the data set (ARC0757I and ARC1030I), there is no way for the local Storage Administrator to know what volumes were used or why volume selection has failed and in order to understand exactly why HSM is failing to select a volume for migration, it is necessary for IBM to examine the PDA, if active. Externalizing the volume names that are being selected and then rejected by HSM would help the local Storage Administrator to why HSM is unable to select a volume for ML1 migration. In the PDA, there appear to be ARC0600I messages that might contain this type of information, but those are not externalized/documented. Externalizing those messages or something similar using an HSM command/parameter would be helpful when debugging ML1 migration failures.

Idea priority Low
  • Guest
    Reply
    |
    Apr 7, 2023
    I recommend that you implement ML1 OVERFLOW volumes. When there is not enough space on ML1 volumes for a data set (due to fragmentation or just available space in general) then the allocation will be done on an ML1 Overflow volume. Allocation for ML1 volumes is standard - volume with the most freespace. This can lead to fragmentation. Allocation for ML1 overflow volumes uses an algorithm to select the volume with the least amount of free space that has enough space for the data set. This algorithm helps ensure that the largest amounts of free space are preserved for the largest allocations.