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 (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
Workspace IBM i
Created by Guest
Created on Nov 27, 2018

Need ability to manage which users are stopped when an SEP breakpoint is reached

Some debugging we really need to call through web front end to test with how information is set up. This means we use the same userid all people in the environment are assigned by the connector. Since debug stops as soon as the program is called.

See CAAC requirement AD0304 for more information at https://www.ibmilug.ihost.com/commonag/treqs.nsf/9c76f872792db457862573af004e1b49/a322d34cf78951e486257b33003c777f?OpenDocument


Use Case:

Current workaround: Either try to tell everyone to avoid a certain operation or else have to debug after work or have their screens freeze up and they think they have an error.

Proposed resolution: Have an option that allows you to put in breakpoints so that the debug doesn't stop a session until it hits a break point which can be set up so only my call hits it.


Idea priority Medium
  • Guest
    Reply
    |
    Feb 6, 2020

    This RFE is now delivered. It is supported for ILE Languages only: ILE RPG, ILE COBOL, ILE CL and ILE C/C++.

    Conditional SEP is supported in both the command line debugger and the RDi debugger.

    IBM i V7R4 already has the update.
    IBM i V7R3 requires these PTFs to be applied:
    SI69800 Debugger support updates for Conditional SEP Support
    SI69802 Graphical debugger client updates for Conditional SEP Support

    The RDi Debugger requires fix pack 9.6.0.7 to be applied.

    In this enhancement, the SBREAK subcommand syntax has been changed:

    ------------ New SBREAK subcommand syntax ---------------------

    >> --:SBREAK-->position--:---------------:--:-------------:--><
    :--User Option--: :--Condition--:

    User Option >> --:----user-->userid----:
    Condition >> --:--when-->expression--:

  • Guest
    Reply
    |
    Jan 7, 2020

    We do not debug socket jobs in production directly since there are so many that can be hit by your request so it is almost impossible to do with the same user ID. We do it only in a dedicated development box since we can control the the number of these socket jobs and debug them all if needed. With in our web apps we have a debug feature we built into all of them to capture things if needed. One of them captures SQL calls that are logged in way that we have the full SQL text available including all values. We use those statements in ACS SQL session that is configured to have all attributes as the DB socket jobs. Then we use ACS debugger.

  • Guest
    Reply
    |
    Jan 29, 2019

    IBM has modified some of the information in this request. In particular, per the Submitter's request, the Headline was updated to be better describe the enhancement requested. The previous headline was: "RDP debug did not stop until it hits breakpoint".

    Please contact us if you have any questions.

  • Guest
    Reply
    |
    Jan 29, 2019

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. It could be sufficient for an SEP to be conditional on an expression. This would be similar to a conditional Line breakpoint.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Nov 28, 2018

    I have the same issue but how would you define "my call" ?

    It would require an extra debug filter on IP-address I guess.