Michael,
Clear out the RemoteSystemsTempFiles directory does not clear your iProjects.
So, if you have an old source in an iProject, it might pull in that source by default! Which sadly happen to me, and it pulled in over 2-year old CODE!!!! Yikes!!!
I have suggested that it should ALWAYS PULL the CURRENT source if available. But, the "Work-Around" is to uncheck the "Search i Projects first for debug source". Not a 100% sure how to clear it out IBM I SEP. Someone mentioned it another post.
I was told it was designed for vendor who do NOT send their source code, but still want to be able to debug their code using iprojects.
After all the Microsoft paradigm is to use "projects", and IBM i needs to follow that. In the Majority of the programming world, they use projects. I guess we need to catch up to rest of the world. <smirk>
I use iProjects all the time. But, it is NOT for NEWBIES, and you need to understand how they work. The basic idea is that the MASTER-COPY is on your PC and/or Network. Which for me can be great! With a few clicks, I push my source and compile on many different systems! Awesome!!!
But, that breaks the standard way we are used to editing code directly on the IBM i.
PS. Any more, I tend to put my iProjects in a separate workspace, that is another work Around...
Has anyone mentioned that RDI has a Huge Learning Curve? <smirk>
Oh well, I will still take RDI with its little quirks over the 1960's SEU with 19/23 line limitation with no color, no code assist, no outline, single click for finding errors, etc...
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Thursday, October 5, 2017 9:58 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] CRRDG3250W Number of source file lines does not match debug information. Clearing cache doesn't help.
"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
--
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:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
midrange.com
