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



"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 10/04/2017 11:43:36 AM:
----- Message from Dan <dan27649@xxxxxxxxx> on Wed, 4 Oct 2017 10:
40:02 -0400 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] CRRDG3250W Number of source file lines does not match
debug information. Clearing cache doesn't help.

The biggest question I have now is why isn't RDi debug using the source
embedded in the program object??? I thought that's why we have the
DBGVIEW
parameter on the compile commands.

On Wed, Oct 4, 2017 at 10:23 AM, Dan <dan27649@xxxxxxxxx> wrote:

As Ken pointed out, you can right-click and switch to the *Listing view
which will use the embedded compile listing. This uses a different editor
for the source (it's not source, it's a compile listing) so there are a
few features that don't work. But it will definitely use the embedded
compile listing. By default the debugger uses the *Source view which it
tries to find. This has allows features that the compile listing doesn't
have.

At times, I've simply closed RDi, gone into my workspace and cleaned out
old source from under the RemoteSystemsTempFiles directory. After
restarting and either debugging or opening the source for edit RDi now has
to download the current source.

Michael Quigley
Computer Services
The Way International

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.