IBM Z Software
This portal is to open public enhancement requests against IBM Z Software products. 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 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
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.
this would be useful, but it would also be very costly to implement without producing either too many false positives or too many false negatives
Maybe i just don't have enough fantasy, but i can't imagine how this can be implemented in a comfortable, robust, generally useful way.
I know programs that check sqlcode directly, others that call functions to do so. No general pattern.
I have no idea how the compiler can reliably check if EXEC SQL is followed by a test of SQLCODE.
just my 0.02€, woecki
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - PL/I Compilers
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - PL/I Compilers
Yes. You're right. And: different SQLs in _one_ programm need different reactions and therefor - maybe - calls on different procs in _one_ programm . . .
Ralf: The Problem with this (PROCNAME=,..) is, that every program have to have their own Compileoptions. So this should be somewhere in the SOURCE (not in *PROCESS !).
Own procedure / option . . .
That sounds to me that it would be fine to have an option with a parm like defining a procname or userexit?
Options like
TESTSQLCODE(ON|OFF|PROCNAME=procname|USEREXIT=uexit)
TESTSQLSTATE(ON|OFF|PROCNAME=procname|USEREXIT=uexit)
??
We mostly have a own procedure to check the SQLCODE / SQLSTATE.
I don't know, if this is possible by checking this rule to another/following procedure call.
Some companies don't check the SQLCODE but SQLSTATE. _My_ RFE would therefor be: ". . . not followed by a test of SQLCODE nor SQLSTATE".
this is a good idea, but it will probably be done under the control of an option