IT07817: WMQ 7.5 MFT TRANSFER LOG SHOWS SUCCESSFULLY TRANSFERRED DESTINATION FILE SIZE OF 0 BYTES INCORRECTLY WHEN USING A PBA

APAR status

• Closed as program error.

Error description

• The WebSphere MQ MFT Protocol Bridge Agent is used to transfer
  files to a remote FTP server.  On the FTP server, the
  destination file is moved/renamed immediately after finishing
  the upload.
  The MQ MFT transfer log shows that the transfer completed
  successfully, but the log shows that the source  file size is
  not 0 bytes, but the transferred file size becomes 0 bytes like
  below:
  .
  <source><file size=14000>
  <destination><file size =0>
  ....
  <supplement>BFGRP0032I: The file transfer request has
  successfully
  .
  The Protocol Bridge Agent creates an internal FileIOWorker
  thread to write the file data for  the file transferred to the
  FTP Server.
  After all of the file data has been written, the FileIOWorker
  thread opens a new connection to the FTP Server and attempts to
  get the attributes for the transferred file, at this point, if
  the file has been moved to a new  location on the FTP Server,
  then FileIOWorker thread is unable to locate the file that it
  has just written, it generates "missing attribute" information
  for this file.
  This information indicates that the size of the file on the FTP
  Server is 0 bytes which is misleading, as it can make users
  incorrectly think that a transfer has failed.
  
  Additional Symptom(s) Search Keyword(s): MQMFT;0 byte;
  

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 that act as the Destination
  Agent for managed transfers.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a Protocol Bridge Agent is acting as the Destination Agent
  for a managed transfer, it will perform the following processing
  when writing a file to an FTP Server:
  
  - Connect to the FTP Server.
  - Create a temporary file (destination file name with ".part"
  extension) on the FTP Server.
  - Write the file data to the file system.
  - Rename the file (removing the ".part" extension).
  - Disconnect from the FTP Server.
  - If the file data has been written successfully, and no errors
  have
     been thrown from the FTP Server:
      - Connect to the FTP Server.
      - Query the final size of the file that has just been
  written.
      - Query the last modified date of the file that has just
  been
  	  written.
      - Disconnect from the FTP Server.
      - Generate a "Success" transfer progress message,
  containing:
          - The file name.
          - The size of the file that has just been written.
          - The last modified date of the file that has just been
  		  written.
      - Publish the progress message.
  - Else
      - Generate a "Failed" transfer progress message.
      - Publish the progress message.
  - End if
  
  If the file that had just been written to the FTP Server was
  moved before the Protocol Bridge Agent tried to get the final
  file size, then the Agent would generate a "Progress" audit
  message for the transfer item that showed the size of the file
  that had been written was 0 (zero) bytes.
  

Problem conclusion

• The Protocol Bridge Agent has been updated so that, if the Agent
  tries to get the final size of the file that it had written and
  finds the file is no longer on the FTP Server, it will generate
  a "Progress" audit message for the transfer item that:
  
  - Shows the destination file size is -2.
  - Contains the supplement "BFGTR0077I: The destination agent was
  unable to determine the size of the file '<filename>' that it
  had written."
  
  An example of a "Progress" audit message containing this
  information is shown below:
  
  <item mode="binary">
      <source disposition="leave" type="file">
          <file last-modified="2015-03-12T13:51:50.658Z"
  &#09;&#09;      size="16131">
             C:\TestFile.5
          </file>
          <checksum method="MD5">
              fbcb567654beda84b46cdf0a116859a4
          </checksum>
      </source>
  
      <destination exist="error" type="file">
          <file size="-2">Server1:/myDirectory/TestFile.5</file>
          <checksum method="MD5">
              fbcb567654beda84b46cdf0a116859a4
          </checksum>
      </destination>
  
      <status resultCode="0">
          <supplement>
              BFGTR0077I: The destination agent was unable to
                          determine the size of the file
                          'Server1:/myDirectory/TestFile.5' that
                          it had written.
          </supplement>
      </status>
  </item>&#09;
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.6
  v8.0       8.0.0.4
  
  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 MFT

• Fixed component ID

  5724H7242

Applicable component levels

• R750 PSY

     UP