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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
SQLRPGLE precompiler - allow usage of large VARCHARS by interpreting the same as SQLTYPE(CLOB)
Currently you cannot use large RPGLE VARCHARs (length >= 32705) in EXEC SQL statements.
I suggest updating the SQL precompiler and SQL processing so that they can be.
This would remove the need for defining SQLTYPE(CLOB) in new programs, VARCHARs could be used instead. And as a result, CLOB data would become interoperable with all the regular RPGLE BIFs such as %trim, %scan, %xlate, etc. with no conversion, and no need to reference different variants of the variable name in different circumstances.
A VARCHAR with a 4 byte prefix (either explicitly with VARCHAR(x:4), or implicit with VARCHAR(x) where x > 65535) has an identical structure in memory to the SQLTYPE DS (4 bytes unsigned int for length, then x bytes character), and the SQL precompiler, when it converts SQL statements, references with with %ADDR so I think this would be a pure precompiler change?
Supporting VARCHARs with a 2 byte prefix would I guess be more complicated as the SQL processing that references the address must know if it has a 2 byte or 4 byte prefix and act accordingly.
This would apply to the other LOB types too, not just CLOB.
This is Intended as an improvement on this other IDEA: https://ibm-power-systems.ideas.ibm.com/ideas/IBMI-I-3732 which suggests the ability to optionally have the SQL precompiler convert SQLTYPE(CLOB) to a VARCHAR(x:4) instead of to the UNS(10)/CHAR(x) DS. The difference being that IDEA might only be SQL Precompiler changes, whereas this one is more complicated.
Do not place IBM confidential, company confidential, or personal information into any field.