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

Re: Syntax error help

Dennis,

AFAIK, PDM/SEU and (I suppose) the rest of green screen development is
"frozen" at 6.1, with no further updates. 7.1 and later will rely on RDi. So
my guess is that there would be little to zero chances of getting this
changed...

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Wed, Jul 7, 2010 at 8:03 AM, Dennis Lovelady <iseries@xxxxxxxxxxxx>wrote:

William, I am not in a position to request changes (current client is V5R3
and administration is hosted). But if I were, I would submit a request for
change to the debugger. Since it has been proven that EVAL %VAR(xxx) is
valid syntax for the EVAL statement, and since it has also been proven that
some variables (such as USER and QUAL) actually NEED that %VAR() "keyword,"
it seems to me that the STRDBG action that is taken when F11 is pressed
while the cursor is on a variable name should be EVAL %VAR(varname) rather
than EVAL varname. Or if not always done, then it should do that for
"reserved words."

Additionally, the words that the debugger has in reserve should also be
well
documented in an easy to find list. I personally have been unable to land
on such a list.

Just a suggestion that may do the RPG world (at least) a favor.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Open 24 hours. Lifeguard on duty 8AM to 8PM. Drowning absolutely
prohibited."
-- Swimming pool suggestions posted at Plantation Bay Resort,
Phillipines


Yes that worked. Thanks to all for your help.

William Moore
California Fine Wire
805-489-5144

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Morgan, Paul
Sent: Tuesday, July 06, 2010 12:15 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Syntax error help

Try using EVAL %VAR(USER) which will work. %VAR() gets you around the
error when you're using a reserved word.

Principal Programmer Analyst
IS Supply Chain/Replenishment
508-253-3934

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Willie J. Moore
Sent: Tuesday, July 06, 2010 2:50 PM
To: 'RPG programming on the IBM i / System i'
Subject: RE: Syntax error help

That is what I am doing now. If I rename field then work great. Will
hunders of files and programs, this could take some time.

William Moore
California Fine Wire
805-489-5144

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Tuesday, July 06, 2010 11:27 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Syntax error help

My, my! This happens even at V5R3. Lucky me: I never saw this until
today.

It's not listed as a reserved word in the RPG manual, and I cannot find
any reserved words mentioned in the docs for STRDBG.

Someone suggested that USER is a reserved word in SQL. I believe it's
reserved in COBOL too... but so what? Curious why that should be an
issue at all, but especially when debugging a non-SQL program.

Sounds like a good time to call the support vendor.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"People are usually more convinced by reasons they discovered
themselves than by those found by others."
-- Blaise Pascal

The syntax error occurs in the debugger, not the compiler or run-time.
I threw together a simple program to test with:

D userid s 10a inz(*user)
D user s 10a
c move userid user
c user dsply
c eval *inlr = *on

Compiles and runs without error. Shows the expected result.

however, if you go into the green-screen STRDBG debugger, set a
breakpoint on the DSPLY line, and when it hits that breakpoint, type
"eval user" (without the quotes) it says:

"Syntax error occurred."

Hitting help shows that the error is CPF7E15. It doesn't provide
much
of use as to why this is a syntax error, or how you are expected to
solve the problem.


On 7/6/2010 12:36 PM, Dennis Lovelady wrote:
What is the message ID of this syntax error? I'm quite confused
because you
say this compiles OK and that it has a syntax error. On what
command
does
the syntax error occur? What additional information can you
provide?

I don't understand your comment below about debug at all.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I get my exercise acting as a pallbearer to my friends who
exercise."
-- Chauncey Depew



I am getting a syntax error on the following field 'USER':
C move userid user

User is a field in our files. We just started having a problem
with
user in our files not being correct. After running a debug and
displaying the user field was when I saw the syntax error. The
compile
ran fine.

Also on the debug line is: EVAL USER

This has worked ok in the past.
Any help would be greatly appreciated.

William Moore
California Fine Wire
wjmoore@xxxxxxxxxxxx
805-489-5144

--
This is the RPG programming on the IBM i / System i (RPG400-L)
mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please
take
a moment to review the archives at
http://archive.midrange.com/rpg400-l.



--
This is the RPG programming on the IBM i / System i (RPG400-L)
mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



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.