× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I would, but my company did not purchase the support option....

Although, IBM was very supportive last time I open a PMR.
I got hit up to purchase support. And then I am always questioned why we haven't purchase support.
And I am trying to wrap up an important project before driving out of town to see family.
I am just being honest, we haven't purchase support, and I do NOT have the time either...

But, in today's tight economy, I do NOT even think about asking I.T. Management...
We have had layoff both in IT and regular employees. Thanks to government regulations driving up cost.

The work around is to clear your break points each time. Which I have been doing since WDSC 6.0

I use to always use the debugger editor, until a co-worker pointed out that he like using the LPEX edit for the following Reasons:
Color Syntax
Edit code while debugging. Of course, you have to restart to find.
Able to use the Filters for Date/Subroutine/Procedure/Variables

The only drawback is the missing icon to show the breakpoints...

Like I said, this is NOT a show stopper.

-Ken Killian-
(423) 510-3129


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Xuan Chen
Sent: Monday, December 17, 2012 10:50 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDP 8.5.1 debug problem: Break point icons not showing...


Hi Ken,

Please open a PMR for it and we will look more into it

Thanks,

Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx





Ken Killian
<kkillian@usxpres
s.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
17/12/2012 10:44
AM Subject
Re: [WDSCI-L] RDP 8.5.1 debug
problem: Break point icons not
Please respond to showing...
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>






Hi,

Now this is a problem that has existed for a long time...

I like to use the LPEX editor for my debug editor. Which I can use the power of LPEX, such as color syntax and find functions. So, I can edit my code, when I find errors! Very Cool!!!!!
<Big Smile>

Problem is when restarting debug, it stops at old break points, but does NOT show the "DOT" for the break-point....

If I right-click, to show the "*LISTING", I then see the break points. But, the break points do NOT show up in Debug using the LPEX editor...

It seems to me that this is a "Re-Paint" error of some sort....

I end up toggling to *LIST view, to remove the break points, that I no longer need...

This is NOT a biggie, nor a show stopper. But, just though I would mention it on this forum. In case others have ran into the same problem...

-Ken Killian-
(423) 510-3129

--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.