CA Symdump Batch Symdump for CICS and Symdump System r10.0 or r11.0 and IBM APAR OA54807 compatibility

Products

• SymDump for CICS
• SymDump Batch

Issue/Introduction

This APAR introduces the OSPROTECT system parameter which specifies the operating system protection mode for unauthorized programs and users. With this apar applied, software must no longer reference the IHAPSA field PSASTAK because the 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.The PSASTAK is related to recovery management and the apar itself changes the definintion of the PSASTAK field in module IHAPSA  to PSACSTK and software continuing to reference PSASTAK can receive a S0C4. 

Is there any specific fix for SYMDUMP (System, Batch and CICS) for the Meltdown mitigation fixes from IBM - APAR OA54807?

Environment

Symdump for CICS, Symdump Batch, and/or Symdump System installed in a z/OS 2.1, 2.2,or 2.3 environment with IBM APAR OA54807 applied.  

Resolution

OA54507 has no impact on CA Symdump for CICS, Symdump Batch, or CA Symdump System

Additional Information

Reference the IBM Knowledge Center for descriptions of

• OA54807
• PSASTAK

Other products did get the same question and Knowledge Documents produced.
Such as:

• KB000108908   Is CA Common Services for z/OS r14.1 impacted by IBM Apar OA54507
• KB000108847   Does CA Datacom/AD get impacted by IBM Apar OA54807