SOLVE:ACCESS: IBM APAR OA54807 COMPATIBILITY
Article ID: 113239
Updated On:
Products
SOLVE:Operations Automation
SOLVE:Access Session Management
SOLVE:FTS
SOLVE
Issue/Introduction
From cust: Is there any specific fix for the SOLVE:Access Session Management
for MVS product for the meltdown mitigation fixes from IBM -- APAR OA54807?
for MVS product for the meltdown mitigation fixes from IBM -- APAR OA54807?
Environment
OS: z/OS.
Resolution
From L2: APAR OA54807 only applies to unauthorized programs. SACCES must be
run from an APF-authorized library or it will terminate at initialization with N00517.
From CT: Just being a little more specific about the item that most concern us:
According to one of the APAR HOLD actions ISVs must no longer reference
the IHAPSA field PSASTAK. With OA54807 PSASTAK is no longer the be-
ginning 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. Is SACCES subjected to this?
From L2: We have no references to PSASTAK in our code--not a concern.
run from an APF-authorized library or it will terminate at initialization with N00517.
From CT: Just being a little more specific about the item that most concern us:
According to one of the APAR HOLD actions ISVs must no longer reference
the IHAPSA field PSASTAK. With OA54807 PSASTAK is no longer the be-
ginning 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. Is SACCES subjected to this?
From L2: We have no references to PSASTAK in our code--not a concern.
Feedback
Yes
No
Powered by
