Re: sep only breaks on the first call to program

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 Response inline

On 10/20/2010 2:37 AM, David FOXWELL wrote:
> -snip-
> > To debug the calling program (which sounds like it's OPM,
> > you'll have to set up a run configuration for an 'iSeries Debug Job.'
> What's that? I have a command ILEEXC with program ILEEXCR (thanks Joe) that I used along time ago when sep worked on V6 for debugging OPM.
I don't understand - SEP has never been usable on OPM programs. It's and 
ILE thing only.

Now run configs are not for the faint of heart, in my opinion - they 
have always defeated me. That was why I went to using the graphical 
iSeries debugger that is included with the Java Toolkit (jt400). I just 
last week saw how easy using SEPs is now in RDp. Of course, I rarely use 
OPM programs now in new work.
> A big problem for me with SEP is having to set the sep itself. It's just so much quicker to use strdbg.
This doesn't make sense either - I've not seen anything easier to do 
than to set a SEP now in RDp - right-click the program or service 
program in RSE, then run it. If there are no display operations, run it 
in batch.

The main reason (as far as I can tell) for SEPs was to make it easy to 
debug jobs other than your own - batch jobs are an example of this, 
server jobs are another really good one. Things like ODBC jobs. I might 
agree that STRDBG is pretty easy for something running in your own 
interactive job. There are still things you can get in the graphical 
debugger that are not to be found in STRDBG - such as "run to location" 
- I love that feature.

Now if you want to use SEPs in STRDBG, you are in for a somewhat tedious 
exercise. I've done it a lot, especially on customer machines when doing 
custom development there. Again, if I can't use RDp there.

Regards
Vern