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 Nov 16, 2016

Consistent use for null values

Currently there are 3 distinct ways to check if a field is or is not null:
1 - RPG uses %nullind()
2 - SQLRPGLE use a positional numeric array (-1 or <> -1)
3 - RPG triggers use a positional indicator (like) array ('0' - '1')

Having a common access to the null attribute can lead to a simplification.

For case 1 e 3 consider also setting the null attribute using a common interface.

Use Case:

Consider this SQLRPGLE example:

DataDs Ds

NullInd s 4b 0 dim(4)



if nullind(3) <> -1;

simply adding or removing a field before Field3 in the DataDs breaks the null test.

Idea priority Medium
  • Guest
    Apr 29, 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
    Aug 25, 2017

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

  • Guest
    Nov 17, 2016

    Just to let you know that there is a new NULLIND keyword in RPG 7.3 that makes it easier to use the null byte maps in trigger programs. See the trigger-program example about halfway down this page:

  • Guest
    Nov 17, 2016

    I would like the option also if a condition statement checks the value of a database field that is null that the result of the condition is false like SQL returns. Not that I want to know if its NULL but the possible value within the field should not be checked if the status is NULL.