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
Correct accuracy of inline error location in ILE C compiler for SQL
When using SQL to create a User Defined Function, the RUNSQLSTM and other interfaces generate C source code and compile it. When the developer also uses the INCLUDE statement in that same code, to pull in some "inline C" code, when there are errors identified in the compiler listing, they are never inserted into the correct location in the code, making code correction of guessing game.
Create an SQL UDTF, such as CREATE TABLE FUNCTION using LANGUAGE SQL. Within the body of that UDTF, include the "include" statement to pull in some inline C code. Make sure there are syntax errors such as missing semi colon, or extra or too few parens, or the wrong type of variable as a parameter.
*=SEVERE==========> CZM0046 Syntax error.
or other CZMnnnn errrors are embedded by the compiler into the listing, 80 to 90% of the time they appear in the wrong location (too far below the actual error, sometime as many as 10 lines or more out of place).
While this may seem like a bug, it needs to be resolved in the RFE process as I am doubtful it can be fixed using the SR process.
Do not place IBM confidential, company confidential, or personal information into any field.