Everything looks good in the PTFs list to me.

Connection to Central service . . . . . . . . . . . . .successful
Connection to Command service . . . . . . . . . . . . .successful
Connection to Data Queue service . . . . . . . . . .successful
Connection to File service . . . . . . . . . . . . . . . .successful
Connection to Record Access service . . . . . . .successful
Connection to Signon service . . . . . . . . . . . . . .successful
Checking PTFs
Rational Developer for i . . successful
Remote System Explorer . . successful
Product 5770WDS found
Option 60 found
PTF SI55236 successful
PTF SI64924 successful
PTF SI52577 successful
PTF SI60690 successful
Product 5770SS1 found
PTF SI53107 successful
PTF SI62949 successful
IBM i Integrated Debugger . . successful
Product 5770SS1 found
PTF SI57638 successful
PTF SI63271 successful
PTF SI63708 successful
PTF SI60383 successful
PTF SI67696 successful
PTF SI68006 successful
PTF SI68114 successful
PTF SI70427 successful
Checking server callbacks
Checking callback to RSE daemon
Callback to xx.xx.xx.xx on port 4300 successful




-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Steve Ferrell via WDSCI-L
Sent: Tuesday, March 3, 2020 12:19 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WDSCI-L] RDi Code Coverage not working - stuck at QTESEPEH

Thanks Ken!

Mitch, you should also check your PTF levels.

Open RSE -> your current connection -> Objects -> right click and press Verify Connection.

Look at the PTFs section.



Steve Ferrell
w. www.helpsystems.com



-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Tuesday, March 3, 2020 11:08 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi Code Coverage not working - stuck at QTESEPEH

External: Pause and review the sender’s email address, any URLs before clicking links, opening attachments, or following requests. When in doubt, contact the Service Desk.


Mitch,

Did you clear all "your jobs" in QUSRWRK, and then restart debug? Just asking for verification...
(As in the screen shot I sent you?)

Next Question, what version of RDI are you using? Did you update to RDi 9.6.0.7? It is a simple update...

You reported issues should not be happing, unless you did not kill all the back-ground jobs.

Another question, does it work in Debug, but not in Code Coverage?

PS. If that does not work, I will have to turn you over the RDI-GURU! Louis! <Evil Smirk> Just kidding!


Developer, Rpg II
Information Technology
Chattanooga, Tn
253129
kkillian@xxxxxxxxxxxx


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mitch Gallman
Sent: Tuesday, March 3, 2020 12:01 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [WDSCI-L] RDi Code Coverage not working - stuck at QTESEPEH

Can't get code coverage to work. My program always gets stuck at QTESEPEH.

Setting the service entry point - I see the following in the error log which I would think is minor.

ISeriesConnection.getAS400ToolboxObject() error running command: AS400Message (ID: CPF2103 text: Library QGPL already exists in library list.):com.ibm.as400.access.AS400Message@14c8ea40

I press the button to switch from debug to code coverage.

Submit my job....and it waits at QTESEPEH.


If I right click on the service entry point and click "Open Launch Configuration" I get the following in the error log:

Message: Unhandled event loop exception
Plug-in: org.eclipse.ui
Exception Stack Trace:
java.lang.NullPointerException
at com.ibm.etools.iseries.debug.internal.ui.IDEALDebuggeeHelper.findOrCreateSEPLaunchConfiguration(IDEALDebuggeeHelper.java:50)
at com.ibm.etools.iseries.debug.internal.ui.sep.actions.PhantomServiceEntryPointOpenLaunchConfigurationAction$1.run(PhantomServiceEntryPointOpenLaunchConfigurationAction.java:45)
at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4821)
at com.ibm.etools.iseries.debug.internal.ui.sep.actions.PhantomServiceEntryPointOpenLaunchConfigurationAction.doAction(PhantomServiceEntryPointOpenLaunchConfigurationAction.java:37)
at com.ibm.etools.iseries.debug.internal.ui.sep.actions.PhantomServiceEntryPointBaseAction.run(PhantomServiceEntryPointBaseAction.java:80)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$$Lambda$36.000000001A8BD170.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)

Session Data:
eclipse.buildId=unknown
java.fullversion=8.0.5.35 - pwa6480sr5fp35-20190418_01(SR5 FP35) JRE 1.8.0 Windows 10 amd64-64-Bit Compressed References 20190417_414854 (JIT enabled, AOT enabled)
OpenJ9 - 777635f
OMR - 16b77d7
IBM - 72459d3
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.ibm.rational.developer.ibmi.product.ide


Any ideas?

Thanks,
Mitch
--
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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