Does CA Datacom - AD gets impacted by IBM APAR OA54807
Article ID: 108847
Updated On:
Products
Datacom
DATACOM - AD
CIS
COMMON SERVICES FOR Z/OS
90S SERVICES
DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
COMMON PRODUCT SERVICES COMPONENT
Common Services
CA ECOMETER SERVER COMPONENT FOC
EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES
INFOCAI MAINTENANCE
IPC
UNICENTER JCLCHECK COMMON COMPONENT
Mainframe VM Product Manager
CHORUS SOFTWARE MANAGER
CA ON DEMAND PORTAL
CA Service Desk Manager - Unified Self Service
PAM CLIENT FOR LINUX ON MAINFRAME
MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
GRAPHICAL MANAGEMENT INTERFACE
WEB ADMINISTRATOR FOR TOP SECRET
Xpertware
Issue/Introduction
Any Software impact when applying IBM APAR OA54807?
We would like to know does CA Datacom - AD will get impacted by applying the IBM APAR OA54807.
It says in the APAR as following 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..
We would like to know does CA Datacom - AD will get impacted by applying the IBM APAR OA54807.
It says in the APAR as following 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..
Environment
z/os, CA Datacom/DB or AD 14.0 and higher
Resolution
Operating System control block PSA was affected by IBM APAR OA54807.The field in the control block called PSASTAK was specifically changed.
Since Datacom/DB does not reference the field, it should not be impacted by this APAR.
Since Datacom/DB does not reference the field, it should not be impacted by this APAR.
Additional Information
Other products did get same question and Knowledge Documents produced.
Such as:
KB000108098 Is CA Common Services for z/OS r14.1 impacted by IBM APAR OA54807
KB000108117 IBM PTF consideration
KB000108350 Any issues or maintenance required for MIM…
Such as:
KB000108098 Is CA Common Services for z/OS r14.1 impacted by IBM APAR OA54807
KB000108117 IBM PTF consideration
KB000108350 Any issues or maintenance required for MIM…
Feedback
Yes
No
Powered by
