Mike,
Awesome! It shows that I missing PTFs!
:)
I will forward to my system administrator, to ask him to get those missing one!
Thanks!
-Ken Killian-
(423) 510-3129
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Hockings
Sent: Wednesday, February 20, 2013 9:56 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] debug no longer working
From RDP's point of view to check the PTFs just expand your RSE
connection, right-click on the Objects element and select the Verify Connection... action. This will start a little dialogue that shows the results of the checks. Expand all the sections fully to be sure you are not missing any messages.
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical Support IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Ken Killian <kkillian@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>,
Date: 2013-02-20 09:39
Subject: Re: [WDSCI-L] debug no longer working
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
Mike,
I have a lot of authority on our development box, how do I check for the latest PTF?
I see some stuff applied with DSPPTF command. But, it has been over 20-years, since I have ever check PTF stuff...
Anyway, if there is a PTF to apply, I will get with our system administrator to apply it. :)
More Details on my Debug Green Screen Session. It cannot find the source to debug.
Which basically makes that DEBUGGER worthless! <LOL>
I get the "Source not found", and when I try to add a source path, that does not work either...
I reported this before...
Here is a message in the Error-Log:
java.lang.NullPointerException
at com.ibm.debug.pdt.internal.core.model.ViewFile.setViewFile(Unknown
Source)
at com.ibm.debug.pdt.internal.core.model.View.change(Unknown Source) at com.ibm.debug.pdt.internal.core.model.Part.updateViews(Unknown Source) at com.ibm.debug.pdt.internal.core.model.Part.getCurrentView(Unknown
Source)
at
com.ibm.debug.pdt.internal.core.model.DebuggeeThread.getLocation(Unknown
Source)
at com.ibm.debug.pdt.internal.core.model.StackFrame.getLocation(Unknown
Source)
at com.ibm.debug.pdt.internal.core.model.StackFrame.getViewFile(Unknown
Source)
at
com.ibm.debug.pdt.core.sourcelocator.PDTSourceLookupParticipant.findSourceElements(Unknown
Source)
at
org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector$SourceLookupQuery.run(Unknown
Source)
at org.eclipse.core.runtime.SafeRunner.run(Unknown Source) at org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.doSourceLookup(Unknown
Source)
at
org.eclipse.debug.core.sourcelookup.AbstractSourceLookupDirector.getSourceElement(Unknown
Source)
at
org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.lookup(Unknown
Source)
at org.eclipse.debug.ui.DebugUITools.lookupSource(Unknown Source) at org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter$SourceLookupJob.run(Unknown
Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
PS. The SEP work fine however! But, it is nice NOT to have to restart my session to get the debugger. Or I can use RDP 8.0, which still works fine.
Just hate switching back to old version... <grin>
Oh well, not a "Show Stopper", but I sure do miss that old functionality.
For now, I have to add SEP, and restart my testing to catch the error...
-Ken Killian-
(423) 510-3129
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Hockings
Sent: Wednesday, February 20, 2013 9:23 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] debug no longer working
Hi, Ken,
The green-screen debug using STRRJESSN should work just fine with RDP 8.5.1. Do you have the latest debugger PTF applied? You can check this with the Verify Connection...
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical Support IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx voice
1-905-413-3199 T/L 313-3199 ITN 23133199
From: Ken Killian <kkillian@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>,
Date: 2013-02-20 08:13
Subject: Re: [WDSCI-L] debug no longer working
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
Too bad the regular debug a session does NOT work on RDP 8.5, like it did on RDP 8.0
I do like the SEP, but sometimes the debug a green screen session, like it used to work...
:(
-Ken Killian-
(423) 510-3129
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Buck Calabro
Sent: Tuesday, February 19, 2013 5:43 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] debug no longer working
On 2/19/2013 5:14 PM, dale janus wrote:
Now that I found remote systems explorer, I have lost debug.
-snip-
Now when I run the job, it completes and RDI never starts debugging.
What am I missing? I did not change the libraries and the service
entry point tab shows the correct program in the correct library with
enabled yes.
I have started and stopped RDI a few times.
I myself never seem to have a problem with debug but my colleagues occasionally report this very issue. The advice I give them is to end their green screen sessions in case there's an activation group issue.
This tends to clear up almost all of the issues they have.
On the rare occasion that hasn't helped, I ENDDBGSVR and STRDBGSVR, which always does the trick.
I never do anything on the SEP menu except for Set, Remove and Refresh.
I do a Refresh after every compile, and Remove when I'm done.
--buck
--
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.
--
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
