IT30034: Protocol bridge agent configuration error is not reported on thefteCreateTransfer command.

APAR status

• Closed as program error.

Error description

• Using IBM MQ Managed File Transfer, if a managed transfer
  request is received that specified an incorrect file server
  name, no error is not reported back to user, other than in the
  agent trace file.
  
  In addition to this, when the managed transfer request was
  submitted via the fteCreateTransfer command using the -w (wait)
  option, the command times out without reporting the
  configuration error.
  

Local fix

• Collect trace to capture the error.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of IBM MQ Managed File Transfer who
  have a protocol bridge agent as the source agent for managed
  transfers.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using an IBM MQ Managed File Transfer (MFT) protocol bridge
  agent as the source agent, then managed transfers would get
  stuck if the fteCreateTransfer command specified a wrong or
  unknown file server name. For example, if the
  ProtocolBridgeCredentials.xml file was configured with the
  entry:
  
    <tns:serverHost name="my.sftp.server5.com">
  
  and the fteCreateTransfer command specified the protocol server
  as "my.sftp.server6", as shown below:
  
    fteCreateTransfer  -w 20 -sm QM_MFT -sa AGENT_1
  '/home/user1/3.txt' -dm QM_MFT -da PBA_AGENT_1 -df
  'my.sftp.server6.com:/tmp/3.txt'
  
  then the managed transfer would never start and could not be
  cancelled. The fteCreateTransfer command would also time out
  waiting for a response from the agent.
  
  This behaviour was due to the way the agent handled the failure
  to find any information on how to connect to the file server.
  

Problem conclusion

• IBM MQ MFT has been updated so that if a managed transfer
  request is made specifying a file server that the protocol
  bridge agent does not know about, then the managed transfer will
  fail with the message:
  
    BFGBR0164E: The protocol server <server name > is not known to
  the protocol bridge"
  
  This will be visible in the MQ Explorer transfer log.
  
  If the managed transfer request was submitted with the -w (wait)
  option, the following message will be reported back to the
  fteCreateTransfer command.
  
    BFGCL0141E: The requested file transfer has completed with no
  files being transferred.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0 LTS   9.0.0.9
  v9.1 CD    9.1.5
  v9.1 LTS   9.1.0.5
  
  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 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