A fix is available
APAR status
Closed as program error.
Error description
You receive the following storage violation message: DFHSM0102 A storage violation (code X'0E06') has been detected by module DFHSMMC2. The 0E06 error code indicates Invalid storage element for TP storage. A TIOA's storage accounting area or SAA has been overlaid. Here is the exception trace entry: *EXC* - SAA_check_failed_during_FREEMAIN_ALL_TP_at_address FUNCTION(FREEMAIN_ALL_TERMINAL) TCTTE_ADDRESS In order to get better documentation you activate the storage violation trap: CSFE DEBUG,CHKSTRM=CURRENT . There is problem with the trap where it will not check terminal storage, unless transaction isolation is active. Before checking terminal storage, code in DFHSMCK wants to be sure the task is running on the QR TCB. It compares the current TCB to SMA_QR_TCB, and if equal will validate the SAA's of the current tasks primary TCTTE. In this case field SMA_QR_TCB was zeros, so the checking of the TIOA's never occurred. Additional Symptom(s) Search Keyword(s): KIXREVDAM
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: Despite CSFE DEBUG,CHKSTRM=CURRENT * * running, when a storage violation of * * a TIOA occurs this is not detected. * **************************************************************** * RECOMMENDATION: * **************************************************************** To investigate a suspected storage violation of a TIOA, CSFE is run with parameters DEBUG,CHKSTRM=CURRENT to perform storage violation checking. DFHSMCK is executed and before performing a check of the TIOAs it tests to see if it is running under the QR TCB. However, if transaction isolation was not active at startup, the QR TCB pointer used in the test will not have been initialised, and as a result, DFHSMCK will not believe it is running under the QR TCB and consequently will not check the TIOAs. As such, if a storage violation occurs, this will not be detected, no exception trace entry will be made and no CICS system dump will be produced.
Problem conclusion
DFHSMDM has been modified such that the QR TCB pointer in the storage manager anchor block, is initialised regardless of whether transaction isolation is active or not at startup.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM94555
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-06
Closed date
2013-08-27
Last modified date
2015-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK97128
Modules/Macros
DFHSMDM
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R800 PSY UK97128
UP13/09/06 P F309
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 March 2015