Java operands are specified when a Java stored procedure or Java stored function is used. For details about Java stored procedures and Java stored functions, see the HiRDB Version 9 UAP Development Guide.
Note that some platforms on which HiRDB runs do not support Java stored procedures and Java stored functions. For details, see Environment supporting Java stored procedures and functions in the HiRDB Version 9 System Operation Guide.
- 204) pd_java_option = "Java-option"[,"Java-option"]...
- ~<character string>
- Specifies Java virtual option startup options. For details about the startup options, see the documents on Java virtual machines.
- Operand rules
- The maximum character string size of a Java option is 255 characters.
- The total character string size of all Java options is 1,024 characters.
- Double quotation mark (") cannot be specified within a Java option.
- A maximum of 20 Java options can be specified.
- Operand specification example
- The following example specifies the initial value of the heap size to be used by a Java virtual machine as 32 megabytes and the maximum value of the heap size as 64 megabytes:
- pd_java_option = "-Xms32m","-Xmx64m"
- 205) pd_java_routine_stack_size = >stack-size-for-use-by-external-Java-routine
- ~<unsigned integer>((1024-2146435072))<<131072>> (bytes)
- Specifies in bytes the stack size to be used by an external Java routine.
- Specification guidelines
- Specify a value that is greater than the stack size specified as a Java option.
- If an operation for specifying both the stack size and native method stack area size for a Java virtual machine is available as a startup option of the Java virtual machine, specify for the pd_java_routine_stack_size operand a value that is greater than the native method stack size.
- Notes
- If a value that is smaller than the stack size specified as a Java option is specified, HiRDB might not run correctly.
- If the stack size being used exceeds the value specified by this operand, HiRDB might not run correctly. However, HiRDB will run correctly if the Java virtual machine detects the stack overflow.
- 206) pd_java_archive_directory = "JAR-file-storage-directory"
- ~<path name> <<$PDDIR/java>>
- Specifies the name of the directory for storing JAR files used by Java stored procedures or Java stored functions.
- Notes
- The specified directory must be created before installation of JAR files.
- The JAR file storage directory is used only for storing JAR files.
- Store only the installed JAR files in the JAR file storage directory.
- Operand rules
- Up to 255 characters can be used for the path name.
- 207) pd_java_classpath = "Java-class-path"
- ~<path name>
- Specifies as an absolute path name the class path to be used by a Java virtual machine.
- The class contained in the path specified by this operand can be referenced from the Java method, which is executed as the processing procedure of a Java stored procedure or Java stored function.
- If a class with the same name exists in the path specified by this operand and in the JAR file specified as an external routine of the Java stored procedure or Java stored function, the path specified by this operand takes precedence.
- Operand rules
- Up to 1,024 characters can be used for the path name.
- 208) pd_java_runtimepath = "Java-Runtime-Environment-root-directory"
- ~<path name> <<$PDDIR/jre>>
- Specifies as an absolute path name the root directory of the Java Runtime Environment.
- Operand rules
- Up to 255 characters can be used for the path name.
- Notes
- Because Java Runtime Environment (JRE) is no longer included, you must add this operand or change its value when you upgrade HiRDB from a version earlier than 07-03 to version 07-03 or later. For notes about upgrading, see Using Java stored procedures and functions in the HiRDB Version 9 Installation and Design Guide.
- 209) pd_java_libpath = "Java-virtual-machine-library-directory"
- ~<path name>
- Specifies the directory that stores the library of the Java virtual machine as a relative path name to the Java Runtime Environment root directory (the value of the pd_java_runtimepath operand).
- Operand default values
- The following table lists the default values for this operand, depending on the OS:
OS | Operand's default value |
---|
HP-UX (32-bit mode) | lib/PA_RISC/hotspot |
HP-UX (64-bit mode) | lib/PA_RISC2.0W/server |
HP-UX (IPF) | lib/IA64W/server |
Solaris (32-bit mode) | lib/sparc/hotspot |
Solaris (64-bit mode) | lib/sparcv9/server |
Linux | lib/i386/server |
Linux (EM64T) | lib/amd64/server |
AIX (32-bit mode) | bin/classic |
AIX (64-bit mode) |
- Operand rules
- A maximum of 255 characters can be used for the path name.
- Operand specification example
- This example assumes that the CPU architecture uses a Hot Spot virtual machine compatible with PA-RISC 2.0; it also assumes use of the HP-UX edition of Java Runtime Environment 1.2.2:
- pd_java_libpath = "lib/PA_RISC2.0/hotspot"
- Note
- Do not specify lib/PA_RISC/classic or lib/PA_RISC2.0/classic for the HP-UX edition; if you do, HiRDB might not run correctly.
- 210) pd_java_stdout_file = "Java-virtual-machine-standard-output-and-standard-error-output-destination-file"
- ~<path name>
- Specifies as an absolute path name the file to which the standard output and standard error output are to be output in a Java virtual machine. If this operand is omitted, the standard output and standard error output of the Java virtual machine are ignored.
- Specification guidelines
- Because the size of the file specified by this operand is extremely large, this operand is not normally specified. It is recommended that this operand be specified during debugging of a Java stored procedure or Java stored function. There is no limit to the size of the file that can be specified by this operand.
- Note
- If there are simultaneous writing attempts from multiple processes, their output contents cannot be guaranteed.
- Operand rules
- Up to 255 characters can be used for the path name.