Question & Answer
Question
Why am I only getting message DFHSM0102 when I use CSFE DEBUG to activate the CICS storage violation trap? I expected to get DFHSM0103 when the storage violation trap detected the storage violation.
Here are the messages I see in the CICS log:
09.31.16 S0018993 +DFHSM0102 CICSAPPL A storage violation (code X'0F0C') has been detected by module DFHSMAR.
09.31.16 S0018993 +DFHME0116 CICSAPPL 121
121 (Module:DFHMEME) CICS symptom string for message DFHSM0102 is
121 PIDS/5655Y0400 LVLS/680 MS/DFHSM0102 RIDS/DFHSMAR PTFS/UI17288
121 PRCS/00000F0C
09.31.16 S0018993 +DFHDU0201 CICSAPPL ABOUT TO TAKE SDUMP. DUMPCODE: SM0102 , DUMPID: 1/0013
09.31.17 S0018993 IEA794I SVC DUMP HAS CAPTURED: 156
156 DUMPID=023 REQUESTED BY JOB (CICSAPPL)
Following is an example of the message I did not receive:
09.31.31 S0018993 +DFHSM0103 CICSAPPL 447
447 A storage violation (code X'0932') has been detected by the storage
447 violation trap. Trap is now inactive.
466 DUMP TITLE=CICS DUMP: SYSTEM=CICSAPPL CODE=SM0103 ID=1/0018
Answer
To properly invoke the SM CHECK function which you request using the CSFE DEBUG transaction, it requires the following 2 conditions to be met:
Master system trace flag must be ON, without this only exception trace entries are written
The EI trace entry should be set to at least "1" or "1-2"
The SYSTR=ON system initialization (SIT) parameter specifies the setting of the master system trace flag. SIT parameter STNTREI=(1) or STNTREI=(1,2) where EI is the application domain component abbreviation controls the level of standard tracing for the EI component. You can also use CETR to control trace and change these values after CICS is initialized.
The SM0103 dump will be triggered and storage checker will be turned off after the dump is taken.
Sharon Yang
IBM CICS Levek2 support
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
02 May 2016
UID
dwa1267727