IBM Support

IT39713: MQ Managed File Transfer database logger puts "Progress" messages containing BFGSS0090E errors to its reject queue

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

  • An MQ 9.2.0.4 Managed File Transfer agent is acting as the
    source agent for managed transfers. Intermittently, managed
    transfers containing multiple transfer items are marked as
    "Partially Successful", and one or more transfer items within
    those managed transfers are marked as "Failed" with the
    supplementary message:
    
    BFGSS0090E: Failed to generate audit information for the source
    transfer item.
    
    If a database logger has been set up for the MQ Managed File
    Transfer topology, it is unable to process any "Progress"
    messages that contain the new BFGSS0090E supplementary message.
    When a message containing this supplementary information is
    received, the database logger puts it onto its reject queue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ Managed File Transfer who:
    
    - Have source agents for managed transfers that are running MQ
    9.2.0.4 Managed File Transfer.
    - And are using a database logger to collect and store
    information about the managed transfers performed in their MQ
    Managed File Transfer topology.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    As part of the fix for APAR IT36500:
    
    - If a managed transfer went into, and then came out of,
    recovery due to the source agent stopping unexpectedly.
    - And, during the recovery processing for a managed transfer,
    the source agent determined that it had written one less
    checkpoint record that the destination agent.
    
    then the source agent would create a dummy checkpoint record and
    restart from the position requested by the destination agent.
    This ensured that the source agent didn't resend any data that
    had already been processed by the destination agent, which
    prevented the issue reported in that APAR from occurring.
    
    Because of the dummy checkpoint, the source agent was unable to
    confirm that the data that it sent before it abended was exactly
    the same as the data that was successfully written by the
    destination agent (for example, the source file might have
    changed while the source agent was down). The changes for
    IT36500 would result in the source agent marking any items that
    were affected in this way as "Failed", with the new
    supplementary information message:
    
    BFGSS0090E: Failed to generate audit information for the source
    transfer item.
    
    The source agent would then publish a "Progress" message
    containing this new supplementary information to the SYSTEM.FTE
    topic on the coordination queue manager for the MQ Managed File
    Transfer topology.
    
    However, the "Progress" messages containing the new BFGSS0090E
    message did not contain any "transfer type" information. This
    meant that if copies of these "Progress" messages were delivered
    to a database logger, the logger would be unable to process them
    and would put them onto its reject queue.
    

Problem conclusion

  • To resolve this issue, MQ Managed File Transfer has been updated
    so that "Progress" messages published by the source agent which
    contain a BFGSS0090E error also include "transfer type"
    information. This ensures that the messages can be successfully
    processed by a database logger.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.4
    
    The latest available 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

    IT39713

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-21

  • Closed date

    2022-01-28

  • Last modified date

    2022-02-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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
02 February 2022