Heap of something...

I reported this error to IBM about one of their LPP's having this in it's
joblog.
MCH6902-The requested heap space operation is invalid.
C2M1212-The pointer parameter passed to free or realloc is not valid.

Message ID . . . . . . : MCH6902 Severity . . . . . . . : 40
Message type . . . . . : Escape
Date sent . . . . . . : 02/18/08 Time sent . . . . . . : 14:48:46

Message . . . . : The requested heap space operation is invalid.
Cause . . . . . : The requested heap space operation is invalid. The
heap
space identifier is -1. The activation group mark is 17. The activation

group mark will be zero if the heap space is not associated with an
activation group. The error type is 2. The error type indicating why the

heap space request is invalid is defined as follows:
0001-Attempt to destroy the default heap space;
0002-Attempt to free or reallocate heap space storage that is not
allocated;

From program . . . . . . . . . : #hmfremi

Instruction . . . . . . . . : 000254

To program . . . . . . . . . . : NFXRT
To library . . . . . . . . . : QDOMFXD
To module . . . . . . . . . : DLL_A
To procedure . . . . . . . . : dllfree
To statement . . . . . . . . : 2

Time sent . . . . . . . . . . : 14:48:46.761624

Thread . . . . . . . . . . . . : 0000008E



Message ID . . . . . . : C2M1212 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 02/18/08 Time sent . . . . . . : 14:48:46


Message . . . . : The pointer parameter passed to free or realloc is not

valid.
Cause . . . . . : The pointer parameter passed to free or realloc was
not
valid. This caused your function call to fail.
Recovery . . . : Correct the invalid pointer parameter being passed to
free
or realloc.
Technical description . . . . . . . . : The value of the pointer passed
to
free or realloc is X'8000000000000000D98858762C0021C0'.

From program . . . . . . . . . : QC2UTIL1

From library . . . . . . . . : QSYS
From module . . . . . . . . : QC2ALLOC
From procedure . . . . . . . : send_C2M1212__FPv
From statement . . . . . . . : 8

To program . . . . . . . . . . : NFXRT
To library . . . . . . . . . : QDOMFXD
To module . . . . . . . . . : DLL_A
To procedure . . . . . . . . : dllfree
To statement . . . . . . . . : 2


Basically I was told not to worry about it. Then again, this is what the
person I talked to heard from the team that supports this out of
Guadalahara.
Is this like normal? Would this error be comparable to someone doing a
DLTF QTEMP/MYFILE (to make sure it's not there before creating it) and a
generic monmsg with no removal of the message from the job message queue?
Or is this really bad form?


Rob Berendt