HIPER SO13422 (R13.5) and SO13442 (R13.0)
Article ID: 192166
Updated On:
Products
OPS/MVS Event Management & Automation
Issue/Introduction
We have received notification of a HIPER SO13422. (BROADCOM NOTE: This also applies to R13.0 Hiper SO13442),
We'd like to know whether or not we are currently exposed to the issue that the HIPER is intended to fix? We would also like to know that if we are exposed to the issue, is there anything we can do to mitigate the risk of the issue occurring as rolling this fix out to production environments could take a while as a result of change restrictions we currently have in place? Following on from the previous question, what is likely to trigger the issue?
We'd like to know whether or not we are currently exposed to the issue that the HIPER is intended to fix? We would also like to know that if we are exposed to the issue, is there anything we can do to mitigate the risk of the issue occurring as rolling this fix out to production environments could take a while as a result of change restrictions we currently have in place? Following on from the previous question, what is likely to trigger the issue?
Environment
Release : 13.5
Component : OPS/MVS
Resolution
SO13422 hiper fix prevents the product from going into emergency shutdown due to recursive s001 abends attempting to issue error messages within the OSF server. We do not have any further information on what caused the recurssive abends that the reporting customer saw, but they could come from seemingly anywhere. Should you ever encounter a similar abend situation, without the fix OPS/MVS will terminate instead of staying up as it should. There is no way to mitigate the situation.
The exposure has apparently been there for a while, and could potentially happen to anyone, although it is rare.
The exposure has apparently been there for a while, and could potentially happen to anyone, although it is rare.
Feedback
Yes
No
Powered by
