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



To add to the knowledge database here...using the information below I found two copies of the same source in that library. The apparent cause of the lines not syncing up? One of the sources was RPGLE, and at some point in the project I had to change it to SQLRPGLE. WDSC saved a copy with SQLRPGLE, then had two copies to work from with the different attribute. So I believe it caused the out of sync issue I experienced. Once I removed the RPGLE source, things started working again. This was because of another program I was working on that just started to cause the debugger to misbehave.

Thanks again for everyone's help, and hope this helps anyone else who is experiencing the same issue.

Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Monday, February 22, 2010 2:03 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debug not in sync (WDSC 7.0.0.8)

Ken,

Here's what I've done when I've had the problem.

Open explorer on the PC and navigate to the RemoteSystemsTempFiles
directory within your workspace. From within that, select the directory
with the name of your system, then QSYS.LIB, and then the library where
your source is located (note you're not really selecting the library, but
rather then folder named after the library), then the source file, and
finally the source member for the program. Delete that source and WDSC
will download it again the next time you try to debug it.

e.g.: C:\WDSC
Workspaces\MYPROFILE\RemoteSystemsTempFiles\MYAS400\QSYS.LIB\MYPROFILE.LIB\QRPGLESRC.FILE\MYSOURCE.RPGLE

I know that I would have expected the source to be refreshed when you
select 'Clear Cache', but it doesn't seem to impact the cached source.
Deleting the file on the PC always works.

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/22/2010 12:53:20 PM:

----- Message from "Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx>
on Mon, 22 Feb 2010 11:10:51 -0600 -----

To:

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

Subject:

[WDSCI-L] Debug not in sync (WDSC 7.0.0.8)

I am having a problem with Debug not in sync with the line numbers.
Since a couple of days ago I have not been able to use Debug to
debug my application. It shows a completely different line number
from the source than what is actually being executed.

Here's what I have tried so far:
-- Recompiled the application
-- Cleared the cache (there are two locations where this can be done)
-- Changed to a different workspace
-- Clicked the Outline view to refresh the outline

No matter what I do, even when new lines are added or existing lines
in the program are removed, it doesn't sync up (and keeps going to
the same line number when I press F5 or F6 the first time when the
application begins).

I've even had it point to the source in two locations; one on the
iSeries, and one on my hard drive. Still comes to the same line
numbers which are not the actual lines being executed.

Any help would be appreciated.

Ken

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.