MSQ/UNX - need documentation on client library backwards compatibility (Doc ID 765038.1)

Last updated on OCTOBER 19, 2023

Applies to:

Goal

PRODUCT:   BEA MessageQ
VERSION: 4.0A
PLATFORM: UNIX

ISSUE:

need documentation on client library backwards compatibility



The limitations on the use of the v4.0A with a v3.2B CLS should be
documented in the release notes or somewhere, even though they might
be obvious.  (The customer just got burned by a third-party library that used
the v4.0A "large message" put for all size messages).

The following is a section that is  documented in the MessageQ for Windows 
NT, V4.0A Client Release Notes.  The customer uses the Unix CL exclusively at this 
point in time,  so nobody has a copy of the NT documentation.

They would like a similar section documented in the UNIX V4.0A Release
Notes.

----------------------------------------------------------------------------------------------------------
MessageQ Server Compatibility

The MessageQ Client for Windows, Version 4.0A runs with all
MessageQ, Version 2.1 or higher message server implementations
with the following exceptions:

o The CLS Security Utility requires MessageQ for UNIX or MessageQ
  for Windows NT, Version 3.1 or later and MessageQ for OpenVMS,
  Version 4.0 or later.

o The Minimum Packet Protocol (MPP) requires MessageQ for UNIX or
  MessageQ for Windows NT, Version 3.1 or later.  MPP is not
  currently implemented on MessageQ for OpenVMS.

  The use of the following new Version 4.0A features requires a
  Version 4.0A MessageQ server:

  -    Large buffer-based and handle-based messages
  -    Self-describing messages
  -    Timeout parameters for pams_attach_q and
       pams_locate_q
  -    The pams_bind_q function and global naming
  -    Publish and subscribe

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.