We IPL'd the production lpar yesterday.
We put the Intertest and Symdump release 11 datasets into the APF authorization and LNKLST.
Also, initialized v11 datasets in CARIMPRM.
The CICS started tasks, however, still reference the v10 datasets.
Some messages from CICS output:
+CASD6049 SYMDUMP V10.0000 COLD ASM 12/13/2017 15.45
+CASD6804 CA SymDump has initialized successfully
DFHAP0001 CICSPA1 An abend (code 0C7/AKEA) has occurred at offset X'000078A8' in module SDHBRMLP.
DFHME0116 CICSPA1
(Module:DFHMEME) CICS symptom string for message DFHAP0001 is
PIDS/5655S9700 LVLS/670 MS/DFHAP0001 RIDS/DFHSRP PTFS/UK76215
AB/S00C7 AB/UAKEA RIDS/SDHBRMLP ADRS/000078A8
DFHDU0205 CICSPA1 A SYSTEM DUMP FOR DUMPCODE: AP0001 , WAS SUPPRESSED BY THE DUMP TABLE OPTION FOR THIS DUMPCODE
Why is this system dump being suppressed?
Z/OS
CICS
Symdump CICS only captures Transaction dumps and will not capture System dumps which is what the AP0001 is.
Symdump CICS only captures Transaction dumps and will not capture System dumps which is what the AP0001 is.
Symdump CICS does have the ability to suppress AP0001 dumps on the SYMI transation configuration screen parameter
Suppress AP0001 dumps: Y (Y,N)
Symdump CICS gets invoked at the CICS global user exit XDUREQ. You can use the transaction IGLU to see the CICS global user exits. My example IGLU below is for CTS 5.4 program IN71 EXIT.
EXIT NAME PROGRAM ENTRY NAME ADDRESS STATUS
XDUREQ IN71EXIT IN71EXIT 800AA000 STARTED
The format of the Suppression message DFHDU0205 the case was opened with tells me CICS suppressed the AP0001 dump
DFHDU0205 CICSPA1 A SYSTEM DUMP FOR DUMPCODE: AP0001 , WAS SUPPRESSED BY THE DUMP TABLE OPTION FOR THIS DUMPCODE
If Symdump CICS suppressed the AP0001 dump you would see the suppression was done by the XDUREQ global user exit program IN71EXIT with the message format below.
DFHDU0205 A11IC4S5 A SYSTEM DUMP FOR DUMPCODE: AP0001 , WAS SUPPRESSED BY THE XDUREQ USER EXIT