heap storage control information was damaged, 4038 abend.

[Prakash Jha]

My team is trying to trigger an IMS transaction from a Java screen. However, we're getting the following error :

Code: Select all

CEE0802C Heap storage control information was damaged. 

I'm not sure where should we start analysing this error? Can some one please guide on this?

[William Collins]

You start by looking up the message, https://www-01.ibm.com/support/knowledg ... s00608.htm. Then you work out where in the program the problem occurs, and whether it is in IMS or Java. Then you locate the problem, which is going to be something overwriting something it shouldn't, or, perhaps, something badly broken with the way a program is called, or a failed linkedit and attempt to use that program. Or something else.

It's a tricky one :-)

[Prakash Jha]

It is actually a tricky one. We have taken our changes back to teh test resion and are investigating on all the posibilities but looks it will take time to get resolution.

Does anyone of you have more suggestions to tell what else can we do rectify this error?

[Robert Sample]

If you get a system dump, work with your site support group to use IPCS to analyze the dump. The problem with this type of error is that the program detecting the heap storage control information damage may have nothing to do with the program that actually caused the damage.

Generally, there's a storage overlay issue -- a program is putting more data into the heap than it should. Storage overlay issues are notoriously difficult to resolve because the cause of the problem may be very distant (in time and memory both) from when the issue is detected. You may need to have the site support group contact IBM for debug assistance as well, depending upon the specifics of the issue.

[William Collins]

When you say you've taken your changes back to the Test, does that mean they worked there originally and failed wherever else you put them?

The message is from Language Environment. LE uses the heap for allocation of program storage. Other things can use the heap. LE has gone to the heap to do "something" and found that it can't because the control information which exists does not make sense again what has been requested.

If it works in test and not elsewhere, look for the set-up differences between the two.

If it works nowhere, look at the IMS and LE setups, consulting the IMS and JAVA installation/customisation guides.

Does the JAVA program work if it doesn't attempt to actually contact IMS? A Hello World-type? This is the first JAVA-contacting-IMS at your site?

The possibilities are too many to deal with on a Forum. You'll probably end up hitting it by tiral-and-error, or IBM, or by paying someone who knows what to do with such a thing.