Any Impact Of IBM APAR OA56279 On CA Top Secret?

Document ID : KB000129648
Last Modified Date : 18/03/2019
Show Technical Document Details
Question:
IBM Hiper APAR OA56279 has the following.

APAR Identifier ...... OA56279 Last Changed ........ 19/03/01 
CICS ABEND0C4 PIC11 ICHSGF00 SGFSIMPL SGFBUFFR ICRX IRRPICRX 
PIC4 ICHRST00 CESTCKEY ICHFRN00 

Symptom ...... AB ABEND0C4 Status ........... CLOSED PER 
Severity ................... 1 Date Closed ......... 19/01/23 
Component .......... 5752XXH00 Duplicate of ........ 
Reported Release ......... 7A0 Fixed Release ............ 999 
Component Name RACF Special Notice HIPER 
Current Target Date ..19/03/15 Flags RESTART/BOOT/IPL 
SCP ................... FUNCTIONLOSS 
Platform ............ 

Status Detail: SHIPMENT - Packaged solution is available for 
shipment. 

PE PTF List: 

PTF List: 
Release 7A0 : UA98409 available 19/02/13 (F902 ) 
Release 7B0 : UA98408 available 19/02/13 (F902 ) 


Parent APAR: 
Child APAR list: 


ERROR DESCRIPTION: 
CICS alerts of an ABEND0C4 via the following DFHXS0001 message: 

DFHXS0001 MYAPPLID An abend (code 0C4/AKEX) has occurred at 
offset X'FFFF' in module DFHXSAD. 
DFHME0116 MYAPPLID 
(Module:DFHMEME) CICS symptom string for message 
DFHXS0001 is 
PIDS/5655Y0400 LVLS/700 MS/DFHXS0001 RIDS/DFHXSAD 
PTFS/UI38813 AB/S00C4 AB/UAKEX ADRS/0000FFFF 

This abend (and accompanying message) is repeated numerous 
times. After the repeated abends, CICS enters an SOS state due 
to related failures in RACF recovery preventing resource 
cleanup. Other subsystems (including TSO and Monitor) also stop 
responding. CICS environment was recycled to relieve the 
condition. 

ANALYSIS: A review of the CICS dump collected showed that the 
ABEND0C4 RSN11 had occurred in RACF module ICHSGF00+2C,HRF77B0. 
CICS had called RACROUTE VERIFY, passing in an ICRX. 

During recovery for this ABEND, ICHRST00 gets control and takes 
an ABEND0C4 RSN4 at ICHRST00+B14,UA93049 before it is able to 
request an SVC Dump. 


LOCAL FIX: 
N/A 


PROBLEM SUMMARY: 
**************************************************************** 
* USERS AFFECTED: * 
* All users of RACF at z/OS 2.2 and higher. * 
**************************************************************** 
* PROBLEM DESCRIPTION: * 
* IRRRCK02 does not call ICHSGF00 correctly in all cases. * 
**************************************************************** 
* RECOMMENDATION: * 
**************************************************************** 
IRRRCK02 does not call ICHSGF00 correctly in all cases. 


PROBLEM CONCLUSION: 
IRRRCK02 has been changed to call ICHSGF00 properly.

Does this affect CA Top Secret? 
Answer:
The module the abends are occurring in (ICHSGF00) is a RACF module, so this shouldn't be a problem with CA Top Secret. We don't have any reports of problems related to this APAR.