Stored Procedure problems with Sybase

AQT sometimes has trouble running Sybase stored procedures, depending on:

• the version of Sybase you are accessing
• the ODBC driver you are using
• whether the ODBC stored-procedures have been implemented correctly in the Sybase Server

The problems AQT has with stored procedure are related to the way AQT determines the parameters for your stored procedure. To get this information AQT uses the ODBC function SQLProcedureColumns. AQT is dependent on this function to work correctly, however for some Sybase implementations this function gives wildly incorrect information. Even on systems where this function works most of the time, it occasionally gives the wrong information.

The Sybase ODBC driver implements the SQLProcedureColumns function by a stored procedure which gets installed on your Sybase Server. This procedure will be installed by your system administrator as part of the setup of the ODBC driver software. If you are having trouble with Run Procedures, you could check with your system administrator that this procedure has been set up correctly, and is the correct version for your ODBC driver.

AQT offers two mechanisms for dealing with these problems:

• in the Run Procedure window you can change the parameter type (IN/OUT/INOUT) if it appears to be incorrect (the parameter type is main thing the Sybase ODBC Driver seems to get wrong).
• if your parameters are wildly inaccurate, you can specify that SQLProcedureColumns is not used; instead an AQT query is used to obtain the parameter info. To specify this, you need to edit your sybasee.cfg (or sybasee1103.cfg) file to have a line with ‘aqtprocparms (note the single quote at the start) in the file.

If you use aqtprocparms, AQT cannot determine the parameter type so it will default to IN. You will need to change this manually to the correct type.