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

(Updated November, 2014)



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 SE 7 APIs. It became generally available in August, 2011 and is periodically updated with cumulative service and improvements. The technology is used with the IBM J9 V2.6 VM.

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

For more product details, read the formal announcement.

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

The IBM JZOS Batch Toolkit for z/OS is updated such that ZFile.obtainDSN() returns null if the specified dsn does not have a DSCB in the VTOC. (In releases earlier than zOS Java SDK 6.0.1, the same method returns a pseudo DSCB.)

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, V6 (5655-R32) are expected to run unchanged on 64-bit SDK for z/OS, Java Technology Edition, V7, provided that they did not use deprecated Java SE 6 APIs. Additionally, in some cases, because of a small number of incompatibilities introduced industry wide between Java SE 6 and SE 7 APIs, some applications may have to change. Details on these incompatibilities are available at the Oracle web site.

Similar to SDK V5 and SDK V6, SDK V7 takes advantage of enhanced z/OS linkage capabilities (XPLINK). Any application code that creates a JVM itself and interacts with the JVM via Java Native Interface(JNI) or any other "call" interface must create the Language Environment (LE) enclave specifying that LE should setup an XPLINK environment. This XPLINK LE enclave must be in place prior to creating the JVM. Further XPLINK details can be found in the IBM Redbook - XPLink: OS/390 Extra Performance Linkage, SG24-5991 and z/OS Language Environment Programming Guide (PDF,3.7MB), SA22-7561.

Statement of direction:
IBM 31-bit SDK for z/OS, Java Technology Edition, V7.0 and IBM 64-bit SDK for z/OS, Java Technology Edition, V7.0 are planned to be the last releases to support the JRIO component. JRIO was deprecated in the IBM SDK for z/OS, Java Technology Edition, V6.0.1 products. Customers and ISVs are encouraged to use the record I/O facilities in the JZOS component instead of the JRIO facilities. For more information about JZOS, see JZOS Java Launcher and Toolkit Overview.

For more information about migration from JRIO to JZOS and sample code, see IBM Java Record I/O (JRIO) to IBM JZOS Batch Toolkit Migration and Sample Code.

Product Content

The IBM 64-bit SDK for z/OS, V7 provides a full function SDK compliant with the Java SE 7 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 Technology Edition, z/OS Java SDK V6 to IBM SDK for z/OS V7, see:

For information about z/OS SDK 7 and additional IBM value add content see:

Getting the Product

Note: The API level is Java SE 7.

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

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

Note: Service (i.e., PTFs) for the SMP/E product will be delivered as two co-req PTFs.

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 Get 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:


November, 2014 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 7 APIs.

PTF number: UI22881 (APARs: PI27136 and PI27138). The build date of the code is:


July, 2014 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 7 APIs.

PTF number: UI19909 (APARs: PI21736 and PI21737). The build date of the code is:


April, 2014 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 7 APIs.

PTF number: UI17387 (APARs: PI15135/PI15136). The build date of the code is:


January, 2014 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 7 APIs.

PTF number: UI14491 (APARs: PI08843/PI08844). The build date of the code is:


November, 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 Java SE 7 APIs.

PTF number: UI11935 (APARs: PM99212/PM99213). The build date of the code is:


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 Java SE 7 APIs.

PTF number: UK95672 (APARs: PM91968/PM91970). 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 Java SE 7 APIs.

PTF number: UK94102 (APARs: PM88278/PM88279). 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 Java SE 7 APIs.

PTF number: UK93173 (APARs: PM84196/PM85899). 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 Java SE 7 APIs.

PTF number: UK92406 (APARs: PM84244-PE/PM84197-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 Java SE 7 APIs.

PTF number: UK92045 (APARs: PM82401/PM82404). 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 Java SE 7 APIs.

PTF numbers: UK83228/UK83229 (APARs: PM75687/PM75689). 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 Java SE 7 APIs.

PTF numbers: UK81634/UK81635 (APARs: PM70867/PM70868). The build date of the code is:


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

PTF numbers: UK78844/UK78845 (APARs: PM63143/PM63144). The build date of the code is:


October, 2011 - General Availability

Original general availability code.

Who Should Use this SDK7 Product

Choosing between the Version 7.0.0 and Version 6.0.1 deliveries

The V7 version of product 5655-W44 has the same underlying technology (IBM J9 V2.6 VM), continues to take advantage of z196 instructions for additional performance, and includes the JZOS level (2.4.0) and enhancements to z/OS Java security in the Version 6.0.1 delivery. The V7 delivery contains the Java SE 7 APIs.

Choosing between the 31-bit and 64-bit deliveries

IBM 31-bit SDK for z/OS, Java Technology Edition, V7 (5655-W43) will be attractive primarily to customers and ISVs whose Java applications are not constrained by 31-bit addressing and who wish to use Java SE 7. 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, V7 (5655-W44).

The z/OS Java SE 7 products are complementary, have the same Java SE 7 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 SDK6 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.


Browse z/OS