|
Platform requirements
Operating systems: Any OS/390® or z/OS® system that is compatible with any of the following:
- IBM® Developer Kit for OS/390, Java™ 2 Technology Edition (5655-D35)
- IBM SDK for z/OS, Java 2 Technology Edition, Version 1.4 (5655-I56)
- IBM 31-bit SDK for z/OS, Java 2 Technology Edition, Version 5 (5655-N98)
- IBM 64-bit SDK for z/OS, Java 2 Technology Edition, Version 5 (5655-N99)
- IBM 31-bit SDK for z/OS, Java Technology Edition, Version 6 (5655-R31)
- IBM 64-bit SDK for z/OS, Java Technology Edition, Version 6 (5655-R32)
Note that Version 2.3.0 contains SDK 6 product support.
Note that Version 1.2.5 includes the 1.2.4 fixes:
- LE Runtime Opts for SDK 1.4 and 5.0
- ZUtil.bpxwdyn() fixed for SDK 1.4 and 5.0.
Version 1.2.5 also includes the following:
- fix for 0C4 in MVS Console support (WAIT4CMD)
- ability to set current directory in launcher STDENV via
cd shell command.
Version 1.2.5 has the same prerequisites as Version 1.2.4, the following in particular: In order to run either Version 1.2.5 or 1.2.4 on pre-zOS 1.6 systems, you must install the appropriate C++/LE compatability PTF: UK03870 for z/OS 1.5, or UK03869 for z/OS 1.4 PTF. It is unknown whether this build will work on versions lower than z/OS 1.4, so those customers should continue to run JZOS 1.2.3.
Installation instructions
Note: Complete installation instructions are contained in the zip files.
Versions 2.3.0, 2.2.1, 2.1.1
Please download the installation instructions (PDF) for this latest version.
Versions 1.2.5 and below
- Download the zip file to your workstation.
- Extract the contents to a local directory.
- Transfer files from your workstation to the z/OS or OS/390 system. Please be sure that you upload the following files in binary (no translation):
- File Host dataset Recfm,Lrecl Space
- jzos.pax 'HLQ.jzos.pax' F/FB,80 2 cylinders
- jzos.loadlib.xmit 'HLQ.jzos.loadlib.xmit' F/FB,80 1 cylinder
- jzos.sampjcl.xmit 'HLQ.jzos.sampjcl.xmit' F/FB,80 5 tracks
If you are uploading using FTP, use the following commands (substituting your own dataset high-level qualfier for "HLQ"):
ftp myzos.myco.com
(Log in with your host name, user ID, and password.)
ftp> bin
ftp> quote site recfm=fb
ftp> quote site lrecl=80
ftp> put jzos.sampjcl.xmit 'HLQ.JZOS.SAMPJCL.XMIT'
ftp> quote site cyl
ftp> quote site pri=2
ftp> put jzos.loadlib.xmit 'HLQ.JZOS.LOADLIB.XMIT'
ftp> put jzos.pax 'HLQ.JZOS.PAX'
ftp> quit
|
If you are uploading using Personal Communications, then use the following commands to transfer the files. Be sure that you are logged on the host and within the READY mode (outside ISPF). Change the session string ("A:") and the destination "HLQ" to the ones you have:
send jzos.pax A:'HLQ.jzos.pax' recfm(f) lrecl(80)
space(2,1) cylinders
send jzos.loadlib.xmit A:'HLQ.jzos.loadlib.xmit' recfm(f) lrecl(80)
space(1,1) cylinders
send jzos.sampjcl.xmit A:'HLQ.jzos.sampjcl.xmit' recfm(f) lrecl(80) space(5,5) tracks
|
- In order to unload the load module library into a PDSE, enter the following TSO command:
tso receive inda('HLQ.JZOS.LOADLIB.XMIT')
|
When prompted with the message Enter restore parameters..., enter the following:
Note: If you get an error "Unable to issue message with prompt for reply", then enable prompting with the following command:
- Repeat in order to unload the sample JCL PDS:
tso receive inda('HLQ.JZOS.SAMPJCL.XMIT')
JZOS Installation and User's Guide 4
Installation
|
When prompted with the message Enter restore parameters..., enter the following:
- From the z/OS UNIX shell, change to the directory under which you want to create the JZOS HFS files and unload the pax data set. (This will create a directory named jzos relative to the current directory, which will be referred to later as JZOS_HOME.):
pax -rvf "//'HLQ.JZOS.PAX'"
|
- Tailor the JZOS batch launcher proc contained in HLQ.JZOS.SAMPJCL(EXJZOSVM), updating it to point to the JZOS load module library that you uloaded in Step 4.
- Follow the instructions contained in HLQ.JZOS.SAMPJCL, and tailor member RUN13 or RUN14 (depending on your Java version).
- SUBMIT the modified JCL and check the job log. If everything was set up properly, the SYSOUT DD should contain output like this:
JZOSVM13(N): C) Copyright IBM Corp. 2005. All Rights Reserved
JZOSVM13(N): Version 1.2.3 (or Version 1.2.5)
JZOSVM13(N): Java Virtual Machine created
JZOSVM13(N): Invoking com.dovetail.jzos.sample.HelloWorld.main()
JZOSVM13(N): com.dovetail.jzos.sample.HelloWorld.main() completed.
|
The STDOUT DD should contain Hello World!
- In order to diagnose problems with the JZOS batch launcher, change the LOGLVL parameter to +I:
// EXEC EXJZOSVM,LOGLVL='+I'
|
Note: Setting this logging level (+I) will dump the environment that is passed to the JVM. The trace level setting +T will produce many messages, some of which may be helpful in tracking down installation problems.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
IBM, OS/390, and z/OS are trademarks of IBM Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
|
|