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



SEP debug is the way to go... If the program you are testing must be run from a 5250 session, just register your Service Entry Point for the program object, and specify the user that will be executing the program (the logged in 5250 user). When you call the program from the 5250 session, the SEP debug catches the invocation and starts the debug session in RSE. I've not had a reason to use anything other than SEP debug since I tried it...

-Eric DeLong

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Wednesday, May 15, 2013 9:49 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: [WDSCI-L] Debug As > Interactive Error CPD0160

Attempting to start Debug from RDP 8.0.3

From a 5250 session: I start the debugger server using STRDBGSVR

In LPEX editor I set breakpoints

From Remote Systems view I right-click the program object,
and select Debug As > Interactive

I get a dialog window:
No interactive job associated with this connection.

From a 5250 session: I enter STRRSESVR NAME(myConnection)

This raises error CPD0160 - Program QRSEMAIN not found in library QDEVTOOLS

I see in Midrange archives that we need: 5722WDS (Option 50, Feature 5050)

Is there anything else I should ask my operations manager to install ?


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.