BFGTR0001 - BFGTR9999

BFGTR0001E: An internal error has occurred. An unexpected method call was made <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0002E: An internal error has occurred. Chunk number <insert_0> is out of the range (<insert_1> - <insert_2>) for the current transfer frame.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0003E: An internal error has occurred. The type identifier ("<insert_0>") for acknowledgment data is invalid.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0004E: An internal error has occurred. Incompatible acknowledgment data version ("<insert_0>")
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0005E: An internal error has occurred. Invalid acknowledgment data (<insert_0>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0006E: An internal error has occurred. No room in transfer frame for file chunk number <insert_0> (addStatus <insert_1>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0011W: No input files in the transfer with ID <insert_0> could be opened.
Severity: 10 : Warning
Explanation: No input files could be opened so the transfer failed and no files were transferred.
Response: Check that the input files exist and are not locked by another application.

BFGTR0012E: The transfer of <insert_0> has failed because of a problem at the destination.
Severity: 20 : Error
Explanation: The receiving agent was unable to create the required destination file.
Response: Check the information from the receiving agent for a full description of the problem.

BFGTR0013E: The agent has received a reason code of ''<insert_0>'' from the message queue interface (MQI). The agent cannot continue processing and will now end.
Severity: 20 : Error
Explanation: The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response: Consult the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0014E: An internal error has occurred. The exception is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0015E: The agent has detected an error condition that prevents the agent from continuing. The error message is: <insert_0>
Severity: 20 : Error
Explanation: The agent has received the specified error. The agent cannot continue processing after receiving this error. The agent process will end.
Response: Use the information in the error message to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0016E: The agent has received an MQI reason code of ''<insert_0>''. The agent cannot continue processing and will now end.
Severity: 20 : Error
Explanation: The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response: Consult the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0017E: An internal error has occurred. The exception is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0018E: The agent has detected an error condition that prevents the agent from continuing. The error message is: <insert_0>
Severity: 20 : Error
Explanation: The agent has received the specified error. The agent cannot continue processing after receiving this error. The agent process will end.
Response: Use the information in the error message to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0019E: The agent has received an MQI reason code of ''<insert_0>''. The agent cannot continue processing and will now end.
Severity: 20 : Error
Explanation: The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response: Consult the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0020E: An internal error has occurred. The exception is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0021E: The agent has detected an error condition that prevents the agent from continuing. The error message is: <insert_0>
Severity: 20 : Error
Explanation: The agent has received the specified error. The agent cannot continue processing after receiving this error. The agent process will end.
Response: Use the information in the error message to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0022E: The agent has received a reason code of ''<insert_0>'' from the message queue interface (MQI). The agent cannot continue processing and will now end.
Severity: 20 : Error
Explanation: The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response: Consult the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0023E: An internal error has occurred. The exception is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0024E: The agent has detected an error condition that prevents the agent from continuing. The error message is: <insert_0>
Severity: 20 : Error
Explanation: The agent has received the specified error. The agent cannot continue processing after receiving this error. The agent process will end.
Response: Use the information in the error message to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0025E: The agent has received a reason code of ''<insert_0>'' from the message queue interface MQI. The agent cannot continue processing and will now end.
Severity: 20 : Error
Explanation: The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response: Consult the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance.

BFGTR0026E: An internal error has occurred. The exception is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0028E: A recoverable I/O error has occurred during a read. The agent will attempt to recover the file transfer. The transfer ID is: <insert_0>. The error message is : <insert_1>
Severity: 20 : Error
Explanation: The agent has received a recoverable I/O exception during a read. The agent will attempt to recover the file transfer.
Response: Review the error message and take appropriate action to resolve the problem

BFGTR0029E: A recoverable I/O error has occurred during a write operation. The agent will attempt to recover the file transfer. The transfer ID is: <insert_0>. The error message is: <insert_1>
Severity: 20 : Error
Explanation: The agent has received a recoverable I/O exception during a write operation. The agent will attempt to recover the file transfer.
Response: Review the error message and take appropriate action to resolve the problem

BFGTR0030E: A recoverable I/O error has occurred during a write operation. The agent will attempt to recover the file transfer. The transfer ID is: <insert_0>. The error message is: <insert_1>
Severity: 20 : Error
Explanation: The agent has received a recoverable I/O exception during a write operation. The agent will attempt to recover the file transfer.
Response: Review the error message and take appropriate action to resolve the problem

BFGTR0032E: Failed status file slice recieved by receiving agent, indicating there is a problem with the source file on the sending agent. File slice is: ''<insert_0>''
Severity: 20 : Error
Explanation: Received file slices with a failed status indicate that the source agent has detected an I/O error whilst opening or reading the source file for a transfer. The details of the failure should be reported by the sending agent and hence this message should not normally be seen.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0033E: File channel is in the closed state for a received file slice, indicating there is a problem with the destination file. File slice is: ''<insert_0>''
Severity: 20 : Error
Explanation: A receiver channel for a file has had a problem (normally a write failure) and hence cannot process the file slice received from the source agent. The details of the original failure should be reported by the receiving agent and hence this message should not normally be seen.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0034E: Receiver channel is null for a received file slice, indicating there is a problem with the destination file. File slice is: ''<insert_0>''
Severity: 20 : Error
Explanation: A receiver channel for a file has had a problem (i.e. could not be opened) and hence cannot process the file slice received from the source agent. The details of the original failure should be reported by the receiving agent and hence this message should not normally be seen.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0035I: The transfer was canceled by user request.
Severity: 0 : Information
Explanation: A user submitted a request for the transfer to be canceled.
Response: None.

BFGTR0036E: The transfer failed to complete successfully.
Severity: 20 : Error
Explanation: An error on the source agent caused the transfer to fail midway through.
Response: Consult the transfer audit log to discover the problem.

BFGTR0039E: The transfer that you attempted to cancel (id: <insert_0>) is already being cancelled.
Severity: 20 : Error
Explanation: The agent received a request to cancel a transfer but the transfer is already in the process of being cancelled. The new request to cancel the transfer is being ignored.
Response: No action required.

BFGTR0040E: The transfer that you attempted to cancel (id: <insert_0>) is already being cancelled.
Severity: 20 : Error
Explanation: The agent received a request to cancel a transfer but the transfer is already in the process of being cancelled. The new request to cancel the transfer is being ignored.
Response: No action required.

BFGTR0041E: A security error occurred while receiving data for transfer <insert_0>. This is likely to be caused by a problem with IBM MQ Advanced Message Security if you are using that product.
Severity: 20 : Error
Explanation: IBM MQ reported a security error of a type normally associated with Advanced Message Security, when receiving data on the agent's data queue.
Response: Inspect the IBM MQ Advanced Messaging Security logs for information about the failure. On Unix platforms, these can be found at /var/ibm/MQ/MQAMS/log/ . On Windows, the location will depend on your chosen install directory. You should also consult the IBM MQ Advanced Messaging Security product documentation. If you are not using Advanced Message Security, check your IBM MQ object authorities, and any SSL settings, instead.

BFGTR0042E: A security error occurred while receiving file data. It was not possible to identify the transfer involved. This is likely to be caused by a problem with IBM MQ Advanced Message Security if you are using that product.
Severity: 20 : Error
Explanation: IBM MQ reported a security error of a type normally associated with Advanced Message Security, when receiving data on the agent's data queue.
Response: Inspect the IBM MQ Advanced Messaging Security logs for information about the failure. On Unix platforms, these can be found at /var/ibm/MQ/MQAMS/log/ . On Windows, the location will depend on your chosen install directory. You should also consult the IBM MQ Advanced Messaging Security product documentation. If you are not using Advanced Message Security, check your IBM MQ object authorities, and any SSL settings, instead.

BFGTR0043E: Temporary directory ''<insert_0>'' specified for MQMFT Connect:Direct bridge agent property ''cdTmpDir'' cannot be created or is invalid.
Severity: 20 : Error
Explanation: Temporary directory specified by MQMFT agent property 'cdTmpDir' cannot be used by the MQMFT Connect:Direct bridge agent.
Response: Check that the temporary directory exists and the MQMFT Connect:Direct bridge agent has authority to read and write to the directory. See the IBM MQ Managed File Transfer documentation for more information.

BFGTR0044E: Cannot determine the destination Connect:Direct node name for the transfer of file: ''<insert_0>''.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0045E: The specified file index: <insert_0> does not specify a valid transfer item. Expected index range: 0 to <insert_1>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGTR0046E: The same target Connect:Direct node name must be specified for each file to be transferred.
Severity: 20 : Error
Explanation: The MQMFT Connect:Direct bridge only supports transfers to or from a single Connect:Direct node.
Response: Check the files specified in your transfer request to ensure they all refer to a single Connect:Direct node.

BFGTR0047E: Cannot determine the Connect:Direct node name for the transfer of file: ''<insert_0>''.
Severity: 20 : Error
Explanation: The MQMFT Connect:Direct bridge only supports transfers to or from a Connect:Direct node.
Response: Check the files specified in your transfer request to ensure they refer to a Connect:Direct node. See the IBM MQ Managed File Transfer documentation for more information.

BFGTR0048I: Transfer of the file has been skipped because one of the other files specified in the transfer request is invalid.
Severity: 0 : Information
Explanation: For transfers to or from a Connect:Direct bridge if any one of the files specified is invalid then none of the other files will be transferred.
Response: Check the reported errors for other files specified in your transfer.

BFGTR0049E: Transfer of the file ''<insert_0>'' might have failed because the associated Connect:Direct process ''<insert_1>'' cannot be found.
Severity: 20 : Error
Explanation: The transfer encountered a problem after starting the Connect:Direct process for the file. On transfer recovery the recorded Connect:Direct process is no longer running and cannot be found in within the Connect:Direct node's statistics. The status of the Connect:Direct process is unknown.
Response: Check the destination Connect:Direct node's file system to determine whether the file transferred successfully. If required submit the file transfer request again.

BFGTR0050E: Transfer with ID ''<insert_0>'' cannot continue because the associated Connect:Direct process ''<insert_1>'' cannot be released from "held due to error" status. Manually release or delete the process from the Connect:Direct node associated with the Connect:Direct bridge agent.
Severity: 20 : Error
Explanation: During recovery of the transfer, an associated Connect:Direct process was found to have a "held due to error" (HE) status. The Connect:Direct bridge agent attempted to release the process but the process continued to have a "held due to error" (HE) status.
Response: Check the identified Connect:Direct process and attempt to either manually release the process or delete it to allow the transfer to complete. Alternatively, cancel the transfer.

BFGTR0051W: The associated Connect:Direct process for transfer ID ''<insert_0>'' for source file ''<insert_1>'' cannot be found.
Severity: 10 : Warning
Explanation: During recovery of the transfer a Connect:Direct process for the file had already been started but could no longer be found. This may be due to the Connect:Direct node's statistics information being purged. The recovery of the transfer will request a new process to repeat the transfer of the file.
Response: No action required.

BFGTR0052E: The end-of-line character for Connect:Direct node ''<insert_0>'' cannot be determined due to an error. The error is <insert_1>
Severity: 20 : Error
Explanation: For a text file transfer, when attempting to determine the end-of-line character for a Connect:Direct node, an error occurred while attempting to contact the node that is part of the Connect:Direct bridge.
Response: Examine the reported error message and attempt to correct the problem. Submit the transfer request again.

BFGTR0053E: The end-of-line character for Connect:Direct node ''<insert_0>'' cannot be determined.
Severity: 20 : Error
Explanation: For a text file transfer, the end-of-line character for the specified Connect:Direct node could not be determined because its operating system is unknown and MQMFT agent property cdDefaultOSType has not been set.
Response: Either update the Connect:Direct bridge agent's network map to include the operating system information for the node that is specified in the transfer request, or set the agent property cdDefaultOSType to a suitable value.

BFGTR0054E: No result information could be obtained for the Connect:Direct process.
Severity: 20 : Error
Explanation: Result information was not available from Connect:Direct for the underlying process.
Response: Check the Connect:Direct logs and attempt to diagnose the issue.

BFGTR0055E: No result information could be obtained for the Connect:Direct process with name ''<insert_0>'' and id ''<insert_1>''.
Severity: 20 : Error
Explanation: Result information was not available from Connect:Direct for the underlying process.
Response: Check for the identified Connect:Direct process directly in the Connect:Direct logs and attempt to diagnose the issue.

BFGTR0056I: Process [name: <insert_0>, number: <insert_1>, transferID: <insert_2>] <insert_3>
Severity: 0 : Information
Explanation: This message provides information for a Connect:Direct process associated with a transfer of a file. The name and number of the process are included along with the associated transfer ID. The actual process definition used to initiate the process with Connect:Direct is also included for your information.
Response: No action required.

BFGTR0057I: Process [name: <insert_0>, number: <insert_1>, transferID: <insert_2>, definitionFile: <insert_3>] <insert_4>
Severity: 0 : Information
Explanation: This message provides information for a Connect:Direct process associated with a transfer of a file that might have been modified using a user-supplied process definition file. The name and number of the process are included along with the associated transfer ID and the name of the process definition file used when generating the process definition. The actual process definition used to initiate the process with Connect:Direct is also included for your information.
Response: No action required.

BFGTR0058I: The transfer frame had a recoverable I/O error while attempting to write to a destination file. The reason is: <insert_0>
Severity: 0 : Information
Explanation: A recoverable I/O error occurred while attempting to write to a file. This might be because the file is locked by another transfer or because of a recoverable I/O sub-system error (for example, an FTP server connection being broken).
Response: No action required.

BFGTR0059I: The transfer receiver timed out waiting for data from the source agent.
Severity: 0 : Information
Explanation: No data has been received from the source agent for a while, even after sending a number of data acknowledgements.
Response: No action required.

BFGTR0060I: The transfer receiver has been requested to enter recovery. Reason: <insert_0>
Severity: 0 : Information
Explanation: A RecoveryWorkItem has been placed on the transfer receiver's work queue. This is requested by the Connect:Direct file processor logic, indicating that the Connect:Direct node connection has been lost.
Response: No action required.

BFGTR0061I: The transfer frame had a recoverable I/O error while attempting to write to a destination file. The reason is: <insert_0>
Severity: 0 : Information
Explanation: A recoverable I/O error occurred while attempting to write to a file. This might be because the file is locked by another transfer or because of a recoverable I/O sub-system error (for example, an FTP server connection being broken).
Response: No action required.

BFGTR0062I: Transfer ID: <insert_0>, from source agent <insert_1>, is entering recovery, after a short pause, due to recoverable error: <insert_2>
Severity: 0 : Information
Explanation: A recoverable error has occurred for a transfer. After a pause (default is 1 minute) the transfer will enter a recovery state, after which it will attempt the file transfer again.
Response: No action required.

BFGTR0063I: Transfer ID: <insert_0>, from source agent <insert_1>, is entering recovery, immediately, due to recoverable error: <insert_2>
Severity: 0 : Information
Explanation: A recoverable error has occurred for a transfer. The transfer will enter a recovery state immediately, after which it will attempt the file transfer again.
Response: No action required.

BFGTR0064I: The transfer sender timed out waiting for a response from the transfer receiver.
Severity: 0 : Information
Explanation: No negotiation response has been received from the transfer receiver within a defined timeout (default is 30 seconds).
Response: No action required.

BFGTR0065I: The transfer frame had a recoverable I/O error while attempting to read from a source file. The reason is: <insert_0>
Severity: 0 : Information
Explanation: A recoverable I/O error occurred while attempting to read from a file. This might be because the file is locked by another transfer or because of a recoverable I/O sub-system error (for example, an FTP server connection being broken).
Response: No action required.

BFGTR0066I: The transfer sender timed out waiting for an acknowledgement from the destination agent.
Severity: 0 : Information
Explanation: No acknowledgement has been received from the destination agent for a while, even after sending a number of acknowledgement expected requests.
Response: No action required.

BFGTR0067I: Transfer ID: <insert_0>, to destination agent <insert_1>, is entering recovery, after a short pause, due to recoverable error: <insert_2>
Severity: 0 : Information
Explanation: A recoverable error has occurred for a transfer. After a pause (default is 1 minute) the transfer will enter a recovery state, after which it will attempt the file transfer again.
Response: No action required.

BFGTR0068I: Transfer ID: <insert_0>, to destination agent <insert_1>, is entering recovery, immediately, due to recoverable error: <insert_2>
Severity: 0 : Information
Explanation: A recoverable error has occurred for a transfer. The transfer will enter a recovery state immediately, after which it will attempt the file transfer again.
Response: No action required.

BFGTR0069E: Process [name: <insert_0>, number: <insert_1>, transferID: <insert_2>] <insert_3>
Severity: 20 : Error
Explanation: This message provides information for a Connect:Direct process associated with a transfer of a file that has failed due to an exception. The name and number of the process are included along with the associated transfer ID. The exception message received is also included for your information.
Response: Determine the cause of the exception using the message provided and re-submit the transfer after the problem has been resolved.

BFGTR0070E: Process [name: <insert_0>, number: <insert_1>, transferID: <insert_2>, definitionFile: <insert_3>] <insert_4>
Severity: 20 : Error
Explanation: This message provides information for a Connect:Direct process associated with a transfer of a file that might have been modified using a user-supplied process definition file but which has failed due to an exception. The name and number of the process are included along with the associated transfer ID and the name of the process definition file used when generating the process definition. The exception message received is also included for your information.
Response: Determine the cause of the exception using the message provided and re-submit the transfer after the problem has been resolved.

BFGTR0071E: The associated Connect:Direct process for source file ''<insert_0>'' cannot be found.
Severity: 20 : Error
Explanation: During a transfer submitted from Connect:Direct, the Connect:Direct process for the source file cannot be found.
Response: Check that the parameter of the preceding 'ftetag' command is set to the source file of the IBM MQ Managed File Transfer transfer. For further information, see the IBM MQ Information Center. Make any necessary changes and resubmit the transfer.

BFGTR0072E: The transfer failed to complete due to the exception : <insert_0>
Severity: 20 : Error
Explanation: The transfer did not complete successfully because the operating system reported an I/O condition. The transfer will be marked as failed and will not be tried again.
Response: Review the reported I/O condition and correct as necessary before trying the transfer again.

BFGTR0073E: No entry for transfer item ''<insert_0>'' at index ''<insert_1>'' could be found. The item has failed to transfer.
Severity: 20 : Error
Explanation: During a transfer via the Connect:Direct bridge, the specified transfer item failed to transfer.
Response: Check that the source item exists and can be read by the source agent. Ensure that the destination agent has permission to write to the destination file or folder, and that there is sufficient disk space. Resubmit the transfer.

BFGTR0074W: Failure to generate source file audit information for transfer ''<insert_0>''. Some audit information may be missing.
Severity: 10 : Warning
Explanation: An exception occurred when attempting to perform checksum calculations and generate the final audit information after recovery processing.
Response: Take appropriate action based on the result code and any supplementary information provided.

BFGTR0075W: The source file has not been deleted because it is possible that the source file was modified after the source file was transferred.
Severity: 10 : Warning
Explanation: A recovery occurred after all the data was sent from the source agent to the destination agent. In this case the source file is unlocked before the source file is deleted, which makes it possible that the source file could be modified before deletion. Therefore it is considered to be unsafe for the source file to be deleted.
Response: Verify that the content of the source file is unmodified. If you are satisfied that the source file is unmodified, manually delete the source file.

BFGTR0076E: This file has not been transferred due to a previous file in this transfer failing.
Severity: 20 : Error
Explanation: The source agent property failTransferOnFirstFailure has been set to true and is active for this managed transfer. Therefore this and subsequent files in this transfer will be failed.
Response: Identify and correct the issue with the first failing file or remove the agent property before trying again.

BFGTR0077I: The destination agent was unable to determine the size of the file ''<insert_0>'' that it had written.
Severity: 0 : Information
Explanation: After successfully writing a file, a destination agent attempted to query the final size of the file and could not locate it. This happens for two reasons: 1) The file was no longer available on the file server 2) The listFormat attribute was incorrect for the file server. As a result of this, a Progress message for the managed transfer will be generated that contains an entry for this file which has the "size" element in the "file" attribute set to -2.
Response: None.

