IBM Mainframe Forum Index
Log In
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register

Storage violation error while calling a program in CICS

IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message

New User

Joined: 24 Aug 2012
Posts: 7
Location: india

PostPosted: Tue Aug 28, 2012 7:06 pm
Reply with quote


This is being my first post not sure I am putting it in right place and in right way :

I need some help from you guys as I am stuck with a storage violation issue in a Ingenium program.

I am looking after a issue where I am getting the below abend in program ABC when it is trying to call XYZ.
I tried to put XPEd on ABC but not sure why when it goes to call XYZ from ABC it does not go to XYZ.

04.54.18 STC30539 +DFHSM0102 BCICS26 A storage violation (code X'0D11') has been detected by module DFHSMMF.
04.54.18 STC30539 +DFHME0116 BCICS26 742
742 (Module:DFHMEME) CICS symptom string for message DFHSM0102 is
742 PIDS/5655S9700 LVLS/660 MS/DFHSM0102 RIDS/DFHSMMF PTFS/UK71156
742 PRCS/00000D11

1 RS1 8022 20120823045418 CEE0802C Heap storage control information was damaged.
RS1 8022 20120823045418 From compile unit CSDF0570 at entry point CSDF0570 at compile unit offset +000176A6 at entry offset +000176A6 at address
RS1 8022 20120823045418 2465E6A6.

Any help is highly appreciated.

Back to top
View user's profile Send private message
Robert Sample

Global Moderator

Joined: 06 Jun 2008
Posts: 8584
Location: Dubuque, Iowa, USA

PostPosted: Tue Aug 28, 2012 7:33 pm
Reply with quote

Did you look up the CEE0802C message in the manual? It says
CEE0802C Heap storage control information was damaged.

Explanation: Internal control information saved in header records within the heap was damaged.

Programmer Response: Ensure that your program does not write data to an area larger than the original allocation. For example, allocating a 100 byte area and then writing 120 bytes to this area could cause damage to a storage header.

System Action: No storage is allocated. A severity 4 condition is signaled and the application is terminated.

Symbolic Feedback Code: CEE0P2
which gives you a starting place for your debugging. Check copy books, in particular, since if more variables were added to a copy book and not all programs were compiled with the new copy book, that alone could cause the storage violation.

And if the heap storage is damaged, program XYZ may never have gotten started, you know.

If "an Ingenium program" means that either ABC or XYZ are programs from a vendor, why did you not go to the vendor FIRST for assistance?
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator

Joined: 14 Jan 2008
Posts: 2504
Location: Atlanta, Georgia, USA

PostPosted: Thu Aug 30, 2012 3:32 am
Reply with quote

Webcast replay: Debugging Storage Violations in CICS. Includes presentation in PDF format -

Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> ABENDS & Debugging


Similar Topics
Topic Forum Replies
No new posts VB file copy COBOL program gives erro... COBOL Programming 3
No new posts AUTHORIZED database error in HALDB IMS DB/DC 2
No new posts Cobol program to determine the sequen... COBOL Programming 2
No new posts Issue with CA Copycat-IGD17100I UNEXP... CA Products 5
No new posts Expected data is not coming up on Fir... CICS 2
Search our Forums:

Back to Top