Skip to main content

 
IBM Systems  > Mainframe servers  > Operating systems  > 

IBM 64-bit SDK for z/OS Java Technology Edition, Version 6.0.1

(Updated May, 2012)

  
dblue_rule.gif
The following is the latest on content, availability and service levels:
Product Content
Getting the Product
Product History
Who Should Use this SDK6.0.1 Product

This product is the z/OS 64-bit Java product that supplies the Java SE 6 APIs. It became generally available in March, 2011 and is periodically updated with cumulative service and improvements. The technology of 6.0.1 modification level is Java 6 with the IBM J9 2.6 VM. This level, unlike the 6.0.0 level, also exploits z196 instructions for improved performance and has some additional JZOS and z/OS Java security enhancements.

The IBM 64-bit SDK for z/OS, Java Technology Edition, V6.0.1 requires:

  • z/OS Version 1 Release 10 or higher

For more product details, read the formal announcement.

Compatibility:
IBM 64-bit SDK for z/OS, Java Technology Edition Version 6 Release 0 Modification 1 (5655-R32) has the same functions as IBM 64-bit SDK for z/OS, Java Technology Edition Version 6 Release 0 Modification 0 (5655-R32) with the following difference:

  • In IBM 64-bit SDK for z/OS, Java Technology Edition Version 6 Release 0 Modification 1 the JRIO function is deprecated. The JRIO function shipped is the same as in Version 6 Release 0 Modification 0 and remains supported. However, customers are encouraged to use the JZOS functionality in lieu of JRIO.

  • Note: Neither the IBM 31-bit SDK for z/OS, Java Technology Edition Version 6 Release 0 Modification 1 nor the IBM 64-bit SDK for z/OS, Java Technology Edition Version 6 Release 0 Modification 1 contain the Encryption Key Manager application (EKM JAR, the jzosekm.jar and sample JCL) in this z/OS Java SDK. Note that the EKM JAR and related material remains included in IBM 31-bit SDK for z/OS, Java Technology Edition Version 6 Release 0 Modification 0.

  • For best performance for most customers, the default garbage collection policy has been changed from OPTTHRUPT to GENCON. Individual customers may still require additional garbage collection tuning for optimal performance. For additional information, see the Diagnostics Guide and the IBM SDK Java Technology Edition, Version 6 Supplement.

All z/OS Java SDK products and modifications levels are independent products and can co-exist on the same z/OS system.

Most Java applications executed on IBM 64-bit SDK for z/OS, Java Technology Edition, V5 (5655-N99) are expected to run unchanged on 64-bit SDK for z/OS, Java Technology Edition, V6, provided that they did not use deprecated Java 2 SDK 5 APIs. Additionally, in some cases, because of a small number of incompatibilities introduced industry wide between Java 2 SDK 5 and SDK 6 APIs, some applications may have to change. Details on these incompatibilities are available at the Oracle web site.

IBMJSSE2 is the sole JSSE security provider. If the provider list includes references to the older IBMJSSE, the IBMJSSE2 introduced in the SDK 1.4.2 products will be invoked. Note that the deprecated com.ibm.net.ssl.* apis will NOT be supported. Use of the deprecated APIs will require code modifications to use APIs supported by the IBMJSSE2 provider.

Back to top



blue_rule.gif

Product Content

The IBM 64-bit SDK for z/OS, V6.0.1 provides a full function SDK compliant with the Java SE 6 APIs.

Documentation is available for content that is additional to the base.

All content above is shipped with the z/OS SDK product and is zAAP eligible.

If you are migrating from Java 2 Technology Edition, SDK5, to IBM SDK for z/OS, see:

For information about SDK6 and additional IBM value add content see:

Back to top



blue_rule.gif

Getting the Product

Note: The API level is Java SE 6.

Before installing the code be sure to check the following links:

The non-SMP/E installable format of the code is available only from the web
Be sure to read additional install information prior to download and install. Check here also after you download and install the code to verify the install.

Download the non-SMP/E format of the code.

The SMP/E installable format of the code is available only through ServerPac or CBPDO

Order IBM SDK for z/OS through a z/OS ServerPac or CBPDO, which can be ordered through the Internet (where available) or through the traditional ordering process.

