IBM Support

IT14176: FTECREATETRANSFER GENERATES A BFGCL02532W MESSAGE WHEN TRANSFERSARE SUBMITTED TO A PROTOCOL BRIDGE AGENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A managed transfer request is submitted to a protocol bridge
    agent, using the command:
    
    fteCreateTransfer -sa FTPAGENT1
    -sm QM1
    -da FTPAGENT2
    -dm QM2
    -t binary
    -de overwrite
    -df /test/jobs/target/testFile.bin
    /test/jobs/source/testFile.bin
    
    The command generates the following output:
    
    BFGCL0035I: Transfer request issued.  The request ID is:
    414d5120514d48503146545055382020550c6da220013095
    BFGCL0253W: No acknowledgement to command from agent within
    timeout.
    
    and the managed transfer fails to run.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7.5 Managed File Transfer component.
    - The IBM MQ V8 Managed File Transfer component.
    
    who have protocol bridge agents which act as the source agent
    for managed transfers, and have no default protocol file server
    configured.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a managed transfer request is submitted to a protocol
    bridge agent, the source_specification can be in one of the
    following formats:
    
    - [protocol file server name]:[filename]
    - [filename]
    
    If the source_specification is defined in the second format,
    then the protocol bridge agent will use it's default protocol
    file server (as specified in it's ProtocolBridgeProperties.xml
    file) when trying to locate the source file.
    
    If a managed transfer was submitted to a protocol bridge agent
    using the fteCreateTransfer command, where the
    source_specification was specified in the format:
    
      [filename]
    
    and no default protocol file server had been defined for the
    agent, then the fteCreateTransfer command generated the
    following messages:
    
      BFGCL0035I: Transfer request issued.  The request ID is:
    <transfer identifier>
      BFGCL0253W: No acknowledgement to command from agent within
    timeout.
    
    and the managed transfer would not run.
    

Problem conclusion

  • The protocol bridge agent has been updated to send back a
    response to the fteCreateTransfer command if it:
    
    - Receives a managed transfer request where the
    source_specification does not explicitly contain a protocol file
    server name.
    - And no default file server has been configured for the agent.
    
    The managed transfer will subsequently run, and be marked as
    "Failed" with the error:
    
    BFGBR0163E: No default protocol server defined for the protocol
    bridge.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.7
    v8.0       8.0.0.5
    
    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

    IT14176

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-08

  • Closed date

    2016-03-31

  • Last modified date

    2016-04-18

  • 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

  • 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:
18 April 2016