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 - SQLTYPE(CLOB:x) to VARCHAR instead of to DS
Add a d-spec and/or ctl-opt keyword to instruct the SQL precompiler to convert SQLTYPE(CLOB:x) (and BLOB etc.) to VARCHAR(x:4) instead of the UNS(10)/CHAR(x) DS that it currently converts to.
// This dcl-s myVar1 SQLTYPE(CLOB:X); // Pecompiles to this: dcl-ds myVar1; myVar_LEN UNS(10); myVar_DATA CHAR(x); end-ds;
// But this dcl-s myVar2 SQLTYPE(CLOB:X:*VAR); // Pecompiles to this: dcl-s myVar2 VARCHAR(x:4);
// And this: ctl-opt SQLLOBTYPE(*VAR); // Applies *VAR globally to the program - makes all SQLTYPE(CLOB:X) act like SQLTYPE(CLOB:X:*VAR)
This would have the benefit of allowing CLOBs to be directly used with 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. All of this serves to simplify the use of CLOB columns in SQLRPGLE processing.
A VARCHAR(x:4) has an identical structure in memory to the 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?
Do not place IBM confidential, company confidential, or personal information into any field.