Is it possible someone else has already set the SEP on the program?
What you can try is to stop the debug server (ENDDBGSVR) and start the
debug server again (STRDBGSVR) and try to set SEP again.
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
David Gibbs <david@xxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
29/09/2009 05:24 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject
[WDSCI-L] Can't set service entry point?
Folks:
This is being cross-posted to WDSCI-L and MIDRANGE-L, as I'm not 100% sure
it's directly related to RDI.
I'm encountering a problem trying to setup a service entry point debug on
a service program with multiple modules.
I've tried debugging the service program using *ALL modules and *ALL
procedures ... and SOME of the procedures will hit a debug breakpoint, but
others wont.
When I try to set a break point on a specific procedure in a specific
module, I get the following error in RDI 7.5:
DBGB0020E: Cannot set service entry point for service program <srvpgm>,
module <mod>, procedure <proc>
Similarly, if I try to set a breakpoint on *ALL procedures in a single
module, I get this error: DBGB0018E Cannot set service entry point for
service program <srvpgm>, module <mod>
I've tried doing a STRSRVJOB / STRDBG on the job & service program (very
hard to catch it, as it's being invoked from Java), but the breakpoint
never hits.
Another (possible) factor ... this service program has been moved from one
system to another (via SAVOBJ to a save file and FTP) ... the service
program SEEMS to debug fine on the system it was compiled on ... but not
on the other system. Both systems are V5R4.
Any thoughts?
david
midrange.com
