RP/MSQ 5.0 (VMS) - V4 client receiving large messages gets 32 nulls before first message (Doc ID 775887.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle MessageQ / MessageQ / 5
Information in this document applies to any platform

Goal

Using V4.0 Client code on Windows, customer attaches to queue 195 as primary queue (SQ in QCT). Then configure
pams_get_msg with PSYM_MSG_LARGE,  and large_area_len greater than 0x8000 (32769 or greater). The first message
received has 32 nulls prepended to message. Subsequent messages are OK. If detach/reattach, again first message
received has 32 nulls prepended to message. 

If the  large_area_len less than 0x8000 (32768 or less), the error does not occur.

These must be the first clients to attach after the CLS is started. Once the CLS has received a pams_get_msg from a
client with parameters, large_area_len set below 0x8000, or without PSYM_MSG_LARGE, then all subsequent attaches by
other client processes, followed by any pams_get_msg (even with large_area_len greater than 0x8000) no longer have
this symptom for the first message receive.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms