Re: [WDSCI-L] Debugging embedded SQL & Sql statements

[rob@xxxxxxxxx]

Try this:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/info/rzala/rzalafinder.htm

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





infosys5@xxxxxxx 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
10/26/2004 09:58 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Fax to

Subject
[WDSCI-L] Debugging embedded SQL  & Sql statements






Group, 
I'm testing the WDSC interactive debugger with a program that has embedded 

sql statements - (working from an example for the embedded sql),  here are 

my questions: 

1) When debugging in WDSC with embedded sql - I haven't found a way to 
view the actual statement. 
2)  When debugging from WDSC, without me having a breakpoint on the 
embedded sql statement, the debugger stops - I have to select "resume" 
each time to resume the debugger. 
3)  And where can a find a reference that displays all the sql status 
codes?  After I do a "Fetch from MyCursor" statement, I am checking the 
sqlstt code for 01503, this works until I come to status code "22008" - 
it's time I figure out what all these codes mean?? 

Thanks for any help. 
Diane Mueller 
_______________________________________________
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.