ACF3@ATH and ACF3@SGN DB2 exit re-link considerations for a Db2 data sharing group

Products

• ACF2 - z/OS
• ACF2
• ACF2 - MISC

Issue/Introduction

A Db2 data sharing group is using ACF2 customized exits ACF3@ATH and ACF3@SGN.
There is ACF2 maintenance that requires a re-link of these exit routines and it is planned to roll out the ACF2 maintenance at LPAR level one at a time.
What are the considerations for not rolling out ACF2 maintenance all at the same time for all systems in a Db2 data sharing group? 

Environment

Release : 16.0

Component : ACF2 for z/OS

Resolution

The important thing to remember is that whatever Db2 exit library that is pointed to at a Db2 level must match the ACF2 maintenance level on the system. If they do not match, there are various types of abends that can be seen depending on the maintenance.

If it is planned to not have the same level of ACF2 maintenance on all LPARs in a data sharing group, then separate Db2 exit libraries will need to be maintained for every environment.

The ACF3@ATH and ACF3@SGN that are loaded at Db2 startup cannot be modified by the user address space, meaning a batch job cannot point to a different Db2 exit library. If the routines are not in the prefix.SDSNEXIT library, it would require changes to the STEPLIB or JOBLIB concatenations in the Db2 start-up procedures.