APAR status
Closed as program error.
Error description
An MQ Managed File Transfer protocol bridge agent (PBA) connects to a file server using the SFTP protocol and acts as the destination agent for a managed transfer. Occasionally, managed transfers involving the agent fail and the managed transfer includes the following supplementary information: BFGBR0119E: Bridge agent was unable to create directory <directory name> because The BFGBR0119E message stops after the word "because", and does not contain any information about why the managed transfer failed.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of MQ Managed File Transfer, who have protocol bridge agents that: - Connect to file servers using the SFTP protocol. - And act as the destination agent for managed transfers. - And process managed transfer requests that require a new directory to be created on the file server. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: MQ Managed File Transfer protocol bridge agents (PBA) use the third-party JSch library to communicate with file servers using the SFTP protocol. If an issue occurs that prevents JSch from being able to perform the requested SFTP operation, it throws an exception back to the PBA. The PBA will catch that exception, and handle it appropriately. If the exception indicates an issue has occured which prevents the managed transfer from being completed, then the PBA will mark the managed transfer as "Failed". The PBA will also generate a supplementary message providing more details about the failure, using information contained within the exception thrown by JSch. Now, if a PBA: - Was acting as the destination agent for a managed transfer. - And received a managed transfer request that required it to create a new directory on the file server. - And the JSch library was unable to create that directory due to a permissions issue. then the exception thrown by JSch would not always contain an additional information. In this situation, the supplementary message generated by the PBA looked like this: BFGTR0072E: The transfer failed to complete due to the exception: BFGBR0119E: Bridge agent was unable to create directory <directory name> because The message stopped after the word "because" which made it appear incomplete, when in fact there was no additional information for the PBA to include.
Problem conclusion
To resolve this issue, MQ Managed File Transfer protocol bridge agents (PBA) have been updated so that: - If they are acting as the destination agent for a managed transfer. - And they are processing a managed transfer request that requires a new directory to be created on the file server. - And the JSch library is unable to create that directory. - And the exception thrown back by JSch does not contain any information about why the directory could not be created. then the PBA will mark the managed transfer as "Failed" with the following supplementary message: BFGTR0072E: The transfer failed to complete due to the exception: BFGBR0209E: Bridge agent was unable to create directory <directory name> --------------------------------------------------------------- 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 number
IT30768
Reported component name
IBM MQ MFT V9.0
Reported component ID
5724H7262
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-10-30
Closed date
2019-12-03
Last modified date
2019-12-04
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.0
Fixed component ID
5724H7262
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 December 2019