Re: Can't set service entry point?

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Service entry point is not the same as the program entry point - the 
latter is only in programs. The former can be set on any executable 
statement.

I think!
Vern

steelville wrote:
> David,
>
> Maybe I'm missing something, because I'm not real familiar with 
> WebSphere yet, though I'm using it, but service programs don't have an 
> entry point do they?
>
> Are you using STRDBG on an actual program that uses the service program? 
> I've never tried to debug procedures in a service program except where 
> the STRDBG was on an actual program.
>
> --Alan
>
>
> David Gibbs wrote:
>   
> > 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
> >
> >   
> >