I've noted this as well.
First, you can change the settings that might speed things up. Under Windows, Preferences, select Run/Debug, Compiled Debug, Animated Step Into. Here, change the three values to lesser values. I have all three of mine set to 100ms, which is the lowest setting you can set it to. Theoretically, this should cause as many as ten lines/second to be debugged, but due to system overhead it actually translates to two or three. I've had it on occasion run at ten lines/second, which is sometimes desirable.
I haven't played with some of the other views and such, but I would experiment with various tabs (like the Values tab described below) and see if you get better results.
What puzzles me is that, at times, the debug run goes fast, and other times, it doesn't. And yet the views I have open haven't changed. Neither are the number of variables I am debugging, if any. So I have yet to understand why it does this behavior.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: March 24, 2014 10:54 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] slow debug
When you run debug make sure the Values tab is _not_ the visible one. In programs with a large number of variables the refresh of that slows things down. Use the Monitor view instead. Fine to use Values in subprocedures etc. but not in old-fashioned monoliths.
On 2014-03-24, at 11:36 AM, Warren Schultz <WSchultz@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Can the creators of RDI please work on getting debug to work faster? That is a big complaint from the folks @ my shop. Some get that "Engine is busy" error, though I personally have not. If you have a source member of any size, you'd better be ready for a long coffee break. Compiles could run faster too. If you want to wean folks away from SEU/PDM, then those basics need to be addressed.
Thanks
Warren S. Schultz
Senior Systems Analyst
American Foods Group, LLC
500 S. Washington St.
Green Bay, WI 54301-4219
Phone: 920-436-6472
Fax: 920-436-6551
Email:
wschultz@xxxxxxxxxxxxxxxxxxxxxx<mailto:wschultz@xxxxxxxxxxxxxxxxxxxxxx
[AFG_logo_signature]
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code
midrange.com
