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 - Monitoring same field from two (or more) programs

In the Monitors view, it is possible to monitor the same field more than once when it appears in two (or more) programs being debugged, or in two (or more) programs in the stack. When done, the field appears in the list multiple times as needed but is not clear which program it is associated with at that time. It would be nice to have the field identified with the program from which it's being monitored from.

Use Case:

I have found several uses of performing a parallel debug using RDi and have a need to monitor the same field in both debugs. For example, program A has a field name called VALUE. Program B is called and has it's own field name of VALUE, but the value may/may not be the same between the two programs. You can monitor both fields but they only appear by their name in the Monitors view. If you need to change the value (e.g. to simulate what would happen), which one do you change? If you pick the wrong one, you will alter the value in the wrong program and not get the desired results.

The suggestion is to include with the field name which debug session it is tied to. Possible suggestions would be to include the library of the object and the object name alongside the field name (i.e. to the left of the field name) so it would help to differentiate the two.

Idea priority Medium
  • Guest
    Sep 23, 2015

    The monitored expressions are context sensitive. When a debug session is selected, only the monitored expressions for the selected debug session will appear in the Monitors view. That means the Monitors view can display different content when you switch between different debug sessions. For this reason, there is no need to label the expression with the program name, because all expressions that you can see in the Monitors view are for the *CURRENT* debug session.

    If you monitor two fields with the same name (suppose the field name is VALUE) from two different programs, initially you will only see one occurrence of VALUE in the Monitors view for each debug session. Later when you restart a new debug session, you may see two occurrences of VALUE in the Monitors view, since the debugger tries to save and restore monitored expressions from all debug sessions. However, these two occurrences of VALUE are just duplicates applying to the current debug session.

  • 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