Re: Debug doesn't break when called second time form samejob

Michael,

Good idea, but won't work in this case.  The calling program is third
party software for which we do not have the source.  The Order/Entry
software provides "exit points" we can use to set up programs we want to
run.  In this case, the software allows us to use our own pick ticket
printing program.  But the software calls our program several times,
once for each different type of order (drop ship, rush, etc). All from
the same submitted job. 

Even so, we have a workaround, which is the green screen debugger.  I
just thought that if the green screen debugger can do it, our friends on
the WDSC team would want to make sure their debugger can do it better
;->

Greg

|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
|Behalf Of MichaelQuigley@xxxxxxxxxx
|Sent: Monday, June 05, 2006 11:34 AM
|To: wdsci-l@xxxxxxxxxxxx
|Subject: Re: [WDSCI-L] Debug doesn't break when called second time form
|samejob
|
|Greg & Xuan,
|
|How we get around this is to debug the program that calls the one you
want
|to debug.  The debug session terminates the first time the program
|completes running.  I prefer debugging with Service Entry Points, but
in
|this case, I set up the debug the old fashioned way and add both
programs
|to the debug configuration.  Then you can set breakpoints, etc. in the
|'called' program and it will stop every time.
|
|HTH,
|Michael Quigley
|AS/400 Programming Coordinator
|The Way International
|www.TheWay.org
|