HP NonStop SQL/MX Messages Manual page 353

Trigger, UDR Server, and Language Manager
Messages (11000 through 11399)
SQL 11229
11229 The Java Virtual Machine produced the following output:
jvm-terminal-output.
Where jvm-terminal-output is diagnostic information generated by the Java
Virtual Machine (JVM) and written to the terminal of an SQL/MX UDR server process.
Cause. The JVM in the SQL/MX UDR server could be successfully started and the
jvm-terminal-output text was captured. See also the errors that accompany this
message for more information.
Effect. The operation fails.
Recovery. Perform whatever corrective action is required to eliminate the JVM startup
errors. Stop and restart the session and retry the SQL/MX statement.
SQL 11230
11230 Multiple compatible methods named method-name were
found in class class-name.
Where method-name is the Java method name specified in the EXTERNAL NAME
clause of a CREATE PROCEDURE statement.
Where class-name is the Java class name specified in the EXTERNAL NAME clause
of a CREATE PROCEDURE statement.
Cause. During the execution of a CREATE PROCEDURE statement, multiple SPJ
methods were found in the specified Java class. Each SPJ method was named
class-name.method-name and had a Java type signature matching the declared
SQL parameter types. If the DYNAMIC RESULT SETS clause specified a value
greater than zero, each method also had one or more trailing
java.sql.ResultSet[] parameters.
Effect. The operation fails.
Recovery. You have two options. Ensure that exactly one SPJ method with the
required attributes exists in the specified class file, or direct SQL/MX to choose a
specific SPJ method by specifying that method's Java type signature in the
EXTERNAL NAME clause, and then resubmit.
SQL 11231
11231 The method method-name(signature) was not found in or
is not a public method of class-name.
Where signature is a Java type signature.
HP NonStop SQL/MX Messages Manual—640324-001
13 -23