|
Have you determined the sqlstt and sqlcod values when this happens?i have my embedded sql use the sqlerror tag to write a history of the error values and the
sql string, with timestamp info. jim franz----- Original Message ----- From: "Brad Stone" <brad@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Friday, January 27, 2006 10:37 AM Subject: SQL Cursor Position Problem in V5R3?
I am working with a customer who is having a problem with what seems like a cursor position problem using embedded SQL. Prior to V5R3 the program worked fine. Now, when they run it the first time, it works fine, but the next time they run it it produces no results, as if it started reading at the EOF. It is a web application (RPG), and if they end the HTTP server and restart it it works fine. Once. They can end the jobs again, restart it and again it works once. Subsequent calls result in no data returned. Which tells me it's job related (at least at the highest level). The program does use cursor positioning in the SQL statement (ie position relative <rrn>) where the first time it always uses 1 as the relative position. Has anyone else experienced issues like this with V5R3? AFAIK, nothing else has changed with the program. Just the new machine and OS. Thanks! Brad --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.