Customers installing the PTF for PH31060 should also install PH36829 at the same time.
This affects customers at both the 10.1 and the 10.5 level.
Ref (a):
https://www.ibm.com/support/pages/apar/PH31060Ref (b):
https://www.ibm.com/support/pages/apar/PH36829 PH31060 fixed an incompatibility issue with the ARSUUPDT exit.
Unfortunately, at the same time it exposed an issue in some exits which was then resolved by PH36829.
Note the following in the HOLD ACTION for PH36829:
This sysmod updates INSTALLDIR/bin/exits/arsusec, arsuupdt, and
arsuupdt. If the installation has copied those to another
location, they will need to get copied again.
This sysmod updates SARSINST(ARSUSEC, ARSUPERM, and ARSUUPDT) to
allow them to call a COBOL program.
If you have been compiling
SARSINST(ARSUSECC or ARSUPERC) solely in order to call a COBOL
program named ARSUSECX, the supplied bin/exits/arsusec and
arsuperm will now do that without needing to compile ARSUSECC or
ARSUPERC.
If you have been compiling SARSINST(ARSUUPDC) only in
order to call a COBOL program named ARSUUPDX, the supplied
bin/exits/arsuupdt will now do that without needing to compile
ARSUUPDC.
If you are compiling SARSINST(ARSUSECC, ARSUPERC,
and/or ARSUUPDC) for other changes, the changes will need to get
reworked in the updated SARSINST(ARSUSECC, ARSUPERC, and/or
ARSUUPDC).In short, the PTFs for these two APARs should be installed together.
Of course, ensure any exits are tested before upgrading to production.