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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 does not intend to provide a solution to this request at this time, so it is being closed. This request is low priority and has a low number of votes. The database team has many higher priority items to work on, so this request is not likely to be implemented anytime soon.
I need them to be issued so that I know the function I asked SQL to perform can not be performed and can inform the user of that.
It's been a while but I think what was happening was each time the job under qsqsrvr fired up if I got the SQL error then as the request ended so did the job and a job log was spooled. We then end up with a bunch of useless job logs.
I believe you mean SQL0532 not SQL0352.
The reason we put messages in the joblog is to help both the customer and IBM to debug.
The same applies to the entire operating system.
In your specific application you expect the SQL0532, but other applications may not.
Thus, it would not be reasonable to make it a system wide control.
I also very much doubt you would want any SQL message to be removed from the joblog because you likely do not handle every possible SQLCODE.
Can you confirm that you are looking for a way to tell SQL to not send a specific message(s) on a job basis?
I suspect the message was SQL0532.