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 Submitted
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Jul 15, 2026

Allow else blocks for monitor groups

In some situations it'd be useful to be able to have an else block in a monitor group to perform some handling that shouldn't be monitored itself and should only run when the monitored statements executed without exception.monitor: dosomething();on-excp MY_ERROR; errorhandling();else; successhandling();endmon;Currently we might do something like this but if the successhandling procedure throws a monitored exception it would be unintentionally handled.monitor: dosomething(); successhandling();on-excp MY_ERROR; errorhandling();endmon;To achieve the intended behavior we need an additional variable to check whether the monitor block got fully executed.success = *off;monitor: dosomething(); success = *on;on-excp MY_ERROR; errorhandling();endmon;if success; successhandling();endif;The Python language has this featurehttps://docs.python.org/3/tutorial/errors.html#handling-exceptions:~:text=raise-,The,example

Idea priority Medium
  • Guest
    Aug 19, 2026

    Thank you for taking the time to submit this IBM Idea and share your feedback with IBM and the broader IBM i community.

    The CAAC has reviewed this Idea and, after careful consideration, does not recommend that IBM move forward with the request in its current form at this time.

    Reason: The CAAC did not identify sufficient benefit to justify adding new RPG syntax for this use case. A MONITOR group is intended to focus on exception handling, while successful completion is already represented by reaching the end of the monitored statements without an exception. When success-specific processing is required, it can be expressed explicitly using existing RPG logic, such as setting a success indicator and conditionally performing the appropriate processing after ENDMON. Adding an ELSE block would duplicate behavior that can already be implemented and could make the control flow more difficult to understand.

    Although the CAAC is not recommending implementation of this request, Ideas such as this help IBM and the CAAC better understand the needs and priorities of the IBM i community. We appreciate your contribution and encourage you to continue submitting IBM Ideas and sharing your feedback.

    Background: The COMMON Americas Advisory Council (CAAC) includes members with a broad range of experience working with small and medium-sized IBM i clients. The CAAC works with IBM i development to help assess the potential value and impact of individual IBM Ideas on the broader IBM i community.

    For more information on the CAAC, visit: https://www.common.org/common-americas-advisory-council/

    Brandon Pederson - CAAC Program Manager