When ordering:

  • The product number is 5655-R32
  • The subscription and service number is 5655-I48

ShopzSeries provides an easy way to plan and order your z/OS ServerPac or CBPDO. It will analyze your current installation, determine the correct product migration, and present your new configuration based on z/OS. Additional products can also be added to your order (including determination of whether all product requisites are satisfied).

ShopzSeries is available in the U.S. and several countries in Europe. In countries where ShopzSeries is not available yet, contact your IBM representative (or Business Partner) to handle your order via the traditional IBM ordering process.

For more details and availability, visit the ShopzSeries Web site.

Be sure to read the Program Directory:


PDF files require Adobe Acrobat Reader   Adobe® Reader®

Back to top



blue_rule.gif

Product History

A brief history of the updates will be kept in this location.

The topmost entries correspond to the code that can be ordered or downloaded from this Web site.

The Service summary contains the following information:

  • PTF numbers and their build dates
  • related APARs and updated classes
  • corresponding Java SE levels
  • where the service can be obtained (Web or order the tape from IBM)
  • whether the SDK level is currently supported
  • clarification of our PTF/APAR processing

grey_rule.gif May, 2012 Maintenance Rollup
A PTF for 64-bit SDK is available that upgrades the product to the latest service levels and provides a full function SDK compliant with Java SE 6 APIs.

PTF numbers: UK78537/UK78538 (APARs: PM63064/PM63066). The build date of the code is:

  • March 23, 2012 for:
    • z/OS V1.10 and above

grey_rule.gif December, 2011 Maintenance Rollup
A PTF for 64-bit SDK is available that upgrades the product to the latest service levels and provides a full function SDK compliant with Java SE 6 APIs.

PTF numbers: UK74829/UK74870 (APARs: PM48231/PM48232). The build date of the code is:

  • November 14, 2011 for:
    • z/OS V1.10 and above

grey_rule.gif June, 2011 Maintenance Rollup
A PTF for 64-bit SDK is available that upgrades the product to the latest service levels and provides a full function SDK compliant with Java SE 6 APIs.

PTF numbers: UK69000/UK69001 (APARs: PM40894/PM40895). The build date of the code is:

  • April 19, 2011 for:
    • z/OS V1.10 and above

grey_rule.gif March, 2011 - General Availability
 

Original general availability code.

 

Back to top



blue_rule.gif

Who Should Use this SDK6.0.1 Product

Choosing between the Version 6.0.1 and Version 6.0.0 deliveries

The 6.0.1 modification level of product 5655-R32 has newer underlying technology (IBM J9 2.6 VM), takes advantage of z196 instructions for additional performance, includes a later JZOS level (2.4.0) and has enhancements z/OS Java security compared to the existing 6.0.0 modification level. The 6.0.0 modification level continues to be orderable and serviced.

Choosing between the 31-bit and 64-bit deliveries

IBM 31-bit SDK for z/OS, Java Technology Edition, V6.0.1 (5655-R31) will be attractive primarily to customers and ISVs whose Java applications are not constrained by 31-bit addressing and who wish to use Java SDK6. In contrast, Java applications that are storage constrained by 31-bit addressing should be able to execute in a 64-bit environment provided by the 64-bit product, IBM 64-bit SDK for z/OS, Java Technology Edition, V6.0.1 (5655-R32).

The z/OS Java SE 6 products are complementary, have the same SDK6 APIs, and can be installed and run at the same time. The 64-bit product is not a replacement for the 31-bit product.

What are the main reasons for staying with the 31-bit product (or keeping it when you add the 64-bit product)?

  1. you are not storage constrained by 31-bit addressing.
  2. your ISV or other middleware requires the 31-bit product.
  3. your customers are comfortable using the existing SDK5 product.

What are the main reasons for going to the 64-bit product?

  1. your applications are storage constrained by 31-bit addressing.
  2. your ISV or other middleware requires the 64-bit Java product.

While the 64-bit product does well in our internal tests, in general, people don't go to a 64-bit version of a product to improve performance. In fact, a Java application that runs without storage constraint with 31-bit addressing would (normally) be expected to run slower with 64-bit.


 

Back to top