IBM 64-bit SDK for z/OS Java 2 Technology Edition, V5



Effective September 30, 2013, IBM 31-bit SDK for z/OS Java 2 Technology Edition, V5 (5655-N98) and IBM 64-bit SDK for z/OS Java 2 Technology Edition, V5 (5655-N99) are no longer supported.

The following is the latest on content, availability and service levels:


This product is the z/OS 64-bit Java product that supplies the Java SDK 5 APIs. It became generally available in December, 2005 and is periodically updated with cumulative service and improvements.

The IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 requires either:

The IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 will be serviced through at least September, 2013. Withdrawal from marketing and withdrawal from service announcements follow the z/OS procedures and lead times. View product support lifecycle announced dates.

For more product details, read the formal announcement.

Compatibility:
IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99) has the same functions as IBM SDK for z/OS, Java 2 Technology Edition (5655-I56), V1.4 with the exception of:

31-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N98) and SDK for z/OS, Java 2 Technology Edition, V1.4 (5655-I56), 64-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99) and IBM Java for OS/390, Java 2 Technology Edition (5655-D35) are independent products and can co-exist on the same z/OS system.

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

64-bit SDK for z/OS, Java 2 Technology Edition, V5 takes advantage of enhanced z/OS linkage capabilities (XPLINK.) The z/OS operating system provides an XPLINK runtime environment for all 64-bit programs, including the Java Virtual Machine (JVM).

Programs interacting with the 64-bit Java product, whether launching the JVM or being called from the JVM through the JNI interface, must be 64-bit programs. Programs dependent on JNI interfaces may require changes at the interface boundary to conform to 64-bit data types. Application JNI routines written in C will need to be recompiled for 64-bit, which may require some code changes.

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.

Product Content

The IBM 64-bit SDK for z/OS, V5 provides a full function SDK compliant with the SDK 5 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, SDK 1.4, to IBM 64-bit SDK for z/OS, see:

If you are migrating from a 31-bit SDK1.4 product, see: Porting Guide.

For information on SDK5 and additional IBM value add content see:

Getting the Product

Note: The Oracle SDK level is SDK 5.

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.
Review the readme.txt file prior to download and install and for verification instructions.

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 64-bit 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:

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® Reader®

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:

July, 2013 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 the SDK 5 APIs.

PTF number: UK95623 (APARs: PM92064/PM92065). The build date of the code is:

May, 2013 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 the SDK 5 APIs.

PTF number: UK94052 (APARs: PM88266/PM88267). The build date of the code is:

April, 2013 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 the SDK 5 APIs.

PTF number: UK93056 (APARs: PM84184/PM85890). The build date of the code is:

March, 2013 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 the SDK 5 APIs.

PTF number: UK92293 (APAR: PM84185-Sec). The build date of the code is:

February, 2013 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 the SDK 5 APIs.

PTF number: UK91797 (APAR: PM82298 and PM82299). The build date of the code is:

November, 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 the SDK 5 APIs.

PTF number: UK83139 (APAR: PM75654). The build date of the code is:

September, 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 the SDK 5 APIs.

PTF number: UK81212 (APAR: PM70854). The build date of the code is:

April, 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 the SDK 5 APIs.

PTF number: UK77394 (APAR: PM60960). The build date of the code is:

November, 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 the SDK 5 APIs.

PTF number: UK73742 (APAR: PM51668). The build date of the code is:

July, 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 the SDK 5 APIs.

PTF number: UK69796 (APAR: PM43609). The build date of the code is:

March, 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 the SDK 5 APIs.

PTF number: UK65646 (APAR: PM34198). The build date of the code is:

February, 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 the SDK 5 APIs.

PTF number: UK64809 (APAR: PM32445). The build date of the code is:

January, 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 the SDK 5 APIs.

PTF number: UK63517 (APAR: PM29840). The build date of the code is:

November, 2010 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 the SDK 5 APIs.

PTF number: UK61391 (APAR: PM24611). The build date of the code is:

August, 2010 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 the SDK 5 APIs.

PTF number: UK59510 (APAR: PM20038). The build date of the code is:

August, 2010 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 the SDK 5 APIs.

PTF number: UK59134 (APAR: PM18985). The build date of the code is:

June, 2010 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 the SDK 5 APIs.

PTF number: UK57326 (APAR: PM15169). The build date of the code is:

March, 2010 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 the SDK 5 APIs.

PTF number: UK54540 (APAR: PM07146). The build date of the code is:

January, 2010 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 the SDK 5 APIs.

PTF number: UK53878 (APAR: PM00991). The build date of the code is:

November, 2009 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 the SDK 5 APIs.

PTF number: UK52004 (APAR: PK98666). The build date of the code is:

July, 2009 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 the SDK 5 APIs.

PTF number: UK48412 (APAR: PK91161). The build date of the code is:

April, 2009 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 the SDK 5 APIs. Upgrade to JZOS 2.3.0 level.

PTF number: UK45914 (APAR: PK85076). The build date of the code is:

December, 2008 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 the SDK 5 APIs. Upgrade to JZOS 2.3.0 level.

PTF number: UK42387 (APAR: PK77008). The build date of the code is:

August, 2008 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 the SDK 5 APIs.

PTF number: UK39054 (APAR: PK70616). The build date of the code is:

July, 2008 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 the SDK 5 APIs.

PTF number: UK38283 (APAR: PK69114). The build date of the code is:

March, 2008 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 the SDK 5 APIs.

PTF number: UK34638 (APAR: PK59135). The build date of the code is:

October, 2007 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 the SDK 5 APIs.

PTF number: UK30954 (APAR: PK55857). The build date of the code is:

August, 2007 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 the SDK 5 APIs.

PTF number: UK27962 (APAR: PK49494). The build date of the code is:

May, 2007 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 the SDK 5 APIs.

PTF number: UK25434 (APAR: PK40165). The build date of the code is:

February, 2007 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 the SDK 5 APIs.

PTF number: UK21795 (APAR: PK38162). The build date of the code is:

October, 2006 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 the SDK 5 APIs.

PTF number: UK18623 (APAR: PK32191). The build date of the code is:

May, 2006 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 the SDK 5 APIs.

PTF number: UK14830 (APAR: PK14830). The build date of the code is:

March, 2006 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 the SDK 5 APIs.

PTF number: UK12793 (APAR: PK21539). The build date of the code is:

Who Should Use this SDK5 Product

IBM 64-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99) will be attractive primarily to customers and ISVs whose Java applications have been constrained by 31-bit addressing and who wish to use Java SDK5. Specifically, pure Java applications that were previously storage constrained by 31-bit addressing should be able to execute in a 64-bit environment.

The product has the same SDK 5 APIs that are in the 31-bit product, IBM SDK for z/OS, Java 2 Technology Edition, V5 (5655-N99). The two products are complementary. They can be installed and run at the same time. In other words, the 64-bit product is not a replacement for the 31-bit product.

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

  1. your applications are storage contrained by 31-bit addressing.
  2. your ISV or other middleware requires the 64-bit Java 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 SDK 5 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.


Browse z/OS