IBM Support

IT34350: MFT File-To-Message transfer with delimiter greater than defaultlength generates two 0 byte messages

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When using a regular expression to split a file during a
    file-to-message transfer, two zero byte message is created in
    the
    destination queue if the transfer fails with an error of type
    BFGIO0196E.
    
    Example of file-to-message transfer:
    fteCreateTransfer -sa AGENT1 -sm QMGR1 -da AGENT2 -dm QMGR2 -dq
    Q1 -t text -dqdt "ABCDEFG" -qi -dqdp prefix  file-transfer.txt
    Error BFGIO0196E
        The delimiter ''<insert_0>'' has matched data of length
    <insert_1> which exceeds the maximum allowed of <insert_2>. The
    text matched by the delimiter is : ''<insert_3>''.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using MFT to perform delimited file-to-message transfer.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    During delimited file-to-message transfer, if the delimiter size
    was greater than the specified size on the destination agent
    (default 5) , two empty messages were seen in the destination
    queue.
    It was expected to see one empty message in the destination
    queue to indicate failure.
    

Problem conclusion

  • MFT Delimited file-to-message processing has been updated such
    that only one empty message is generated when delimiter size
    exceeds specified size on destination agent.
    As there is only one empty message, this will not have group ID
    and will not have LAST_MSG_IN_GROUP flag set on the IBM MQ
    message.
    
    If -qmp option is provided with fteCreateTransfer command and
    delimiter size exceeds the set size, then a single message is
    written to destination queue with the IBM MQ message properties
    set.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.8
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.2
    
    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

    IT34350

  • Reported component name

    IBM MQ MFT V9.1

  • Reported component ID

    5724H7272

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-24

  • Closed date

    2020-10-27

  • Last modified date

    2020-10-27

  • 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

    IBM MQ MFT V9.1

  • Fixed component ID

    5724H7272

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
28 October 2020