Re: Debug doesn't break when called second timeform samejob

Xuan,

I think you are correct.  I've got a plate full right now, but I'll try
to test the SEP scenario on the green screen later today or tomorrow.  I
was not using SEP on the green screen before (didn't know it was
possible), so what you say makes a lot of sense.

Thanks

Greg

|-----Original Message-----
|From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
|Behalf Of Xuan Chen
|Sent: Monday, June 05, 2006 2:01 PM
|To: Websphere Development Studio Client for iSeries
|Subject: Re: [WDSCI-L] Debug doesn't break when called second timeform
|samejob
|
|Hi Greg,
|
|Could you please describe what green screen debugger scenario you used
in
|more details?  From your posting before, I don't think you used service
|entry point feature available in green screen debugger.  Could you
please
|try the following system debugger SEP scenario?
|
|5250 session I
|   Use command:
|   STRDBG libname/progname
|   to start the a debug session.
|   Use command:
|   SBREAK line#         (where line# is the first executable line of
this
|   program)
|   to set a service entry point on the first executable line of this
|   program
|
|Run your application like you normally did.
|
|5250 session I
|You should receive a message telling you that a service entry point is
hit.
|Press F1 on that message, and you could see the instruction of how to
debug
|your application.
|
|5250 session II (another green screen session)
|   Use command:
|   STRSRVJOB
|   to put the job described in the message to service (like the command
|   described in the F1 help).
|   Use command
|   STRDBG libname/progname
|   to start debug this program on the job it is running now.
|
|5250 session I
|Press Enter to the message to release the job
|
|5250 session II
|The program should stop at the first executable line.
|Run your program into complete in this debug session (or could you
actually
|do this?)
|
|Did you see that you get a message in session 1 again (that means a SEP
is
|hit)?  Since I did not have your application setup here, I used a
normal
|5250 session trying to mimic your scenario, and did not see the SEP hit
the
|second time.  The reason is that SEP is only for any job which is not
under
|debug yet.  And in this case of green screen debugger, this job is
already
|been debug, so SEP will not be hit.
|
|
|For WDSc debugger, it is a bit different.  My guessing here is that the
|default behaviour for using service entry point to invoke a debug
session
|is to specify terminate debugger when program is completed.  While the
|debugger is busy cleaning up when a program is complete running
(undebug
|the program), before it actually finished, the program got called
again.
|At this time, since debugger has not undebugged the job yet, the job
still
|considered under debug, so SEP will not get notified (SEP only for job
not
|currently under debug yet).
|
|I think for your specific scenario, you want  the debug session started
by
|SEP do not check "specified terminate debugger when program is
completed",
|so that you could set normal source breakpoint.  But unfortunately, for
|debugger invoked by SEP, this option is not available.  I will add
|"providing a way to display launch configuration dialog even for
session
|started by SEP" into the list of limitation we will going to address
for
|our next release.
|
|Thanks,
|
|Xuan Chen,  Problem Determination Tools for iSeries
|(905) 413-3769 T/L 969-3769
|xuanchen@xxxxxxxxxx
|
|
|
|
|
|             "Fleming, Greg
|             \(ED\)"
|             <GFLEMING@evergla
To
|             desdirect.com>            "Websphere Development Studio
|             Sent by:                  Client for iSeries"
|             wdsci-l-bounces@m         <wdsci-l@xxxxxxxxxxxx>
|             idrange.com
cc
|
|
Subject
|             06/05/2006 11:45          Re: [WDSCI-L] Debug doesn't
break
|             AM                        when called second time form
|                                       samejob
|
|             Please respond to
|                 Websphere
|                Development
|             Studio Client for
|                  iSeries
|             <wdsci-l@midrange
|                   .com>
|
|
|
|
|
|
|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
||
|
|--
|This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
|mailing list
|To post a message email: WDSCI-L@xxxxxxxxxxxx
|To subscribe, unsubscribe, or change list options,
|visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
|or email: WDSCI-L-request@xxxxxxxxxxxx
|Before posting, please take a moment to review the archives
|at http://archive.midrange.com/wdsci-l.
|
|
|--
|This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
|mailing list
|To post a message email: WDSCI-L@xxxxxxxxxxxx
|To subscribe, unsubscribe, or change list options,
|visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
|or email: WDSCI-L-request@xxxxxxxxxxxx
|Before posting, please take a moment to review the archives
|at http://archive.midrange.com/wdsci-l.