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?
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.
Here on my LPAR the default for TERMTHDACT is
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
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)'
Please add this PARM to your abending program.
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.