I am upgrading ACF2 from release 15 to release 16. Do I need to convert the ACF2 databases?

book

Article ID: 37752

calendar_today

Updated On:

Products

CA ACF2 CA ACF2 - z/OS CA ACF2 - MISC

Issue/Introduction

When upgrading ACF2 from release 15 to release 16, is there a need to convert the ACF2 databases?
In the installation document for version 16.0, there is information about the migration operations, what needs to be done when migrating from version 15.0 to version 16.0 ?
Are there any other migration considerations?

 

Environment

Release:
Component: ACF2MS

Resolution

This is in regards to upgrading from ACF2 version 15.0 to 16.0.

  • There is no conversion process or maintenance needed to upgrade from ACF2 release 15.0 to 16.0. 
  • Any site defined ACF2 exits need to be re-assembled and linked.
  • No conversion of the ACF2 databases is required.
  • It is not recommended "implementing" any of the 16.0 enhancement changes until you are sure that you will   
    not be backing off of r16.
  • At IPL time you may get ACF79600 messages that some of the GSO records are outdated.  That is expected for any ACF2 16.0 GSO record enhancement changes had been made. To bring in the new record, all you need to do is make a change to record field, even if the change is exactly the same. Sample messages:

    ACF79600 WARNING - OPTS IS AN OUTDATED GSO RECORD FOR SYSID xxxx
    ACF79600 WARNING - BACKUP IS AN OUTDATED GSO RECORD FOR SYSID xxxx 
    ACF79600 WARNING - CLASMAP IS AN OUTDATED GSO RECORD FOR SYSID xxxx