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
The idea would be to create a json datatype as happens in other dbms. This allows you to create fields in json type files (and not blobs as suggested in some documentation) while also verifying their actual validity.
Consolidate documentation for Services and documentation for the system catalog into one area.
Instead of placing the documentation for IBM i Services underneath "Performance and query optimization" move it to "Db2 for i catalog views". Take these links: Db2® for i Services: https://www.ibm.com/docs/en/i/7.5?topic=optimization-db2-i-service...
We provide Webservices on IBM. The webservice consumers do an authentication with different types of tokens, e.g. RS256 (azure) or keycloak. It is very difficult, to verify such tokens in RPGLE. Yes, there are APIs like qc3verifysignature. But it ...
improve MERGE by adding the option "WHEN NOT MATCHED BY SOURCE THEN DELETE"
Today, it is impossible to use the DELETE clause behind WHEN NOT MATCHED.Some DBMS other than DB2 allow this.Would it be possible to add this feature, like in this example ? MERGE target_table USING source_table ON merge_condition WHEN MATCHED THE...
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, VARCHA...
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. // Thisdcl-s myVar1 SQLTYPE(CLOB:X);// Pecompiles to th...
Make the AES algorithm compatible with AES calculated by different software platforms. The ENCRYPT_AES sql function can encrypt a DB column. Unfortunately the algorithm is IBM proprietary [The internal encryption algorithm used is from the CLiC To...
Do not place IBM confidential, company confidential, or personal information into any field.