Bypassing affinity management during the IMS ESTAE process
If you use IMS to manage generic resource affinities, you can control whether or not IMS uses or bypasses the VTAM® generic resource logic in the IMS ESTAE exit. To use the IMS ESTAE process, indicate GRESTAE=Y for terminal sessions and GRMESTAE=Y for MSC link sessions in the DFSDCxxx IMS.PROCLIB member data set.
GRESTAE=Y or GRMESTAE=Y indicates that IMS should follow the existing ESTAE logic to delete affinity for nodes where no status remains before closing the ACF/VTAM ACB. GRESTAE=N or GRMESTAE=N indicates that IMS should close the ACF/VTAM ACB immediately to expedite IMS termination, and leave affinity for all nodes set.
IMS VTAM generic resource logic in the IMS ESTAE exit attempts to delete generic resource affinity if no terminal or MSC link status remains. The IMS ESTAE routine uses the VTAM delete affinity force option (ENDAFFNF) which does not require the sessions to be disconnected from the VTAM terminal first.
The following table summarizes how generic resource affinities are managed based on whether affinities are VTAM or IMS managed and which GRESTAE options are indicated in the DFSDCxxx IMS.PROCLIB member data set.
| Affinity manager | GRESTAE/GRMESTAE option | Generic resource affinities management |
|---|---|---|
| IMS | Y | IMS manages generic resource affinities, including
during ESTAE processing. IMS resets affinity during the ESTAE process that occurs during IMS failure. |
| IMS | N | IMS manages generic resource affinities, except
during ESTAE processing. IMS does not reset affinity during the ESTAE process that occurs during IMS failure. |
| VTAM | Y or N | VTAM manages generic resource affinities. |