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



Jon,

That is correct.

Breakpoints are remembered by the source file (They are markers in the 
eclipse file).  But in order to install it into the program, we need the 
program information (library name, program name and type), since iSeries 
does not have program/service program loading event. 
Since you start your debug session with a different program, the debugger 
did not have the program information for the breakpoint.

One way you could overcome this behaviour is to start your debug session 
wtih multiple programs and service programs.  To do that, you could select 
multiple programs and service programs in the RSE, and choose Debug 
(prompt) and one of the choices. 

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx





"Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/05/2006 11:47 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
wdsci-l@xxxxxxxxxxxx
cc

Subject
[WDSCI-L] Debugging RPG400 code






Anyone have any experience using RPG400 code with the debugger?

It is "remembering" the break points I set in the program - but doesn't 
seem
to action them unless I first step-into it from an RPG IV program - after 
that
it seems to remember and will break just fine.

Anyone else seen this?

Jon Paris
Partner400
www.Partner400.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.