IBM Support

IC99557: WEBSPHERE MQ MANAGED FILE TRANSFER REPORTS ERROR BFGIO0171E WMQAPIEXCEPTION RC 2085 WHEN ATTEMPTING TO OPEN CLUSTERED QUEUE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When performing file-to-message transfers with WebSphere MQ
    Managed File Transfer where the destination queue is a clustered
    queue that is not local to the destination agent's queue
    manager, and no queue manager name has been specified on the
    managed transfer request, the transfers fail with the following
    exception:
    
    BFGTR0072E: The transfer failed to complete due to the exception
    : BFGIO0171E: Opening a queue for writing failed due to a Java
    IOException or WMQApiException with message text cc=2 rc=2085
    op=openQueue - MQOPEN (Queue Manager: , Queue Name: , Open
    Options: 16400)
    
    If the destination queue specified for the transfer was an alias
    to a WebSphere MQ clustered queue that is not local to the
    destination agent's queue manager, the transfer would instead
    fail with this exception:
    
    BFGTR0072E: The transfer failed to complete due to the exception
    : BFGIO0171E: Opening a queue for writing failed due to a Java
    IOException or WMQApiException with message text cc=2 rc=2082
    op=openQueue - MQOPEN (Queue Manager: , Queue Name: , Open
    Options: 16400)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This APAR affects all users of the WebSphere MQ Managed File
    Transfer File-to-Message function who want to write to a
    WebSphere MQ cluster queue that is not local to the destination
    agent's WebSphere MQ queue manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When a new transfer was requested and the destination was a
    queue, if a queue manager name was not specified using the
    syntax QUEUE@QUEUEMANAGER on the managed transfer request, then
    the WebSphere MQ Managed File Transfer destination agent always
    used the name of it's agent queue manager in the ObjectQMgrName
    field of the MQOD when opening the queue.
    
    If the queue specified in the managed file transfer request was
    not local to the destination agent's queue manager, or didn't
    resolve to a local queue in the case of an alias queue, then the
    transfer would fail with a WebSphere MQ error, as described in
    the Problem Description for this APAR.
    

Problem conclusion

  • The WebSphere MQ Managed File Transfer agent code has been
    updated such to permit writing to a WebSphere MQ cluster queue,
    or an alias to a WebSphere MQ cluster queue, for file-to-message
    transfers.
    
    A new boolean agent property, enableClusterQueueInputOutput, is
    now available to enable the support of writing to cluster queues
    that are not local to the destination agent's queue manager.
    When this property is set to the value "true" in the destination
    agent's agent.properties file, like so:
    
    enableClusterQueueInputOutput=true
    
    managed file transfer requests that specify only a destination
    queue name, without a queue manager, will cause the destination
    agent to omit any value for the ObjectQMgrName field of the MQOD
    when opening the specified destination queue. This will result
    in the destination agent's queue manager determining which
    clustered queue manager on which to open the destination queue,
    as per normal WebSphere MQ clustering. The WebSphere MQ Managed
    File Transfer destination agent specifies the MQOO_BIND_ON_OPEN
    open option such that the target queue manager after the MQOPEN
    call becomes fixed.
    
    Note that the new enableClusterQueueInputOutput agent property
    must be specified in addition to the existing
    enableQueueInputOutput agent property for file-to-message
    transfers.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.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

    IC99557

  • Reported component name

    WMQ FTE

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-21

  • Closed date

    2014-03-24

  • Last modified date

    2014-04-23

  • 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 FTE

  • Fixed component ID

    5724H7242

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCUHLE","label":"WMQ Managed File Transfer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
23 April 2014