|
I have IBM's SQL Reference and Programming Concepts pdfs, but still was unable to directly correlate file exception errors to specific SQLCOD & SQLSTT values. But I did find a useful article "Foolproof Techniques to Check SQL Statements" on iSeriesNetwork (article ID 11360) that I will use as a basis for my development. Matt and Rick: Thanks for your help. - Dan --- "Haas, Matt" <Matt.Haas@xxxxxxxxxxxxxxxxxxx> wrote: > Dan, > > Negative SQLCOD's are always an error and positive codes are warnings and > informational > messages. The Information Center for V5R1 has a link to them in the Database > section. > > To test for end of file, you should check for SQLCOD = 100. 100 = no records. > > Better yet would be to check SQLSTT which is much more detailed and also > cross platform if that > makes any difference. > > Matt __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com
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
