JDBC CallableStatement, plain Program Call, and output parameters...

We have a single point of entry for our legacy system - an OPM Cobol program - which I have a functional ProgramCall approach working. (Five arguments, where two of them contain return values and I need to have an initial CHGLIBL call).

I am now looking at using pooled connections, and I have an AS400ConnectionPool approach working (which saves 0.3 seconds in average), but I would like to see how a JDBC Stored Procedure behaves as these pooling mechanisms are highly tuned.

I can invoke a program without arguments with

CallableStatement cs = c.prepareCall("call FOOBAR/dummy()");
cs.execute();

and I can invoke my program with "call FOOBAR/myprog('1','2','3','4','5')" as it takes five arguments (if there are less I get a MCH0801)

Unfortunately I need the output values, so I try with a c.prepareCall("call FOOBAR/myprog(?,?,?,?,?)") which immediately fails with "[SQL0204] MYPROG i FOOBAR af typen *N er ikke fundet," (complains that the program of type *N has not been found).

I have looked around and it appears that for this to work an actual stored procedure must be defined in the database, and not just the program to call. The wording in rzahh.pdf is "The stored procedure being called must already be stored in the database".

The question is then, does "the stored procedure" refer to an actual stored procedure created with "CREATE PROCEDURE ... etc..." or can it just shortcut to a program found in a library?

Thanks for any answers :)