IBM Support

IT05666: WMQ-FTE V7.0.4 USING A MONITOR ON A QUEUE WITH BATCH SIZE > 1 MAY RESULT IN INCORRECT COMPLETION STATUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A resource monitor for a queue was defined with a batch size set
    to a value greater than one.
    
    The monitor was triggered and detected a number of messages on
    the queue and attempted to transfer them as a single batch.
    
    The first message in the batch was transferred successfully, but
    the rest of the messages in the batch appeared in MQExplorer to
    be successfully transferred but no transfers occurred and the
    messages remained on the input queue.
    

Local fix

  • use groupId="${groupId}
    and
    batch size on the monitor (-bs option) MUST be set to 1.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of WebSphere MQ File Transfer
    Edition and WebSphere MQ Managed File Transfer who use a
    resource monitor to monitor a queue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A resource monitor for a queue was defined with a batch size set
    to a value greater than one.
    
    The monitor was triggered and detected a number of messages on
    the queue and attempted to transfer them as a single batch. The
    first message in the batch was transferred successfully, but the
    rest of the messages in the batch appeared in MQExplorer to be
    successfully transferred but no transfers occurred and the
    messages remained on the input queue.
    
    The product code expected a direct link between the message id
    of the message being processed and the id of the transfer it was
    part of when single messages (not part of an MQ message group)
    were being processed. The message id of the message and the
    transfer id must be identical.
    
    If multiple messages were processed in a single batch (which
    forms a single transfer and hence a single transfer id), then
    only the first message would match this criteria. The remaining
    messages in the batch would not be processed and would remain on
    the input queue.
    

Problem conclusion

  • The product code has been modified to override the value
    specified by the -bs parameter on the resource monitor and set
    it to the value 1 when the monitor executes if the monitor is
    for a queue.
    
    The following message will be written to the output0.log file
    when the batch size has been overridden:
    
    BFGDM0122W: The batch size for monitor {0} has been set to 1 at
    execution time because the batch size for a monitor on a queue
    cannot exceed this value.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.5
    v7.5       7.5.0.6
    v8.0       8.0.0.2
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT05666

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-11-21

  • Closed date

    2015-02-22

  • Last modified date

    2015-11-28

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

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

Fix information

  • Fixed component name

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 November 2015