× 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 have seen this before when the program or service program is optimized.
If this is the problem you can fix it by doing a chgpgm or chgsrvpgm

John Sherrill
Content Manager OnDemand for i Development
T/L 938-6086 or 720-396-6086
Internet: jlsherr@xxxxxxxxxx
355 Quill Lane Matthews, NC 28105



From: "Larenzo Alexander" <Larenzo.Alexander@xxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Clientfor System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 08/26/2010 01:57 PM
Subject: [WDSCI-L] iSeries Debugger Gone Wild
Sent by: wdsci-l-bounces@xxxxxxxxxxxx



I'm using WDSC 7 and working with the iSeries Debugger. Most of the time
it works fine but sometimes it appears to be going wild. When I step
with F5, the debug line is jumping to unpredictable areas in my source
code. I was thinking maybe it had to do with me making changes to the
source code and recompiling. So I tried refreshing the service entry
point and that didn't work, I tried removing the service entry point and
added another one and that didn't work. I closed debugger and WDSC and
reopened it and that didn't work. I even rebooted my PC and stop and
started the Debug Remote server and that didn't work.



If anyone has any suggesting on what to try next or what causes this, I
would greatly appreciated it. I guess back to Green Screen debugger I
go, for now. J



Thanks


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.