RE: (no subject)

Lol, that's funny.  I'm sure "they"'ll have a fix for this as soon
as someone sends them a bug report.  Just an oversight, I'm sure.

I guess until the fix you'll have to do
/endfree
C            Eval    EndedBadly = *on;
/Free
blah blah.

Regards,

Jim Langston

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Westdorp, Tom
Sent: Thursday, September 20, 2001 12:36 PM
To: rpg400-l@midrange.com
Subject: (no subject)


I'm working on a service program on R510 that has the following defined in
it:

D EndedBadly      s               n

Now that we're using r510 on all the boxes, and Code/400 has the cool option
to convert it to /free I figure Why not?"

Well TIME to a 12 digit RESULT field is one reason, but...

anyway after conversion an attempt to compile generates a couple of the
following:

214800   If pa_BALANCE <> TestBalance;

214900     EndedBadly = *On;

======>       aaaaaaa

*RNF5247 20 a      214900  The scope delimiter of the ENDyy operation is not
valid.
215000   Else;

215100     EndedBadly = *Off;

======>       aaaaaaa

*RNF5247 20 a      215100  The scope delimiter of the ENDyy operation is not
valid.
215200   EndIF;

*RNF5247 20      4 The scope delimiter of the ENDyy operation is not valid.

Is EndedBadly some sort of IBM Reserved Word now?  :-)

Is this a bug or is it now impermissible to have field names that begin with
"end"?
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.