|
Hi David, If a variable name matches a name of one of the debugger commands (like STEP, BREAK, etc.) a special syntax is required. In this situation, you will need to bring up the 'Monitor Expression' dialog and enter the following: %VAR(STEP). This syntax will work for any variable, but only required for those that match names of debugger commands. In this scenario you will have to use 'Monitor Expression' dialog. Hope this helps, Vadim Berestetsky Distributed Debugger Development Internet: berestet@ca.ibm.com David Wright <dwright@celsinc.com>@midrange.com on 01/15/2002 07:10:41 PM Please respond to code400-l@midrange.com Sent by: code400-l-admin@midrange.com To: "CODE400-L (E-mail)" <CODE400-L@midrange.com> cc: Subject: Variable named STEP In my RPG400 programs, I have a variable named STEP which holds the next routine the program will go to. When I try to add STEP to the Program Monitors, I get a popup 'CPF7E15 : Syntax Error Occurred'. Is debugger interpreting this like a STEP in a For/Next loop? _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-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.