|
This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I am in the process of reading "SQL/400 Developer's Guide" by Paul Conte
and Mike Cravitz. Quite good.
Words of wisdom:
You might veer away from SQLCOD and navigate towards SQLSTT.
I haven't quite standardized on anything - yet.
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
"Bob Slaney" <rjslaney@us.ibm.com>
Sent by: rpg400-l-admin@midrange.com
10/18/2002 06:17 AM
Please respond to rpg400-l
To: "rpg400-l" <rpg400-l@midrange.com>
cc:
Fax to:
Subject: Error Handling in SQLRPGLE Programs
I am wondering what you do about error handling in embedded SQL programs.
Checking SQLCOD values of 0 or 100 is a start. WHENEVER is better than
nothing. Has anyone written an error handling module and put it in a
service program? If so, can you describe your logic? I am trying to design
an error handling architecture and a dose of practical experience would
validate (or otherwise) my thinking.
Thanks.
Bob
Bob Slaney/Atlanta/IBM@IBMUS (Lotus Notes)
Internet id: rjslaney@us.ibm.com
VM id: DALVM1.RJSLANEY@VM
Tieline 445-7374 Direct (770)835-7374
FAX tie 445-7579 Direct (770)835-7579
IBM Learning Services
iSeries Courseware Developer
IBM Corp.
3200 Windy Hill Road
Atlanta, GA 30339
WG07C13
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.