APAR status
Closed as program error.
Error description
An error message was output from the Managed File Transfer component of the following form: BFGIO0121E: An internal error has occurred. Insufficient data for checksum state (expected #.#.#.#:/Destination/Filename bytes, received {1} bytes) instead of the expected error message which would have provided the actual size of the file in question.
Local fix
n/a
Problem summary
**************************************************************** USERS AFFECTED: This affects users of IBM MQ Managed File Transfer with a Protocol Bridge Agent. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: A File Transfer request is made to a Protocol Bridge Agent using the checksum md5 options. If the validation of the source/destination files fails it will report a 'BFGIO0121E' error message, providing a fully qualified filename as part of the error description. However the message text stated that this field was to be a numerical field representing the expected size for the file in bytes. In addition, the stated received byte size would always display '{1}'. For example, a message was output of the form: BFGIO0121E: An internal error has occurred. Insufficient data for checksum state (expected 0.0.0.0:/ftp/BigText.txt bytes, received {1} bytes)
Problem conclusion
The error message has been changed to provide the fully qualified filename, as well as the md5 checksum values that was expected, as well as those calculated from the file. For example, the error message now reads in for the form: BFGIO0121E: An internal error has occurred. The expected checksum for the file '0.0.0.0:/fpt/BigText.txt' does not match the data received for the file content (expected '87691a7a9ac41be0fc7235d49ab9a6d2' value, received '87691a7a9ac41be0fc7235d49ab9a6d2' value). --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.2 LTS 9.2.0.2 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 number
IT34133
Reported component name
MQ BASE V9.2
Reported component ID
5724H7281
Reported release
920
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-09-07
Closed date
2020-10-14
Last modified date
2020-10-14
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
MQ BASE V9.2
Fixed component ID
5724H7281
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]
Document Information
Modified date:
25 March 2021