|
Optional Install:
SDK 1.4.2 SR6 and later contains newly integrated Java (JZOS) batch capability. If that batch capability is going to be used, then the optional installation section (at the end of this readme) should be done. That optional installation section is very similar to the instructions for the existing (unsupported) JZOS on alphaWorks.
The JZOS function is only supported on z/OS V1.4 and above.
Getting the code:
You can download the retail version of the code to your workstation by choosing the IBM SDK 1.4 for z/OS file UK50752.PAX.Z.
To assist you with the download, a link to Download Director is available. Download Director is a highly reliable tool designed to resume an interrupted download connection, access files through the firewall, and download large files.
To verify that the download was complete you should determine if the file sizes of the files downloaded match the file sizes listed on the IBM download server web page and in the readme on that download site. The information on this web page regarding PTF number, file sizes and exact "java -version" is specific for SDK 1.4.2 SR13 FP2, but the format will be similar for all SRs and the readme on the download site will have the exact details for the SR downloaded. See also the product history.
The current size of the files on the IBM server are as follows:
UK50752.PAX.Z 91648 KB 91648103 bytes
Once the file has been downloaded to your workstation, you will need to use a binary transfer to move the file to an HFS directory on your z/OS system with an adequate amount of space. An HFS directory with at least
- 180MB of space (the non-debug version)
is recommended.
Prereqs and Recommended Service:
There are no specific APARs required for z/OS v1.7 and above.
The following APARs (and corresponding PTFs) are required for your z/OS V1.6 (5694-AO1) or z/OS.e V1.6 (5655-G52) System:
- OA08155 (PTF UA12453)
- OA08252 (PTF UA13606)
- PQ90923 (PTF UQ92626)
The following APARs (and corresponding PTFs) are required for your z/OS V1.5 (5694-AO1) or z/OS.e V1.5 (5655-G52) System:
- PQ84190 (PTF UK03870) - June 7, 2005 availability (required for JZOS usage)
- OA08155 (PTF UA12452)
- PQ90923 (PTF UQ92625)
The following APARs (and corresponding PTFs) are required for your z/OS V1.4 (5694-AO1) or z/OS.e V1.4 (5655-G52) System:
- PQ84190 (PTF UK03869) - June 7, 2005 availability (required for JZOS usage)
- OA08155 (PTF UA12451)
- PQ90923 (PTF UQ92624)
- OA07174 (PTF UA10295)
- OA06691 (PTF UA10070)
- PQ69548 (PTF UQ77316)
- PQ54074 (PTF UQ71321)
- PQ66118 (PTF UQ71530)
- PQ60748 (PTF UQ71263)
- PQ72565 (PTF UQ76197)
- PQ61928 (PTF UQ70204)
- PQ60892 (PTF UQ71361)
- OW54362 (PTF UW95336)
The following APARs (and corresponding PTFs) are recommended for your z/OS V1.4 (5694-AO1) or z/OS.e V1.4 (5655-G52) System:
- PQ72197 (PTF UQ75719)
- PQ72266 (PTF UQ75723)
- PQ71219 (PTF UQ76026)
Java will NOT function without the required APARs.
Download, Uncompress and Install the code:
- Download the UK50752.PAX.Z file and optionally the readme file to your workstation.
- To verify that the download was complete you should determine if the file sizes of the files downloaded match the file sizes listed on the IBM download server web page.
- Once the file has been downloaded to your workstation, you will need to use a binary transfer to move the file to your z/OS system. You can ftp to an HFS file, or use the 3270 file transfer to a RECFM(VB) dataset.
- Create an HFS or zFS filesystem dataset into which you will later expand the pax file. Mount this filesystem at /usr/lpp/java/J1.4.
- Copy directory (cd) to /usr/lpp/java and unpax the uploaded UK50752.PAX.Z file. If you uploaded it to the HFS, use:
pax -ppx -rvzf UK50752.PAX.Z
or for an upload to a dataset, use:
pax -ppx -rvzf "//'UK50752.PAX.Z'"
If you are not able to restore the code archive with this command, it may be because you do not have the necessary authority (see "Required authorization") to restore the program control bit. In this case, you can issue the following command:
pax -pp -rvzf UK50752.PAX.Z
Notes:
- SDK 1.4 comes packaged with the +p bit already set for the files in the "J1.4/bin" and "J1.4/bin/classic" directories.
- Certain applications may require that the program control bit be set.
Required authorization:
To restore the files with the proper permission bits, you must have the following authority:
- - UID(0) or access to BPX.SUPERUSER.FACILITY class
- - Access to BPX.FILEATTR.APF
- - Access to BPX.FILEATTR.PROGCTL
- - Access to BPX.FILEATTR.SHARELIB
Note: Access to BPX.FILEATTR.* could be used instead.
This is the typical authority you require to install z/OS.
Note: Certain applications may require that the program control bit be set. The 31-bit SDK 5 comes packaged with the +p bit already set for the files in the "J5.0/bin" and "J5.0/bin/j9vm" directories. Using the zAAP processor requires that the +a bit be set; the product comes packaged with the +a bit already set, but if a pax file is installed without the required authorization, the +a bit will no longer be set and the work will run on a general purpose processor. The Java virtual machine will issue warning:
JVMHP030: Unable to switch to IFA processor - issue "extattr +a libj9ifa23.so
Alternatively, the pax file could be reinstalled with the required authorization in order to allow continued execution on zAAP processors.
Verification:
Post Installation Information
If you were successful in downloading and uncompressing all the files, there should be a file titled "JDK_INSTALL_OK" in the directory J1.4.
Set the Environment
The installation below assumes you installed the code into the following directory:
/mydir/java
Set the following environment variables:
export PATH=/mydir/java/J1.4/bin:$PATH
export DISPLAY=hostname.of.my.machine:0.0
Verify the Install
To verify that the install process completed successfully, issue the following command:
java -version
You will see the following message showing the java version level and other information:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition
(build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM z/OS
Persistent Reusable
VM build cm142ifx-20090918 (SR13 FP2)
(JIT enabled: jitc))
The CLASSPATH environment variable can be updated. For example, issue the following command to set the CLASSPATH variable:
export CLASSPATH=.:/path/to/my/classes:$CLASSPATH
In this example, the JVM will first look for the required classes in the current directory. If the required classes are not found there, the JVM will look in the /path/to/my/classes directory.
For more information please see the z/OS Java website.
http://www.ibm.com/servers/eserver/zseries/software/java
Optional Install of the JZOS Batch Launcher function introduced in SDK1.4.2 SR6 ( Note: The new JZOS MVS console functions do not require installation of the Batch launcher capability.)
The following is taken from the JZOS Installation Guide that is available on the above website. The instructions are very similar to those for current users of JZOS, including those using the IBM alphaWorks version.
- These instructions assume that the non-SMP/E pax file has been uploaded and unpaxed per the Java SDK product install instructions.
Note: If the batch launcher function is not installed, steps 2-6 are not followed and JZOS batch launcher function can not be used. However, all other JVM functions can still be used, including the new JZOS system services and file I/O.
- Allocate any needed MVS PDSE or PDS data sets. For your information, the SMP/E install will, by default, place a load module in SYS1.SIEALNKE, a sample PROC in SYS1.PROCLIB and sample JCL in SYS1.SAMPLIB. (For installation into private data sets, suggested allocation sizes are F/FB,80 5 tracks for SAMPJCL and for SAMPPROC. For LOADLIB allocation recommendations refer to Appendix C. SMP/E Install ++HOLD Information, item "Define new data set using the following attributes". Note: This information can be sent if required.)
- Copy loadmod to a PDSE, PROC, and JCL to a PDS from the unpaxed file. The load module will be found in <JAVA_HOME>/mvstools. The sample JCL and PROC will be found in <JAVA_HOME>/mvstools/samples/jcl. For example, for the 1.4 SDK and using the default target libraries, issue the following commands under a USS shell:
cp JVMJCL14 "//'SYS1.SAMPLIB(JVMJCL14)'"
cp JVMPRC14 "//'SYS1.PROCLIB(JVMPRC14)'"
cp -x JVMLDM14 "//'SYS1.SIEALNKE(JVMLDM14)'"
- Change the sample JCL and PROC as appropriate for your environment. Specifically, update JCL with JOB card information, update the JCL and PROC with HLQ where the PROC and LOADLIB exist, and update the PROC with the location of JAVA_HOME. Make sure your sample JCL or PROC included a STEPLIB to the load library unless that load library is included in your LNKLST member.
- SUBMIT the modified JCL and check the job log. If everything was set up properly, the SYSOUT DD should contain output like this:
JVMJZBL1001N JZOS batch Launcher Version: 2.0.0
2006-06-30
JVMJZBL1002N Copyright (C) IBM Corp. 2005.
All rights reserved.
java version "1.4.2"
Java (TM) 2 Runtime Environment, Standard Edition
(build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM z/OS
Persistent Reusable
VM build cm142ifx-20090918 (SR13 FP2)
(JIT enabled: jitc))
JVMJZBL1023N Invoking HelloWorld.main()...
JVMMZBL1024N HelloWorld.main() completed.
JVMJZBL1021N JZOS batch launcher completed,
return code=0
Hello World
- To diagnose problems with the JZOS batch launcher, change the LOGLVL parameter to '+l':
// EXEC JVMLDM14,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.
| 
