This is current design.  It happens for the subroutine in main procedure. 
Variables view displays the local variables in current scope. Subroutine 
does not define local variables.  Instead of showing nothing, debugger 
displays the local variables of the enclosing subprocedure.  However, the 
subroutine in main procudure is processed differently and no variable is 
displayed. 

There is inconsistent behavior here, for subroutine in main procedure and 
other subprocesures.  We definitely welcome community's feedback for the 
behavior.


Thanks,

Li Ding
iSeries AD, IBM Toronto Lab
Email: lding@xxxxxxxxxx 
Phone:  (905) 413-4393,  T/L:  969-4393,  Fax: (905) 413-4850
Internal Mail Address: D1/Dept.089/8200/MKM


AGlauser@xxxxxxxxxxxx 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
07/14/2006 11:47 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


I have noticed this as well.  One thing I noticed is that the variables 
view seems to be properly updated if you 'Run to location' to get into the 

subroutine, or break due to a breakpoint that is located in the 
subroutine.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 14/07/2006 12:37:15 PM:

When I (and another programmer here) are in debug and the program enters
a subroutine, the variables and their values are no longer visible.
Is this a bug or by design. I searched the forum, but didn't see any
answers.

My version is 

Version: 6.0.1

Build id: 20050725_1800

I can see the variables if I add them to the monitor, so I can work
around  the problem, but it doesn't seem like I should have to.

Mike

_______________________ 
Michael Roderick 
IT Senior Programmer/Analyst 
Farmers Co-Operative Dairy 
(902)-835-4005 ext 3226 



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.