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
When creating SQL tables with the keyword "FOR" system names to support legacy code, then for "FOR" system name is not available in the SQL-CLI api's.
The "SQLColAttribute" should support SQL_DESC_SYSTEM_COLUMN
We are in a situation where we converts DDS databases into SQL databases so each table is now created similar to this:
CREATE OR REPLACE TABLE mytable ( Active_Job_Name FOR MYACTJOB char(26) ) RCDFMT mytableR;
We are using the "FOR" system name - to cater for legacy applications. Also over the years we have made an abstraction layer that returns object graphs (used for JSON, XML, CSV etc) based on the resultset - this is done with SQL-CLI.
However all the access to the new tables need to know the original column name so the legacy code will not have to be rewritten.
The "SQLColAttribute" function need to support SQL_DESC_SYSTEM_COLUMN but it does not exists in the supported list:
Do not place IBM confidential, company confidential, or personal information into any field.