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 RMM
Created by Guest
Created on Dec 23, 2019

RMM should keep RMM database in sync with VTS and TCCB

We have had several instances over the years where the issuance of an RMM command has resulted in the RMM database being out of sync with the TCDB and VTS volume repository. In general we would like RMM to keep its' repository in sync with the TCDB and VTS volume status.

The specific scenario we encountered recently is the ejection/deletion of VTS scratch tapes. We currently have the VTS scratch categories set to 2 day expire hold. This causes any RMM deletion of the volume to be rejected by the VTS. This leaves the VTS volume and TCDB intact but the RMM volume is deleted causing additional effort to clean up the three databases. We would like RMM to reject the command and keep the RMM entry intact allowing easy resubmission of the same command later once the volume has passed its' expiration.

Here's an example of a command that caused the RMM volume entry to be deleted.
RMM DV 5B0951 REMOVE EJECT

Idea priority Medium
  • Guest
    Reply
    |
    Dec 29, 2019

    We are a DFRMM shop and normally we do not need to run EXEC PGM=EDGUTIL,PARM='VERIFY(SMSTAPE)' to correct RMM against the TCDB sync issues, but I fully support any STORADMIN in the field that has any out of sync scenarios with a fast RFE fix.