We're not doing a lot of SQL here for new database
stuff, but we are building a lot of stored procedures
for client queries and database updates from the web.
So my interest in this product was more specific to
stored procedures, however I'm having some
difficulties. I tried a JDBC connection to my 400
which works fine. The object list shows all my
procedures in my selected schema, when I click on a
procedure object the work panel shows an Info and
Column tabs, the Column tab however, doesn't show any
procedure parameter information. When I use an ODBC
connection instead, then I get all the parameter info
in the Column tab. I believe I'm using a current
version of the JT400.jar. I'm not an expert in any of
this stuff, but I believe I have everything configured
correctly. I was wondering if you've experienced this
limitation with the JDBC connection.
What are the advantages or disadvantages of
using a JDBC connection over the ODBC connection?
My second biggest problem is the SQL editor doesn't
like running our stored procedure scripts. These
scripts compile just fine using IBM's OPSNAV
(Operations Navigator) RUNSQLSTM processor in program
CWBUNDBS.EXE. Squirrel has difficulty parsing the
multiple SQL statements that are typical of a stored
procedure created via OPSNAV. Even if I try to
highlight and run the specific create procedure
statement portion, it fails on invalid
END_OF_STATEMENT errors . I've tried toggling on and
off the ; delimiter but still can't get the procedure
created through the Squirrel editor.
What are your experiences with this? Any workarounds
or special techniques I should be using? Also does
Squirrel provide a way to test stored procedures with
INOUT or OUT parameters? I don't have the client
language skills to develop something quick to test
these kinds of stored procedures before I hand them
off to our Java developers for use. Thanks for you
time. Attached is a sample of a typical DB2400 stored
procedure script file.