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



You can jump into an already running program, you just can't use a SEP do
so.

SEP = Service Entry Point, "entry" being the keyword. They are invoked
when the program/module is entered.

To debug a running program, follow the steps Jon outlined.

Charles

On Wed, Feb 18, 2015 at 10:48 AM, Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I had the user exit the program and restart - as soon as the user exited
and re-started the program, debug was invoked in RDi. I did not have to
have to use the pull-down menu you mentioned below.

Then when I was finished debugging, I ended the SEP and cleared the
breakpoints... but for some reason, that didn't really end it. RDi jumped
right back into debug when the user encountered that line of code again. I
had the user back out of the program, and received a message RDi that the
job had terminated.

This seems VERY disconnected... according to my RDi screens, I was no
longer servicing a job and was no longer debugging... yet I was.

If I can't "jump into" an already running program (like I can with
STRSRVJOB and STRDBG), the RDi debug is inferior in that aspect. I use
that all the time to look at issues that are not easily recreated.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, February 18, 2015 10:08 AM
To: Wdsci-L
Subject: Re: [WDSCI-L] Set Service Entry Point for another user

The way to do that kind of debug is to attach the debugger to the job in
question. You do this via the debug pull down in the workbench and then I
would normally use the Debug Configurations and then select Debug Job. In
the dialog you can select the user name to help filter the jobs and then
select the one you want.

An SEP (no matter what user) is only triggered when the program starts up
- if the program is already active it will have no effect.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 18, 2015, at 9:49 AM, Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I'm missing something... I would like to debug another user's running
program. On green screen, I used to STRSRVJOB then STRDBG.

I thought that RDi would allow me to set a service entry point,
specifying the program and the user by username. However this doesn't seem
to be working. My user profile has QSECOFR authority.

Does the user have to exit and re-enter the program?
Greg
--
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.


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.