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 Future consideration
Categories Usability
Created by Guest
Created on Jul 18, 2013

Extract To function should not be tightly coupled to CARMA view and MVS subproject

The "Extract To" function is a neat feature that allow developers to associate program modules to the CARMA source control (Endevor in our case). However, this function is so tightly coupled that it severely limits its usage.

1) It ties to a particular CAMRA view
If the view has been changed, it will lose the connection (even after re-creating the CAMRA view using the same criteria)

2) It ties to a particular subproject
If we need to split a MVS subproject into multiple MVS subprojects, the only way to make it work is to re-extract it and manually merge all the changes we made on that file.

3) It ties to a particular file in a specific environment
If the file has been moved from one environment to another one, it will lose its connectivity.

We will like to make this function loosely-coupled so that it will link the MVS file directly to the CARMA element. It will allow developers to associate the MVS files to different MVS subprojects. Plus, it will not be limited to a particular CARMA 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
    |
    Apr 8, 2014

    we continue to evaluate this RFE

  • Guest
    Reply
    |
    Sep 19, 2013

    This RFE describes 3 separate enhancement requests as defined in the description field. Items 1 and 3 are consistent with our roadmap and are being considered for delivery in the next 2 year time frame. Thanks.

    Item 2 is a valid requirement but delivery within the RFE 2 year window is not likely. Please resubmit in 12-18 months for reconsideration if still valid.