RE: SQL Cursor Position Problem in V5R3?

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

Brad,

I wonder if they had changed the compile command defaults for CLOSQLCSR to
*ENDMOD.  At the release update, these would have gone back to
*ENDACTGRP.....

To correct this type of issue once and for all, have them add a SQL options
block to the SQLRPGLE source.....

C/EXEC SQL                 
C+ Set Option              
C+     DatFmt    = *Iso,   
C+     Naming    = *Sys,   
C+     Commit    = *None,  
C+     UsrPrf    = *User,  
C+     DynUsrPrf = *User,  
C+     CloSqlCsr = *EndMod 
C/END-EXEC                 


Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Brad Stone
Sent: Friday, January 27, 2006 9:38 AM
To: Midrange Systems Technical Discussion
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