After you step into the service program, (on the top right corner of your
debug perspective), click on the "Programs" tab to switch to Programs view.
There should be a list of program/service program under debug.
Check the full path of the service program to see if that is the one you
want to debug. It could be possible that when you invoked your store
procedure from operation navigator, it picked up a different version of
service program.
Thanks,
Xuan Chen, Problem Determination Tools for IBM i
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
<RDutil@xxxxxxxx>
Sent by:
wdsci-l-bounces@m To
idrange.com <wdsci-l@xxxxxxxxxxxx>
cc
07/02/2012 01:19 Subject
PM Re: [WDSCI-L] Debugging Service
Program with WDSCi 7.0
Please respond to
Rational
Developer for IBM
i / Websphere
Development
Studio Client
for System i &
iSeries
<wdsci-l@midrange
.com>
Thanks for your reply, Paul. I just wanted to respond to your
suggestions/questions.
1.) I did specify the correct library (as opposed to *LIBL) when adding my
SEP. I'm using my development library.
2.) My user profile is specified on the SEP's for both the stored procedure
and the service program. As I mentioned previously, the program halts on
my breakpoint in the stored procedure. However, it does not do the same
for the service program. So, I don't think that is the problem.
3.) Now, I did get an interesting result when breaking on a source line in
the stored procedure and 'stepping into' the subprocedure from the service
program. It did step into the service program, however the WDSCi source
debugger opened up a new source member. Instead of showing me the source
from the service program (DRGDAYSRV.SQLRPGLE), it opened up this new source
member titled 'DRGDAYSRV.STATEMENT' that consisted of lines like this "241
*STMT:971 HYDASBIDREVDAYS". I'm guessing this is some kind of list of
SQL statements and their line numbers from the service program. The
service program is a mix of RPGILE code and SQL statements. It never broke
on any of the RPGILE code in the program, so I just let the program resume
and complete.
I have no idea what to make of my result when 'stepping into' the
subprocedure from the service program. Any ideas out there?
Thank you,
Ray Dutil
IT Department
Great Lakes Dredge and Dock Co., LLC
Office: 630-574-2552
RDutil@xxxxxxxx
message: 3
date: Tue, 7 Feb 2012 08:48:44 +0000
from: Paul Bailey <PaulBailey@xxxxxxxxxx>
subject: Re: [WDSCI-L] Debugging Service Program with WDSCi 7.0
I haven't used WDSC 7 or debugged service programs for a while, but I do
remember one or two minor d'oh moments that you also might be suffering
with.
When you set the SEP do you use *LIBL or do you specify which library the
service program is running in? If you select *LIBL, is your library list in
WDSC set correctly to include the same service program object that the
stored procedure (thru' navigator) will be finding?
There is a user profile entry on the SEP form, so what do you put in there?
You are meant to put the user that will be running the service program,
which is not always your user profile in the case of stored
procedure-called programs. I found debugging the calling stored procedure
and then looking at the jobs which have locks on your user profile is the
best way to find out which user is running the stored procedure.
Lastly, did you "step into" the subprocedures when you debugged the stored
procedure program? That may be a work around for you if you haven't tried
it already.
I did do this a lot some years ago, so I'm sorry I can't remember more
details of problems I had. (There were several difficulties, but trial and
error eventually got me there.)
-Paul.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of RDutil@xxxxxxxx
Sent: 07 February 2012 02:20
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Debugging Service Program with WDSCi 7.0
I am working with WDSCi 7.0 and our IBM i is V5R4 still. Are there any
known issues with debugging service programs using this combination that
anyone is aware of? I have just recently learned how to use the tool to
debug standard RPGILE programs, and this is my first attempt at debugging
service program. I am also fairly new to creating service programs. So,
it's very probable that I am just not doing things properly.
I have an RPGILE stored procedure program (S_DLYSUM) that is invoking a
couple of subprocedures from a service program. I compiled the service
program (DRGDAYSRV) as a *MODULE object type making sure the debug *source
option was used. Then I created the service program and compiled my stored
procedure program as well as creating the stored procedure (in that order).
I started up the debug server. Then, I added the service entry point on
the service program. I'm not sure if the correct way to do that is to
specify the module and procedure from the service program I want to debug,
or to leave those two options as *ALL. I've tried it both ways with no
results.
Then I invoke the stored procedure from Operations Navigator. But, the
execution never halts when it hits the service program. I also added a
service entry point on the stored procedure to make sure that I was getting
to section of code where the subprocedure from the service program would be
invoked. The stored procedure breaks right at the point I was expecting.
So, my questions are the following. Is there a known issue with WDSCi 7.0
in debugging service programs? Did I make any obvious mistakes creating my
service program? Or did I make any obvious mistakes in setting up the
service entry point on the service program? Is there anything else I might
be overlooking?
Thanks for your time,
Ray Dutil
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.
Scanned by MailDefender - managed email security from intY -
www.maildefender.net
Important
This email transmission and any files with it are strictly
confidential to the intended recipient and may be legally
privileged. Any views or opinions presented are solely
those of the author and do not necessarily represent those
of BHSF. If you are not the intended recipient, you must
not copy, disclose or distribute its contents in any way.
If you have received this e-mail in error, please notify
the sender and delete the e-mail from your system.
We have taken steps to ensure this e-mail and attachments
are free from any virus but do not accept any
responsibility once this e-mail has been transmitted. You
should scan any attachments for viruses.
No contract may be concluded on behalf of BHSF Limited by
e-mail.
Registered Office:
BHSF Limited
Gamgee House, 2 Darnley Road, Birmingham B16 8TE.
www.bhsf.co.uk
Registered in England number 35500.
BHSF is authorised and regulated by the Financial Services
Authority.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.
midrange.com
