Skip to main content

 
IBM Systems  > Servers  > Mainframe servers  > Software  > 

Readme for IBM 31-bit SDK for z/OS, Java 2 Technology Edition V5 (5655-N98)

(last updated July, 2009)

  

dblue_rule.gif

Optional Install of the JZOS Batch Launcher:

Starting with the delivery of SDK5 SR3, this product 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.

Getting the code:

The following file may be downloaded to your workstation and installed on z/OS V1.6 and above or z/OS.e V1.6 or above.

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 5 SR10, 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 size of the files on the IBM server for SDK 5 SR10 is as follows:

   UK48410.PAX.Z               112448422 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 at least 180MB of space.

Prerequisites - Java will NOT function without these APARs.

Uncompress and Install the code:

Once you have the code in your HFS directory you will need to uncompress the file to complete the installation.

  1. Download the UK48410.PAX.Z file and optionally the readme file to your workstation.

  2. 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.

  3. 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.

  4. Create an HFS or zFS filesystem dataset into which you'll later expand the pax file. Mount this filesystem at: /usr/lpp/java/J5.0.

  5. cd to /usr/lpp/java and unpax the uploaded UK48410.PAX.Z file. If you uploaded it to the HFS, use: 
       pax -ppx -rvzf UK48410.PAX.Z

    or for an upload to a dataset, use:

       pax -ppx -rvzf "//'UK48410.PAX.Z'"

    The command will create and expand the code in directory J5.0.

    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 UK48410.PAX.Z

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

If you were successful in downloading and uncompressing all the files, there should be a file titled "JDK_INSTALL_OK" in the directory J5.0 (for the 31-bit product).

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/J5.0/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:

31-bit "java-version":
   java version "1.5.0"
   Java(TM) 2 Runtime Environment, Standard Edition 
   (build pmz31dev-20090707 (SR10))
   IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 
   z/OS s390-31 j9vmmz3123-20090707
   (JIT enabled)
   J9VM - 20090706_38445_bHdSMr
   JIT  - 20090623_1334_r8
   GC   - 200906_09)
   JCL  - 20090705

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 about the GA versions of z/OS Java 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 SDK5 SR3 (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.

  1. 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.


  2. 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. Note: This information can be sent if required.)

  3. 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 5.0 SDK and using the default target libraries, issue the following commands under a USS shell: 
    cp JVMJCL50 "//'SYS1.SAMPLIB(JVMJCL50)'"
cp JVMPRC50 "//'SYS1.PROCLIB(JVMPRC50)'"
cp -x JVMLDM50 "//'SYS1.SIEALNKE(JVMLDM50)'"
  4. 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.

  5. 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.3.0 2008-05-12
JVMJZBL1002N Copyright (C) IBM Corp. 2005.  
All rights reserved.
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition 
(build pmz31dev-20090707 (SR10))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 
z/OS s390-31 j9vmmz3123-20090707 (JIT enabled)
J9VM - 20090706_38445_bHdSMr
JIT  - 20090623_1334_r8
GC   - 200906_09)
JCL  - 20090705 
JVMJZBL1023N Invoking HelloWorld.main()...
JVMMZBL1024N HelloWorld.main() completed.
JVMJZBL1021N JZOS batch launcher completed, 
   return code=0
Hello World
  6. To diagnose problems with the JZOS batch launcher, change the LOGLVL parameter to '+l': 
    // EXEC JVMLDM50,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.


 

suncup.gif