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 Languages - RPG
Created by Guest
Created on Oct 22, 2019

Enable Retrieval of SQL constraint violation error information in RPG program

Current RPG support requires programmers to use IBM i APIs plus considerable coding to determine what constraint has caused an error. For example, when using an SQL insert on table, where a check or foreign key constraint is used, a violation of the constraint doesn't readily provide sufficient information to notify the user in the program. A function or operation to immediately return the name of the constraint, would be ideal.

Use Case:

You can not easily find which DB2 constraint has caused an SQL insert, update, delete to fail. The amount of code required could be reduced if DB2 and RPG had a method to directly retrieve the name of the constraint being violated from either an SQL Communication area, a built-in function or an SQL Diagnostics area. To illustrate this issue, one might read the article(s) previously written by Paul Tuohy, to show approaches to handle constraint violations. He uses APIs, message retrieval etc. Could a new aporoach be devised To alert the programmer with SQL State and then get the constraint from a field in the SQL CA? {}.

Idea priority Medium
  • Guest
    Apr 27, 2021

    I suppose one could also use services such as this:
    to retrieve that information.

  • Guest
    Apr 17, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    Regarding the EXEC SQL statements, it is not possible for RPG to provide a built-in function that would return that information. However, the name of the constraint can be found in the SQLCA and information about the constraint can be obtained by using GET DIAGNOSTICS.

    Regarding RPG native I/O statements, information about the constraint can be obtained by coding a procedure similar to that described in the referenced article

  • Guest
    Apr 16, 2020

    You can use the SQL statement GET DIAGNOSTICS CONDITION 1 :ConstraintName = CONSTRAINT_NAME to retreive the name of the violated constraint into your RPG variable ConstraintName. You'll have to execute this statement each time SQLSTT (which you test after each SQL statement, don't you ?) is in the 23xxx range.