With IBM PTF UA96475 applied is there any concern with CA ACF2?
Software must no longer reference the IHAPSA field PSASTAK.
With this PTF, PSASTAK is no longer the beginning of the
normal FRR stack. PSACSTK is an existing pointer to the
beginning of the normal FRR stack.
Software that references PSASTAK must be converted to use
PSACSTK as the pointer to the normal FRR stack
Release : 16.0
Component : CA ACF2 for z/OS
CA ACF2 does not have any code referencing PSASTAK
and so is not affected by IBM PTF UA96475.
"z/OS HIS Sampling Work Unit Address
Macro IHAPPR maps the z/OS HIS sampling program parameter.
The program parameter bytes 0-3 contain a work unit address.
This APAR incompatibly changes the work unit address such
that some high and low order bits will contain state
information. Based on the work unit type, a
new work unit specific mask must be applied to remove the
work unit state and obtain the work unit address. Applying
the new work unit specific mask will yield the expected
result with and without the APAR.
The work unit specific masks are as follows:
Use this mask to isolate the WEB address for SRB mode
PPR_WU_ADDR_MASK_SRB EQU X'7FFFFFF8'
Use this mask to isolate the TCB address for task mode
PPR_WU_ADDR_MASK_TASK EQU X'00FFFFF8'
ACTION:
Software must no longer reference the IHAPSA field PSASTAK.
With this PTF, PSASTAK is no longer the beginning of the
normal FRR stack. PSACSTK is an existing pointer to the
beginning of the normal FRR stack.
Software that references PSASTAK must be converted to use
PSACSTK as the pointer to the normal FRR stack.
1 Apply service as noted in the dependency hold and any
related service from Independent Software Vendor products
to correct references to PSASTAK.
2 Scan code for software developed by your installation for
references to PSASTAK.
3 Convert references of PSASTAK to use PSACSTK as a pointer
to the normal FRR stack.
What you might see:
Software that continue to reference PSASTAK may experience
ABEND0C4 and other symptoms after this PTF is applied.)."