Skip to Main Content
IBM Power Ideas Portal

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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Oct 18, 2016

Referential Constraint issues job log

The problem: qsqsrvr running an SQL request and it receives back an error: SQL0352.

The qsqsrver job then job logs.

I am depending on the database to give me this feedback (SQL0352) however I want to control whether or not it job logs.

Per the PMR we have tried everything that both the ISV Support group and we could think of to stop the job logging.

I am working in a web services environment where the IBM i is serving up the data. We have extensive dependencies built into the database and allow the database to do much of the policing of data with that knowledge. I need SQL to error, but do not want the job log.

This feedback from SQL is essential to the operation of the application, however the job logs are really quite useless and would never be referenced by the end user as this is a cloud solution and they have no access. Yes I could create a scheduled job that went and deleted these logs but I really should be able to configure this so it does not joblog.

Use Case:

User requests the delete of an employee.

Web Services accepts the request and attempts to delete the employee.

SQL returns an SQL0352 as there are other related tables with referential constraints defined which must be cleared first. Yes you could do a cascading delete, however in this case if there are constraints against the employee he should not be deleted nor should the related table entries.

Idea priority Medium
  • Guest
    Apr 15, 2021

    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.

  • Guest
    May 10, 2019

    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.

  • Guest
    May 9, 2019

    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?

  • Guest
    May 14, 2018

    I suspect the message was SQL0532.