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 Future consideration
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Aug 16, 2019

Allow ability to control JobLog write with On-Error

Add an operational extender to the on-error opcode that would allow for control over a joblog write. When the programmer has stated that a specific error condition is trapped/controlled, we should be able to optionally suppress the job log message.

Add extender (N) or similar value to the on-error opcode: on-error(n)

Use Case:

Simple example with the common RNX0105 and %dec:

dcl-s txt char(10);
dcl-s num packed(10:0);
dcl-c NUM_LEN %len(num);
dcl-c NUM_DEC %decpos(num);
dcl-c ERR_CHAR_VALUE const(0105);

txt = '1A234';
num = %dec(txt : NUM_LEN : NUM_DEC);
on-error ERR_CHAR_VALUE;
num = -1;

This code will result in RNX0105 being written to the job log even though we have intentionally trapped and adjusted for the error.

This RFE is to update the on-error opcode so that
on-error(n) 0105;
would not write RNX0105
while maintaining
on-error 0105:
would still write RNX0105 to the job log.

Idea priority Medium
  • Guest
    Jun 23, 2020

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. This impacts everyone who cares about cleaning up the joblog, so it does have broad user appeal. An alternative approach would be to write selected log entries to a database table.

    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

    For more details about CAAC's role with RFEs, see

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Apr 21, 2020

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this request.

  • Guest
    Apr 17, 2020

    IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.

  • Guest
    Aug 17, 2019

    I would extend this RFE to include the MONITOR opcode. I have many customers who will not use the monitor approach because of the number of log file entries that are created. In fact I would say in many ways this is even more important for monitor that on-exit.