BFGTR0078W: An I/O exception was caught closing a channel during transfer checkpoint processing. The message in the exception was: ''<insert_0>''
Severity: 10 : Warning
Explanation: The file system returned an I/O exception to the destination agent when closing a channel to a destination item as part of generating a transfer checkpoint.
Response: Take appropriate action based on the I/O exception and any supplementary information provided.

BFGTR0079E: An I/O exception was caught creating a file channel for a source file. The message in the exception was: ''<insert_0>''
Severity: 20 : Error
Explanation: The file system returned an I/O exception to the source agent when attempting to create a file channel.
Response: Take appropriate action based on the I/O exception and any supplementary information provided.

BFGTR0080E: An I/O exception was caught opening a file channel for a source file. The message in the exception was: ''<insert_0>''
Severity: 20 : Error
Explanation: The file system returned an I/O exception to the source agent when attempting to open a file channel and lock the underlying file.
Response: Take appropriate action based on the I/O exception and any supplementary information provided.

BFGTR0081I: Transfer ID: ''<insert_0>'' is now in recovering state. The agent will wait for <insert_1> seconds for the transfer to recover.
Severity: 0 : Information
Explanation: A managed file transfer has entered into recovering state. Any successfully transferred items before the transfer entered into recovering state will remain on the destination.
Response: Ensure that destination agent,protocol servers are running and can accept the file transfer requests, before the agent terminates recovering transfer.

BFGTR0082I: Transfer ID: ''<insert_0>'' that was in a recovering state, has now resumed.
Severity: 0 : Information
Explanation: A managed file transfer that was in recovering state has now resumed. Transfer will continue from the point it stopped before entering into recovery.
Response: No user action is required.

BFGTR0083E: The transfer has failed because of a problem at the destination.
Severity: 20 : Error
Explanation: The receiving agent was unable to create the required destination file.
Response: Check the information from the receiving agent for a full description of the problem.

BFGTR9999E: <insert_0>
Severity: 20 : Error
Explanation: If this message does not give enough information, check the accompanying error messages for further information.
Response: For further information on resolving this error, see the problem determination information on the product Web site.