Re: SEP Debugger not finding the right source -- WDSCI-L

I have discovered just today that I am having the same problem now
that I was helping the coworker with last week. Mine is a totally
different program object.

In my case, the STRDBG is using the Listing view.

I did confirm that the source for the module for my service program is
the one I was manually selecting in WDSc.

Kyle

On 9/1/06, Xuan Chen <xuanchen@xxxxxxxxxx> wrote:

Kyle,

When you use STRDBG to debug your application, which view did it use,
Source view or Listing view (Listing view also has a statement number in
the view)?

Please use DSPPGM command to look into the module information of your
service program, and check what is its source location.  And please check
if that source location is the one you opened.

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx





             "Kyle Collie"
             <kcollie@xxxxxxxx
             m>                                                         To
             Sent by:                  "Websphere Development Studio
             wdsci-l-bounces@m         Client for iSeries"
             idrange.com               <wdsci-l@xxxxxxxxxxxx>
                                                                        cc

             09/01/2006 12:32                                      Subject
             PM                        [WDSCI-L] SEP Debugger not finding
                                       the right source

             Please respond to
                 Websphere
                Development
             Studio Client for
                  iSeries
             <wdsci-l@midrange
                   .com>






I have spent a good part of this morning helping a co-worker debug a
series of programs and subprocedures in service programs. We set a SEP
on the entry program and call it. All is good at this point. We step
into the code. Still good until we get to the first call to a
subprocedure. When we step into it, we get a screen telling us that
the source cannot be found. It has three buttons. If we select the
button for the compile listing, it works fine, but each time through
in debug is the same way. If we select the button to find the source
and browse to the correct, modified source in her development library,
It opens the source but always enters the subprocedure source at the
wrong line. Actually, it is not even in the correct subprocedure.

We have cleared the WDSc cache, removed all SEP's, stopped and
restarted the debug server and recompiled / recreated all programs and
service programs, including the modules, after confirming the
development library is at the top of the library list.

Also, we can debug this same series of programs from the GS (STRDBG)
without any problems.

What am I missing?

Kyle
--
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.