×
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.
The corresponding SQLCODE message (SQL0545) gives the same text as what GET DIAGNOSTICS EXCEPTION gave me. The message text in the joblog is also the same. The Cause listed in the joglog does include the constraint name. Any painless way to get that programmatically?
-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Wednesday, December 30, 2015 8:08 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: 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
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
