Hi Paul,
Got the reason on why the message exit was working on the sender side of NT
but was not working on the receiver side which was on AIX. The code which
was setting the MQRFH2 header part of the message was setting the values in
the UNIX way for the MQLONGs which was Big Endian and the NT si
e for this to work.
Thanks in advance for your help.
Kind Regards
Aby Philip
-Original Message-
From: Paul Clarke
To: [EMAIL PROTECTED]
Sent: 9/5/02 12:31 PM
Subject: Re: Message exit length for alteration
>Thanks Paul,
>Will do it that way. I was thinking that at MQXR_TERM time
Clarke
To: [EMAIL PROTECTED]
Sent: 9/5/02 12:31 PM
Subject: Re: Message exit length for alteration
>Thanks Paul,
>Will do it that way. I was thinking that at MQXR_TERM time I would have
the
>exitBuffer address with me so that I could free it off..anyway this
looks
to
>be a solution.
>Thanks Paul,
>Will do it that way. I was thinking that at MQXR_TERM time I would have
the
>exitBuffer address with me so that I could free it off..anyway this looks
to
>be a solution. In my case the pointer would have to be reallocated for
every
>MQXR_MSG call because I would not know what was th
can check for
the memory already allocated and free the fellow.
Thanks Paul.
Kind Regards
Aby Philip
-Original Message-
From: Paul Clarke
To: [EMAIL PROTECTED]
Sent: 9/5/02 4:16 AM
Subject: Re: Message exit length for alteration
>Hi,
>I also noticed that in the documentation ther
>Hi,
>I also noticed that in the documentation there is a mention that the
>previous exitBuffer address is returned in the next invocation of the
>message exit, so I guess I can free the memory then...That should be
>fine...but in any case if there is something wrong with this approach...or
>if th
Hi,
I also noticed that in the documentation there is a mention that the
previous exitBuffer address is returned in the next invocation of the
message exit, so I guess I can free the memory then...That should be
fine...but in any case if there is something wrong with this approach...or
if there is
