× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Wow! This seems completely backwards from what was supposed to happen.
Prior to r4, the precompiler used the physical sequence of the SQL in your RPG
source member to generate such errors. In r4, it was supposed to allow you to
specify things in a logical sequence, such as inside of *INZSR. 
I'm surprised it used to work for you.

-Bob Cozzi

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Wagner, Linda
Sent: Tuesday, July 25, 2006 8:11 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Embedded sql Set Option on V5R4

We have a lot of sqlrpgle programs that use the Set Option in the *inzsr.
Everything worked fine until we upgraded to V5R4 and we get pre-compiler
errors.  The only way around this is if we remove the code from the inzsr
and add it before any sql code.  We put it in the inzsr so we'd be sure it
always ran before any other sql code.  Does anyone know if there's anyway
around this or are we stuck changing all of our programs before the next
time we compile them?

 

Thanks.

Linda Wagner 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.