I don't even have the variables tab open. I use the Monitor tab. You can
double click a variable in the code during debug and it will show up in
the Monitor tab. That way you are only tracking the variables that matter
to you. And yes, it runs much faster.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
"Haas, Matt (CL Tech Sv)" <matt.haas@xxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
11/05/2009 04:35 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc
Subject
RE: Debugging Remote Stored Procedure Calls
The only time I notice WSDC being slow is when there are massive amounts
of variables. Clicking another tab on the area the variables show up in to
hide them speeds things up considerable.
Matt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of David Gibbs
Sent: Thursday, November 05, 2009 4:11 PM
To: RPG programming on the IBM i / System i
Subject: Re: Debugging Remote Stored Procedure Calls
Michael Scott - IS wrote:
Albeit, slow.
Slower than debugging it the old fashioned way? :)
IMO, SEP debug speeds up my development by a factor of 2 or 3. Especially
since I'm often debugging 3 layers of code at the same time (client,
server, and host).
david
midrange.com
