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.
I suppose one could also use services such as this:
https://www.ibm.com/docs/en/i/7.4?topic=services-joblog-info-table-function
to retrieve that information.
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 https://www.itjungle.com/2018/09/05/guru-handling-constraint-violations-in-rpg/.
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.