Re: We have a mystery

Except that sqlstate is not a numeric value so testing for < '02' will
include errors in classes like '0A' and '0E'. In fact there are defined
classes that go all the way up to '0Z' and user defined classes that start
with I - Z.

If I wanted to find a successful execution I would test >= '00' and < '02',
but generally I am looking for errors, so I tend to use < '00' or >= '02'.

On Thu, Oct 12, 2017 at 1:28 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/12/2017 12:46 PM, Mike Cunningham wrote:

Sqlstate = 01545 An unqualified column name has
been interpreted as a correlated reference.

Any SQLSTATE that begins with '01' is a warning, not a failure. So
rather than test for '00000' and '01004', consider testing for < '02',
although there may be good reason to heed the warning (like truncation).

Still don’t know why it only issues that 01545
state when run in the larger CL.

Chuck Pence expressed some thoughts in this thread:
https://archive.midrange.com/midrange-l/201403/msg00888.html

--
--buck


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD