RE: MIDRANGE-L Digest, Vol 6, Issue 1954

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

<snip #1>

When my sql procedure bombs the system does not tell me the stmt
number where the error occured.  When testing sql procedures from
STRSQL that return result sets I have to signoff and signon after
every test because otherwise the cursor stays open.

</snip #1>

I recommend using Run SQL Scripts to test stored procedures that return
result sets.  You can see the data and I haven't run into issues with
cursors staying open.

<snip #2>

debugging an sql procedure is barely functional. ( have to know the C
structure my variables are declared in. cant use F10 to step to the next
stmt. )

</snip #2>

As for debugging, I went through the same pains, until I started using
visual iSeries System Debugger built into Run SQL Scripts.  If you compile
your SQL PL stored procedures with option *DBGVIEW, you can actually step
through the SQL statements themselves, without looking at the ugly,
generated C code (unless you choose to do so, there is an option for it).
Once in Run SQL Scripts just hit Ctrl-D or click on Run->Debugger to invoke
it.

<snip #3>

In RPG you cant read the result set.

</snip #3>

Yes you can, using CLI.  It's not hard to use CLI if you've ever had to code
any ODBC code on other platforms.

With the V5R3 CL enhancements you can call a stored procedures in CL using
CLI as well.  I've written a small sample of CL/CLI combo in of our
newsletter articles.  That said, I do NOT encourage using CLI in CL... it's
ugly :)

Elvis


RPG & DB2 Summit | Minneapolis | October 1-4
Mike Cain - DB2 for i5/OS Temporary Indexes - The Good, The Bad, The Ugly
October 16 
2007 System i Fall Technical Conference | Orlando | November 4-7
Celebrating 10-Years of SQL Performance Excellence on IBM System i, eServer
iSeries and the server affectionately known as the AS/400 

-----Original Message-----
On Behalf Of Steve Richterore money and more people?

there are plenty of needed improvements to i5/os that IBM is not
willing do.  I am doing SQL procedure work lately on v5r4.  I cant
call an sql procedure directly from CL with parameters.  debugging an
sql procedure is barely functional. ( have to know the C structure my
variables are declared in. cant use F10 to step to the next stmt. )
When my sql procedure bombs the system does not tell me the stmt
number where the error occured.  When testing sql procedures from
STRSQL that return result sets I have to signoff and signon after
every test because otherwise the cursor stays open.   With LINQ in
.NET 3.0 you can call an sql procedure and join the result set to a
database table.  In RPG you cant read the result set.

-Steve