I have worked with stored procedure calls from Impromptu on both Oracle and MS SQL for about three years. I have the stored procedures populate real reporting tables, so I have avoided the problems in the new release supporting a result set. Through Imp ver 5 the SP call [Execute] in the macro language worked relatively well (you sometimes had to add extra null values to passed variables i.e. FY+"", lcInt+0). The "new" method (I used it occasionally in prior versions before it was fully supported) is to embed your SQL call in the SQL tab of Query|Profile on the menu. For SQL Server it works as advertised. For Oracle, I found I had to enclose the SP call in a SQL 'snippet' as it:
Call BEGIN SP_NAME('?Prompt1?','?Prompt2'); End;
This would work most of the time, but I found that the SP was not always getting the variable data correctly. On both platforms I wound up using an ODBC call via CognosScript.
i.e.:
Query1 = "BEGIN USG_MOD_CLS('"+sFyCd+"',"+Cstr(iPdNo)+",'"+sLike+"','"+sAction+"','"+sModBy+"'); END;"
retcode = SQLExecQuery(connection,Query1)
This also does not handle returned OUTPUT parameters from the procedure, but I put the return data into a control table and read it via ODBC.
Hope this helps anyone else that has struggled with stored procedures in Impromptu.
Dave Griffin