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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
The pervasive use of SQL in RPG IV along with the habitual use of NULL-capable fields justifies adding a ALLOW(*NULL) keyword to stand-alone fields, data structure subfiles, as well as parameters. It would be used on things like the SQL FETCH clause to allow Developers to avoid having to code a second 2-byte int and then check it for negative or positive values.
A new built-in function: %IsNull would be a huge get. After a FETCH operation, we could easily determine if a value is null. Today, the FETCH INTO :SalesID :salesIDnullIndy syntax is vexing at best, error-prone and not inviting. Code can run for "centuries" and then suddenly one day issue a "NULL Indicator required for column SALESID in blah, blah blah." message. Clearly this is a developer error, but in RPG, this should be easier to manage. I would rather just add an ALLOW(*NULL) keyword to the host variable definition and then issue an %IsNULL (or ignore it) and be done with it. Instead, today I have to:
Understand I need to define a 2-byte integer.
Add that 2-byte int as a value between the SALESID field and the next fields on the FETCH.
Check that 2-byte int field is negative value to determine if it is null.
vs
if %isNULL(SALESID); ...
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
One aspect of this Idea that is not supported in RPG is the ability to use SQL-style null-indicators which are 2-byte integers.
There is an existing Idea, IBMI-I-1111, requesting support in RPG for SQL-style null-indicators. The title of that Idea is "Option for EXTNAME/LIKEREC(*NULL) to create SQL-type int(5) indicator subfields", but if the Idea is implemented, it would also be possible to request SQL-style null indicators for stand-alone fields and data structure subfields.
Therefore, this Idea is being closed as a duplicate of Idea IBMI-I-1111.
https://ibm-power-systems.ideas.ibm.com/ideas/IBMI-I-1111
- IBM Power Systems Development