You probably know this already, Mike. The SQL pre-processor converts your SQL statements to API calls in RPG IV. But the RPG IV code that's generated is - shall we say - ugly. (But then, we would not normally see it. Provided it works OK, who cares?)

It would help to see a little more of the original source code. On first inspection, I wonder if the IF SQLSTT statement, (which, BTW can be written as IF SQLSTATE) should be shifted a little to the right, (column 8 onwards)? (It doesn't look as though you're using **FREE.)

Brian.

On 17/08/2018 04:22, Mike Wills wrote:
Wow, I am really out of practice. I am having a compile error on a program
that I wrote quite a while ago. I am having issues getting it to compile.
I'm using free-format SQL and it appears like it's trying to compile this
into C specs. Thoughts as to where to look? This is program in production
and I need to make a minor change to.

031500
031500
031600 if sqlStt = SQL_SUCCESS;
031600
031700 //* exec sql
031700
031800 //* declare c1 cursor for sel;
031800
031900 //* exec sql
031900
032000 //* open c1;
032000
032000 C |Z-ADD -4
SQLER6 SQL 032000
======>aa b

*RNF5505 30 a 032000 Positions 6-7 are not blank in a free-format
calculation
specification.

*RNF5347 30 b 032000 An assignment operator is expected with the
EVAL operation.
*RNF5501 20 032000 The comment entry on a free-form calculation is
not valid.
*RNF5505 30 Positions 6-7 are not blank in a free-format
calculation
specification.

032000 C SQL_00008 |IFEQ 0
SQL 032000
======>aa

*RNF5505 30 a 032000 Positions 6-7 are not blank in a free-format
calculation

--
Mike Wills
http://mikewills.me
Ph: 507-933-0880


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-2019 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].