SQL/MX 3.2 Guide to Stored Procedures in Java (H06.25+, J06.14+)

Getting Started
HP NonStop SQL/MX Release 3.2 Guide to Stored Procedures in Java—691166-001
2-11
Using Multiple UDR_JAVA_OPTIONS Settings in
One Application
If you specify different UDR_JAVA_OPTIONS settings in the same application, be
aware of the Performance Considerations of Using Multiple UDR_JAVA_OPTIONS
Settings on page 2-11.
Determining the Uniqueness of UDR_JAVA_OPTIONS
Settings
Two or more UDR_JAVA_OPTIONS settings are considered to be different when their
character string literals do not match during a case-sensitive string comparison. The
case, white space, and order in which the options appear within each character string
literal must be the same for UDR_JAVA_OPTIONS settings to be considered identical.
For example, these UDR_JAVA_OPTIONS settings in separate CONTROL QUERY
DEFAULT statements are considered to be the same:
CONTROL QUERY DEFAULT UDR_JAVA_OPTIONS
'-Xmx32M -Djava.class.path=/usr/otherclasses';
CALL...
CONTROL QUERY DEFAULT UDR_JAVA_OPTIONS
'-Xmx32M -Djava.class.path=/usr/otherclasses';
CALL...
However, each of these UDR_JAVA_OPTIONS settings is different because of the
different order of the options:
CONTROL QUERY DEFAULT UDR_JAVA_OPTIONS
'-Xmx32M -Djava.class.path=/usr/otherclasses';
CALL...
CONTROL QUERY DEFAULT UDR_JAVA_OPTIONS
'-Djava.class.path=/usr/otherclasses -Xmx32M';
CALL...
These UDR_JAVA_OPTIONS settings are considered different because of differences
in white space:
CONTROL QUERY DEFAULT UDR_JAVA_OPTIONS
' -Xmx32M -Djava.class.path=/usr/otherclasses ';
CALL...
CONTROL QUERY DEFAULT UDR_JAVA_OPTIONS
'-Xmx32M -Djava.class.path=/usr/otherclasses';
CALL...
Performance Considerations of Using Multiple
UDR_JAVA_OPTIONS Settings
When an SQL/MX application executes CALL statements under different
UDR_JAVA_OPTIONS settings, multiple SQL/MX UDR server processes service the
application. NonStop SQL/MX maintains an SQL/MX UDR server process for each