SQL/MX Guide to Stored Procedures in Java (G06.24+, H06.03+)
Getting Started
HP NonStop SQL/MX Guide to Stored Procedures in Java—523727-004
2-12
JVM Startup Options for Each SPJ Caller
Precedence of JVM Startup Options
A UDR_JAVA_OPTIONS setting in a CONTROL QUERY DEFAULT statement takes 
precedence over the setting in the SYSTEM_DEFAULTS table. See JVM Startup 
Options for Each SPJ Caller on page 2-12.
Displaying the UDR_JAVA_OPTIONS in Effect for a Node
To show the UDR_JAVA_OPTIONS setting in effect for the system, enter the 
SHOWCONTROL ALL command in an MXCI session. For more information about 
SHOWCONTROL, see the SQL/MX Reference Manual.
JVM Startup Options for Each SPJ Caller
To set JVM startup options for each caller of an SPJ, use a CONTROL QUERY 
DEFAULT statement. A UDR_JAVA_OPTIONS setting in a CONTROL QUERY 
DEFAULT statement takes precedence over the system-defined default setting, which 
is OFF, and settings in the SYSTEM_DEFAULTS table.
For the effect of the UDR_JAVA_OPTIONS setting on different callers, see:
•
Scope of JVM Startup Options in an SPJ Method on page 2-12
•
Scope of JVM Startup Options in Statically Compiled Applications on page 2-12
•
Scope of JVM Startup Options in Dynamically Compiled Applications on page 2-13
•
Scope of JVM Startup Options in an MXCI Session on page 2-14
For information about the syntax of the CONTROL QUERY DEFAULT statement, see 
the SQL/MX Reference Manual. 
Scope of JVM Startup Options in an SPJ Method
A UDR_JAVA_OPTIONS setting within an SPJ method does not affect the SPJ 
environment in which the SPJ is executing. It affects only the SPJ environment of 
CALL statements that the SPJ method executes. In general, avoid nesting CALL 
statements in an SPJ. For more information, see Nested Java Method Invocations
 on 
page 3-5.
Scope of JVM Startup Options in Statically Compiled 
Applications
The UDR_JAVA_OPTIONS setting in a statically compiled CONTROL QUERY 
DEFAULT statement affects statically compiled CALL statements in the line order 
scope of the application. 
For example, this CONTROL QUERY DEFAULT statement in an embedded SQL 
program in C affects the maximum Java heap size of the SPJ environment in which the 
next statically compiled CALL statement executes:
/* Set application-specific system properties for 
/* the SPJ environment. */










