Re: SQL and V5R1

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

while things have changed, this is a common mistake.

Example code always pointed to the simple test of SQLCOD = 100 for record
not found.
Anyone that has crossed paths with any other database will tell you that you
REALLY should be using SQLSTATE under all circumstances. While the SQLCODE
of 0 and 100 are (AFAIK) universal, other values in there may or may not
appear to be universal.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"If you pick up a starving dog and make him prosperous,
  he will not bite you. This is the principal difference
  between a dog and a man."

    - Mark Twain

----- Original Message -----
From: "Bill Erhardt" <ERHARDT@BaldwinHQ.com>
To: "'Mid Range list - Questions'" <MIDRANGE-L@midrange.com>
Sent: Friday, November 01, 2002 8:40 AM
Subject: SQL and V5R1


> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> I realize that this may be old news (since V5R2 is out) but I've just been
> told that in V5R1 IBM has changed the return values for SQLCOD.  It now
has
> flavors and where V4R5 and below returned a 0 or 100 may not return the
same
> value in V5R1.  It has to do with if all of the selected fields are
> returned.  We were told to test a field SQLSTT (a 5 byte character value)
> for '00000' (SQLCOD value of 0) of '02000' (SQLCOD value of 100).  Has
> anyone heard of this?
> Bill Erhardt
> Baldwin Hardware
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>