Symdump Batch does not capture LE U4039 abends?

Document ID : KB000122457
Last Modified Date : 05/12/2018
Show Technical Document Details
Issue:
We have CA Symdump Batch installed on our LPAR. A production job (COBOL program) abended with USER COMPLETION CODE=4039 REASON CODE=00000000, but no dump was captured by Symdump Batch.
Why was the dump not captured? Can we configure Symdump batch to capture U4039 abends?
 
 
Environment:
Z/OS
Cause:
As per the documentaion the LE option TERMTHDACT(UADUMP) generates a U4039 abend when an unhandled condition occurs of severity 2 or greater. CA SymDump Batch will not report on this abend.
 
Resolution:
Override TERMTHDACT=(DUMP)

Here on my LPAR the default for TERMTHDACT is

TERMTHDACT(TRACE,,96)
 
I have a test program TSTCASRA that abends by design. Below is the EXEC statement to run the program
 
//STEP1 EXEC PGM=TSTCASRA
 
I can see the for TERMTHDACT on the output is
 
TERMTHDACT(TRACE,,96)
 
When I add the PARM card below to the EXEC statement I see it overrides the TERMTHDACT to DUMP.
 
//STEP1 EXEC PGM=TSTCASRA,PARM='/TERMTHDACT(DUMP)'
 
TERMTHDACT(DUMP,,96)
 
Please add this PARM to your abending program.
PARM='/TERMTHDACT(DUMP)'
 
The client overrode the TERMTHDACT=(UADUMP) to TERMTHDACT=(DUMP) as shown above and the dump was captured. The client will change his LE option to TERMTHDACT=(DUMP) so U4039 abends are captured.