IDM 3.5 Engine2 patch on SLES 10, eDir 8.8 SP1, FT2.

JDBC 3.5 (with the latest .2 patch).

Have a DB (Oracle) that provides a Stored procedure for getting the next
value of the PK_SEQUENCE to use for inserting a new user.

Problem is the stored procedure expects an IN, OUT format. I.e. Pass it
the Column name to get the next value for, and it will return it in a
variable. As opposed to returning the value as a return code (I guess).

How do I handle the syntax for this case?

I have Sub Options set with
Generation Retrieval method set to subscription event (default)
retrieval timing set to Before row insertion (default)
Method and timing set to
IDM.CLIENTS("_SMSYSADMIN_.SMSysGetNextRecNumDB(PK_ SEQUENCE)")

The SMSysGetNextRecNumDB is the one expecting a second variable.

Any suggestions? Getting some amusing errors, which point me back at
this issue.

Like:

<status level="warning">The number of parameters declared for stored
procedure '_SMSYSADMIN_.SMSYSGETNEXTRECNUMDB' does not match the number
of passed parameters. There is/are 2 declared parameter(s) and 1 passed
parameter(s).</status>

<status level="warning">Parameter type mismatch detected in stored
procedure '_SMSYSADMIN_.SMSYSGETNEXTRECNUMDB'. Parameter 'VALNAME' at
index 1 is of type 'IN' and field 'IDM.CLIENTS.PK_SEQUENCE' passed to it
is of type 'INOUT'.</status>

<status level="warning">Parameter SQL type mismatch detected in stored
procedure '_SMSYSADMIN_.SMSYSGETNEXTRECNUMDB'. Parameter 'VALNAME' at
index 1 is of type 'java.sql.Types.OTHER' and field
'IDM.CLIENTS.PK_SEQUENCE' passed to it is of type
'java.sql.Types.DECIMAL'.</status>