|
works fine for me using:
EVAL USER
EVAL %VAR(USER)
both return the value of the variable with no errors. must be a PTF issue
on the system you're on
Thanks,
Tommy Holden
From: "Crispin Bates" <cbates@xxxxxxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Date: 07/07/2010 08:23 AM
Subject: Re: Syntax error help
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
Dennis,
Thanks for checking it on yor system.
This also causes the same problem on my 6.1 system.
Duser S 10
/Free
User='FRED';
*INLR=*on;
/End-Free
EVAL and EVAL %VAR() both fail.
Anyone with a 6.1 system care to see if they can get the value of User in
debug on this simple example?
Thanks,
Crispin.
----- Original Message ----- From: "Dennis Lovelady" <iseries@xxxxxxxxxxxx>
To: "'RPG programming on the IBM i / System i'" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, July 07, 2010 8:51 AM
Subject: RE: Syntax error help
Not sure why user2 would be ambiguous. I tried this on a V5R3 systemand
did not have that result. Everything seems well (if I use %VAR(user) of
course).
Must be a V6 thing?
--
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 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.