I've never been a fan of having to have the SET Options be the first SQL
code to appear in the program in a top-down fashion.
SET OPTION is never executed but is the equivalent of the H-Specs for
embedded SQL.
Have you ever complained about H-Specs being in front of all other
specifications?
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Kurt Anderson
Gesendet: Wednesday, 10. February 2010 18:51
An: 'RPG programming on the IBM i / System i'
Betreff: RE: SQL: RNF5347E An assignment operator is expected with the EVAL
operation.
I figured the source member type was too easy a solution, but that was the
only I was duplicating the issue.
Glad you got it resolved.
I've never been a fan of having to have the SET Options be the first SQL
code to appear in the program in a top-down fashion.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, February 10, 2010 11:41 AM
To: RPG programming on the IBM i / System i
Subject: Re: SQL: RNF5347E An assignment operator is expected with the EVAL
operation.
Source type was SQLRPGLE.
Problem was twofold.
1 - Added exec sql into main body which put it before set options which
resulted in error about not allowed.
2 - Having the not allowed confused precompiler (oh Gina!!!!!) to no end.
This caused the RNF5347 error over a perfectly fine sql statement.
Simple fix was to move the main body sql statement to the fetch cursor
subprocedure. Resolved both issues.
Rob Berendt
midrange.com
