Where do I set this? I tried properties of the javaw.exe executable, but found nothing...also nothing in the preferences of RDP unless I am just not looking at the right branch...
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Bucknum
Sent: Monday, February 06, 2012 4:04 PM
To: Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries
Subject: Re: [WDSCI-L] Noted issues with RDP V8.0.3.1
Have you tried setting the processor affinity of the javaw process to
just one core? I can't say that I've seen this with RDi/p, but I've had
several games that required this fix in order to eliminate jerky game
play.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tarr, Kenneth
Sent: Monday, February 06, 2012 1:09 PM
To: 'Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries'
Subject: Re: [WDSCI-L] Noted issues with RDP V8.0.3.1
I haven't opened up a PMR but have another situation (possibly related
to #1?) that has started. In this case, the Monitors view suddenly
stopped working. That is, it will not display any of the fields I
selected. But on a future debug session (could be several later),
suddenly all the fields I selected appeared. Sometimes duplicated
because I tried selecting them more than once. Not sure why this
started. I would experiment with a new workspace, but work demands
prevent me from experimenting right now.
As for #3 and #4, the PC I have is a dual processor PC @ 2.4Ghz. I'll
check the processes running behind the scenes to see if one (or more) of
them are causing issues with the debug speed.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Hockings
Sent: Thursday, February 02, 2012 3:06 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Subject: Re: [WDSCI-L] Noted issues with RDP V8.0.3.1
Hi Kenneth,
For your first issue (1) could I suggest that before opening a PMR you
first try with a new workspace without importing preferences, etc?
The other issues (3) and (4) to do with automated stepping performance,
is
as you might expect dependent up on the response times of the IBM i, the
network and the local PC. In most cases the IBM i and the network are
not
likely the bottleneck. So I would tend to look closely at the PC and
see
what other processes are running. My understanding is that each step is
done "full speed" and the automated stepping done by delaying between
steps. The symptoms that you describe in (4) almost seem to me that the
PC is not able to keep the UI updated as fast as the debug is stepping.
As
Xuan suggests, maybe a slower stepping speed would give you more
consistent results?
Mike
Mike Hockings, P.Eng.
IBM Rational Developer for System z and Power Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: "Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx>
To: "'Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
Date: 2012-02-02 13:34
Subject: Re: [WDSCI-L] Noted issues with RDP V8.0.3.1
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
I'll open a PMR on the first issue.
As you were replying to this message, I was actively in a debug session.
With the speeds set to 100ms which should be ten lines per second, the
stepping was about three lines per second instead. At times I stop the
automatic stepping to analyze some data or make some notes, then resume.
This I do multiple times during my debug. At one particular time, when
I
resumed the automatic stepping, it suddenly picked up speed and was
clocking at about seven lines per second with the same settings.
(Several
times in the past it suddenly picks up and is clocking at ten lines per
second based on the settings. I usually use this setting to speed
through
some code, then stop the animated stepping and use the manual in
sections
where I want to clearly see after each line what's happening.)
What I also noted is that, between each start and stop of the automated
stepping, the stepping speed remained consistent. As there are constant
fluctuations going on behind the scenes on the System i, I would expect
to
see fluctuations in the stepping animation, but I do not. The one
constant I have seen of late is that it starts off slow, then something
causes it to speed up as I do these stop/start motions. I haven't seen
it
slow down when it does pick up speed. I will try different microsecond
settings and see what happens there, and let you know of my results.
I'll
be actively debugging today so I should be able to collect some results
along the way.
-- Ken
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Xuan Chen
Sent: Thursday, February 02, 2012 11:38 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
for
System i & iSeries
Cc: Alan Boxall
Subject: Re: [WDSCI-L] Noted issues with RDP V8.0.3.1
Hi Ken,
For the first problem, I cannot produce it using RDp 8031 driver.
Please
open a PMR so we can look more into it. Thanks.
For the automatic stepping problem, since the speed also depends on your
client/server machine speed, and also network connection speed, this
interval is just a guide line. Could you please try to set it to a
lower
interval (like 5 per second) to see if the behaviour will be better?
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Tarr, Kenneth"
<Kenneth.Tarr@ass
ociatedbank.com>
To
Sent by: "'Rational Developer for IBM i /
wdsci-l-bounces@m Websphere Development Studio
Client
idrange.com for System i &
iSeries'"
<wdsci-l@xxxxxxxxxxxx>
cc
01/02/2012 02:05
PM
Subject
[WDSCI-L] Noted issues with RDP
V8.0.3.1
Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>
The latest update of RDP seems to be working better, but there are a few
small issues, primarily with the Debug perspective.
1) In Debug, I used to be able to right click in the Monitors panel and
had the option to add a field for monitoring. That option no longer
exists. The only way to watch a field is to select it from the LPEX
Editor view and add it that way. Sometimes keying in the field is much
quicker than searching for it then adding it that way. In fact I still
see the + sign icon but it is always unselectable.
2) Also in Debug, on the Breakpoints panel, there was never a + sign to
begin with. But there you can right click and add a breakpoint for line
or watch.
3) I know I've complained about this before and there wasn't much that
could be done then, but the animated stepping speed is still
inconsistent.
It's set at 100ms so it should step through ten lines per second, but is
stepping at a whopping speed of two lines per second. And then
sometimes
it suddenly takes off and does step as fast as I set it. I disabled as
many panels as I didn't need, but that didn't seem to clear it up.
(Almost
like that Snickers commercial with Ozzy Osbourne saying "I just don't
feel
like it"...lol) Still think there's something there, but this time I
will
ask the community if they've noted this issue (for those who have used
this feature).
4) Still have the issue where suddenly when in the animated stepping
speed mode, the LPEX Editor stops updating which line it's on. The
Debug
panel then starts flashing as if it's updating the debug stack every
step
(most steps it doesn't), and even the font of the Debug label on the
panel
briefly becomes italicized between each step (weird). Fortunately I got
this behavior to stop when I changed the Layout option from Automatic to
Breadcrumb, at least for now.
Otherwise it's performing much better this version.
-- Ken
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 t
o be used, and cannot be used, by a taxpayer for the purpose of
avoiding penalties under the Internal Revenue Tax Code
--
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 t
o be used, and cannot be used, by a taxpayer for the purpose of
avoiding
penalties under the Internal Revenue Tax Code
midrange.com
