Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Under review
Created by Guest
Created on Dec 22, 2025

REMIGRATE libraries to ML2

When processing migrated libraries there is an option REMIGRATE which moves back volumes which are to be recalled. This parameter is only working fine if library is recalled from ML1. In this case library is migrated back to ML1 volume.

If recall is from ML2 than library is migrated back to ML1 only. This way it is both filling both ML1 space and takes unnecessary time because remigrating to ML2 would avoid any additional overhead because dataset simply would be reconnected (if dfhsm is setup accordingly). In this case there is only an update to dfhsm MCDS required. 

Remigrating ML2 libraries back to ML1 volume fills up ML1 volumes, potentialy causing issues.

Idea priority Medium