Re: WDSCI-L Digest, Vol 6, Issue 130

Jerry,

Another thing you could check is to make sure there's not another copy of
the program in a different library which is getting run in the target job.
That's burned me a few times.

Michael Quigley
AS/400 Programming Section
The Way International
www.TheWay.org

wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/19/2008 09:55:50 PM:

date: Tue, 19 Feb 2008 21:58:54 -0500
from: Xuan Chen <xuanchen@xxxxxxxxxx>
subject: Re: [WDSCI-L] SEP debug won't start up

Is the user ID used to set SEP is the same as the user id that ran the
program?

Thanks,

Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx





"Gerald Kern" <gkern@xxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/19/2008 08:49 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] SEP debug won't start up






R7.0.0.4, all the latest patches. V5R4.

I have a program newly compiled (w/ debug view = *source) so the date

last

used is blank and days used count is zero.

I set a service entry point, run the program that should call the newly
compiled program, but the SEP debug session never starts.

Preferences are set to update prod files. Check the attributes of the
object
and can see date last used now updated and days used count at 1.

Rebooted pc & tried again no luck. No signs of profile swapping.

How do I determine why the debug session isn't starting up? (The debug
server is started - otherwise I couldn't set the SEP.)

Thanks for any ideas!

Regards, Jerry