IC98577: WMQFTE V7.0.4: USER METADATA IS IGNORED DURING FILE-TO-MESSAGE TRANSFERS WHEN AGENT PROPERTY MAXINLINEFILESIZE IS SET.

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.4
WebSphere MQ V7.5 Fix Pack 7.5.0.4

APAR status

• Closed as program error.

Error description

• User Metadata is not reflected as a message property in the
  resulting file-to-message transfer using WebSphere MQ File
  Transfer Edition version 7.0.4. This user Metadata gets
  ignored, because the agent property maxInlineFileSize is
  defined for one or both of the participating agents; in the
  agent.properties file. Defining maxInlineFileSize causes the
  agents to make use of inline file transfers to improve transfer
  performance.
  

Local fix

• Stop using the inline transfer function by commenting out the
  "maxInlineFileSize" property in the respective
  agent.properties file for the source WebSphere MQ FTE agent.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the WebSphere MQ File Transfer Edition v7.0.4.3 and
  later, and WebSphere MQ Managed File Transfer v7.5.0.2 and
  later, who are:
  
  (a) Performing file to message transfers
  
  (b) Using the 'maxInlineFileSize' property defined in the source
  agent's 'agent.properties' file
  
  (c) Performing the transfer with metadata defined (the -md
  option on fteCreateTransfer for example)
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  As of WebSphere MQ File Transfer Edition v7.0.4.3, new
  function was added to permit file transfers to be transferred
  'inline' when doing file to file or file to message transfers.
  
  This mode of operation may optimise the transfer request, as
  it has the potential to reduce the number of messages which flow
  between the coordination queue manager and the agents when doing
  a file transfer.
  
  The new function is activated by setting a property in the
  source agents agents.properties file:
  
      maxInlineFileSize=
  
  where "" dictates the maximum size of the file which is being
  transferred for the inline function to operate.
  
  
  When a file to message transfer was requested which made use
  of the inline function, metadata defined in the transfer request
  was not populated into the RFH2 header of the transferred
  message.
  
  For example, consider a transfer which was initiated to transfer
  a file to a message on a queue, using the '-md' flag to
  include user metadata:
  
  fteCreateTransfer -sa AGENT1
                    -sm FTE_QMGR
                    -da AGENT2
                    -dm FTE_QMGR
                    -md "MyMetaData=apples"
                    -sd delete
                    -dq "DESTINATIONQ"
                    -qs 4M
                    -qmp true
                    myfileToTransfer.txt
  
  it was expected to see this metadata defined as user
  properties within the RFH2 header of the transferred message,
  for example:
  
  
    apples
  
  
  However this property was not defined in the transferred message
  if the 'inline' function was used during the file transfer.
  

Problem conclusion

• The WebSphere MQ File Transfer Edition and WebSphere MQ
  Managed File Transfer code has been updated such that when using
  the 'inline' function to transfer the file, user metadata is
  also transferred through the system into the transferred
  message, so that it is present in the user properties of the
  RFH2 header of the message on the transfer destination queue.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.4.4
  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 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