× 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.


  1.  Home
  2. RPG400-L
  3. December 2008

Re: Supported Syntax in SQLRPGLE in V6R1. Changed?

Pete

There is something about stuff that has to appear first in source now - might have started in V5R4 - I hope this tickles someone's memory. But it is like DECLARE CURSOR and such need to be at the top of the source.

I dunno!

Vern

Pete Helgren wrote:
Well, I don't get it. Seems like there is something different about the way host variables are defined and used since V5R3M0. I went back to using the 270 I have at V5R3M0 so I could get this fix compiled and out to the customer but it is awfully strange that an SQLRPGLE source member from a V5R3M0 box can't be pulled over and compiled in V6R1M0.

Once I get this out to the customer, I'll call IBM. Seems like it would be something simple but after searching all afternoon on the 'Net, I haven't found anything promising.

Pete


Brian Johnson wrote:
On Thu, Dec 4, 2008 at 3:17 PM, Pete Helgren <Pete@xxxxxxxxxx> wrote:

Thanks Brian.

Do you know if host variable use changed in 6.1?


Sorry, I'm not there yet, still working at V5R3. The work-around for the
problem I'm thinking about was to use CRTSQLRPGI GENLVL(30) to accept the
'error' and allow the compile to continue. Perhaps your command default was
changed at V5R3 but hasn't been propagated to the V6 box.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.