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



This error is documented on a IBM tech doc, which can be found here:

http://www-01.ibm.com/support/docview.wss?uid=nas1ee71ca2f7700ad31862570bb00619997

<http://www-01.ibm.com/support/docview.wss?uid=nas1ee71ca2f7700ad31862570bb00619997>It
states:

Error message CPF7E15 will be received when pressing F11 or using EVAL to
display a variable if the variable name is a reserved word that is used in
the system debugger.

The following example re-creates the problem:

*************** Beginning of data
****************************************************
d progstat sds
d user 254 263
d user2 s 10 inz(*user)
c user dsply
c user2 dsply
c seton lr
****************** End of data
*******************************************************

Steps used to demonstrate the issue:
1Start debug on the program.2Step to the first executable statement.3Press
F11 on the variable 'user'. Message CPF7E15 is received. The cause of the
error is that 'user' is a reserved word in the system debugger.To evaluate
the value of the variable, you must use EVAL %VAR(user).

*Note: *This message is no longer issued on R610.


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



On Tue, Jul 6, 2010 at 2:21 PM, Dennis Lovelady <iseries@xxxxxxxxxxxx>wrote:

When I compile there are no errors. The 'EVAL USER' shows up on the
'Debug' line and when I place the cusser on the field is where the
'Syntax error' displays.

It acts like USER is a reserved word within STRDBG. For example, 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 a lot of
files and programs.

Well, the fact that the debug tool doesn't display a particular 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.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
To err is human, to moo bovine.



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