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 Delivered
Workspace z/OS
Categories DFSMS RMM
Created by Guest
Created on Aug 20, 2018

RMM should surface reason volumes are not returned to scratch

Technote Reference #: S1000836 currently documents the process one needs to go through when attempting to determine why a particular logical volume was not returned to scratch during the last housekeeping run. Just going through those steps for a single logical volume is very time consuming and not very scalable for a larger number of volumes.

RMM should provide a way to surface the reason that a logical volume isn't eligible to be returned to scratch at any point in time. We should be able to determine if any single volume or a range of volume will not be scratched during the previous housekeeping run and why they are being kept. This reason should include which dataset on the volume is preventing the volume from going scratch.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 4, 2023
    This idea has been delivered in z/OS 3.1, which was made generally available 9/29/2023.
  • Guest
    Reply
    |
    Jan 14, 2019

    .We agree that it is very important to make it easier to understand what prevents a volume from being returned to scratch. We are investigating a number of different approaches, which may include adding a new field to the LISTVOLUME subcommand output, adding new messages to RMM housekeeping output, and making improvements to the RMM ISPF dialogs.