Re: Embedded SQL - Join problems

On 22-Jul-2010 08:59, Shannon Wolf wrote:

Yes I opened and close the cursor.

fWOP05U if e k disk
FWOP05UL1 IF E K DISK
F RENAME(WOR05U:WOR05UA)

C/EXEC SQL
C+ DECLARE C1 CURSOR FOR
C+ SELECT
C+ CONO15,PLNO15, <<SNIP>>

FWiW: I have seen very many "SQL" RPG programs similarly coded for F-specs, where there was never any intent for Row Level Access I\O; i.e. the programs only did SQL, and none of SETLL, READE, et al. If that is the case here, probably the USROPN should be coded for the file in order to avoid the unnecessary implicit open; i.e. do not perform two opens when the program starts, and then later the SQL open(s). If the files are not declared user-open for a reason, e.g. in order to utilize the RPG open to catch any errors during open processing which are presumed to be the same errors that might also be problematic for the SQL [e.g. file not found], then consider that the SQL performs its own validation during open and has its own errors being reported. The SQL error conditions during open are not limited to only what the RLA open might catch, so the SQL errors must still be tested irrespective of what errors an RPG open might catch.

Regards, Chuck