I got S04E abends in DB2 stored procedure STCs pointing to ACF04DSR+x'220' reason code 00E50013. Why was a dump produced?

Article Id: 39472
Status: Published
Updated On: 14-02-2018 07:55
Legacy Id: TEC1471316
Products:
CA ACF2 , CA ACF2 - DB2 Option , CA ACF2 for zVM , CA ACF2 - z/OS , CA ACF2 - MISC , CA PanApt , CA PanAudit
Issue/Introduction:

Problem:

I received the following abend in a DB2 stored procedure started task.

CCSR010E ACF9C000 S04E at 2A2910D8 LMOD ACF9C000 CSECT ACF04DSR +000220 DB2CSP01 STARTING IEFPROC 
CCSR021I OWNER = CA ACF2 R15.0 
CCSR022I MODULE = ACF04DSR FMID = CAX1F00 RMID = CAX1F00 
CCSR060I BREAKING EVENT ADDRESS: 00000000 00FF66F2 
CCSR061I PSW: 07040000 80000000 00000000 2A2910D8 
CCSR062I ILC: 02 INTERRUPT CODE: 78 
CCSR067I COMPLETION CODE S04E REASON CODE 00E50013 

The IBM documented description of this reason code states That no dump is produced
why did I get a dump?

 

Resolution:

00E50013                                

 Explanation                                                                

 A DB2 execution unit has been abended. This abend code must ultimately be
 issued by resource managers when the CANCEL exit is driven as a result of a suspend request.                                                           

 System action                                                              

 The agent cancel processing continues.  
 Normally, this situation does not result in a dump. However, a dump might  
 result if the situation is encountered by other resource managers, outside 
 of DB2. When that happens, the dump can be ignored or suppressed.    

 

In this case, ACF2 for z/OS is the "other resource manager".
Our estae gets control and causes a dump to occur.
This dump can be ignored. ACF2 is not the cause of the abend.

 

    

                                                                            

Environment:

Release:
Component: ACF2MS