SE39049: WEBSPHERE MQ PUTTING APPLICATION FAILS WITH 2030 (MQRC_MSG_TOO_BIG_FOR_Q) WHEN MESSAGE SEGMENTATION ALLOWED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • Enduser has the following definitions for a putting application
    (MQPUT):
    - Application buffer definition is 100 bytes
    .
       memcpy(md.Format,          /* character string format */
       MQFMT_STRING, (size_t)MQ_FORMAT_LENGTH);
       md.MsgFlags =  MQMF_SEGMENTATION_ALLOWED;
       md.Version  =  MQMD_VERSION_2;
       pmo.Options =  MQPMO_LOGICAL_ORDER; /* Logical Order */
       pmo.Version =  MQPMO_VERSION_2;
    .
    - transmission queue has a maximum message length of 50
    .
    For WebSphere MQ V6 and V7, the putting application fails with
    reason code 2030 (MQRC_MSG_TOO_BIG_FOR_Q) when putting to a
    transmission  queue via a remote queue definition. If the
    enduser puts a message to a normal local queue there is no
    failure.
    .
    Additional Keywords: XMITQ segmentation allowed MsgFlags MQMD
    message flags MAXMSGL max maximum length
    .
    

Local fix

  • Set the maximum message length (MAXMSGLEN) value back to it
    default value of 4194304 for the transmission queue.
    

Problem summary

  • Enduser has the following definitions for a putting application
    (MQPUT):
    - Application buffer definition is 100 bytes
    .
    memcpy(md.Format, /* character string format */
    MQFMT_STRING, (size_t)MQ_FORMAT_LENGTH);
    md.MsgFlags = MQMF_SEGMENTATION_ALLOWED;
    md.Version = MQMD_VERSION_2;
    pmo.Options = MQPMO_LOGICAL_ORDER; /* Logical Order */
    pmo.Version = MQPMO_VERSION_2;
    .
    - transmission queue has a maximum message length of 50
    .
    For WebSphere MQ V6 and V7, the putting application fails with
    reason code 2030 (MQRC_MSG_TOO_BIG_FOR_Q) when putting to a
    transmission queue via a remote queue definition. If the enduser
    puts a message to a normal local queue there is no failure.
    .
    Additional Keywords: XMITQ segmentation allowed MsgFlags MQMD
    message flags MAXMSGL max maximum length
    .
    

Problem conclusion

  • The WMQ Application Programming Guide does not discuss the use
    of MAXMSGLEN with respect to transmission queues.
    
    The following updates should be added to section:
    "Writing a WebSphere MQ application" subsection:
    "Getting messages from a queue" subsection:
    "Handling messages greater than 4MB long" subsection:
    "Message Segmentation" subsection:
    "Segmentation and Reassembly by queue manager"
    
    http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ib
    m.mq.csqzal.doc/fg12700_.htm
    
    After this text:
    "The application buffer must be large enough to contain the
    reassembled message (unless you include the
    MQGMO_ACCEPT_TRUNCATED_MSG option)."
    
    Add the following text:
    "If the MAXMSGLEN attribute of a queue is to be modified to
    accommodate message segmentation, then consider:
    
        * The minimum message segment supported on a local queue is
    16 bytes.
        * For a transmission queue, MAXMSGLEN must also include the
    space required for headers. Consider using  a value at least
    4000 bytes larger than the maximum expected length of user data
    in any message segment that could be put on a transmission
    queue."
    

Temporary fix

Comments

APAR Information

  • APAR number

    SE39049

  • Reported component name

    WMQ ISERIES V6

  • Reported component ID

    5724H7206

  • Reported release

    600

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-06

  • Closed date

    2009-10-28

  • Last modified date

    2009-10-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R600 PSY

       UP

  • R601 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere MQ
APAR

Software version:

6.0

Reference #:

SE39049

Modified date:

2009-10-28

Translate my page

Machine Translation

Content navigation