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 Delivered
Created by Guest
Created on Jun 15, 2016

RDz - Better distinction between Delete and Remove in a MVS Subproject

This RFE is the result of an example of confusion in the use of MVS Subprojects.
PDS'es and PDS-members can be added to a subproject. Developers can work with these items using the subproject.
Once they are ready, the items can be removed from the subproject.
And this is where the confusion appears.
When a member is selected, you have two options in the submenu: Delete and Remove. Even though RDz asks for a confirmation when the Delete is chosen, it happens that developers delete the member even if they do not want that.
the suggestion is to solve this in one of the following ways:
1. Do not show the Delete action in a subproject. If users want to delete a PDS or a member, they should do that from the Remote Systems view.
2. Change the order in which the menu options Delete and Remove are presented when working in a subproject. The Remove should be presented first.
3. Change the description of the menu actions: Delete should be something like: Delete from the host
Remove could be: Remove from subproject only.

I hope this explains the situation clearly.

Idea priority High
  • Guest
    Reply
    |
    Nov 10, 2016

    We've delivered the following items:

    Part 1 was delivered in RDz version 8 via a host option named DISABLE_DELETE_IN_SUBPROJECT that will disable the Delete menu item in the context menu of z/OS subprojects. Refer to the Host Customization guide for more details.
    Part 2 will be delivered in a future release (v14.0.0.3).
    Part 3 will not be delivered as we believe the text in the resulting dialogs after the options are chosen is sufficient to distinguish the options from one another and prevent the user from making an incorrect choice.