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.

Add a new idea Subscribe
Status Delivered
Workspace IBM Developer for z/OS
Categories Host Tooling Integration
Created by Guest
Created on Aug 6, 2009

RELATED IDEAS

delete of PDS or files toot easy from RDz

if from the z/OS Projects view a user right click on a PDS or a file under a PDS and Delete, a window pops up telling: Warning: the remote object is permanently deleted. But it's too easy to delete by mistake. In ISPF if you want to delete, you need some volontary action (point to the file, then delete). Here, you could delete while you just want to remove from project. There's a menu item for that but as Remove from Subproject is not just below Delete, it brings confusion. A possibility would be to remove de Delete functionality from the z/OS projects view letting only the Remove from Project and keep the Delete in the Remote System view.

Idea priority High
  • Guest
    Reply
    |     Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for System z

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Developer for System z

  • Guest
    Reply
    |     May 25, 2010

    This request has been delivered in a previous RDz release.

  • Guest
    Reply
    |     May 23, 2010

    This RFE is being evaluated for a delivery in a future release.

  • Guest
    Reply
    |     Nov 8, 2009

    This requirement has been accepted and will be evaluated for a release within the next two years.

  • Guest
    Reply
    |     Sep 30, 2009

    Please see comments posted below

  • Guest
    Reply
    |     Sep 27, 2009

    RE: "At DELETE time, it is not obvious that he is selecting a test or production object..."

    In this scenario, your users should not be able to delete the production copybooks pulled in via Show Dependencies unless they're RACF authorized. Is it currently not the case?

    The current RDz behavior is consistent w/ Eclipse i.e. the pop-up warning is the last line of defense for when someone presses the Del key. If RDz is to change this behavior it will be inconsistent with the platform as well as other toolings built on it. Further, if a user is not RACF authorized, he/she should not be able to delete a resource even if RDz attempts to delete it.

  • Guest
    Reply
    |     Sep 16, 2009

    Let us refine our comment on the difference with classic TSO/ISPF where a user voluntary action is required. In RDz the user can "include dependencies" in the MVS subproject. This will add the copybooks from our "production" source library in the project. Some in a single view, the user will then have a mix of sources from the test library (the pgm+copybooks he is working on) and the production library (the dependent copybooks that he has included). At DELETE time, it is not obvious that he is selecting a test or production object. We would like to secure us against such user errors. The suggested "dual security" could be a quick fix solution for us.

  • Guest
    Reply
    |     Sep 13, 2009

    I don't think that the author means what screendante talks about. It seems to me that the author wants a "we're about to delete dataset aaa.bbb.ccc etc". Do you really want to delete it? It's too easy to "mis-click" with a mouse and delete a dataset that you didn't mean to.

  • Guest
    Reply
    |     Sep 3, 2009

    extra comment from the customer:
    With respect to RFE2966, can I just make a suggestion.
    One quick solution might be to implement in the RDZ gateway something
    similar to CICS bind and link security.
    This could implement 2-level security as follows:
    - to edit, delete, a dataset or member, a user needs to have the
    appropriate authorization in RACF (as now is the case)
    - but also the RSE started task must have the same authorization (could
    be customization option e.g. RSE_TWO_LEVEL_SECURITY=YES)
    In that case, if either the user or RSE stc does not have the required
    UPDATE access, the action in RDZ would fail.
    This would be fully RACF compliant, and would give us an option to
    (easily) reduce the security risk by limiting access to datasets via
    the RSE stc.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.