IT06213: SERVICEABILITY ENHANCEMENTS FOR WEBSPHERE MQ FILE TRANSFER EDITION V7.0.4 AND LATER

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.5

APAR status

• Closed as program error.

Error description

• Some of the configuration settings for WebSphere MQ File
  Transfer Edition (WMQ-FTE) do not use optimum values for general
  WebSphere MQ File Transfer Edition and WebSphere MQ Managed File
  Transfer (WMQ-MFT) usage and problem diagnosis.
  
  This can lead to a slow down in resolution of issues via the IBM
  Support process.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This APAR affects users of WebSphere MQ File Transfer Edition
  V7.0.4, WebSphere MQ Managed File Transfer V7.5 and V8.0.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  There are four issues being addressed as part of this
  serviceability APAR.
  
  Issue 1
  -----------
  The "commandMessagePriority" property sets the priority of both
  internal messages and command messages for the fteStopAgent,
  fteCancelTransfer and ftePingAgent commands.
  For WebSphere MQ File Transfer Edition, this property is set in
  wmqfte.properties. For WebSphere MQ Managed File Transfer, this
  property is set in installation.properties.
  
  The default value given to this property was equivalent to the
  priority of other messages that flow through the file transfer
  network. If a large number of transfer requests to transfer many
  small files were submitted in quick succession, for example, the
  new transfer requests would become queued on the source agent's
  command queue. The external and internal messages had the
  default WebSphere MQ message priority so the internal messages
  were blocked by the new transfer requests. This would cause the
  transfer negotiation time to be exceeded and for the transfers
  to go into recovery.
  
  Issue 2
  -----------
  The "logTransferRecovery" property, which is set in
  agent.properties for both WebSphere MQ File Transfer Edition and
  WebSphere MQ Managed File Transfer, is used to enable the
  reporting of transfer recovery diagnostic messages which are
  reported in the agent's event log. The default value for this
  property was 'false', which means that no recovery messages were
  written to the output0.log file for the agent.
  
  Issue 3
  -----------
  A "-d" parameter can be used on the "fteShowAgentDetails"
  command to display diagnostic information about an agent when
  used with WebSphere MQ Managed File Transfer v7.5 and later. In
  order to use this parameter, when using the WebSphere MQ Managed
  File Transfer V7.5, the property "enableFunctionalFixPack=7502"
  also had to be set in the "installation.properties" file. The
  enableFunctionalFixPack property is not required to be set with
  WebSphere MQ Managed File Transfer V8.
  
  Issue 4
  -----------
  If an agent encountered an unrecoverable error, it used to log a
  message to the output0.log file and exit.
  

Problem conclusion

• The following changes have been made to the product code as a
  result of this APAR.
  
  Issue 1
  -----------
  The default value for "commandMessagePriority" has changed to 8.
  
  This means that, if the WebSphere MQ queue attribute DEFPRTY
  (Default priority) on an agent command queue is less than or
  equal to 7, then internal negotiation messages will be
  prioritised ahead of new transfer requests. If the value of the
  DEFPRTY attribute is set to either 8 or 9, then either DEFPRTY
  or the "commandMessagePriority" property will
  need to be changed to maintain the effectiveness of
  "commandMessagePriority".
  
  Issue 2
  -----------
  The default value for "logTransferRecovery" has changed to
  "true". As a result of this, transfer recovery information will
  now be written to the output0.log file. An example of one of
  these messages is shown below:
  
  BFGTR0068I: Transfer ID:  entering recovery, immediately, due to
  recoverable error: BFGTR0064I: The transfer sender timed out
  waiting for a response from the transfer receiver.
  
  Issue 3
  -----------
  The WebSphere MQ Managed File Transfer v7.5 product has been
  modified to remove the need for "enableFunctionalFixPack" to be
  set in installation.properties when using the "-d" parameter on
  the fteShowAgentDetails command.
  
  Issue 4
  -----------
  The product code now been updated to generate an FDC if it
  encounters an unrecoverable error. The agent will also exit.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.4.5
  v7.5       7.5.0.6
  v8.0       8.0.0.3
  
  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 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 FILE TRANSF

• Fixed component ID

  5724R1000

Applicable component levels

• R704 PSY

     UP