Ken,
I tried to reproduce your scenario, but I cannot. Debugger works fine when
attaching to a running job (the application has a unmonitored exception).
Is your program OPM or ILE, and does what kind of debug views it has (*ALL,
or *LISTING)? If *ALL, is the source member is the same location where the
program is compiled?
And please also start your RDp with the following modification of
eclipse.ini file (it should be in the installation directory of yoru RDp):
Remove "-Xnolinenumbers" from the file.
After RDp is restarted, please set this checkbox in the preferences:
Run/Debug -> Compiled Debug -> Trace engine connection
When you encounter this problem, please send me the .log file from your
workspace's .metadata directory.
And there should also be some epdcdumpXX.hex files in the .metadata
directory. Please me the latest one (this one should be corresponding to
the debug session which has problem).
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
Ken Killian
<kkillian@usxpres
s.com> To
Sent by: "Rational Developer for IBM i /
wdsci-l-bounces@m Websphere Development Studio Client
idrange.com for System i & iSeries"
<wdsci-l@xxxxxxxxxxxx>
cc
16/01/2013 03:19
PM Subject
Re: [WDSCI-L] RDP 8.5.1 debug
problem: "Source not found."
Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>
I worded that wrong...
I mean to debug and EXAMINE ONLY, and see what cause the Bad Data-issue
from a vendor web-service...
Production Debug is to quickly diagnose any error, to provide immediate
cause of the error.
By correct the error, I meant find the Error in debug, and do an emergency
check-out and update. And then re-promote in the morning, for paper work.
Get manager approval, etc...
So by "Fix", I meant find the error, and check-out and fix....
I ended up ending the job, adding a SEP debug, and then restart to find the
error. Which was a big pain. Since I had to wait 5-minutes for the auto
restart. And because I was tired, I forgot to change the Debug User profile
to QUSER, instead of my own. On Debug-Job, I can use "*" for the current
job-number and Job-user. Very nice!
Oh well, it is sort of complicated. I am actually pull data from a
web-service into an xml file.
I use SEP 99% of the time anyway. I have grown to like that over the
Debug-Job.
But, as stated before, it worked on WDSC 6.0, WDSC 7.0, RDP 7.5, RDP 7.6,
RDP 8.0, and RDP 8.0.3. Not sure if I missed any release. Only have been
using this I.D.E. for 7-years...
-Ken Killian-
(423) 510-3129
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Ray Rhyno
Sent: Wednesday, January 16, 2013 7:50 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Cc: wdsci-l-bounces@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDP 8.5.1 debug problem: "Source not found."
Curious question - You mean your company actually allows DEBUG on a
production job running on a production system? Your a lucky Guy but the
company is not so lucky. As you know with debug you can stiff User ID's
password. I realize this is a debug RDP issue and it needs to be fixed for
development environments. Debug is definitely a must for development
environments. But allowing the use of debug in the middle of the night to
fix a production job running on a production system. That is scary stuff.
From: Ken Killian <kkillian@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 01/16/2013 07:18 AM
Subject: Re: [WDSCI-L] RDP 8.5.1 debug problem: "Source not found."
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
More information on this Debug program with "Source not found"
RDP 8.5.1: If I "Debug job", like my session: QPADEV0001, and click
Step-INTO, the debug works GREAT!
But...
RDP 8.5.1: When I say to debug a job current running in batch, then I get
the message: "Source not found."
RDP 8.3.0: So, I turned around and fire up RDP 8.0.3, and the "Debug Job"
works flawlessly! <Joy Joy>
So, RDP 8.5.1 got broke somehow on this release...
I often have job passing information around to different data-queues, so
the ability to debug batch job, has always been a great help to me.
Now, I must remember to fire up RDP 8.0.3, when called in the middle of the
night, and I need to debug a production job.
So, I ask the question again, is anyone else running into this problem
beside me? Where they can no longer debug a batch-job using RDP 8.5.1 or
RDP 8.5? It would be good to find out that I am NOT the only one.
:)
-Ken Killian-
(423) 510-3129
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Ken Killian
Sent: Tuesday, January 15, 2013 3:24 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] RDP 8.5.1 debug problem: "Source not found."
Xuan and other users encounter the debug job source error,
Yes, I tried the DEBUG job alone WITHOUT the Service entry points.
I keep forgetting to try my old RDP 8.0.3 to debug jobs. But, when called
late at night, it is hard to remember. I had to restart the job several
times, to catch in debug. Often, I forget to put in the production user
name for debug with the "Service Entry points"...
For debugging for development, I love the Service Entry points. But, for a
job failure, the "Debug-Job" use to be GREAT, when it worked on RDP 8.0.3.
I just enter in the name. And leave the User & Job-Number as "*" to select
the current active job! Perfect!
Shucks, IBM site requires registration, which is understandable...
https://www-947.ibm.com/support/servicerequest/Home.action
You can use SR/PMR to report problems on nearly all IBM supported software
products
My company didn't purchase support. Out of approximately, 18 developers,
only about 4 of us RDP. The rest stick to RELIABLE SEU... <Big Frown>
Oh well, is anyone else running into this error, where the source Cannot be
found for "Debug Job"? Or am I the only one encountering this error?
If someone is a registered support customer, could they be as so kind to
enter in the PMR on this?
Thanks!
Last time I open a PMR, IBM was very helpful, but informed me that my
company didn't NOT purchase a service contract. Unfortunately, like a lot
of places, our budget is tight.
With less than 25% of the staff using RDP, it is hard to justify. But at
least we have the license for RDP!
I get the same thing from the other developers: "Why learn something new,
when SEU works fine, with NO ERRORS..."
But, I think I am slowly getting some developers, to at least try it...
I get the old excuse: "Never enough time to learn something new. It's
navigation is too hard to learn, etc..."
Okay, I will step down from my soap-box... <LOL>
-Ken Killian-
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Xuan Chen
Sent: Tuesday, January 15, 2013 2:10 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] RDP 8.5.1 debug problem: "Source not found."
Hi Ken,
It is quite obvious, but just to confirm... SEP and debug currently
running job are debugging the same program?
Could you please open a PMR so I can look more into it? Thanks.
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
Ken Killian
<kkillian@usxpres
s.com> To
Sent by: "Rational Developer for IBM i /
wdsci-l-bounces@m Websphere Development Studio Client
idrange.com for System i &
iSeries"
<wdsci-l@xxxxxxxxxxxx>
cc
15/01/2013 01:25
PM Subject
Re: [WDSCI-L] RDP 8.5.1 debug
problem: "Source not found."
Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>
Hi,
Last night, I ran into the source not found for the source debug....
This is where I try to slam a current running program into debug, to view
select variables. And it cannot find the source. I get the error message
"Source not found"...
And yet, the "Service Entry Points" works fine. It can find the source....
<perplex look>
I tried search the email, and I could not find reported issue on this.
Please advise if I missed it...
I guess about 98% of the time, I use "Service Entry Point" instead of the
debug job. But, the Debug job should still work. It doesn't even work when
I manually put in the look up path. Very frustrating...
When trying to encourage other Developers to use RDP, it is discouraging,
when things do NOT work...
-Ken Killian-
(423) 510-3129
From: Ken Killian
Sent: Monday, December 17, 2012 10:37 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries'
Subject: RDP 8.5.1 debug problem: "Source not found."
Hi,
Using the RDP 8.5.1 to debug a job, it CANNOT find the source....
But, using the Service entry points, it DOES find the source....
Any idea why the debug job cannot find the source. I even tried adding the
ibm source file, and it still cannot find the source....
I get the "Source not found" and the "Edit Source Lookup Path..."
button...
Which shows my source files...
Am I missing something here? Has anyone else ran into this problem on RPD
8.5/8.5.1?
Not sure if a PMR/Trouble-ticket was open on this or not.
-Ken Killian-
(423) 510-3129
From: wdsci-l-bounces@xxxxxxxxxxxx<mailto:wdsci-l-bounces@xxxxxxxxxxxx> [
mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Parkins
Sent: Sunday, October 21, 2012 12:53 PM
To: Rational Developer for IBM i / Websphere Development Studio Clientfor
System i & iSeries
Subject: Re: [WDSCI-L] Tips/Tricks for Installing RDp 8.5?
I have always used IBM Installation Manager to initiate the installation.
Seems to do the trick without a hitch. Worth updating IM first to the
latest version, (free download).
Brian Parkins.
--
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<mailto:WDSCI-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or emai
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
Consider the environment. Only print when necessary. Préserver
l'environnement. Imprimer que si nécessaire.
If you are not the intended recipient, please notify the sender immediately
and without any other actions on this email, destroy and delete this
message and any related attachments from your computer. Si vous n?êtes pas
la ou le destinataire visé, veuillez en aviser immédiatement l?expéditeur,
et sans aucune autre action sur la présente communication, détruisez et
supprimez de votre ordinateur le message et toutes les pièces jointes
connexes.
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
