From what I can see of your statement,
I don't see a reason you would need
parameter markers.

I think you would need parameter markers
if you had a >dynamic< sql statement,
but I don't see anything in your post
indicating the statement would need
to be prepared (dynamic statements must
be prepared).

One common reason a statement is dynamic and
therefore requires a preparation step is a
library name must be set/changed at run-time.

An extreme example is the statement itself
is not known until run-time (think STRSQL).

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Thursday, November 08, 2012 7:21 AM
To: Midrange Systems Technical Discussion
Subject: Embedded SQL Dynamic Selection

So folks...sorry to be a pest...but is the reason I'm getting an SQL5011 on this statement:

Fetch C1 For :Maxrows Rows Into :Wkinvmstp;

Is because my Declare looks like this:

Exec SQL
Select * From INVMSTP
Where Imvnda Between :HostFld1 And :HostFld2 And ...
(a long statement)

and it needs to be parameter markers instead of host variables in the WHERE clause?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To 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.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page