IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Hi!
The difference is naturally huge! The 53 and 58 have massive overhead problems. The serviceability IFCID 340 is lightweight but is sometimes issued for SQLCODE = 0 and for positive SQLCODEs which are not so interesting. The major problem is it has no "statement id" so then finding the SQL that died is incredibly difficult. I would be very happy with just adding the "statement id" to the IFCID 340 and making it a "proper" IFI and not serviceability. I cannot believe it is much effort as Db2 must know the ID when the SQL gets a "bad" return code.
An example of why this would be so good is SQLCODE -501 caused by CLOSE CURSOR and the cursor not being OPEN. This is crazy overhead and I know a firm where they get over 20 Million a day... To find all these culprits and do a simple code change is required. Another example with dynamic SQL is, when using parameter markers, an INSERT or UPDATE with invalid date format. JAVA does this all the time but you must try and find the application... very difficult indeed!
Roy
Hello Roy, The Db2 for z/OS development team re-reviewed this enhancement request and question, how is this different from IFCID 53/58 for each SQL statement?
For IFCID 53/58, we provide the entire SQLCA which contains the SQLCODE for that particular statement. Could you please elaborate a bit more on this?
Thank you.
The Db2 for z/OSTeam