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
DB2 for LUW and z/OS provide the capability to rename a column. DB2 for i should have the same functionality. Renaming a column's system name should be included, too.
In our IT department, Data Studio is used to create or modify tables and indexes. The developers try to correctly name the columns, long and system, but occasionally mistakes are made. Our DBE reviews the tables and indexes before promotion to production, too, and usually catches the incorrect names.
For empty tables it's OK to drop a column and add it back with the correct names.
Recreating the table is an option, too, unless it's a parent with dependents. The constraints have to be dropped then recreated. This may not be possible on a production system running 24x7.
When tables contain data the solution is even more difficult. Especially when the data loading process is complex and/or date/time sensitive, i.e. snapshot values for a point in time.
A hack can be used if both long and system names need to be changed. But the hack gets much worse if only one of the column names should be changed. And a hack, aka QID (quick and dirty), may compound the problem rather than resolve it.
Using a statement like "ALTER TABLE table_name RENAME column TO new_column_name FOR SYSTEM NAME short_column_name" would work correctly every time and eliminate the need for a hacked solution.
Do not place IBM confidential, company confidential, or personal information into any field.