Re: Set Service Entry Point for another user

Ahhh... I understand the difference now. So I'm not completely following
you when you say... " 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."

Is there a document you could point me to that describes or shows how to
do this?

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

You said you wanted to connect to the existing job ... so that's what I
described. You could have "jumped into" the stalled program using the
technique I described.

SEP stands for Service _Entry_ Point. Program entry so it wan't the tool
for the job you described, but as you noted it was fired when the program
was restarted.

I have not experienced the problem you describe - it is possibly
Activation Group related. Did you try having the User sign-off? Have you
checked via Verify Connection if your PTFs are up to date? If neither of
those actions reveals anything then I suggest that you open an APAR with
IBM.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

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

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