|
This is fantastic, and it works for me, but tell me: where did you find that
in the help? I did look, didn't see.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A fanatic is one who can't change his mind and won't change the subject."
-- Winston Churchill
According to the help text:When I compile there are no errors. The 'EVAL USER' shows upIt acts like USER is a reserved word within STRDBG. For example,
on the 'Debug' line and when I place the cusser on the field
is where the 'Syntax error' displays.
if you type:
EVAL EVAL
EVAL QUAL
Or EVAL with other debug commands, you will get the same
complaint, same CPF7E15 error, et cetera.
If this is a reserved word we are going to have to change aWell, the fact that the debug tool doesn't display a particular
lot of files and programs.
variable isn't necessarily cause for mass change to your
programs. That is, unless the value of USER is critical to the
debug process and cannot be determined through other means. I
wouldn't change anything yet. Although I haven't landed on a
solution - I did give it the old college try and haven't quite
given up yet - there may be some help from IBM or your service
vendor on this. I'd recommend calling for help.
Do let us know what you find.
Display a Variable - Help
Debug command: EVAL %VAR(EVAL)
Result: DEC = 22.1
Comment: If the variable has the same name as a debug
command, the %VAR keyword must be used.
So for this specific example, issue: EVAL %VAR(user)
Regards, Chuck
--
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.