|
The following is the latest on content, availability and service levels:
This product is the z/OS 31-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 31-bit SDK for z/OS, Java 2 Technology Edition, V5 requires either:
- z/OS Version 1 Release 6 or higher
- z/OS.e Version 1 Release 6 or higher
The IBM 31-bit SDK for z/OS, Java 2 Technology Edition, Version 5 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 31-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N98) has the same functions as IBM SDK for z/OS, Java 2 Technology Edition (5655-I56), V1.4 with the exception of:
- Persistent reusable function
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 SDK for z/OS, Java Technology Edition, V1.4 (5655-I56) are expected to run unchanged on 31-bit SDK for z/OS, Java 2 Technology Edition, V5, provided that they did not use deprecated Java 2 SDK 1.4 APIs. Additionally, in some cases, because of a 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.
31-bit SDK for z/OS, Java 2 Technology Edition, V5 can take advantage of enhanced z/OS linkage capabilities (XPLINK.) The z/OS operating system provides an XPLINK runtime environment for programs, including the Java Virtual Machine (JVM). This contrasts with the Java product, SDK for z/OS, Java 2 Technology Edition, V1.4 (5655-I56), where it is necessary to ensure that an XPLINK environment is in place when the JVM is launched.
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 31-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, SDK1.4, to IBM SDK for z/OS, see:
For information about 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
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-N98
- 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:
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 Oracle SDK 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
 November, 2011 Maintenance Rollup
A PTF for 31-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: UK73733 (APAR: PM51660). The build date of the code is:
- October 20, 2011 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
July, 2011 Maintenance Rollup
A PTF for 31-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: UK69795 (APAR: PM43607). The build date of the code is:
- June 27, 2011 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
March, 2011 Maintenance Rollup
A PTF for 31-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: UK65645 (APAR: PM34197). The build date of the code is:
- February 14, 2011 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
February, 2011 Maintenance Rollup
A PTF for 31-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: UK64679 (APAR: PM32441). The build date of the code is:
- February 11, 2011 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
January, 2011 Maintenance Rollup
A PTF for 31-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: UK63505 (APAR: PM29779). The build date of the code is:
- December 8, 2010 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
November, 2010 Maintenance Rollup
A PTF for 31-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: UK61387 (APAR: PM24610). The build date of the code is:
- October 8, 2010 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
August, 2010 Maintenance Rollup
A PTF for 31-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: UK59501 (APAR: PM20035). The build date of the code is:
- August 13, 2010 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
August, 2010 Maintenance Rollup
A PTF for 31-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: UK59131 (APAR: PM18984). The build date of the code is:
- July 1, 2010 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
June, 2010 Maintenance Rollup
A PTF for 31-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: UK57325 (APAR: PM15167). The build date of the code is:
- May 11, 2010 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
March, 2010 Maintenance Rollup
A PTF for 31-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: UK54541 (APAR: PM07167). The build date of the code is:
- February 15, 2010 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
January, 2010 Maintenance Rollup
A PTF for 31-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: UK53749 (APAR: PM00612). The build date of the code is:
- December 23, 2009 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
November, 2009 Maintenance Rollup
A PTF for 31-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: UK51963 (APAR: PK98549). The build date of the code is:
- November 6, 2009 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
July, 2009 Maintenance Rollup
A PTF for 31-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: UK48410 (APAR: PK91160). The build date of the code is:
- July 7, 2009 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
April, 2009 Maintenance Rollup
A PTF for 31-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: UK45902 (APAR: PK85074). The build date of the code is:
- April 8, 2009 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
December, 2008 Maintenance Rollup
A PTF for 31-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: UK42388 (APAR: PK77007). The build date of the code is:
- December 10, 2008 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
August, 2008 Maintenance Rollup
A PTF for 31-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: UK39047 (APAR: PK70615). The build date of the code is:
- August 11, 2008 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
July, 2008 Maintenance Rollup
A PTF for 31-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: UK38281 (APAR: PK69074). The build date of the code is:
- July 10, 2008 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
March, 2008 Maintenance Rollup
A PTF for 31-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: UK34636 (APAR: PK59120). The build date of the code is:
- March 15, 2008 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
October, 2007 Maintenance Rollup
A PTF for 31-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: UK30941 (APAR: PK55819). The build date of the code is:
- October 25, 2007 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
August, 2007 Maintenance Rollup
A PTF for 31-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: UK27953 (APAR: PK49493). The build date of the code is:
- August 1, 2007 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
May, 2007 Maintenance Rollup
A PTF for 31-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: UK25371 (APAR: PK40164). The build date of the code is:
- May 11, 2007 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
February, 2007 Maintenance Rollup
A PTF for 31-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: UK21775 (APAR: PK38082). The build date of the code is:
- February 1, 2007 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
October, 2006 Maintenance Rollup
A PTF for 31-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: UK18621 (APAR: PK32190). The build date of the code is:
- October 2, 2006 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
May, 2006 Maintenance Rollup
A PTF for 31-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: UK14829 (APAR: PK25468). The build date of the code is:
- May 24, 2006 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
March, 2006 Maintenance Rollup
A PTF for 31-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: UK12779 (APAR: PK21538). The build date of the code is:
- March 2, 2006 for:
- z/OS V1.6 and above
- z/OS.e V1.6 and above
Who Should Use this SDK5 Product
IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N98) will be attractive primarily to customers and ISVs whose Java applications are not constrained by 31-bit addressing and who wish to use Java SDK5. 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 2 Technology Edition, V5 (5655-N99).
The two products are complementary, have the same SDK5 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)?
- you are not storage constrained by 31-bit addressing.
- your ISV or other middleware requires the 31-bit product.
- your customers are comfortable using the existing SDK5 product.
What are the main reasons for going to the 64-bit product?
- your applications are storage constrained by 31-bit addressing.
- 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.
|
November, 2011 Maintenance Rollup