On 19/02/2008, at 7:07 AM, rob@xxxxxxxxx wrote:
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?
I think it's bad form but then I think leaving unnecessary messages
in the job log is also bad form.
MCH6902 says the error type is 2 which means the code tried to free
or realloc heap space that isn't allocated. This can be caused by
freeing an already freed pointer or reallocing a freed pointer or
freeing or reallocing using a pointer from malloc/calloc that has
been messed with.
As far as I know the purpose of this message is to help developers
find code defects related to dynamic storage management--hence the
run-time converts the MCH6902 *ESCAPE into a C2M1212 *DIAG message.
If the message is a result of freeing an already freed pointer then
it will not cause a problem for the code and can be ignored (but one
hopes the developer will fix the root cause in a future release). If
it is caused by a failed realloc, or by a free or realloc on a 'bad'
pointer, then that will likely manifest as 'peculiar' behaviour.
I think some investigation as to the cause of the problem should be
performed before saying "don't
worry about it". Perhaps they've done that and know it's OK hence the
response?
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
