Upgrading ACF2 or z/OS release, what needs to be done?
Article ID: 37752
ACF2ACF2 - z/OSACF2 - MISC
When upgrading ACF2 or z/OS release, is there a need to convert the ACF2 databases or re-assemble and link exits? Are there any other migration considerations?
Release: Component: ACF2MS
This is in regards to upgrading ACF2 or a/OS releases.
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.
For z/OS upgrades the ACF2/JES2 or ACF2/JES3 interface need to be re-assembled and linked. Sample JCL members JXBUMJ2 and JXBUMJ3 in the ACF2 installation CAX1JCL0 library can be used to re-assemble and link the JES2 and JES3 interface respectively.
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