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



Sorry if it's already been said, but I'm pretty sure the issue you're
running into is actually a result of v5r4 not v6r1. In v5r4 the
top/down order of SQL within the program now matters. Also, at my old
job we got bit by using a procedure called SQLOpen which is now a
reserved word at v5r4 - note: bad idea to start a name with SQL*.

However there are SQL changes in 6.1 as well I believe, including the
use of local host variables.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Friday, December 05, 2008 10:59 AM
To: RPG programming on the IBM i / System i
Subject: Re: Supported Syntax in SQLRPGLE in V6R1. Changed?

I change the command defaults so I don't even have to remember anything
(except to change the defaults on a new release!)

I just got this from Common:

COMMON Webcast - What's New in RPG for V6R1

So I guess I'll check it out to find out why my SQLRPGLE programs from
V5R3M0 no longer compile in V6R1M0 (Barbara Morris should know if anyone

does!)

Pete


Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
the SET OPTION is not mandatory...but is much better than trying to
remember and manually key them in on the compile options 8^)

Thanks,
Tommy Holden



From:
Pete Helgren <Pete@xxxxxxxxxx>
To:
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Date:
12/05/2008 10:10 AM
Subject:
Re: Supported Syntax in SQLRPGLE in V6R1. Changed?
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



Even if none were ever used before? That is, is the Set Option now a

required entry in an SQLRPGLE program? I usually set the options at
compile time.

Pete


Helge Bichel wrote:

The SQL Set Option has to appear first in the source when on V5R4.

exec Sql
Set Option Commit = *NONE, CloSQLCsr = *ENDMOD;

Brgds
Helge


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [

mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg

Sent: Friday, December 05, 2008 5:38 AM
To: RPG programming on the IBM i / System i
Subject: 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.