The agent name that we have specified is too short. The minimum number of characters allowed in an agent name is <insert_0>.
Severity
20 : Error
Explanation
The agent name that we have specified was too short. Specify a longer agent name.
Response
Specify an agent name that is at least as long as the length specified in the message.
BFGAG0002E
The agent name that we have specified is too long. The maximum number of characters allowed in an agent name is <insert_0>.
Severity
20 : Error
Explanation
The agent name that was specified was too long. Specify a shorter agent name.
Response
Specify an agent name that is no longer than the maximum length specified in the message.
BFGAG0003E
The agent name that we have specified contains characters that are not permitted in an agent name.
Severity
20 : Error
Explanation
Agent names can contain characters that are valid for IBM MQ object names only. Consult the IBM MQ product documentation for more information about which characters are valid as object names.
Response
Specify an agent name that contains only characters that are valid for an IBM MQ object name.
BFGAG0004E
We have specified an incorrect number of arguments on the command line.
Severity
20 : Error
Explanation
This command accepts a single command line argument only.
Response
Specify a single command line argument only.
BFGAG0005E
An internal error has occurred. The argument was <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.
The agent was unable to load its configuration and cannot continue running. The agent process will end.
Response
Examine previous error messages to determine the nature of the configuration problem. Use this information to correct the problem, if possible. Otherwise contact the IBM support center if we need further assistance.
BFGAG0007E
An internal error occurred that prevented process startup. The exception was <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.
BFGAG0008E
The property named <insert_0> was either omitted or has no value in the agent.properties file. The agent process will now end.
Severity
20 : Error
Explanation
The named property must be present and correctly specified in the configuration file, otherwise the process cannot start.
Response
Use the information in the message to determine which changes are needed in the configuration file specified. Update the configuration file with these changes and restart this process.
BFGAG0009I
Transfer file <insert_0> to <insert_1> (transfer id: <insert_2>).
Severity
0 : Information
Explanation
Information.
Response
None.
BFGAG0010E
Transfer (<insert_0>) failed because of a file reader exception <insert_1>.
Severity
20 : Error
Explanation
The file transfer was unsuccessful because of a problem reading the source file.
Response
Look at the reason for the failure to understand why the transfer failed and take the appropriate action as necessary.
BFGAG0011I
Transfer (<insert_0>) complete. <insert_1>
Severity
0 : Information
Explanation
Information.
Response
None.
BFGAG0012I
The coordination queue manager has not been specified in the properties file. The agent's presence will not be published.
Severity
0 : Information
Explanation
The coordination queue manager has not been specified in the properties file so the agent's presence will not be published.
Response
Add the missing property value if you require the agent's presence to be published.
BFGAG0014W
Transfer of file <insert_0> to <insert_1> not started because the system is shutting down.
Severity
10 : Warning
Explanation
The file transfer was unsuccessful because the system is shutting down.
Response
No action required.
BFGAG0017W
The audit message for transfer ID <insert_0> failed to publish the STARTED message.
Ensure that the coordination queue manager properties have been specified correctly in the properties file. Ensure that the coordination queue manager is running.
BFGAG0018W
The audit message for transfer ID <insert_0> failed to publish the PROGRESS message.
Ensure that the coordination queue manager properties have been specified correctly in the properties file. Ensure that the coordination queue manager is running.
BFGAG0019W
The audit message for transfer ID <insert_0> failed to publish the COMPLETED message.
Ensure that the coordination queue manager properties have been specified correctly in the properties file. Ensure that the coordination queue manager is running.
BFGAG0020W
An internal error has occurred. An audit message for transfer ID <insert_0> has been received in an unexpected sequence. An Audit Started must be performed first
Severity
10 : Warning
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGAG0021W
An internal error has occurred. An audit message for transfer ID <insert_0> has been received in an unexpected sequence. An Audit Started must be performed first.
Severity
10 : Warning
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGAG0023E
The agent is already running. An exclusive lock cannot be acquired on file: <insert_0>. This agent instance cannot continue and will end.
Severity
20 : Error
Explanation
This agent process has detected that another instance of the agent is running. Only one instance of an agent process can be running at any one time, so this agent process will end. The mechanism used to detect that another instance of the agent process is running is an exclusive lock on the named file.
Response
No action is required.
BFGAG0024E
The agent cannot open file ''<insert_0>'' and will end. The file could not be opened because of: <insert_1>.
Severity
20 : Error
Explanation
The agent process could not open the specified file, for the specified reason. The agent process must be able to access this file in order to start successfully. The agent process will now end.
Response
Use the information in the message to investigate why the agent cannot open the specified file. If possible, resolve the problem and reissue the command to start the agent. If necessary, contact the IBM support center if we need further assistance to resolve this problem.
BFGAG0025I
The agent process has ended with return code <insert_0>.
Severity
0 : Information
Explanation
The agent process has ended with the specified reason code.
Response
No action is required.
BFGAG0026I
The agent process is starting.
Severity
0 : Information
Explanation
The agent process is starting.
Response
No action is required.
BFGAG0027W
Waiting for queue manager "<insert_0>" to become available.
Severity
10 : Warning
Explanation
An attempt to connect to the queue manager has failed and the agent is now waiting for the queue manager to become available.
Response
No action is required.
BFGAG0028I
Connected to queue manager "<insert_0>".
Severity
0 : Information
Explanation
This agent has successfully made a connection to the queue manager.
Response
No action is required.
BFGAG0029E
An internal error has occurred. There is already a thread running this method.
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.
BFGAG0030E
An internal error has occurred. The method has been invoked before main processing.
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.
BFGAG0031E
An internal error has occurred. The method has been invoked using the thread responsible for main processing.
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.
BFGAG0032W
The agent received MQI reason code <insert_0> when trying to open queue ''<insert_1>'' on the default local queue manager.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot open the specified queue belonging to the default local queue manager. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0033W
The agent received MQI reason code <insert_0> when trying to open queue ''<insert_1>'' on local queue manager ''<insert_2>''.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot open the specified queue belonging to the specified local queue manager. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0034W
The agent received MQI reason code <insert_0> when trying to open queue ''<insert_1>'' on the default queue manager with connection name ''<insert_2>'' and channel ''<insert_3>''. The agent will try the operation again every <insert_4> seconds.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot open the specified queue belonging to the remote default queue manager. The agent will keep trying the operation again at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0035W
The agent received MQI reason code <insert_0> when trying to open queue ''<insert_1>'' on the queue manager ''<insert_2>'' with connection name ''<insert_3>'' and channel ''<insert_4>''. The agent will try the operation again every <insert_5> seconds.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot open the specified queue belonging to the specified remote queue manager. The agent will keep trying the operation again at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0036E
The agent received MQI reason code <insert_0> when opening queue ''<insert_1>'' on the default local queue manager. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to open the specified queue belonging to the default local queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0037E
The agent received MQI reason code <insert_0> when opening queue ''<insert_1>'' on local queue manager ''<insert_2>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to open the specified queue belonging to the specified local queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0038E
The agent received MQI reason code <insert_0> when opening queue ''<insert_1>'' on the default remote queue manager with connection name ''<insert_2>'' and channel ''<insert_3>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to open the specified queue belonging to the default remote queue manager on the specified host. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0039E
The agent received MQI reason code <insert_0> when opening queue ''<insert_1>'' on the remote queue manager ''<insert_2>'' with connection name ''<insert_3>'' and channel ''<insert_4>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to open the specified queue belonging to the specified remote queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0040E
An internal error occurred. The MQI reason code is <insert_0>, the queue is <insert_1>, the queue manager is <insert_2> on host <insert_3>, port <insert_4> and channel <insert_5>.
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.
BFGAG0041E
The agent cannot establish a bindings mode connection to the default queue manager and will now end. The reason is: <insert_0>
Severity
20 : Error
Explanation
The agent could not establish a bindings mode connection to the default queue manager, for the specified reason. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Use the information in the message to diagnose the problem. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0042E
The agent cannot establish a bindings mode connection to queue manager ''<insert_0>'' and will now end. The reason is: <insert_1>
Severity
20 : Error
Explanation
The agent could not establish a bindings mode connection to the specified queue manager for the specified reason. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Use the information in the message to diagnose the problem. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0043E
The agent cannot establish a client mode connection to the default queue manager with connection name ''<insert_0>'' and using channel ''<insert_1>''. The agent will now end. The reason is: <insert_2>
Severity
20 : Error
Explanation
The agent could not establish a client mode connection to the default queue manager for the specified reason. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Use the information in the message to diagnose the problem. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0044E
The agent cannot establish a client mode connection to queue manager ''<insert_0>'' with connection name ''<insert_1>'' and using channel ''<insert_2>''. The agent will now end. The reason is: <insert_3>
Severity
20 : Error
Explanation
The agent could not establish a client mode connection to the specified queue manager, for the specified reason. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Use the information in the message to diagnose the problem. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0045W
A bindings transport mode connection cannot be established to the default queue manager. The reason code is <insert_0>.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot establish a bindings mode connection to the default queue manager because of the specified MQI reason code. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0046W
A bindings transport mode connection cannot be established to queue manager ''<insert_0>''. The reason code is <insert_1>.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot establish a bindings mode connection to the specified queue manager because of the specified MQI reason code. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0047W
A client transport mode connection cannot be established to the default queue manager with connection name ''<insert_0>'' and using channel ''<insert_1>''. The reason code is <insert_2>. The agent will try the operation again every <insert_3> seconds.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot establish a client mode connection to the default queue manager because of the specified MQI reason code. The agent will keep trying the operation again at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0048W
A client transport mode connection cannot be established to queue manager ''<insert_0>'' with connection name ''<insert_1>'' and using channel ''<insert_2>''. The reason code is <insert_3>. The agent will try the operation again every <insert_4> seconds.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot establish a client mode connection to the specified queue manager because of the specified MQI reason code. The agent will keep trying the operation again at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0049E
The agent received MQI reason code <insert_0> when establishing a bindings transport mode connection to the default queue manager. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to establish a bindings transport mode connection to the default queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0050E
The agent received MQI reason code <insert_0> when establishing a bindings transport mode connection to the queue manager ''<insert_1>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to establish a bindings transport mode connection to the specified queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0051E
The agent received MQI reason code <insert_0> when establishing a client transport mode connection to the default queue manager with connection name ''<insert_1>'' and using channel ''<insert_2>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to establish a client transport mode connection to the default queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0052E
The agent received MQI reason code <insert_0> when establishing a client transport mode connection to the queue manager ''<insert_1>'' with connection name ''<insert_2>'' and using channel ''<insert_3>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to establish a client transport mode connection to the specified queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0053E
An internal error has occurred. The reason code is <insert_0>, the queue manager is <insert_1> on host <insert_2>, port <insert_3> and channel <insert_4>.
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.
BFGAG0054I
The agent has established a bindings transport mode connection to the default queue manager. The agent is ready to be used for transfers.
Severity
0 : Information
Explanation
The agent is connected to the specified queue manager. The agent is ready to be used for transfers.
Response
No action is required.
BFGAG0055I
The agent has established a bindings transport mode connection to queue manager ''<insert_0>''. The agent is ready to be used for transfers.
Severity
0 : Information
Explanation
The agent is connected to the specified queue manager. The agent is ready to be used for transfers.
Response
No action is required.
BFGAG0056I
The agent has established a client transport mode connection to the default queue manager with connection name ''<insert_0>'' and channel ''<insert_1>''. The agent is ready to be used for transfers.
Severity
0 : Information
Explanation
The agent is connected to the specified queue manager. The agent is ready to be used for transfers.
Response
No action is required.
BFGAG0057I
The agent has established a client transport mode connection to queue manager ''<insert_0>'' with connection name ''<insert_1>'' and channel ''<insert_2>''. The agent is ready to be used for transfers.
Severity
0 : Information
Explanation
The agent is connected to the specified queue manager. The agent is ready to be used for transfers.
Response
No action is required.
BFGAG0058I
The agent has successfully initialized.
Severity
0 : Information
Explanation
The agent has successfully initialized and is preparing to process transfers.
Response
No action is required.
BFGAG0059I
The agent has been successfully started.
Severity
0 : Information
Explanation
The agent has been started and is processing transfers.
Response
No action is required.
BFGAG0060I
The agent has completed its current transfers and is now stopping.
Severity
0 : Information
Explanation
A request to stop the agent has been received. All current transfers have been completed and the agent is now stopping.
Response
No action is required.
BFGAG0061E
The agent ended abnormally
Severity
20 : Error
Explanation
The agent ended abnormally because of an error.
Response
Review previous error messages in the event log for details of the error.
BFGAG0062E
The agent has received MQI reason code ''<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 we need further assistance.
BFGAG0063E
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.
BFGAG0064E
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 we need further assistance.
BFGAG0065E
The agent has received MQI reason code ''<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 problem. Resolve the problem. Contact the IBM support center if we need further assistance.
BFGAG0066E
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.
BFGAG0067E
The agent cannot establish a bindings mode connection to the default queue manager and will now end. The agent cannot find a bindings library: <insert_0>
Severity
20 : Error
Explanation
The agent could not establish a bindings mode connection to the default queue manager because the agent could not locate an appropriate bindings library. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the product documentation to determine how to configure the location that the bindings library is loaded from. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0068E
The agent cannot establish a bindings mode connection to queue manager ''<insert_0>'' and will now end. The agent cannot find a bindings library: <insert_1>
Severity
20 : Error
Explanation
The agent could not establish a bindings mode connection to the specified queue manager because the agent could not locate an appropriate bindings library. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the product documentation to determine how to configure the location that the bindings library is loaded from. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0069E
The agent cannot establish a bindings mode connection to the default queue manager and will now end. The required libraries are not in the STEPLIB: <insert_0>
Severity
20 : Error
Explanation
The agent could not establish a bindings mode connection to the default queue manager because the agent could not locate the required libraries. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the product documentation to determine how to configure the STEPLIB to reference the required libraries. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0070E
The agent cannot establish a bindings mode connection to queue manager ''<insert_0>'' and will now end. The required libraries are not in the STEPLIB: <insert_1>
Severity
20 : Error
Explanation
The agent could not establish a bindings mode connection to the specified queue manager because the agent could not load the required libraries. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the product documentation to determine how to configure the STEPLIB to reference the required libraries. If possible, resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0071I
The agent has suspended its current transfers and is now stopping.
Severity
0 : Information
Explanation
A request to stop the agent has been received. All active transfers have been suspended and the agent is now stopping. Any outstanding commands will be stopped if they do not complete after a short period of time.
Response
No action is required.
BFGAG0072E
The agent is unable to complete initialization because of a problem with SSL configuration: <insert_0>.
Severity
20 : Error
Explanation
A request to start the agent could not be processed because of an SSL configuration issue. This problem prevented the agent from starting.
Response
Resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0073E
The agent is unable to complete initialization because of a problem with SSL configuration: <insert_0>.
Severity
20 : Error
Explanation
A request to start the agent could not be processed because of an SSL configuration issue. This problem prevented the agent from starting.
Response
Resolve the problem and restart the agent. Otherwise contact the IBM support center if we need further assistance.
BFGAG0074E
The agent process does not have permission to read from or write to the specified transfer sandbox location "<insert_0>" and will end.
Severity
20 : Error
Explanation
The agent would be unable to read or write any files and cannot continue running. The agent process will end.
Response
Examine previous error messages to determine the nature of the configuration problem. Use this information to correct the problem, if possible. Otherwise contact the IBM support center if we need further assistance.
BFGAG0075E
The agent process does not have permission to read from or write to any of the specified transfer sandbox locations and will end.
Severity
20 : Error
Explanation
The agent would be unable to read or write any files and cannot continue running. The agent process will end.
Response
Examine previous error messages to determine the nature of the configuration problem. Use this information to correct the problem, if possible. Otherwise contact the IBM support center if we need further assistance.
BFGAG0076W
The agent process does not have permission to read from or write to the specified transfer sandbox location "<insert_0>", but will continue because other locations are available.
Severity
10 : Warning
Explanation
The agent would be unable to read or write files to one of the given sandboxes.
Response
Examine previous error messages to determine the nature of the configuration problem. Use this information to correct the problem, if possible. Otherwise contact the IBM support center if we need further assistance.
BFGAG0078E
The license terms of IBM MQ Managed File Transfer for z/OS do not permit client transport mode connections to be used to connect an agent process to the queue manager.
Severity
20 : Error
Explanation
Agents running on z/OS are not allowed to use client transport mode connections.
Response
Change the Agent's configuration to use bindings transport mode connections instead.
BFGAG0079E
The agent has received MQI reason code ''<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 we need further assistance.
BFGAG0080E
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.
BFGAG0081E
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 we need further assistance.
BFGAG0082E
The agent process does not have permission to read from or write to the specified transfer sandbox location "<insert_0>" and will end. Additional information: <insert_1>
Severity
20 : Error
Explanation
The agent would be unable to read or write any files and cannot continue running. The agent process will end.
Response
Examine previous error messages to determine the nature of the configuration problem. Use this information to correct the problem, if possible. Otherwise contact the IBM support center if we need further assistance.
BFGAG0083E
The agent''s transfer root directory ''<insert_0>'' is not a valid directory or the agent does not have the necessary permissions to use it. The process will end.
Severity
20 : Error
Explanation
The agent would be unable to read or write any files specified with relative paths and cannot continue running. The agent process will end.
Response
Examine previous error messages to determine the nature of the configuration problem. Use this information to correct the problem, if possible. Otherwise contact the IBM support center if we need further assistance.
BFGAG0084I
An operator request to immediately shut down this agent has been received.
Severity
0 : Information
Explanation
An operator shutdown request has been received from the system operator.
Response
No action is required.
BFGAG0085I
An operator request to immediately shut down this agent is being processed.
Severity
0 : Information
Explanation
This agent is performing an immediate shutdown following an operator request.
Response
No action is required.
BFGAG0086I
An operator request to shut down this agent has been received.
Severity
0 : Information
Explanation
An operator shutdown request has been received.
Response
No action is required.
BFGAG0087I
An operator request to shut down this agent is being processed.
Severity
0 : Information
Explanation
An operator shutdown request is being processed.
Response
No action is required.
BFGAG0088E
Operator command <insert_0> is not valid
Severity
20 : Error
Explanation
An invalid operator command was received by the agent
Response
Correct and re-enter the command.
BFGAG0089E
Invalid operator command <insert_0> ignored.
Severity
20 : Error
Explanation
An invalid operator command has been ignored.
Response
Correct and re-enter the command.
BFGAG0090I
This agent has been configured as a protocol bridge MQMFT agent.
Severity
0 : Information
Explanation
The agent has been successfully configured to operate as a protocol bridge MQMFT agent.
Response
No action is required.
BFGAG0091W
Invalid compression property value <insert_0> ignored.
Severity
10 : Warning
Explanation
An invalid compression property has been ignored.
Response
Fix the compression property value in the agents property files.
BFGAG0092I
The ''<insert_0>'' file will be used to request JVM diagnostic information.
Severity
0 : Information
Explanation
The JVM diagnostic service facility is enabled, which will help provide additional diagnostic information. For certain MQMFT agent environments, such as when running as a background process on Windows, the way of capturing JVM diagnostics is to have this facility enabled. JVM diagnostics should only be captured at the request of IBM service.
Response
No user action is necessary.
BFGAG0093W
A non-production service facility is enabled. The ''<insert_0>'' file will be used to request the generation of diagnostic trace.
Severity
10 : Warning
Explanation
A non-production service facility is enabled, which will help provide additional diagnostic information. This product function should only be enabled at the request of IBM service.
Response
No user action is necessary.
BFGAG0094W
A non-production service facility is enabled. The ''<insert_0>'' file will be monitored to request that the agent process end.
Severity
10 : Warning
Explanation
A non-production service facility is enabled, which will help provide additional diagnostic information. This product function should only be enabled at the request of IBM service.
Response
No user action is necessary.
BFGAG0097E
An internal error has occurred. Java diagnostic information cannot be generated because of: <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.
BFGAG0098I
A request to end the agent JVM process has been received.
Severity
0 : Information
Explanation
A request to end the agent JVM process has been submitted to the JVM process. The agent process will now end.
Response
No user action is necessary.
BFGAG0101E
The property named ''<insert_0>'' was specified as having the value ''<insert_1>'' in the agent.properties file. This is not a valid value for this property. The values ''true'' and ''false'' are the only valid values for this property. The agent process will now end.
Severity
20 : Error
Explanation
The named property must be correctly specified in the configuration file, otherwise the process cannot start.
Response
Use the information in the message to determine which changes are needed in the configuration file specified. Update the configuration file with these changes and restart this process.
BFGAG0102E
The property named ''<insert_0>'' was specified as having the value ''<insert_1>'' in the agent.properties file. This is not a valid value for this property. The values ''all'', ''failures'' and ''none'' are the only valid values for this property. The agent process will now end.
Severity
20 : Error
Explanation
The named property must be correctly specified in the configuration file, otherwise the process cannot start.
Response
Use the information in the message to determine which changes are needed in the configuration file specified. Update the configuration file with these changes and restart this process.
BFGAG0103E
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 we need further assistance.
BFGAG0104I
The authority check for user ''<insert_0>'' and authority ''<insert_1>'' has mapped to checking the ''<insert_2>'' authority on queue ''<insert_3>''.
Severity
0 : Information
Explanation
The authority check for the specified user has been mapped to the specified IBM MQ authority of the specified queue.
Response
No user action is required.
BFGAG0105I
The authority check for user ''<insert_0>'' and authority ''<insert_1>'' has passed.
Severity
0 : Information
Explanation
The specified user has the specified authority and will be permitted to perform the associated operation.
Response
No user action is required.
BFGAG0106W
The authority check for user ''<insert_0>'' and authority ''<insert_1>'' has failed.
Severity
10 : Warning
Explanation
The specified user does not have the specified authority and will not be permitted to perform associated the operation.
Response
Determine if the specified user should be able to carry out the operation. If so, use the information provided in the product documentation to grant the user the specified permission. If not, use the information provided by the message to notify the specified user that they are not authorized to perform the operation.
BFGAG0107E
The agent has received a reason code of ''<insert_0>'' from the 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 problem. Resolve the problem. Contact the IBM support center if we need further assistance.
BFGAG0108E
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.
BFGAG0109E
A required IBM MQ Queue (<insert_0>), used for authority checking, is not defined to the queue manager to which this agent is connected (<insert_1>). The agent cannot continue without this queue being defined and will now end.
Severity
20 : Error
Explanation
The specified queue is not defined to the specified queue manager. The queue is required for agent authority checking and the agent cannot continue without the queue being defined. The agent process will end.
Response
The queue, specified by the message, is only required if the agent is configured to perform authority checking. Verify whether the agent is required to perform authority checking. If it is then define the specified queue. If it is not then disable this function of the agent. For more assistance consult the product documentation.
BFGAG0110E
The property named ''<insert_0>'' was assigned an incorrect value of ''<insert_1>''. Valid values for the property are either ''none'' or ''java''. The agent process will now end.
Severity
20 : Error
Explanation
The named property must be assigned one of the specified values, otherwise the process cannot start.
Response
Use the information in the message to determine which changes are needed in the configuration file specified. Update the configuration file with these changes and restart this process.
BFGAG0111E
The standby connection name is not valid: ''<insert_0>''. The agent process will now end.
Severity
20 : Error
Explanation
The specified standby connection name is not valid. Standby connection names must consist of a hostname immediately followed by a port number enclosed in parenthesis, for example: HOST.IBM.COM(1414). The agent process will not start if the standby connection name is incorrectly specified.
Response
Modify the agent.properties file so that the value assigned to the 'agentQMgrStandby' property is a valid standby connection name. Restart the agent.
BFGAG0112E
The standby connection name specifies a port number which is not valid: ''<insert_0>''. The agent process will now end.
Severity
20 : Error
Explanation
The specified standby connection name specifies a port number which is not valid. Port numbers must be a non-negative numeric valid. The agent process will not start if the connection name specifies a port number which is not valid.
Response
Modify the agent.properties file so that the value assigned to the 'agentQMgrStandby' property is a valid standby connection name. Restart the agent.
BFGAG0113E
The standby connection name duplicates the primary connection details: ''<insert_0>''. The agent process will now end.
Severity
20 : Error
Explanation
The specified standby connection name specifies the same host and port as the primary connection details for the agent. This would result in the agent not being highly available and so the agent will not start using this configuration.
Response
Modify the agent.properties file so that the value assigned to the 'agentQMgrStandby' does not duplicate the values assigned to the 'agentQMgrHost' and 'agentQMgrPort' properties. Restart the agent.
BFGAG0114I
No suitable root directory can be found for transfers that specify a relative path. This agent will not accept transfers that specify relative paths.
Severity
0 : Information
Explanation
The agent has been started without the 'transferRoot' property and the home directory for the user that started the agent either does not exist or cannot be both read from and written to. The agent will not accept file transfers that specify relative paths to files being transferred.
Response
No user action is required if the agent does not need to accept transfers that specify relative paths. If the agent requires to be able to process transfers that specify relative paths then either configure the agent using the 'transferRoot' property, or ensure that the user used to run the agent process has a valid home directory.
BFGAG0115I
Relative path transfer root directory: <insert_0>
Severity
0 : Information
Explanation
The agent will use the specified directory as the root directory for any file transfers which specify a relative path.
Protocol bridge agents are not supported on 'MFT Agent' installations of IBM MQ Managed File Transfer, they are only supported on 'MFT Service' installations.
Response
Configure the agent as a standard agent or install the IBM MQ Managed File Transfer Service.
BFGAG0117E
The agent is configured as a protocol bridge MQMFT agent and a sandbox has been configured.
Severity
20 : Error
Explanation
Sandboxes are not supported on protocol bridge MQMFT agents.
Response
Remove the sandboxRoot property from agent property file to disable the sandbox or configure the agent as a standard MQMFT agent.
BFGAG0119E
The agent has received MQI reason code ''<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 problem. Resolve the problem. Contact the IBM support center if we need further assistance.
BFGAG0120E
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.
BFGAG0121E
The agent cannot be configured with both the ''<insert_0>'' and ''<insert_1>'' properties.
Severity
20 : Error
Explanation
The agent cannot start because it has been incorrectly configured. The agent permits at most one of the specified properties to be specified, however both properties were specified. The agent process will now end.
Response
Consult the product documentation for more information about each of the specified properties. Change the configuration for the agent so that at most one of the properties is specified. Restart the agent process.
BFGAG0122E
The agent cannot start because of a problem with the user sandbox configuration.
Severity
20 : Error
Explanation
The agent cannot start because it has detected a problem with the user sandbox document. Consult the earlier error messages to determine the cause of the problem.
Response
Use the earlier error messages to help resolve the problem. When the problem has been resolved, restart the agent process.
BFGAG0123W
The agent received MQI reason code <insert_0> when opening the coordination queue ''<insert_1>'' on coordination queue manager ''<insert_2>'' from the agent queue manager ''<insert_3>''.
Severity
10 : Warning
Explanation
The agent received the specified MQI reason code when the agent attempted to open a coordination queue on the coordination queue manager. This will limit the reporting of transfer log information and status of scheduled transfers and resource monitoring, but will not stop the agent from transferring files.
Response
Investigate the health of the coordination queue manager and the configuration between the agent queue manager and the coordination queue manager and restart the agent as necessary.
BFGAG0124E
The agent received MQI reason code <insert_0> when opening a coordination queue ''<insert_1>'' on the coordination queue manager ''<insert_2>'' from the agent queue manager ''<insert_3>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to open a queue on the coordination queue manager from the agent queue manager. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Verify that the specified coordination queue manager name is correct in the coordination properties and that a transmission channel has been established between the agent queue manager and the coordination queue manager. If the agent queue manager is running on z/OS and is in an MQ cluster with the coordination queue manager, ensure that the channel initiator (CHINIT) is running. Resolve the problem and restart the agent.
BFGAG0125W
The maximum size to which the java heap can grow is ''<insert_0>''MB, which is the default value. This value may be too low dependent on the agent''s work load.
Severity
10 : Warning
Explanation
The default maximum memory size to which the java heap can grow may be too low. This may result in an agent failure with an out of memory error if the agent is processing multiple concurrent transfers.
Response
For more information, refer to 'Hints and tips for using MFT' under the 'MFT general troubleshooting' topic of the product documentation in the IBM MQ section of IBM Knowledge Center.
BFGAG0126E
One or more files specified in the extendedSecurityPath property were not found. The IBM MQ Advanced Message Security interceptor might not be loaded, or it might be partially loaded and malfunction. The agent will stop. The missing file(s) are: <insert_0>
Severity
20 : Error
Explanation
If we are using IBM MQ Advanced Message Security with MQMFT, you specify the location of the AMS library jars in the extendedSecurityPath property in a suitable property file. This message indicates that one or more of the jar locations specified does not exist.
Response
Ensure that IBM MQ Advanced Message Security is properly installed and that the paths in the extendedSecurityPath property are correct.
BFGAG0127E
One or more file names specified in the extendedSecurityPath property were invalid. The IBM MQ Advanced Message Security interceptor might not be loaded, or it might be partially loaded and malfunction. The agent will stop. The files involved are: <insert_0>
Severity
20 : Error
Explanation
If we are using IBM MQ Advanced Message Security with MQMFT, you specify the location of the AMS library jars in the extendedSecurityPath property in a suitable property file. This message indicates that one or more of the file paths specified was invalid. Specifically, the Java URL libraries reported an exception when converting the file path to an absolute URL with a file: scheme. The originally reported error(s) are included at the end of the message.
Response
Ensure that the paths in the extendedSecurityPath property are correct. Depending on your operating system you may need to escape some characters or use Unix-style path separators even on a non-Unix platform.
BFGAG0128W
The agent is running in a mode which cannot load the IBM MQ Advanced Message Security interceptor. The agent will continue, but AMS facilities will not be available.
Severity
10 : Warning
Explanation
If we use the extendedSecurityPath property in the property files, the agent attempts to load the AMS Java classes from the specified jar files. This is done using the standard agent classloader. This error indicates that the classloader which loaded the agent class is not the expected MQMFT agent classloader and so the AMS jars cannot be loaded.
Response
Ensure that MQMFT is installed correctly and being run according to the published documentation. If this does not solve the problem, contact the IBM Support Center for assistance.
BFGAG0131I
This agent has been configured as a Web Gateway agent.
Severity
0 : Information
Explanation
The agent has been configured to operate as a Web Gateway agent.
Response
No action is required.
BFGAG0132E
IBM MQ reported a problem with the SSL configuration for this agent (IBM MQ reason code: <insert_0>). The agent process will now exit.
Severity
20 : Error
Explanation
The agent has detected a problem with the SSL configuration used to connect to IBM MQ. For more details, consult the IBM MQ product documentation using the indicated reason code. The agent process is not able to continue after it encounters this condition and will exit.
Response
Use the information available from the IBM MQ product documentation to resolve the SSL related issue. Restart the agent process.
BFGAG0133E
This is an 'MFT Agent' installation of IBM MQ Managed File Transfer and the agent is configured as a Web Gateway agent.
Severity
20 : Error
Explanation
Web Gateway agents are not supported on 'MFT Agent' installations of IBM MQ Managed File Transfer, they are only supported on 'MFT Service' installations.
Response
Configure the agent as a standard agent or install the IBM MQ Managed File Transfer Service.
BFGAG0134I
A request to end the agent JVM process has been received.
Severity
0 : Information
Explanation
A request to end the agent JVM process has been submitted to the JVM process. The agent process will now end.
Response
No user action is necessary.
BFGAG0135W
A non-production service facility is enabled. The ''<insert_0>'' file will be monitored and the agent process will end if the file ceases to exist.
Severity
10 : Warning
Explanation
A non-production service facility is enabled, which will help provide additional diagnostic information. This product function should only be enabled at the request of IBM service.
Response
No user action is necessary.
BFGAG0136W
The command level for queue manager <insert_0> cannot be obtained. IBM MQ reason code: <insert_1>
Severity
10 : Warning
Explanation
The command level could not be obtained from the agent's queue manager. Normally this is not an issue. However for an MQMFT agent on z/OS connected to a WebSphere MQ V6.0.0 or WebSphere MQ V7.0.1 queue manager, if a fatal error occurs, it can result in the agent being unable to shut down.
Response
Refer to the IBM MQ product documentation for more information about the error code. When you have resolved the issue, restart the agent process.
BFGAG0137I
The agent is running as Windows service: ''<insert_0>''.
Severity
0 : Information
Explanation
The agent process is running as a Windows service.
Response
No action is required.
BFGAG0138I
The agent configured as Windows service ''<insert_0>'' is running in the foreground, and not as a Windows service.
Severity
0 : Information
Explanation
The agent process is configured to run as a Windows service but is currently running as a foreground process, since it was started with the -F command line option.
Response
No action is required.
BFGAG0139I
The agent has suspended its current transfers and is now stopping.
Severity
0 : Information
Explanation
A request to stop the agent has been received. All active transfers have been suspended and the agent is now stopping. Any outstanding commands will be stopped. Note that the agent had to force a shutdown because some transfers did not respond to the request to stop.
Response
No action is required.
BFGAG0140E
The agent has requested all transfers to stop but some transfers have failed to respond in time.
Severity
20 : Error
Explanation
A request to stop the agent has been received. Some active transfers are still running. After these respond to the request to stop, the agent will shut down. Any outstanding commands will be stopped if they do not complete after a short period of time.
Response
No action is required.
BFGAG0141E
The agent encountered a security error while attempting to open its data queue, <insert_0>. See the Explanation and User Action for this message in the IBM MQ Managed File Transfer product documentation.
Severity
20 : Error
Explanation
The agent uses a queue to receive incoming file data. The agent opens this queue when it starts up. On this occasion, IBM MQ has reported a security error. This might be due to a misconfiguration of IBM MQ Advanced Message Security, or a security policy which is not appropriate for this IBM MQ Managed File Transfer network. It is also possible for this error to occur due to an incorrect configuration of IBM MQ's own authority records.
Response
Ensure that the required set of authorities exist for the agent user, as defined in the topic "Managing authorities for resources specific to IBM MQ Managed File Transfer". If the agent runs in bindings mode, the agent user is the user which started the agent. If the agent runs in client mode the agent user may be the user which started the agent, but may instead be a different user (for example, if MCAUSER is set on the agent's channel, or if the userIdForClientConnect property is not appropriately set). In addition, review the agent queue manager's error logs and if using IBM MQ Advanced Message Security consult the IBM MQ product documentation for assistance on configuring security policies. For more information, see the product documentation for IBM MQ.
BFGAG0142E
The agent encountered a security error while attempting to open its data queue, <insert_0>. See the Explanation and User Action for this message in the IBM MQ Managed File Transfer product documentation.
Severity
20 : Error
Explanation
The agent uses a queue to receive incoming file data. The agent opens this queue when it starts up. On this occasion, IBM MQ has reported a security error.
Response
Ensure that the required set of authorities exist for the agent user, as defined in the topic "Managing authorities for resources specific to IBM MQ Managed File Transfer". If the agent runs in bindings mode, the agent user is the user which started the agent. If the agent runs in client mode the agent user may be the user which started the agent, but may instead be a different user (for example, if MCAUSER is set on the agent's channel, or if the userIdForClientConnect property is not appropriately set). For more information, see the product documentation for IBM MQ.
BFGAG0143E
This is an embedded installation of IBM MQ Managed File Transfer and the agent is configured as a Connect:Direct bridge agent.
Severity
20 : Error
Explanation
Connect:Direct bridge agents are not supported with embedded installations of IBM MQ Managed File Transfer.
Response
Configure the agent as a standard MQMFT agent.
BFGAG0144E
Incompatible properties have been configured for the MQMFT agent.
Severity
20 : Error
Explanation
Protocol bridge agent properties and Connect:Direct bridge agent properties must not be configured on the same MQMFT agent.
Response
If we have configured a Connect:Direct bridge agent, ensure you have not set properties that are specific to protocol bridge agents. If we have configured a protocol bridge agent, ensure you have not set properties that are specific to Connect:Direct bridge agents.
BFGAG0145I
This MQMFT agent has been configured as a Connect:Direct bridge agent. Connect:Direct JAI version: <insert_0>
Severity
0 : Information
Explanation
The MQMFT agent has been successfully configured to operate as a Connect:Direct bridge agent.
Response
No action is required.
BFGAG0146E
This is a z/OS installation of IBM MQ Managed File Transfer and the agent is configured as a Connect:Direct bridge agent.
Severity
20 : Error
Explanation
Connect:Direct bridge agents are not supported with IBM MQ Managed File Transfer for z/OS.
Response
Configure the agent as a standard MQMFT agent.
BFGAG0147E
Incompatible properties have been configured for the MQMFT agent.
Severity
20 : Error
Explanation
Protocol bridge agent properties must not be configured on an MQMFT agent that is configured as a Web Gateway agent.
Response
If we have configured a Web Gateway agent, ensure you have not set properties that are specific to protocol bridge agents. If we have configured a protocol bridge agent, ensure you have not set the agentType property to WEB_GATEWAY.
BFGAG0148E
The agent has been configured as a Connect:Direct bridge agent but the cdNode property has not been defined.
Severity
20 : Error
Explanation
MQMFT agent property cdNode, which specifies the Connect:Direct node to use, must be configured for a Connect:Direct bridge agent.
Response
Either reconfigure the agent so that it is not a Connect:Direct bridge agent or update the agent properties to include the cdNode property.
BFGAG0150E
Failed to initialize the Connect:Direct credential mappings in ConnectDirectCredentials.xml
Severity
20 : Error
Explanation
The Connect:Direct bridge agent requires that the credential mappings in ConnectDirectCredentials.xml are successfully initialized.
Response
Check for previous errors in the agent event log to determine the cause of the problem. Correct the problem and then restart the Connect:Direct bridge agent.
BFGAG0151E
Failed to initialize the Connect:Direct JAI library.
Severity
20 : Error
Explanation
The Connect:Direct bridge agent requires that the JAI library (CDJAI.jar) is present in the product installation root 'lib' directory.
Response
Check that the Connect:Direct JAI library is present in the product installation root 'lib' directory and try starting the agent again.
BFGAG0152E
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.
The Connect:Direct bridge agent requires that the process definitions in the process definitions file are successfully initialized.
Response
Check for previous errors in the agent event log to determine the cause of the problem. Correct the problem and then restart the Connect:Direct bridge agent.
BFGAG0154E
Failed to initialize the Connect:Direct node properties file <insert_0>
Severity
20 : Error
Explanation
The Connect:Direct bridge agent requires that the node properties in the node properties file are successfully initialized.
Response
Check for previous errors in the agent event log to determine the cause of the problem. Correct the problem and then restart the Connect:Direct bridge agent.
BFGAG0155W
The AgentQueueManagerConnectionListener onDisconnect method has thrown a RuntimeException. The exception is: <insert_0>
Severity
10 : Warning
Explanation
The user-defined onDisconnect method called when the agent disconnected from the agent queue manager has thrown a RuntimeException during its execution. The agent has continued but the onDisconnect method might not have functioned as intended.
Response
Check the reason for the RuntimeException being thrown.
BFGAG0156W
The AgentQueueManagerConnectionListener onConnect method has thrown a RuntimeException. The exception is: <insert_0>
Severity
10 : Warning
Explanation
The user-defined onConnect method called when the agent connected to the agent queue manager has thrown a RuntimeException during its execution. The agent has continued but the onConnect method might not have functioned as intended.
Response
Check the reason for the RuntimeException being thrown.
BFGAG0157E
The agent has suspended its current transfers and is now stopping.
Severity
20 : Error
Explanation
A request to stop the agent has been received. All active transfers have been suspended and the agent is now stopping. Any outstanding commands will be stopped. Note that the agent had to force a shutdown because some transfers did not respond to the request to stop.
Response
No action is required.
BFGAG0158W
Invalid compression property value <insert_0> ignored.
Severity
10 : Warning
Explanation
An invalid compression property has been ignored.
Response
Fix the compression property value in the agents property files.
BFGAG0159W
Invalid compression property value <insert_0> ignored.
Severity
10 : Warning
Explanation
An invalid compression property has been ignored.
Response
Fix the compression property value in the agents property files.
BFGAG0160I
The additional function in Fix Pack <insert_0> has been enabled for this agent.
Severity
0 : Information
Explanation
The wmqfte.properties file contains an entry that has enabled the optional additional function that is available in the given fix pack release.
Response
No action is required.
BFGAG0161E
IBM MQ reported a problem with the SSL configuration for this agent (IBM MQ reason code: <insert_0>. Diagnostic message code: <insert_1>). The agent process will now exit.
Severity
20 : Error
Explanation
The agent has detected a problem with the SSL configuration used to connect to IBM MQ. For more details, consult the IBM MQ product documentation using the indicated reason code and diagnostic message code. The agent process is not able to continue after it encounters this condition and will exit.
Response
Use the information available from the IBM MQ product documentation to resolve the SSL related issue. Restart the agent process.
BFGAG0162E
The agent received MQI reason code <insert_0> with diagnostic message code <insert_1> when establishing a client transport mode connection to the default queue manager with connection name ''<insert_2>'' and using channel ''<insert_3>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to establish a client transport mode connection to the default queue manager. For more details, consult the IBM MQ product documentation using the indicated reason code and diagnostic message code. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0163E
The agent received MQI reason code <insert_0> with diagnostic message code <insert_1> when establishing a client transport mode connection to the queue manager ''<insert_2>'' with connection name ''<insert_3>'' and using channel ''<insert_4>''. The agent cannot continue and will end.
Severity
20 : Error
Explanation
The agent received the specified MQI reason code when the agent attempted to establish a client transport mode connection to the specified queue manager. For more details, consult the IBM MQ product documentation using the indicated reason code and diagnostic message code. This problem prevented the agent from carrying out further work and caused the agent to end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem and restart the agent.
BFGAG0164E
The property named ''<insert_0>'' was assigned a value of ''<insert_1>'' which is greater than then maximum supported value of ''<insert_2>''. The agent process will now end.
Severity
20 : Error
Explanation
The property value that was specified was too large. Specify a smaller value.
Response
Specify a value that is no larger than the maximum size given in the message.
BFGAG0165E
The agent received an unsupported interprocess communications message. Message contents: <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.
BFGAG0166W
The service name property of the interprocess communications mechanism <insert_0> has not been defined or is set to a blank service name.
Severity
10 : Warning
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGAG0167W
The interprocess communications mechanism for service name <insert_0> has failed to start, because of error: <insert_1>
Severity
10 : Warning
Explanation
The interprocess communications mechanism has failed to start for the reason given. This means that local communication with the agent for diagnostic monitoring and control purposes is not possible.
Response
Examine the reason given for the failure and take action as appropriate. When the problem is resolved, restart the agent to enable the interprocess communications mechanism. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGAG0168I
A request to immediately shut down this agent has been received.
Severity
0 : Information
Explanation
An external shutdown request has been received and this agent is performing an immediate shutdown.
Response
No action is required.
BFGAG0169I
A request to shut down this agent has been received.
Severity
0 : Information
Explanation
An external shutdown request has been received and this agent is now waiting for the current transfer to complete.
Response
No action is required.
BFGAG0170W
The agent has ended because the queue manager is unavailable. The agent will be restarted when the queue manager becomes available.
Severity
10 : Warning
Explanation
The agent has ended because the queue manager is no longer available. When the queue manager becomes available again the process controller will restart the agent.
Response
If the queue manager was deliberately stopped, then no action is required. Otherwise the queue manager should be investigated to discover the cause of the problem.
BFGAG0171E
The agent has ended abnormally with return code <insert_0>.
Severity
20 : Error
Explanation
The agent ended abnormally because of an error. If this is recoverable then the agent will be automatically restarted by the process controller.
Response
None, normally this type of error can be tolerated. But if the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGAG0172E
The agent has been prevented from starting because it has been configured as a protocol bridge agent, which is not supported on 4690 OS.
Configure the agent as a standard agent and attempt to start it again.
BFGAG0173E
The agent has been prevented from starting because it has been configured as a Connect:Direct bridge agent, which is not supported on 4690 OS.
Severity
20 : Error
Explanation
The Connect:Direct bridge function cannot be used on 4690 OS.
Response
Configure the agent as a standard agent and attempt to start it again.
BFGAG0174E
The agent has been prevented from starting because it has been configured as a Web Gateway agent, which is not supported on 4690 OS.
Severity
20 : Error
Explanation
The Web Gateway function cannot be used on 4690 OS.
Response
Configure the agent as a standard agent and attempt to start it again.
BFGAG0175E
License agreement not yet accepted: Installation will not work until the license agreement is accepted.
Severity
20 : Error
Explanation
The license agreement must be accepted before installation can proceed.
Response
Use the ftelap command to view and accept the license before proceeding
BFGAG0176E
The directory ''<insert_0>'' specified for the transferRoot agent property is not valid. For a 4690 OS agent this property must refer to an absolute path. The agent cannot continue.
Severity
20 : Error
Explanation
When specifying the value of the transferRoot property for an agent running on 4690 OS, the path specified must be absolute. Relative path values for transferRoot are not supported.
Response
Change the value of transferRoot to an absolute path.
BFGAG0177E
The agent.properties file has the doNotUseTempOutputFile property set to true, which is not supported on 4690 OS.
Severity
20 : Error
Explanation
It is not supported for 4690 agents to write directly to the final destination file. Therefore the doNotUseTempOutputFile property must be set to false or defaulted to false.
Response
Check the contents of the agent.properties file for the agent and ensure that the doNotUseTempOutputFile property is set to false or defaulted to false.
BFGAG0179E
The agent has ended abnormally with return code <insert_0>.
Severity
20 : Error
Explanation
The agent ended abnormally because of an error.
Response
Restart the agent. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGAG0180W
A bindings transport mode connection cannot be established to the default queue manager. The reason code is <insert_0>. The agent will try the operation again every <insert_1> seconds.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot establish a bindings mode connection to the default queue manager because of the specified MQI reason code. The agent will keep trying the operation again at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGAG0181W
A bindings transport mode connection cannot be established to queue manager ''<insert_0>''. The reason code is <insert_1>. The agent will try the operation again every <insert_2> seconds.
Severity
10 : Warning
Explanation
The agent cannot transfer file information because the agent cannot establish a bindings mode connection to the specified queue manager because of the specified MQI reason code. The agent will keep trying the operation again at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
The agent received MQI reason code <insert_0>. Agent recovery will be initiated.
Severity
0 : Information
Explanation
The agent received a recoverable MQI reason code. Agent recovery will be initiated if the agent is not stopping or is not already recovering beacuse of an earlier recoverable error.
Response
No action required.
BFGAG0184W
The agent property ''<insert_0>'' has been defined but the "agentSslTrustStore" property has not been defined. Secure TLS handshaking will not be requested if the agent attempts to connect to its agent queue manager using the CLIENT transport mode.
Severity
10 : Warning
Explanation
An agent will only attempt to connect to its queue manager using a secure TLS connection when the "agentSslTrustStore" property has been defined.
Response
Ensure the "agentSslTrustStore" property has been defined and points to a valid certificate store if a TLS CLIENT transport mode connection to the agent's queue manager is required.
BFGAG0185W
The agent property ''<insert_0>'' has been defined but one of the "agentSslCipherSpec" or "agentSslCipherSuite" properties have not been defined. For secure CLIENT transport mode connections, a cipher must be specified, which corresponds to the one defined on the server-connection channel, that is used by the agent to connect to its queue manager.
Severity
10 : Warning
Explanation
While validating the defined properties in the agent.properties file, an expected set of TLS property combinations was found to be incomplete. Secure TLS handshaking may fail with the current configuration.
Response
Define one of the "agentSslCipherSpec" or "agentSslCipherSuite" properties with a value that maps to the MQ CipherSpec defined on the server-connection channel used by the agent. Please refer to the product documentation for more details.
BFGAG0186W
The agent property ''<insert_0>'' has been defined but the associated agent property ''<insert_1>'' has not been defined. Secure TLS handshaking may fail with the current configuration.
Severity
10 : Warning
Explanation
While validating the defined properties in the agent.properties file, an expected set of TLS property combinations was found to be incomplete.
Response
Review the agent's TLS property settings to ensure they are complete. Please refer to the product documentation for more details.
BFGAG0187E
The attempt to connect to a queue manager has failed because of missing or incorrect security details.
Severity
20 : Error
Explanation
An attempt to connect to a queue manager has failed because of an authorization issue. A potential cause of the failure might be because a password of more than 12 characters in length was provided when authorizing using Compatibility Mode. Passwords longer than 12 characters in length are only supported when using MQCSP authentication.
Response
In the situation when a password greater than 12 characters in length is used to authenticate with the queue manager, ensure that the useMQCSPAuthentication parameter is set to true for the user entry in the credentials file. In all other cases review the MFT configuration and update the credentials file to include the necessary information to allow connection to the queue manager.
BFGAG0190W
The agent is connected to a queue manager and was not able to determine whether the queue manager was suitably licensed for IBM MQ Managed File Transfer usage.
Severity
10 : Warning
Explanation
This message is output when IBM MQ Managed File Transfer agent is connected to a queue manager but could not confirm whether the queue manager was licensed for usage with IBM MQ Managed File Transfer. The IBM MQ Managed File Transfer agent can be used with a queue manager on distributed, z/OS or appliance platforms providing it has correct entitlement. On distributed platforms the queue manager must have IBM MQ Advanced or IBM MQ Managed File Transfer entitlement. On z/OS platforms the queue manager must have IBM MQ Advanced VUE, IBM MQ Managed File Transfer or IBM MQ Advanced entitlement.
Response
Confirm that we have an appropriate license for using IBM MQ Managed File Transfer agent with the queue manager it is connecting to.
BFGAG0191I
The agent is connected to a queue manager which is suitably licensed for usage with IBM MQ Managed File Transfer.
Severity
0 : Information
Explanation
This message is output when IBM MQ Managed File Transfer agent is connected to a queue manager which is suitably licensed for usage with IBM MQ Managed File Transfer. On distributed platforms the queue manager must have IBM MQ Advanced or IBM MQ Managed File Transfer entitlement. On z/OS platforms the queue manager must have IBM MQ Advanced VUE, IBM MQ Managed File Transfer or IBM MQ Advanced entitlement.
Response
No action is required.
BFGAG0192I
The agent has successfully initialized as an active instance on host ''<insert_0>''.
Severity
0 : Information
Explanation
The agent has successfully initialized as active instance and is preparing to process transfers.
Response
No action is required.
BFGAG0193I
The agent has successfully initialized as a standby instance on host ''<insert_0>''.
Severity
0 : Information
Explanation
The agent has successfully initialized as a standby instance and is waiting to take over.
Response
No action is required.
BFGAG0194E
An instance of this agent is already running elsewhere. Hence this instance cannot continue and will end.
Severity
20 : Error
Explanation
An instance of this agent is already running on another machine.
Agent queue ''<insert_0>'' required for high availability is not defined in agent queue manager.
Severity
20 : Error
Explanation
An agent queue is required for agent high availability configuration to work. The queue isis not defined in the agent queue manager.
Response
Define the required agent queue and resubmit the request.
BFGAG0196E
Failed to open agent queue ''<insert_0>'' due to a security error. The IBM MQ reason code is <insert_1>.
Severity
20 : Error
Explanation
The specified user does not have the PUT and GET authority on agent high availability queue.
Response
Use the information provided in the product documentation to grant the user the specified permission.
BFGAG0197E
Failed to open agent queue ''<insert_0>''. The IBM MQ reason code is <insert_1>.
Severity
20 : Error
Explanation
Agent encountered an IBM MQ error while accessing high availabilty queue.
Response
Use the information provided for the error code in the product documentation and take necessary action.
BFGAG0198E
High availability function not supported for agent type ''<insert_0>''. Agent will stop.
Severity
20 : Error
Explanation
Hight availability function is supported only for STANDARD and BRIDGE type agents. It is not supported for CD_BRIDGE and Embedded type agents.
Response
Modify agent configuration and resubmit the request.
BFGAG0199E
The version of IBM MQ Managed File Transfer installed on standby machine does not match with the version on active instance running elsewhere. This instance of agent will stop.