RE: Help with SQL compile issue

Are your statements physically in order? In my experience, the embedded
SQL statements (prepare/open/fetch/close) must appear in physical order
in the source code, regardless of the actual/logical execution order.

If you have
Mainline - open/fetch/close
*inzsr - prepare/declare

It will not work.

I try to put all embedded SQL in subprocedures, and have them ordered
correctly in the program. Then call them wherever.

HTH,
Loyd



Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Monday, February 11, 2008 11:32
To: midrange-l@xxxxxxxxxxxx; rpg400-l@xxxxxxxxxxxx
Subject: Help with SQL compile issue

I have a program with the following code:
In InzSr
C/Exec SQL
C+ PREPARE SMO_SELECTION FROM :sSelect
C/End-Exec
C/Exec SQL
C+ DECLARE MO_SELECTION CURSOR FOR SMO_SELECTION
C/End-Exec
EndSr



Later, in execution
C/Exec SQL
C+ Open MO_SELECTION using
C+ :FCmp, :TCmp,
C+ :FCust, :TCust,
C+ :FLoc, :TLoc,
C+ :FItem, :TItem,
C+ :FSer, :TSer,
C+ :FSTag, :TSTag
C/End-Exec

Get pre-compile error, SQL0504 35 761 Position 17 Cursor MO_SELECTION
not declared.

Get the same error on the cursor for the FETCH, and the CLOSE

I can not determine why I am getting the error in the pre-compiler.

Thanks,


Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical
Solutions V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions
Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions
Implementer V5R3