Re: CEE0810 Error on Reallocate Statement

Lorraine,

This is in a SRVPGM and it happens at the fifth call to this SRVPGM?

What aparmaeters are passed to the procedure? vaues of variables wa, b2,
array.

IIRC, leaving a subprocedure destroys the local variables. Perhaps defining
it as STATIC may solve it.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 30-7-2008 at 10:22 Lorraine.Ford@xxxxxxxxxxx wrote:

One of our developers is running into a hard halt error, CEE0810, on a

reallocate statement. This is in a service program, which another

program is using CALLP to access. She has her pointer and array defined

as follows:

d array s 32a dim(32767)
d based(arrayPtr)
d arrayPtr s *

Does her initial allocation:

// allocate storage, if necessary
if wa = *zero;
wa = 100;
arrayPtr = %alloc(wa * 32);
endif;

And then reads records from a file using SQL. It's that data she's going

to store in the array. So, if it's determined she needs to store

more than 100 elements, the program attempts to reallocate:

if b2 > wa;
wa += 100;
arrayPtr = %realloc(arrayPtr:wa * 32);
endif;

The reallocate fails with CEE0810:
The starting address for reallocation is not valid.
Function check. CEE0810 unmonitored by PGMNAME at statement 0000000855,

instruction X'0000'

No one has any idea what the problem is, research has turned up nothing.

Could the problem be something like since this is a service program, and

it's on the 5th call to the service program that the reallocate logic is

executed, somehow the program has lost the location of the original

allocation so it doesn't know where to go to reallocate? There's no other

logic in the program that's manipulating the value of the pointer

other than the allocate and reallocate statements above.