Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Created by Guest
Created on Sep 11, 2015

RFE Request - Duplicate debugging, only one view?

When doing a parallel debug (I am simultaneously debugging the same application between two systems), it does show a separate branch in the Debug view...but only one Listing view. Should there be a separate view tab for each debug session? It is possible to bring up both views by clicking on the correct stack entry, but they share the same tab, making comparing the two side by side difficult.

Use Case:

You are parallel debugging a program on your development system and the same program on your test system, to identify why it works on one and not the other. To be able to step through the code to find where the logic deviates is possible through RDi. However you have to know which stack entry to select between the two when doing this because they both share the same source tab for debugging. The suggestion is to provide a separate tab for each debug source view.

The Debug view tab (located above the debug source view if you haven't reconfigured your debug perspective) should also interact when you select which one of the debug source view tabs you highlight; it should reposition itself to the stack entry last highlighted on that tab.

Idea priority Medium
  • Guest
    Sep 23, 2015

    The Eclipse editor has a design paradigm that only one source tab is opened for one particular source in the editor area. This is easy to understand because allowing the same source to be edited from multiple panes can create synchronization issues. In the described parallel debug scenario, if the source object is loaded from different remote systems, then you should see two different source tabs (one for each debug session). You can open a bug if that is not the case. However, if the source is loaded from the same local project, or you are debugging another instance of the same program on the same remote host, then two debug sessions will share only one source tab since you are debugging the same source file even if you have two different debug sessions. The debugger does not have a way to break the editor's rule of one tab per source.

  • Guest
    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 Power Systems

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