DB2 MQ Listener error sql0440

Published 04 February 2004

Authors: Chuck Ballard


We successfully added a Java stored procedure to the DB2 MQ Listener configuration. However, when we executed the procedure, it ended with error sql0440.


We created a Java stored procedure for DB2 MQ Listener using the DB2 Development Center, and it ran without error. The task of the stored procedure is to parse the message passed to it by the DB2 Listener and update the data warehouse. To enable this, we used an input parameter, inMsg, that was defined for the stored procedure.

We successfully added this to the DB2 MQ Listener configuration. However, when we ran DB2 MQ Listener we received an sql0440 error message.

There are several situations where you could receive this message. In our situation it was because we did not specify an output parameter. We did not originally supply one because we did not require one. However, DB2 MQ Listener uses a fixed format and so requires an output parameter, and it requires the name of outMsg. The following is the stored procedure format required by DB2 MQ Listener:

Schema.proc(in inMsg inMsgType, out outMsg outMsgType)

The variables inMsgType and outMsgType are discovered at startup time, and the datatypes varchar, CLOBand BLOBare all supported.

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Follow IBM Redbooks

Follow IBM Redbooks