This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGSS0002E
An internal error has occurred. Transfer ID <insert_0>. State <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.
BFGSS0003E
An internal error has occurred. Transfer ID <insert_0>. State <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.
BFGSS0004E
An internal error has occurred. Transfer ID <insert_0>. Required state <insert_1>. Actual state <insert_2>.
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.
BFGSS0005E
An internal error has occurred. Transfer ID <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.
BFGSS0009E
An internal error has occurred. Transfer ID <insert_0>. State <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.
BFGSS0011E
An internal error has occurred. Transfer ID <insert_0>. State <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.
BFGSS0012E
An internal error has occurred.
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.
BFGSS0013E
An internal error has occurred. Transfer ID <insert_0>. State <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.
BFGSS0014E
An internal error has occurred. Transfer ID <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.
BFGSS0015E
An internal sequence error relating to audit has occurred. Transfer ID <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.
BFGSS0016E
An internal error relating to audit and state has occurred. Transfer ID <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.
BFGSS0017E
An internal sequence error relating to audit has occurred. Transfer ID <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.
BFGSS0018E
An internal error relating to locating a checkpoint on the receiving agent has occurred. Transfer ID <insert_0>. File index <insert_1>. File position <insert_2>.
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.
BFGSS0019E
An internal error has occurred. Transfer ID <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.
BFGSS0020E
A sending transfer with the transfer ID <insert_0>, is already present within the agent.
Severity
20 : Error
Explanation
The transfer ID of a transfer, which is the message ID of the transfer request message that initiated the transfer, must be unique.
Response
If we are using a queue monitor to submit message to file transfer requests, ensure that the message IDs of the messages on the input queue are unique. If we are putting transfer request messages to the agent command queue either let the queue manager default the message ID, or ensure that the message IDs specified are unique. If we cannot resolve the problem, contact the IBM support center for further assistance.
BFGSS0021E
An internal error has occurred. Transfer ID <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.
BFGSS0022E
An internal error has occurred. Transfer ID <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.
BFGSS0023E
The agent is configured to use IBM MQ queues that contain data created using a later version of the product. The agent cannot run in this configuration and will end.
Severity
20 : Error
Explanation
The agent has detected that the agent has been configured to use queues that contain data created using a later version of the product. The agent cannot use this data and will end, to avoid making incompatible changes to the data.
Response
Check that the agent has been correctly configured and, if necessary, make corrections to the agent's configuration. Check to see if a later version of the product has been installed. If appropriate make use of the later version of the product. If we cannot resolve the problem, contact the IBM support center for further assistance.
BFGSS0024E
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 further assistance is required.
BFGSS0025E
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.
BFGSS0026W
The Transfer ID ''<insert_0>'' that we have requested to cancel could not be found.
Severity
10 : Warning
Explanation
The agent has received a request to cancel a transfer but the transfer could not be found. This might be because the transfer completed before the cancel request was processed by the agent. It might also be caused because you supplied an incorrect transfer ID to the fteCancelTransfer command. The cancel request has been ignored.
Response
If the transfer has already completed no action is required. If you specified an incorrect transfer ID for the fteCancelTransfer command, reissue the fteCancelTransfer command with the correct transfer ID.
As a result of a file transfer, a queue manager has attempted to handle a message that is too large.
Response
As a result of a file transfer, a queue manager has attempted to handle a message that is too large. Queue managers, channels (if you using client connections), and queues all have a maximum message length attribute. If this maximum message length differs between the three IBM MQ objects, the queue manager value takes precedence, followed by the channel value, and finally the queue value. For further information on how to alter the maximum message length attribute, refer to the IBM MQ product documentation in IBM Knowledge Center. Alternatively, contact the IBM support center for further assistance.
BFGSS0028E
The message is too large for the channel.
Severity
20 : Error
Explanation
As a result of a file transfer, a channel has attempted to handle a message that is too large.
Response
As a result of a file transfer, a channel has attempted to handle a message that is too large. Queue managers, channels (if you using client connections), and queues all have a maximum message length attribute. If this maximum message length differs between the three IBM MQ objects, the queue manager value takes precedence, followed by the channel value, and finally the queue value. For further information on how to alter the maximum message length attribute, refer to the IBM MQ product documentation in IBM Knowledge Center. Alternatively, contact the IBM support center for further assistance.
As a result of a file transfer, an attempt has been made to put too large a message onto a system queue.
Response
As a result of a file transfer, an attempt has been made to put a message that is too large onto an IBM MQ Managed File Transfer system queue. Queue managers, channels (if we are using client connections), and queues all have a maximum message length attribute. If this maximum message length differs between the three IBM MQ objects, the queue manager value takes precedence, followed by the channel value, and finally the queue value.For further information on how to alter the maximum message length attribute, refer to the IBM MQ product documentation in IBM Knowledge Center. Alternatively, contact the IBM support center for further assistance.
BFGSS0030W
The agent is already acting as the source agent for the maximum number of file transfer operations and unable to queue further requests, due to the queued transfer limit of <insert_0> being reached. The new transfer request will not be carried out.
Severity
10 : Warning
Explanation
The agent is already acting as the source agent for the maximum number of file transfer operations that the agent has been configured to allow. The new transfer request will not be carried out.
Response
Resubmit the transfer request again later, when the agent has completed some of its current workload. Consider increasing the maximum number of transfers (maxSourceTransfers) and the maximum number of transfers that may be queued (maxQueuedTransfers) by the agent. Consult the product documentation for more information on how to do this.
BFGSS0031W
The agent is already acting as the destination agent for the maximum number of file transfer operations, which is currently set to <insert_0>. The new transfer request will not be carried out.
Severity
10 : Warning
Explanation
The agent is already acting as the destination agent for the maximum number of file transfer operations that the agent has been configured to allow. The new transfer request will not be carried out.
Response
Resubmit the transfer request again later, when the agent has completed some of its current workload. Consider increasing the maximum number of transfers that the agent can participate in. Consult the product documentation for more information on how to do this.
BFGSS0032E
Too many files specified for transfer receiving agent (limit is: <insert_0>)
Severity
20 : Error
Explanation
The number of files for the transfer exceeds the maximum allowed by the receiving agent.
Response
Either reduce the number of files for the transfer to an acceptable level and resubmit or consider increasing the maximum number of files for a transfer. Consult the product documentation for more information on how to do this.
BFGSS0033E
Too many files specified for transfer sending agent (limit is: <insert_0>)
Severity
20 : Error
Explanation
The number of files for the transfer exceeds the maximum allowed by the sending agent.
Response
Either reduce the number of files for the transfer to an acceptable level and resubmit or consider increasing the maximum number of files for a transfer. Consult the product documentation for more information on how to do this.
BFGSS0034E
An internal error has occurred relating to a message on the STATE Queue. Transfer ID <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.
BFGSS0035W
The request to cancel Transfer ID ''<insert_0>'' has timed out.
Severity
10 : Warning
Explanation
The agent has received a request to cancel a transfer but it could not be completed within 30 seconds. The transfer has not been cancelled.
Response
Check that the transfer is not waiting in a user exit routine. Contact the IBM support center if further assistance is required.
BFGSS0036E
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. MQI exception is: ''<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.
BFGSS0037E
An internal error 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.
BFGSS0038E
The agent has detected an error condition that prevents the agent from continuing. The error message 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.
BFGSS0039I
The state store entry for transfer id <insert_0> has been upgraded from Version <insert_1> to Version <insert_2>.
Severity
0 : Information
Explanation
The agent has detected a state store entry on the SYSTEM.FTE.STATE.<agentName> queue from a previous version of MQMFT and automatically upgraded it to the current version of the agent.
Response
No user action is required.
BFGSS0040W
The transfer request has been failed as the source is a trial version agent and the destination is a full version agent.
Severity
10 : Warning
Explanation
The source is a trial version agent and the destination is a full version agent. This combination is not supported and the transfer request has been failed.
Response
Review the MQMFT configuration and where necessary upgrade trial version agents to full agents.
BFGSS0041W
The agent is not permitted to initiate new transfers, due to the configured maximum number of sender transfers being zero. The new transfer request will not be carried out.
Severity
10 : Warning
Explanation
The agent has been configured such that it is not allowed to act as a sending agent for a transfer. The new transfer request will not be carried out.
Response
Either submit the request to an agent that is permitted to initiate transfers or reconfigure the agent's maxSourceTransfers property to a value greater than zero. Consult the product documentation for more information on how to do this.
BFGSS0042W
The destination agent ''<insert_0>'' is not permitted to act as a destination for new transfers, due to the configured maximum number of receiver transfers being zero. The transfer request will not be carried out.
Severity
10 : Warning
Explanation
The agent has been configured such that it is not allowed to act as a receiving agent for a transfer. The new transfer request will not be carried out.
Response
Either specify a different destination agent for the transfer or reconfigure the destination agent's maxDestinationTransfers property to a value greater than zero. Consult the product documentation for more information on how to do this.
BFGSS0043E
The agent''s configuration requires the MQ queue <insert_0> to have a maximum depth of at least <insert_1>, but its maximum depth is <insert_2>.
Severity
20 : Error
Explanation
The agent uses the state store queue for holding transfers known to the system. The agent's configured limits for use of the queue exceed the maximum supported by the queue. Hence the agent will not start.
Response
Reconfigure the agent properties or state store queue (SYSTEM.FTE.STATE.<agentName>) such that the sum of agent property values maxQueuedTransfers, maxSourceTransfers and maxDestinationTransfers is less than the maximum depth of the state store queue. Consult the product documentation for more information on how to do this.
BFGSS0044W
The file has transferred successfully but the source agent was unable to delete the source file.
Severity
10 : Warning
Explanation
A source disposition of delete was specified but the source agent was unable to delete the source file.
Response
Check that agent has the required access to delete the file and that the file is not locked. If required delete the source file manually.
BFGSS0045W
The agent''s configuration specifies a maxQueuedTransfers value of <insert_0> but the minimum required is the value specified for maxSourceTransfers, which is <insert_1>. maxQueuedTransfers has been updated to be <insert_1>.
Severity
10 : Warning
Explanation
The agent properties specify a value that is too small for the maxQueuedTransfers property. The agent has increased the value such that the agent can function correctly.
Response
Update the agent's properties to correct the value of maxQueuedTransfers or maxSourceTransfers such that maxQueuedTransfers is greater or equal to maxSourceTransfers.
BFGSS0046W
The agent''s configuration specifies a negative value of <insert_0> for maxSourceTransfers. This is not permitted. maxSourceTransfers has been updated to the default value of <insert_1>.
Severity
10 : Warning
Explanation
The agent properties specify a value that is too small for the maxSourceTransfers property. The agent has set the value to the default such that the agent can function correctly.
Response
Update the agent's properties to correct the value of maxSourceTransfers such that it is greater or equal to 0.
BFGSS0047W
The agent''s configuration specifies a negative value of <insert_0> for maxDestinationTransfers. This is not permitted. maxDestinationTransfers has been updated to the default value of <insert_1>.
Severity
10 : Warning
Explanation
The agent properties specify a value that is too small for the maxDestinationTransfers property. The agent has set the value to the default such that the agent can function correctly.
Response
Update the agent's properties to correct the value of maxDestinationTransfers such that it is greater or equal to 0.
BFGSS0048E
The agent is configured to use IBM MQ queues that contain data created using a later version of the product. The agent cannot run in this configuration and will end.
Severity
20 : Error
Explanation
The agent has detected that the agent has been configured to use queues that contain data created using a later version of the product. The agent cannot use this data and will end, to avoid making incompatible changes to the data.
Response
Check that the agent has been correctly configured and, if necessary, make corrections to the agent's configuration. Check to see if a later version of the product has been installed. If appropriate make use of the later version of the product. If we cannot resolve the problem, contact the IBM support center for further assistance.
BFGSS0049E
Agent ''<insert_0>'' and agent ''<insert_1>'' have inconsistent levels of authority checking.
Severity
20 : Error
Explanation
A file transfer between the two specified agents could not take place because the agents have been configured with inconsistent levels of authority checking. For files to be transferred between agents, both agents must be configured to use the same level of authority checking.
Response
Configure the specified agents so that their 'authorityChecking' properties match. Restart the agents so that the changes to take effect. Retry the transfer.
BFGSS0050E
The transfer has not been cancelled as the partner agent user identifier (<insert_0>) does not match the user identifier of the agent that started the transfer operation (<insert_1>).
Severity
20 : Error
Explanation
The partner agent requested the cancellation of the transfer operation, however the user identifier associated with the partner agent does not match the user identifier specified when the partner agent started the transfer operation. The transfer operation has not been cancelled.
Response
No action is required.
BFGSS0051E
The transfer has not been cancelled as the user requesting the cancel operation (<insert_0>) does not have either the <insert_1> or the <insert_2> required authority.
Severity
20 : Error
Explanation
The specified user, that requested the cancel operation, does not have either of the required authorizations, required to perform the cancel operation. The cancel operation will not be carried out.
Response
Determine if the specified user should be able to perform the cancel operation. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the user the specified authority to the specified agent. If the user should not be able to cancel transfers then inform the specified user that they are not authorized to perform the action and should stop trying to perform the cancel operation.
BFGSS0052E
The transfer has not been cancelled as the user requesting the cancel operation (<insert_0>) does not have either the <insert_1> or the <insert_2> required authority.
Severity
20 : Error
Explanation
The specified user, that requested the cancel operation, does not have either of the required authorizations, required to perform the cancel operation. The cancel operation will not be carried out.
Response
Determine if the specified user should be able to perform the cancel operation. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the user the specified authority to the specified agent. If the user should not be able to cancel transfers then inform the specified user that they are not authorized to perform the action and should stop trying to perform the cancel operation.
BFGSS0053E
The transfer has not been cancelled as the user requesting the cancel operation (<insert_0>) did not request the original transfer and does not have the <insert_1> authority.
Severity
20 : Error
Explanation
The specified user, that requested the cancel operation, is not the same user as created the transfer. Also, the specified user does not have the authority required to cancel transfers belonging to other users. The requested cancel operation will not be carried out.
Response
Determine if the specified user should be able to perform the cancel operation. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent. If the user should not be able to cancel transfers then inform the specified user that they are not authorized to perform the action and should stop trying to perform the cancel operation.
BFGSS0054E
The transfer has not been cancelled as the user requesting the cancel operation (<insert_0>) does not have either the <insert_1> or the <insert_2> required authority.
Severity
20 : Error
Explanation
The specified user, that requested the cancel operation, does not have either of the required authorizations, required to perform the cancel operation. The cancel operation will not be carried out.
Response
Determine if the specified user should be able to perform the cancel operation. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent. If the user should not be able to cancel transfers then inform the specified user that they are not authorized to perform the action and should stop trying to perform the cancel operation.
BFGSS0055E
The transfer has not been cancelled as the user requesting the cancel operation (<insert_0>) does not have either the <insert_1> or the <insert_2> required authority.
Severity
20 : Error
Explanation
The specified user, that requested the cancel operation, does not have either of the required authorizations, required to perform the cancel operation. The cancel operation will not be carried out.
Response
Determine if the specified user should be able to perform the cancel operation. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent. If the user should not be able to cancel transfers then inform the specified user that they are not authorized to perform the action and should stop trying to perform the cancel operation.
BFGSS0056E
The transfer has not been cancelled as the user requesting the cancel operation (<insert_0>) did not request the original transfer and does not have the <insert_1> authority.
Severity
20 : Error
Explanation
The specified user, that requested the cancel operation, is not the same user as created the transfer. Also, the specified user does not have the authority required to cancel transfers belonging to other users. The requested cancel operation will not be carried out.
Response
Determine if the specified user should be able to perform the cancel operation. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent. If the user should not be able to cancel transfers then inform the specified user that they are not authorized to perform the action and should stop trying to perform the cancel operation.
BFGSS0057E
The transfer has not been cancelled as the partner agent user identifier (<insert_0>) does not match the user identifier of the agent that started the transfer operation (<insert_1>).
Severity
20 : Error
Explanation
The partner agent requested the cancellation of the transfer operation, however the user identifier associated with the partner agent does not match the user identifier specified when the partner agent started the transfer operation. The transfer operation has not been cancelled.
Response
No action is required.
BFGSS0058E
Agent ''<insert_0>'' and agent ''<insert_1>'' have inconsistent levels of authority checking.
Severity
20 : Error
Explanation
A file transfer between the two specified agents could not take place because the agents have been configured with inconsistent levels of authority checking. For files to be transferred between agents, both agents must be configured to use the same level of authority checking.
Response
Configure the specified agents so that their 'authorityChecking' properties match. Restart the agents so that the changes to take effect. Retry the transfer.
BFGSS0059E
The user (<insert_0>) associated with the destination agent (<insert_1>) does not have the authority (<insert_2>) required to transfer files from agent (<insert_3>).
Severity
20 : Error
Explanation
The specified destination agent does not have authority to transfer files from the specified source agent.
Response
Determine if the specified agent should be able to transfer files to the specified agent. If the agent should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent.
BFGSS0060W
The agent''s configuration specifies a value of <insert_0> for senderTransferRetryInterval. This is not permitted. The minimum permitted value is <insert_1> milliseconds. senderTransferRetryInterval has been updated to the default value of <insert_2> milliseconds.
Severity
10 : Warning
Explanation
The agent properties specify a value that is too small for the senderTransferRetryInterval property. The agent has set the value to the default such that the agent can function correctly.
Response
Update the agent's properties to correct the value of senderTransferRetryInterval such that it is greater or equal to the minimum acceptable value.
BFGSS0061E
The agent is unable to determine the depth of queue <insert_0> due to INQUIRE access being unavailable. The agent cannot continue processing and will now end.
Severity
20 : Error
Explanation
The agent need to determine the depth of the state store queue to function correctly. INQUIRE queue access is required to determine the depth of a queue, but this is not available. The agent will not continue.
Response
Add INQUIRE access for the user id under which the agent is to run or run the agent under a suitably privileged user. Consult the IBM MQ product documentation to determine how to manage queue access authorities.
BFGSS0062W
queuedTransferPriorityWeighting agent property value (<insert_0>) is invalid. Must be greater or equal to 0. Agent will use a value of <insert_1>.
Severity
10 : Warning
Explanation
The queuedTransferPriorityWeighting agent property has been set to an invalid value. The agent has adjusted the property to an acceptable value.
Response
Update the queuedTransferPriorityWeighting agent property to an acceptable value. Consult the IBM MQ Managed File Transfer documentation to understand how to set this value.
BFGSS0063E
The destination agent has been requested to shutdown and will not process the new transfer request for transfer id: <insert_0>
Severity
20 : Error
Explanation
A request was initiated to shutdown the destination agent whilst a new transfer request was made from a source agent. The transfer request has been rejected by the destination.
Response
Resubmit the failing transfer request when the destination agent has been restarted.
BFGSS0064W
The transfer request has been failed as the source is a full version agent and the destination is a trial version agent.
Severity
10 : Warning
Explanation
The source is a full version agent and the destination is a trial version agent. This combination is not supported and the transfer request has been failed.
Response
Review the MQMFT configuration and where necessary upgrade trial version agents to full agents.
BFGSS0065E
This file was included in the transfer request but failed to transfer due to a problem reading the file on the source agent.
Severity
20 : Error
Explanation
This agent expected a file to be sent, based on the original transfer request, but never received that file.
Response
Review the Transfer Log published by the source agent to diagnose the cause of this problem.
BFGSS0066I
This file was included in the transfer request but did not transfer completely before the transfer was cancelled.
Severity
0 : Information
Explanation
This agent expected a file to be sent, based on the original transfer request, but did not completely receive it before the transfer was cancelled.
Response
n/a
BFGSS0067W
The file has transferred successfully but the source agent was unable to delete the source file due to the following IOException: ''<insert_0>''
Severity
10 : Warning
Explanation
The source disposition of the transfer is set to delete but the source agent failed to delete the source file due to an IOException.
Response
Check the text of the IOException for the reason for the failure to delete the source file. If required manually delete the source file.
BFGSS0068W
The properties of ''agentStatusPublishRateLimit=<insert_0>'' and ''agentStatusPublishRateMin=<insert_1>'' are invalid. These will be ignored and agent default values will be used instead.
Severity
10 : Warning
Explanation
One or more of the property values, agentStatusPublishRateLimit and agentStatusPublishRateMin have invalid values. Both must be positive and the former must be less than or equal to the latter.
Response
Review the agent properties and correct as necessary before restarting the agent.
BFGSS0069E
The destination agent ''<insert_0>'' does not support output to an IBM MQ queue.
Severity
20 : Error
Explanation
The destination must be running IBM MQ File Transfer Edition version 7.0.3.0 or later to support output to a queue.
Response
Update the destination to a later version of IBM MQ Managed File Transfer and then retry the transfer.
BFGSS0070E
An IBM MQ error was reported when accessing the destination agent''s data queue (<insert_0> on <insert_1>) in order to send the file data messages. The reported error was <insert_2> (<insert_3>). IBM MQ Managed File Transfer was not able to recover from this error and so the transfer will be stopped.
Severity
20 : Error
Explanation
The queue named in the message is used by the destination agent to receive the file transfer data. This queue is located on the destination agent's agent queue manager. The source agent puts messages to this queue to transfer the data. An error was reported to the source agent when it attempted either to open the queue or to put a message on it. This might be caused by a misconfiguration at the data queue itself, or at another queue manager through which the messages pass.
Response
Consult the IBM MQ documentation to understand the meaning of the error and the appropriate problem determination steps.
BFGSS0071E
An IBM MQ authorization error (MQRC 2035) was reported when accessing the destination agent''s data queue (<insert_0> on <insert_1>) in order to send the file data messages. IBM MQ Managed File Transfer cannot overcome this error and so the transfer will be stopped. We should ensure that object authority records are set appropriately in the IBM MQ network. If we are using IBM MQ Advanced Message Security ensure that security policies have been appropriately configured.
Severity
20 : Error
Explanation
The queue named in the message is used by the destination agent to receive the file transfer data. This queue is located on the destination agent's agent queue manager. The source agent puts messages to this queue to transfer the data. An authorization error was reported to the source agent when it attempted either to open the queue or to put a message on it. This indicates that the user account used by the agent does not have appropriate authority to use the queue. If multiple queue managers are involved in the transfer, the required authority might apply to a resource other than the data queue itself, for example a transmission queue for connection channels between queue managers. This error is also reported by IBM MQ Advanced Message Security.
Response
Check that the agent user has appropriate authorities on the data queue. Consult the IBM MQ documentation to understand what other authorities might be required.
BFGSS0072E
A security error (MQRC 2035) was reported when accessing the destination agent''s data queue (<insert_0> on <insert_1>) in order to send the file data messages. IBM MQ Managed File Transfer cannot overcome this error and so the transfer will be stopped. IBM MQ Advanced Message Security is enabled for this agent, so we should check the MQ AMS logs (for example, /var/ibm/MQ/MQAMS/log/ on Unix platforms) to help determine the cause of the error. It is also possible that object authority records are not set appropriately in the IBM MQ network.
Severity
20 : Error
Explanation
The queue named in the message is used by the destination agent to receive the file transfer data. This queue is located on the destination agent's agent queue manager. The source agent puts messages to this queue to transfer the data. An authorization error was reported to the source agent when it attempted either to open the queue or to put a message on it. This IBM MQ error code is used to report most problems with IBM MQ Advanced Message Security, and the agent is configured to use that product so it is a likely cause. However, it is also possible that this could be a standard IBM MQ authority problem.
Response
Examine the IBM MQ Advanced Message Security logs to determine the underlying problem. If no WMQ AMS problems are apparent, consider treating this as a standard IBM MQ authority problem and see the documentation for error code BFGSS0071E.
BFGSS0073W
An error occurred while attempting to open the reply queue or put a message on the reply queue ''<insert_0>@<insert_1>'' for the file transfer ID ''<insert_2>''. The reason for the failure is: ''<insert_3>''.
Severity
10 : Warning
Explanation
On completion of the transfer, the agent failed to send a reply message to the reply queue that was specified in the transfer request. This error did not cause the transfer to fail.
Response
Check the transfer log for the outcome of the transfer. Determine the cause of the failure and make any appropriate changes to the reply queue definitions for future transfer requests.
BFGSS0074I
This transfer has been canceled before the transfer completed.
Severity
0 : Information
Explanation
This transfer has been canceled before the transfer completed.
Response
No user action is required.
BFGSS0075W
The transfer ID ''<insert_0>'' that you requested to be cancelled has already completed sending the data. Therefore, the transfer has not been cancelled.
Severity
10 : Warning
Explanation
The agent has received a request to cancel a transfer but the transfer has already completed sending the data.
Response
No action is required.
BFGSS0076E
The TransferSender thread for the file transfer with ID ''<insert_0>'' did not successfully restart. Final checksum and audit processing cannot complete.
Severity
20 : Error
Explanation
The source agent attempted to restart a TransferSender thread to recalculate the final checksum data before publishing the transfer completed audit information. However the restarted TransferSender thread did not complete the necessary processing and the checksum data was not available.
Response
If the problem persists, see problem determination information in the product documentation.
BFGSS0077E
Attempt to read file path: ''<insert_0>'' has been denied. The file path is located outside of the restricted transfer sandbox.
Severity
20 : Error
Explanation
The agent was unable to process the managed transfer request as the transfer specification was not within the restricted transfer sandbox.
Response
Ensure that the transfer specification only refers to locations within the restricted sandbox.
BFGSS0078E
Attempt to read file path: ''<insert_0>'' has been ignored as another transfer item in the managed transfer attempted to read outside of the restricted transfer sandbox.
Severity
20 : Error
Explanation
The agent was unable to process the current transfer item as another transfer item in the request contained a wildcard transfer which was located outside of the restricted transfer sandbox.
Response
Ensure that the transfer specification only refers to locations within the restricted sandbox.
BFGSS0079E
Attempt to read file ''<insert_0>'' has been denied. The file is located outside of the restricted transfer sandbox.
Severity
20 : Error
Explanation
The agent was unable to read the specified file as it is not within the restricted transfer sandbox.
Response
Ensure that the transfer specification only refers to locations within the restricted sandbox.
BFGSS0080E
Attempt to read file: ''<insert_0>'' has been ignored as another transfer item in the managed transfer attempted to read outside of the restricted transfer sandbox.
Severity
20 : Error
Explanation
The agent was unable to process the current transfer item as a previous transfer item in the request contained a wildcard transfer which was located outside of the restricted transfer sandbox.
Response
Ensure that the transfer specification only refers to locations within the restricted sandbox.
BFGSS0081E
Recovery of transfer ID: ''<insert_0>'' timed out after <insert_1> seconds. The managed transfer has been terminated.
Severity
20 : Error
Explanation
A managed file transfer has been in recovery and has now been terminated by the agent. Any successfully transferred items before the transfer was terminated will remain on the destination.
Response
Ensure that destination MFT Agent, File servers are running and can accept the file transfer requests.
BFGSS0082I
Transfer ID:''<insert_0>'', to destination agent ''<insert_1>'', cannot proceed at the current time as the destination agent is currently processing its maximum number of destination transfers. The managed transfer will be retried in ''<insert_2>'' milliseconds.
Severity
0 : Information
Explanation
The destination agent is currently processing its maximum number of destination transfers. Hence it isunable to process further requests at the current time. The managed transfer will be retried.
Response
No action is required.
BFGSS9999E
<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.