Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF
Options that affect Java SMP/E for z/OS User's Guide SA23-2277-01 |
|
To support the HTTPS communications with the IBM Automated Delivery Request server, SMP/E uses
the capabilities of Java™ 6.
Specifically, SMP/E requires IBM 31-bit SDK for z/OS, Java Technology
Edition Version 6 (5655-R31), or the IBM 64-bit SDK for z/OS, Java
Technology Edition Version 6 (5655-R32), or a logical successor. SMP/E
supplies several Java application
classes, which after SMP/E is installed, reside in the /usr/lpp/smp/classes directory
in the UNIX file system on the z/OS® system. In order for SMP/E
to use these application classes, they and the Java runtime must be available in the execution
environment for SMP/E. Because neither can be accessed using a STEPLIB
DD statement, you specify the locations for the Java runtime and the SMP/E application classes
using the javahome and classpath attributes
in the CLIENT data set. The javahome attribute
is used to specify the directory where the Java run time resides, and the classpath attribute
is used to specify the search path for Java application
classes. For example:
If the
SMP/E Java application classes
are not installed on the driving z/OS system’s UNIX file system, you can use appropriate
mount points and directory structure to point to a target system’s
directories where SMP/E is installed. This is useful if you use STEPLIB
to access a target system’s base SMP/E programs in order to
ensure the base SMP/E programs and the application classes are at
the same service level. For example:
As
an alternative to the javahome and classpath attributes
in the CLIENT data set, you can also use the SMPJHOME and SMPCPATH
DD statements or DDDEF entries to specify the location of the Java run time and the SMP/E application
classes. If specified, the SMPJHOME and SMPCPATH DD statements override
any values specified on the javahome and classpath attributes.
For example:
The javadebugoptions attribute
is used to specify any Java command-line
parameters, including debug and trace options. Such options determine
what debug and trace information should be produced when SMP/E invokes
its Java application classes.
The debug and trace information is written to the PRINT file for
the HFSCOPY utility (SYSPRINT is the default). Although it is not
necessary all of the time, it is a good idea when first using the
RECEIVE ORDER command, to specify the following value to ensure that
basic debug and trace information is produced for reference:
Although
it is not necessary, it is also possible to specify other Java command-line parameters that affect the
operation of the Java Virtual
Machine (JVM). For example, if you encounter a Java error that indicates there is insufficient
space in the Javaheap, you can specify an option to override the default
maximum Java heap size:
|
Copyright IBM Corporation 1990, 2014
|