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 Feb 18, 2024

New ASSERT op-code

Assertions are good programming style and widely in use in C, C++ and other languages.

The idea is to have an ASSERT op-code like that:

   assert sqlcode in %list(0:100) 'Unexpected SQLCODE = '+%char(sqlcode);
   assert sqlcode = *zero %msg(...) %target(*caller);

So syntactically:

   assert boolean-expression string-constant|%msg(..) [%target(..)];

Which would be equivalent to something like:

   if not (sqlcode = *zero);
snd-msg *escape 'SQLCODE is not zero!';

But the new op-code would provide:

  1. A "positive" notation like in "contract programming"

  2. An shorter and easier to read notation

  3. A wider adoption of exceptions/messages

Idea priority High
  • Guest
    Jun 10, 2024
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea 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 Idea.
  • Guest
    Mar 15, 2024

    It's true that it's easy to write an assert() procedure, but with an assert() procedure, the joblog would show the assert() procedure as the sender, making it more difficult to determine the problem.

    The advantage of an ASSERT opcode would be that the joblog would show the current procedure and statement number as the sender of the error message.

    - Barbara Morris, IBM

  • Guest
    Feb 26, 2024

    Created a service program and procedure named ASSERT is so easy to do. Have you tried that?