HP NonStop SQL/MX Messages Manual page 349

Trigger, UDR Server, and Language Manager
Messages (11000 through 11399)
Recovery. Either correct the CALL statement so that the null value is not used, or
change the Java data type of the parameter to the corresponding Java wrapper type.
For example, if the Java data type is integer, change it to java.lang.Integer. Note
that to change the Java data type, the procedure must be dropped and re-created.
SQL 11216
11216 Java execution: Data overflow occurred while retrieving
data at parameter position parameter number.
Cause. During execution of a CALL statement, numeric or string overflow occurred
while processing the stored procedure output value returned in parameter parameter
number.
Effect. The operation fails.
Recovery. Increase the field size of the SQL data type for the specified parameter.
SQL 11217
11217 Java execution: Data overflow occurred while retrieving
data at parameter position parameter number. Value is
truncated.
Cause. During execution of a CALL statement, numeric or string overflow occurred
while processing the stored procedure output value returned in parameter parameter
number.
Effect. None; this is a warning message.
Recovery. Increase the field size of the SQL data type for the specified parameter.
SQL 11218
11218 A Java method completed with an uncaught Java
exception. Details: string.
Cause. During execution of a CALL statement, a Java exception was thrown.
Effect. The operation fails.
Recovery. Review the Java method. Determine whether it is appropriate in your
application for this exception to be thrown or whether it should be caught and handled
by your user-defined routine. Retry the SQL/MX statement.
HP NonStop SQL/MX Messages Manual—640324-001
13 -19