× 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.



<snip>
On the SQLCOD vs. SQLSTT blurb
<snip>

I also seem to recall something from IBM about possible values > 0 in SQLCOD 
when there wasn't really an error giving a false failure in programs checking 
SQLCOD.  I doubt I could put my hands on it now but I remember it being around 
the V5R1 timeframe.  That's when I switched to SQLSTT.

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Haas, Matt
Sent: Friday, January 07, 2005 3:35 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Open/Close of Files


For single record access, using SQL will dramatically slow the program down.

On the SQLCOD vs. SQLSTT blurb, the issue isn't cross platform portability. The 
real issue is that SQLSTT's are a standard and SQLCOD's aren't. SQLSTT's are 
very unlikely to change but SQLCOD's do change from time to time. The last time 
I'm aware of a change was in going from V4R5 to V5R1.

Matt


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.