× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. December 2015

Re: SQLSTATE 23513, get constraint name?

Take a look at the job log - there are often more messages that were logged before the one you are seeing. And getting an SQLSTATE, there will definitely be some kind of messages out there

Also check SQLCODE for a value - that value is often made part of a message ID - for example, if SQLCODE is 367, say, the message ID will be SQL0367.

But that message, if any, will be part of the job log.

This is a WAG, but based on seeing lots of messages logged in other error conditions for SQL.

HTH
Vern

On 12/30/2015 7:59 AM, Justin Taylor wrote:
I have an SQLRPGLE program that's doing a SQL INSERT. It sometimes gives me a SQLSTATE 23513 (INSERT, UPDATE, or MERGE not allowed by CHECK constraint.). A GET DIAGNOSTICS EXCEPTION gives me the text for 23513, but I'd like to be able to programmatically retrieve the constraint name. Any good way to do that?


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.