COBOL - Group home

COBOL 4.2, 5.1 & 5.2, ABO 1.2 End of Service Dates

By Dan Zhang posted Thu April 02, 2020 12:43 PM

  

On Feb 5, 2019, IBM announced the end of service dates (revised announcement for v4 here and revised announcement for v5 here) for Enterprise COBOL v4.2, Enterprise COBOL v5.1, Enterprise COBOL v5.2 and ABO v1.2. 

 

Products to be withdrawn from service on April 30, 2020:

  • IBM Enterprise COBOL for z/OS                                 5.1.x    5655-W32
  • IBM Enterprise COBOL Developer Trial for z/OS        5.1.x    5655-TRY
  • IBM Enterprise COBOL for z/OS                                 5.2.0    5655-W32
  • IBM Enterprise COBOL Developer Trial for z/OS        5.2.0    5655-TRY
  • IBM Enterprise COBOL Value Unit Edition for z/OS    5.2.0    5697-ECV
  • IBM Automatic Binary Optimizer for z/OS                    1.2.0    5697-AB1

Product to be withdrawn from service on April 30, 2022:

  • IBM Enterprise COBOL for z/OS                                  4.2.0    5655-S71

 

Are extensions available?

For an additional fee extended support will be available after the end of support (EOS) dates for these products.

 

What do the COBOL EOS dates mean?

Withdrawing service for Enterprise COBOL v4.2, v5.1 and v5.2 means clients can no longer open PMRs or get APAR fixes the COBOL compiler after the end of service dates become effective. Code compiled with these compilers will continue to run. In addition, the COBOL runtime, which is part of the z/OS Language Environment, will continue to be supported.

Clients who are currently still on COBOL v4.2 are encouraged to plan and start their migration to COBOL v6 as soon as possible. There are 24 months to complete the migration before COBOL v4 goes out of service. Plan your migration by attending a free COBOL Migration and Performance workshop - register here. View the latest workshop replay, where you will learn about tools like the IBM COBOL Migration Assistant interactive checklist.

 

How can I enhance migration to COBOL v6?

Clients can also enhance migration to COBOL v6 by using IBM Automatic Binary Optimizer for z/OS (ABO) to improve the performance of older compiled code. Use COBOL v6 for new development, maintenance and modernization, and use ABO to improve the performance of the COBOL modules without a recompilation plan. ABO optimizes existing compiled binaries for the latest IBM Z hardware.

Clients who are currently on COBOL v5.1 or v5.2 can easily upgrade to COBOL v6.3 since COBOL v6 uses the same technology base as COBOL v5.  MLC clients can continue to use COBOL v4.2 without support as long as the monthly charge is paid. Clients using COBOL v5 Value Unit Edition (VUE) with S&S coverage can upgrade to COBOL v6 VUE at no cost.

 

What do the ABO EOS dates mean?

Clients who are currently using Automatic Binary Optimizer (ABO) v1.2 with S&S can upgrade to Automatic Binary Optimizer v2.1.  Clients who have stayed current can upgrade at no cost. Withdrawing service for ABO v1.2 means clients can no longer open PMRs or get APAR fixes for the ABO v1.2 optimizer after the end of service date becomes effective. Modules optimized with ABO v1.2 will continue to run. The ABO runtime, which is part of the z/OS Language Environment, will continue to be supported.

 

If you have any questions, please contact Roland Koo (rkoo@ca.ibm.com).