I've been smashing my mind from this for some time now.

I'm using iBatis with my JAVA code to operate Saved Proc dwelling in Sybase DB.

Saved procedure is expecting some parameters. couple of seem to be declared as VARCHAR (6)

So during my iBatis mapping used to do the next for individuals parameters.

<parameter property="searchUserId" jdbcType="String" javaType="java.lang.String" mode="IN"/>

However, after i do that I recieve the next error.

--- Check the statement (update procedure failed).  
--- Cause: java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0SL: Unsupported SQL type 1111.
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0SL: Unsupported SQL type 1111.

And So I transformed my mapping to following:

<parameter property="searchUserId" jdbcType="VARCHAR" javaType="java.lang.String" mode="IN"/>

which eliminated the mistake above, however, the parameter searchUserId gets worth of null passed in to the SP. I understand without a doubt that from the java code I'm not passing null.

Has someone faced this problem? what must i change my mapping to??

Your parameter element looks ok, following the switch to use VARCHAR as jdbcType. Would you range from the relaxation from the parameter element and also the procedure element in the mapping file, and also the code that produces the parameter map and calls the query?

It may be something simple just like a typo when creating the map passed in to the query (a minimum of this is the type of mistake I'd make -- I understand I have been sporadic about benefiting "userId" while using the Ibatis).