IBM Support

PI64172: MFT file transfer fails with rc 2030 - MQRC_MSG_TOO_BIG_FOR_Q

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The MQ V8 Managed File Transfer component on z/OS was used to
    start a text transfer from a queue to a fixed record format data
    set.
    The queue contained a large number (400,000) of small messages
    with no end-of-line characters, so the messages were treated as
    a single text line.
    
    When the transfer took a checkpoint it failed to put a message
    to the agent state queue and the agent failed with errors:
    
    BFGSS0024E: The agent has received a reason code of '2030' from
    the message queue interface (MQI). The agent cannot continue
    processing and will now end.
    BFGSS0029E: The message is too large for WebSphere MQ Managed
    File Transfer queue: 'SYSTEM.FTE.STATE.XXXXX'.
    BFGAG0179E: The agent has ended abnormally with return code 70.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ V8 Managed File Transfer
    component on z/OS who are transferring text messages to a fixed
    record format data set.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When MQ V8 Managed File Transfer component on z/OS (MFT)
    executes a transfer to a data set, the destination agent writes
    information on an ongoing basis to the data set so it does not
    build up a large amount of internal state data for the transfer.
    
    However in the case of text transfers to a fixed format data
    set, trailing spaces must be trimmed from the lines of text
    before they are written to the data set, so the destination
    agent needs to buffer up a complete line of data so that it can
    decide whether there are trailing spaces that need to be
    trimmed.  (Note, there is a transfer parameter named -skeep
    which allows spaces to be retained but this only applies when
    the source of the transfer is a file - it is not applicable to
    when the transfer source is a queue)
    
    In the scenario which caused this APAR, the message data on the
    queue data did not contain any EOL characters, so the data was
    effectively a single line of 40,000,000 characters.  The
    TrimmedTextWriter in the destination agent kept buffering all
    that data looking for an EOL, and each time it took a checkpoint
    it put a message to the state queue containing all the data it
    had seen so far, plus the data in the previous checkpoints.
    Eventually it built a checkpoint message which exceeded the
    maximum message size for the queue and the put failed.  At this
    point the agent failed with the error:
    
    BFGSS0024E: The agent has received a reason code of '2030' from
    the message queue interface (MQI). The agent cannot continue
    processing and will now end.
    BFGSS0029E: The message is too large for WebSphere MQ Managed
    File Transfer queue: 'SYSTEM.FTE.STATE.XXXXX'.
    BFGAG0179E: The agent has ended abnormally with return code 70.
    

Problem conclusion

  • MQ V8 Managed File Transfer agent was modified to update the
    algorithm which is used to store data to the state queue.  This
    allows the agent to handle text transfers which include a very
    long line of text.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.7
    v9.0 CD    9.0.1
    v9.0 LTS   9.0.0.1
    
    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

    PI64172

  • Reported component name

    WMQ MFT Z/OS

  • Reported component ID

    5655MFT00

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-15

  • Closed date

    2016-09-30

  • Last modified date

    2017-06-01

  • 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 MFT Z/OS

  • Fixed component ID

    5655MFT00

Applicable component levels

  • R800 PSY

       UP

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

Document Information

Modified date:
01 June 2017