View previous topic :: View next topic |
Author |
Message |
tiger_wen Beginner
Joined: 04 Nov 2005 Posts: 12 Topics: 4
|
Posted: Mon Jan 19, 2009 2:05 am Post subject: HELP,I got 'Heap storage control information was damaged.' |
|
|
Plz refer to the following msg:
Quote: | Traceback:
DSA Addr Program Unit PU Addr PU Offset Entry E Addr E Off
1A5A93A0 CEEHDSP 1A3F1560 +0000497E CEEHDSP 1A3F1560 +00004
1A5A9208 CEEHSGLT 1A403558 +0000005C CEEHSGLT 1A403558 +00000
1A5A9158 CEEV#FRS 1A4DB6F0 +00000D60 CEEV#FRS 1A4DB6F0 +00000
1A5A90B0 CEEVFRST 1A4E6E30 +00000066 CEEVFRST 1A4E6E30 +00000
1A5A8ED0 IGZCFCC 1A5725D0 +000002CA IGZCFCC 1A5725D0 +00000
1A5A8DA0 G00U001B 1A301AD8 +0000045E G00U001B 1A301AD8 +00000
1A5A8BC0 IGZCFCC 1A5725D0 +000002CA IGZCFCC 1A5725D0 +00000
1A5A8730 G00D059 1A94BB58 +00005222 G00D059 1A94BB58 +00005
1A5A8550 IGZCFCC 1A5725D0 +000002CA IGZCFCC 1A5725D0 +00000
1A5A7BE8 G00A007 1A778B08 +00015FB6 G00A007 1A778B08 +00015
1A5A7A08 IGZCFCC 1A5725D0 +000002CA IGZCFCC 1A5725D0 +00000
1A5A7710 G00A035 1A76C538 +00000D86 G00A035 1A76C538 +00000
1A5A7530 IGZCFCC 1A5725D0 +000002CA IGZCFCC 1A5725D0 +00000
1A5A7030 G00B002B 1A32CD10 +00002896 G00B002B 1A32CD10 +00002
Condition Information for Active Routines
Condition Information for CEEHSGLT (DSA address 1A5A9208)
CIB Address: 1A5A9CB0
Current Condition:
CEE0802C Heap storage control information was damaged.
Location:
Program Unit: CEEHSGLT Entry: CEEHSGLT Statement: Offset: +0000005C
Storage dump near condition, beginning at location: 1A4035A4
+000000 1A4035A4 F010D20B D0801000 58A0C2B8 58F0A01C 05EFD20B D098B108
|
Any comments is welcome.Thanks in advance! |
|
Back to top |
|
|
dbzTHEdinosauer Supermod
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
|
Posted: Mon Jan 19, 2009 9:59 am Post subject: |
|
|
tiger,
unfortunately I have had no experience with this error,
but I have experience finding error explanations.
Quote: |
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
|
in the event that you don't have the URL for IBM's z/OS error message lookup:
http://www-03.ibm.com/systems/z/os/zos/bkserv/lookat/ _________________ Dick Brenholtz
American living in Varel, Germany |
|
Back to top |
|
|
|
|