BFGCL0001 - BFGCL9999

BFGCL0001E: An internal error has occurred. 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.

BFGCL0002E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <insert_1>. A connection could not be established to queue manager <insert_2>, on host ''<insert_3>'' using port <insert_4> and channel <insert_5>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered. The problem occurred while trying to establish a client transport mode connection to the specified queue manager, using the specified connection information.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0003E: A messaging problem prevented the command from completing successfully, for queue <insert_3> on queue manager <insert_2>. The IBM MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0004E: Unable to determine the source queue manager to use.
Severity: 20 : Error
Explanation: It is not possible to determine which source queue manager to use for the transfer.
Response: Explicitly specify the source queue manager as a command line argument.

BFGCL0005E: Unable to determine the destination queue manager to use.
Severity: 20 : Error
Explanation: It is not possible to determine which destination queue manager to use for the transfer.
Response: Explicitly specify the destination queue manager as a command line argument.

BFGCL0006E: An internal error has occurred. 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.

BFGCL0007E: One, or more, source file specifications must be supplied.
Severity: 20 : Error
Explanation: The command has been issued with no source file specifications. A source file specification corresponds to one or more files, a directory, or a data set to transfer. The command requires that at least one source file specification is provided.
Response: Refer to the command line help or to the product documentation to determine how to specify source file specifications. Reissue the command supplying one or more source file specifications.

BFGCL0008E: The ''<insert_0>'' property must be specified on the command line.
Severity: 20 : Error
Explanation: The specified property must be specified on the command line of the command.
Response: Reissue the command specifying the missing property.

BFGCL0009E: Exactly one of the following properties must be specified on the command line: ''<insert_0>'', ''<insert_1>'', ''<insert_2>'' or ''<insert_3>''.
Severity: 20 : Error
Explanation: The command has been issued without any one of the specified properties present. The command requires that exactly one of these properties is specified.
Response: Refer to the command line help or to the product documentation to determine which property to specify. Reissue the command supplying exactly one of the properties.

BFGCL0010E: The ''<insert_0>'' command line property cannot be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two specified properties cannot be specified together. A maximum of one of the specified options can be present for a single invocation of the command.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0011E: An internal error has occurred. 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.

BFGCL0012E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0013E: A maximum of one pattern specification can be supplied.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that can be interpreted as a pattern specification. The command requires that zero or one patterns are specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying either no pattern specification or a single pattern specification.

BFGCL0014W: No agents exist that match the current selection criteria.
Severity: 10 : Warning
Explanation: The command has completed successfully but no agent information can be listed. This is either because no agents are registered with the coordination queue manager or because the pattern specified as part of the command did not match any agents that are registered with the coordination queue manager.
Response: If a pattern was specified, consider reissuing the command with a more inclusive pattern.

BFGCL0015E: A maximum of one agent name can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as an agent name. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0016E: An agent name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no agent name parameter. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0017W: No agent exists that matches the name specified on the command line.
Severity: 10 : Warning
Explanation: The command has completed successfully but no agent information can be listed. This is because no agent is registered with the coordination queue manager using the agent name specified as a command line argument.
Response: Check that the agent name specified is correct. If the agent name is not correct, reissue the command with the correct agent name. If the agent name is correct, verify that the command is being issued to the same coordination queue manager that the agent is configured to use. If this does not resolve the problem, contact the IBM support center.

BFGCL0018E: An internal error has occurred. 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.

BFGCL0019E: A maximum of one agent name can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as an agent name. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0020E: An agent name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no agent name parameter. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0021E: Unable to determine the queue manager to use.
Severity: 20 : Error
Explanation: It is not possible to determine which queue manager to send the stop request to.
Response: Explicitly specify the queue manager as a command line argument.

BFGCL0023E: The agent could not be started because it was not able to open a lock file: <insert_0>.
Severity: 20 : Error
Explanation: The command could not open the specified file. The command to start the agent requires that the command is able to open this file. The agent has not been started.
Response: Use the information in the message to investigate why the file could not be opened. If possible, resolve the problem and reissue the command to start the agent. If this does not resolve the problem, contact the IBM support center for assistance.

BFGCL0024E: A maximum of one agent name can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as an agent name. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0025E: An agent name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no agent name parameter. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0026E: An internal error has occurred. The product installation directory cannot be determined.
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.

BFGCL0027E: The ''<insert_0>'' property is not specified in the ''<insert_1>'' properties file. This property must be present, otherwise the agent cannot be started.
Severity: 20 : Error
Explanation: The specified property is missing from the specified properties file. The property must be present, otherwise the agent cannot be started. As a result, the command has not started an agent process.
Response: Add the specified property to the properties file. Reissue the command to start the agent.

BFGCL0028E: The agent name of ''<insert_0>'' specified in the ''<insert_1>'' properties file does not match the agent name in the directory path in which the properties file is stored.
Severity: 20 : Error
Explanation: The specified agent name does not match the path used to locate the properties file. Both the agent name specified in the properties file and the path to the properties file must match. The agent has not been started.
Response: Modify the agent name in the specified properties file to match the agent name component of the path to the properties file.

BFGCL0029E: Another instance of agent ''<insert_0>'' is already running.
Severity: 20 : Error
Explanation: Another instance of the agent is already running. Only a single instance of any given agent can run at one time. A second instance of the agent has not been started.
Response: No action required.

BFGCL0030I: The request to start agent ''<insert_0>'' on this machine has been submitted.
Severity: 0 : Information
Explanation: The request to start the specified agent has been successfully submitted.
Response: No action is required.

BFGCL0031I: Agent log files located at: <insert_0>
Severity: 0 : Information
Explanation: The agent process, started by this command, is recording logging information to the specified location.
Response: No action is required.

BFGCL0032E: The command has failed to start agent ''<insert_0>'' due to: <insert_1>
Severity: 20 : Error
Explanation: The command has failed to start the specified agent process due to the specified problem.
Response: Use the information in the message to investigate the problem. Resolve the problem, if possible, and reissue the start agent command. If this does not resolve the problem, contact the IBM support center for assistance.

BFGCL0033E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <insert_1>. A connection could not be established to queue manager <insert_2>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered. The problem occurred while trying to establish a bindings transport mode connection to the specified queue manager.
Response: Refer to the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0034I: Stop request issued to agent ''<insert_0>''.
Severity: 0 : Information
Explanation: The command has successfully issued a stop request to the specified agent. When the agent receives this request, the agent will stop.
Response: No action is required.

BFGCL0035I: Transfer request issued. The request ID is: <insert_0>
Severity: 0 : Information
Explanation: The command has successfully issued the transfer request.
Response: No action is required.

BFGCL0036E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0> and the reason code was <insert_1>. A connection could not be established to the default queue manager on host ''<insert_2>'' using port <insert_3> and channel <insert_4>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered. The problem occurred while trying to establish a client transport mode connection to the default queue manager, using the specified connection information.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0037E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0> and the reason code was <insert_1>. A connection could not be established to the default queue manager.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered. The problem occurred while trying to establish a bindings transport mode connection to the default queue manager.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0038E: Could not find file ''<insert_0>''.
Severity: 20 : Error
Explanation: The command could not find the specified file. The command to start the agent requires that the command is able to open this file. The agent has not been started.
Response: Determine why the file is not present in the expected location. If possible, restore the file from a backup or re-create the agent configuration using the supplied tools.

BFGCL0039E: Could not find file ''<insert_0>''.
Severity: 20 : Error
Explanation: The command could not find the specified file. The command to start the agent requires that the command is able to open this file. The agent has not been started.
Response: Determine why the file is not present in the expected location. If possible, restore the file from a backup or re-create the agent configuration using the supplied tools.

BFGCL0040E: The same file specification cannot be both the source and the destination for a transfer operation.
Severity: 20 : Error
Explanation: You have provided the same file specification for both the source and the destination of a file transfer. Transferring data onto itself is not supported. This transfer will not be carried out.
Response: Correct the command line arguments so that the same file specification is not used as both the source and the destination of the transfer. Submit the command again.

BFGCL0042E: An internal error has occurred. 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.

BFGCL0043I: Specify the '-h' command line parameter to see more usage information.
Severity: 0 : Information
Explanation: Specify the '-h' parameter to display usage information about the command.
Response: No action required.

BFGCL0044E: The file ''<insert_0>'' already exists. Run the command again specifying the -f parameter to force file to be overwritten.
Severity: 20 : Error
Explanation: The file ''{0}'' exists, and you are trying to overwrite the file.
Response: If you want to overwrite the file, specify the '-f' parameter on the command line.

BFGCL0046E: The data directory specified in install.properties does not exist.
Severity: 20 : Error
Explanation: The product has been configured to use a data directory that does not exist.
Response: Check that the data directory specified in the install.properties file exists.

BFGCL0047E: The directory ''<insert_0>'' already exists.
Severity: 20 : Error
Explanation: The directory ''{0}'' exists and you are trying to overwrite the directory.
Response: If you want to overwrite the directory, specify the '-f' parameter on the command line

BFGCL0048E: An unknown parameter was specified on the command line: ''<insert_0>''
Severity: 20 : Error
Explanation: The command line parameter indicated is not a valid parameter for this command.
Response: Correct the command line so that only valid parameters are specified. If necessary, issue the command with a '-h' parameter to display usage information.

BFGCL0049E: An agent name must be specified when creating an agent.
Severity: 20 : Error
Explanation: We cannot create an agent without specifying an agent name.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0050E: Cannot find wmqfte.properties file. Run fteSetupCoordination to rectify this problem.
Severity: 20 : Error
Explanation: The wmqfte.properties file cannot be found.
Response: Run the fteSetupCoordination command to rectify the problem.

BFGCL0051E: A coordination queue manager must be specified when creating an agent.
Severity: 20 : Error
Explanation: We cannot create an agent without specifying the coordination queue manager.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0052E: An agent queue manager must be specified when creating an agent.
Severity: 20 : Error
Explanation: We cannot create an agent without specifying the agent's queue manager.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0053I: Agent configured and registered successfully.
Severity: 0 : Information
Explanation: Agent configured and registered successfully.
Response: No action required.

BFGCL0054E: The call to create directory ''<insert_0>'' failed.
Severity: 20 : Error
Explanation: The call to create the specified directory failed.
Response: Check that we can write to the directory space you specified.

BFGCL0055E: An internal error has occurred. The ''<insert_0>'' file cannot be located in the product install directory ''<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.

BFGCL0056E: Port property should be an integer in the range 0 and 65534. You entered ''<insert_0>'', correct the parameter and retry.
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.

BFGCL0057E: An internal error has occurred. The product data directory ''<insert_0>'' does not exist.
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.

BFGCL0058E: You have specified a port or channel parameter without specifying a host. If you want to use a client connection, you must specify a host.
Severity: 20 : Error
Explanation: You have specified a port or channel parameter without specifying a host. If you want to use a client connection, you must specify a host.
Response: Run command again specifying a host with the parameter -agentQMgrHost.

BFGCL0059E: The file ''<insert_0>'' already exists. Run command again specifying the -f parameter to force file to be overwritten.
Severity: 20 : Error
Explanation: The specified file already exists, and you are trying to overwrite the file.
Response: If you want to overwrite the file, specify the '-f' parameter on the command line.

BFGCL0060E: Cannot connect to host ''<insert_0>''.
Severity: 20 : Error
Explanation: Cannot connect to the specified host.
Response: Check the host is reachable from the machine you are running the command from.

BFGCL0061E: There was a problem connecting to IBM MQ. The reason code was: ''<insert_0>''.
Severity: 20 : Error
Explanation: There was a problem connecting to IBM MQ described by the specified reason code.
Response: Check the MQRC reason codes and take appropriate action.

BFGCL0062E: There was a problem connecting to IBM MQ. The reason code was: ''<insert_0>''.
Severity: 20 : Error
Explanation: There was a problem connecting to IBM MQ described by the specified reason code.
Response: Check the MQRC reason codes and take appropriate action.

BFGCL0063E: There was a generic input/output exception. The message given was: ''<insert_0>''.
Severity: 20 : Error
Explanation: There was a generic input/output exception.
Response: Correct the error in the exception and try again.

BFGCL0064E: You have specified a port or channel parameter without specifying a host. If you want to use a client connection, you must specify a host.
Severity: 20 : Error
Explanation: You have specified a port or channel parameter without specifying a host. If you want to use a client connection, you must specify a host.
Response: Run command again specifying a host with the parameter -commandQMgrHost.

BFGCL0065E: You have specified a port or channel parameter without specifying a host. If you want to use a client connection, you must specify a host.
Severity: 20 : Error
Explanation: You have specified a port or channel parameter without specifying a host. If you want to use a client connection, you must specify a host.
Response: Run command again specifying a host with the parameter -coordinationQMgrHost.

BFGCL0066E: The directory ''<insert_0>'' does not exist. Run fteSetupCoordination using the -p parameter to specify a non default coordination queue manager.
Severity: 20 : Error
Explanation: The specified directory does not exist. Run the fteSetupCoordination command using the -p parameter to specify a non-default coordination queue manager.
Response: Run fteSetupCoordination command specifying a non-default coordination queue manager using the -p parameter.

BFGCL0072E: The specified directory ''<insert_0>'' does not exist. Check the spelling, or run fteSetupCoordination to create directory.
Severity: 20 : Error
Explanation: The specified directory does not exist. Check the spelling or run the fteSetupCoordination command to create the directory.
Response: The specified directory does not exist. Check the spelling, or run the fteSetupCoordination command to create the directory.

BFGCL0073I: The specified queue manager ''<insert_0>'' is already the default queue manager. No changes have been made.
Severity: 0 : Information
Explanation: The specified queue manager is already the default queue manager. No changes have been made.
Response: No action required.

BFGCL0074I: The specified configuration options ''<insert_0>'' are now the default.
Severity: 0 : Information
Explanation: The specified configuration options are now the default.
Response: No action required.

BFGCL0075E: A maximum of one data directory can be specified for the command.
Severity: 20 : Error
Explanation: You have specified more then one directory or parameter on the command line.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the full data directory path

BFGCL0076E: The user must specify a data directory for the command.
Severity: 20 : Error
Explanation: The command has been issued with no data directory. The command requires that exactly one data directory parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the full data directory path

BFGCL0077E: The data.link file already exists in the specified data directory ''<insert_0>''.
Severity: 20 : Error
Explanation: The data directory is already in use by another IBM MQ Managed File Transfer installation. Specify the -f parameter before the specified data directory to force the command to configure the directory.
Response: The data directory is already in use by another IBM MQ Managed File Transfer installation. Specify the -f parameter before the specified data directory to force the command to configure the directory.

BFGCL0078E: There was an error when trying to find the file: ''<insert_0>''.
Severity: 20 : Error
Explanation: The command failed to create the file. Check we have the required permissions and retry.
Response: The command failed to create the file. Check we have the required permissions and retry.

BFGCL0079E: There was an input/output error when trying to use the file: ''<insert_0>''.
Severity: 20 : Error
Explanation: The command failed to create the file. Check we have the required permissions and retry.
Response: The command failed to create the file. Check we have the required permissions and retry.

BFGCL0080E: The specified directory: ''<insert_0>'' is not empty. Specify the -f parameter before the directory if you still wish to use this directory.
Severity: 20 : Error
Explanation: The data directory is not empty. Specify the -f parameter before the specified data directory to force the command to configure the directory.
Response: The data directory is not empty. Specify the -f parameter before the specified data directory to force the command to configure the directory.

BFGCL0081E: The command was unable to create the file: ''<insert_0>''. Check that we have the required permissions and retry.
Severity: 20 : Error
Explanation: The command was unable to create the file. Check that we have the required permissions and retry.
Response: The command was unable to create the file. Check that we have the required permissions and retry.

BFGCL0082E: The command was unable to create the file: ''<insert_0>''. Check that we have the required permissions and retry.
Severity: 20 : Error
Explanation: The command was unable to create the file. Check that we have the required permissions and retry.
Response: The command was unable to create the file. Check that we have the required permissions and retry.

BFGCL0083E: The agent ''<insert_0>'' is still running. Before deleting the agent, you must run fteStopAgent to stop the agent.
Severity: 20 : Error
Explanation: The agent you want to delete is still running. An agent cannot be deleted until it stopped.
Response: Run the fteStopAgent command for the agent you want to delete. Reissue the fteDeleteAgent command when the agent has stopped.

BFGCL0084E: The command was unable to delete the directory: ''<insert_0>''. Check that we have the required permissions and retry.
Severity: 20 : Error
Explanation: The command failed to delete the directory.
Response: Check that we have the required permissions to delete directories. Reissue the command.

BFGCL0085E: The command was unable to delete the agent ''<insert_0>'' because the agent does not exist. Check spelling and try again.
Severity: 20 : Error
Explanation: The command did not complete because the command could not find the \ agent. Check the spelling of the agent name and reissue the command.
Response: Check the spelling of the agent name.

BFGCL0086E: The command was specified with no agent name. Run the command with the -h parameter to see the usage information.
Severity: 20 : Error
Explanation: You must specify an agent name for this command. Run command with the -h parameter to see usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0087E: A maximum of one set of configuration options can be specified as an argument.
Severity: 20 : Error
Explanation: You have issued the command with more than one parameter that has been interpreted as a set of configuration options. You must specify exactly one set ofconfiguration options for this command. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one set of configuration options parameter.

BFGCL0088E: Only one agent name can be specified as an argument. Run the command with the -h parameter to see usage information.
Severity: 20 : Error
Explanation: You must specify a single agent name for this command. Run the command with the -h parameter to see the usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0089E: The command was run without a traceLevel parameter. Run the command with the -h parameter to see usage information.
Severity: 20 : Error
Explanation: The trace request was not processed because the command was run without a traceLevel parameter. Run the command with the -h parameter to see usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0090E: Unable to determine which queue manager to use. Explicitly specify the queue manager as a command line argument.
Severity: 20 : Error
Explanation: It is not possible to determine which queue manager to send the trace request to.
Response: Refer to the command line help or to the product documentation.

BFGCL0091I: The trace request was successfully sent to agent ''<insert_0>''.
Severity: 0 : Information
Explanation: The trace request was successfully sent to the specified agent. The agent will receive the request and update its trace specification based on that request. Any trace information will be generated in the directory that the agent outputs its logs to.
Response: No action is required. We can confirm that the agent has processed the request by looking for a corresponding entry in the agent's log file.

BFGCL0092I: Use the following MQSC commands to clear and delete the agent''s queues on queue manager ''<insert_0>''.
Severity: 0 : Information
Explanation: A file has been created that contains the required MQSC commands to complete the deletion of an agent.
Response: Use the file generated to delete the local queues for the agent.

BFGCL0093E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0094E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0095E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0096E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0097E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0098E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0099E: The ''<insert_0>'' command line property cannot be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two specified properties cannot be specified together. A maximum of one of the specified options is allowed on a single invocation of the command. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0100E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0101E: The ''<insert_0>'' command line property can only be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two properties must be specified together. The command cannot be completed.
Response: Refer to the command line help or to the product documentation, to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0102E: The ''<insert_0>'' command line property cannot be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: We cannot specify the two specified properties together. A maximum of one of the specified options is allowed for a single invocation of the command. The command cannot be completed.
Response: Refer to the command line help or to the product documentation, to determine the correct set of command line properties required. Reissue the command using a corrected set of command line properties.

BFGCL0103E: A maximum of one agent pattern can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as an agent pattern. The command requires that no more than one agent pattern parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent pattern parameter.

BFGCL0105W: No schedules exist that match the current selection criteria.
Severity: 10 : Warning
Explanation: The command has completed successfully but no schedule information can be listed. This is either because no schedules are registered, or because the pattern specified as part of the command did not match any schedules that are registered.
Response: If a pattern was specified, consider reissuing the command with a more inclusive pattern.

BFGCL0106E: An error occurred when trying to unregister the agent with the coordination queue manager. The agent might still be registered with the coordination queue manager.
Severity: 20 : Error
Explanation: The command failed to unregister the agent with the coordination queue manager.
Response: Consult the product documentation for more information.

BFGCL0107I: The agent has been successfully deleted.
Severity: 0 : Information
Explanation: The request to delete the specified agent has been completed successfully.
Response: No action required.

BFGCL0108E: An internal error has occurred. 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.

BFGCL0109E: A maximum of one schedule identifier can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as a schedule identifier. The command requires that exactly one schedule identifier parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one schedule identifier parameter.

BFGCL0110E: A schedule identifier parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no schedule identifier parameter. The command requires that exactly one schedule identifer parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly schedule identifier parameter.

BFGCL0111E: Unable to determine which queue manager to use.
Severity: 20 : Error
Explanation: It is not possible to determine which queue manager to send the delete scheduled transfer command to.
Response: Explicitly specify the queue manager as a command line argument.

BFGCL0112E: An agent name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no agent name parameter. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Explicitly specify the agent name as a command line argument.

BFGCL0113E: The schedule identifier ''<insert_0>'' is not valid
Severity: 20 : Error
Explanation: The command has been invoked with a schedule identifer parameter that is not a positive integer. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the schedule identifier as a positive integer.

BFGCL0114I: The request to delete scheduled transfer ''<insert_0>'' issued to agent ''<insert_1>''.
Severity: 0 : Information
Explanation: The command has successfully issued a delete scheduled transfer request to the specified agent. When the agent receives this request, the agent will delete the scheduled transfer.
Response: No action is required.

BFGCL0115E: The XML parser has detected the following error in an XML message <insert_0>.
Severity: 20 : Error
Explanation: A received XML message has failed to match the defined schema.
Response: Review the XML message and correct the message as necessary to match the schema.

BFGCL0116E: The XML parser has detected the following error in an XML message <insert_0>.
Severity: 20 : Error
Explanation: A received XML message has failed to match the defined schema with an unrecoverable error.
Response: Review the XML message and correct the message as necessary to match the schema.

BFGCL0117E: The XML parser has detected the following error in an XML message <insert_0>.
Severity: 20 : Error
Explanation: A received XML message has failed to match the defined schema and reported a warning.
Response: Review the XML message and correct the message as necessary to match the schema.

BFGCL0118E: An internal error occurred while attempting to read the XML message.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: This exception is unexpected. The cause is not immediately known.

BFGCL0119E: An internal error occurred while attempting to configure the parser.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: This exception is unexpected. The cause is not immediately known.

BFGCL0120E: A internal problem occurred relating to the decoding of an XML message.
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.

BFGCL0121E: The XML schema checker reports the following problem "<insert_0>"
Severity: 20 : Error
Explanation: A file transfer request received by this agent has failed the XML schema check.
Response: Validate the generation of the file transfer request to ensure the request complies with the XML schema.

BFGCL0122E: An internal error has occurred. 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.

BFGCL0123E: The trace level specified ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The value passed to the command is not supported. Valid trace values are all, verbose, moderate, flow, and off.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying a valid trace level.

BFGCL0124E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0125I: Ensure that the BFG_DATA environment variable is set to ''<insert_0>'' before issuing further commands.
Severity: 0 : Information
Explanation: The BFG_DATA environment variable must be set to the specified data directory value. This environment variable is used, by other commands, to determine the location of the product data directory.
Response: Set the BFG_DATA environment variable to the specified value. For more information refer to the MQ Info center

BFGCL0126I: We can optionally delete the IBM MQ objects used by this agent from queue manager <insert_0>.
Severity: 0 : Information
Explanation: The IBM MQ objects used by the agent are no longer required. We can delete the object definitions from the specified queue manager.
Response: Optionally, delete the IBM MQ objects from the specified queue manager. For more information about the objects used by an agent, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCL0128I: The agent requires a number of IBM MQ objects to be defined to queue manager <insert_0>. Ensure these definitions are present before starting the agent.
Severity: 0 : Information
Explanation: The agent requires a number of IBM MQ objects to be defined to the specified queue manager. These definitions are required for the agent process to function correctly. Ensure that we have defined the appropriate IBM MQ objects before you start the agent.
Response: Refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/. Use this information to determine the object definitions required. Define these objects to the specified queue manager. After we have defined these objects, start the agent.

BFGCL0130E: The metadata parameter <insert_0> is missing an = and is incorrectly formatted.
Severity: 20 : Error
Explanation: The metadata parameter does not have the correct format and the name and data pairs can not be identified correctly. The command cannot be completed.
Response: Review this metadata parameter and ensure the parameter follows the format of = and each pair is separated by a comma. Reissue the command.

BFGCL0131E: An internal error has occurred. 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.

BFGCL0132E: A maximum of one transfer identifier can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as a transfer identifier. The command requires that exactly one transfer identifier parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one transfer identifier parameter.

BFGCL0133E: A transfer identifier parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no transfer identifier parameter. The command requires that exactly one transfer identifer parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one transfer identifier parameter.

BFGCL0134E: Unable to determine which queue manager to use.
Severity: 20 : Error
Explanation: It is not possible to determine which queue manager to send the fteCancelTransfer command to.
Response: Explicitly specify the queue manager as a command line argument.

BFGCL0135E: An agent name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no agent name parameter. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Explicitly specify the agent name as a command line argument.

BFGCL0136E: The transfer identifier ''<insert_0>'' is not valid
Severity: 20 : Error
Explanation: The command has been issued with a transfer identifier parameter that is not a 48-character hexadecimal string. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the transfer identifier as a 48-character hexadecimal string.

BFGCL0137I: The request to cancel transfer ''<insert_0>'' issued to agent ''<insert_1>''.
Severity: 0 : Information
Explanation: The command has successfully issued a cancel transfer request to the specified agent. When the agent receives this request, the agent will cancel the transfer.
Response: No action is required.

BFGCL0138E: An internal error has occurred. 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.

BFGCL0139I: The requested file transfer has successfully completed.
Severity: 0 : Information
Explanation: The command has successfully completed with all requested files being transferred to the destination.
Response: No action is required.

BFGCL0140W: The requested file transfer has completed with partial success.
Severity: 10 : Warning
Explanation: The command has completed with some of the requested files being transferred to the destination.
Response: Review the log messages to identify which files have not been transferred and why.

BFGCL0141E: The requested file transfer has completed with no files being transferred.
Severity: 20 : Error
Explanation: The command has failed and none of the requested files have been transferred to the destination.
Response: Review the log messages to identify the reason for this failure.

BFGCL0142I: The file transfer request has been submitted. The command is waiting for notification of the transfer's completion.
Severity: 0 : Information
Explanation: The command has successfully been submitted to the agent. The command is waiting for the results of the transfer.
Response: No action is required.

BFGCL0143E: Could not open file ''<insert_0>''. The agent could not be cleaned because of: <insert_1>.
Severity: 20 : Error
Explanation: The command could not open the specified file. The fteCleanAgent command needs to be able to open this file. The agent has not been cleaned.
Response: Use the information in the message to investigate why the file could not be opened. If possible, resolve the problem and reissue the command to clean the agent. If this does not resolve the problem, contact the IBM support center for assistance.

BFGCL0144E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code and reason code specified in the message indicate the type of problem encountered.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0145E: A maximum of one agent name can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as an agent name. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0146E: An agent name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no agent name parameter. The command requires that exactly one agent name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one agent name parameter.

BFGCL0147E: Unable to determine which queue manager to use.
Severity: 20 : Error
Explanation: It is not possible to determine which queue manager to send the clean request to.
Response: Explicitly specify the queue manager as a command line argument.

BFGCL0148E: The agent ''<insert_0>'' is running.
Severity: 20 : Error
Explanation: The agent is running. The clean command can only be issued if the agent is not running.
Response: Stop the agent and reissue the command.

BFGCL0149I: The agent ''<insert_0>'' has been cleaned.
Severity: 0 : Information
Explanation: The command has successfully cleaned the queues for the specified agent.
Response: No action is required.

BFGCL0150E: Not all of the queues for agent ''<insert_0>'' could be opened.
Severity: 20 : Error
Explanation: The agent, or any other application, must not have any of the agent's 5 queues opened. For the fteCleanAgent command to run successfully, the command must be able to open all of the agent's queues for exclusive access.
Response: Stop the agent and any other applications that have any of the agent's queues open. Then reissue the command.

BFGCL0151E: The command has failed to clean agent ''<insert_0>'' because of: <insert_1>
Severity: 20 : Error
Explanation: The command has failed to clean the specified agent because of the specified problem.
Response: Use the information in the message to investigate the problem. Resolve the problem, if possible, and reissue the clean agent command. If this does not resolve the problem, contact the IBM support center for assistance.

BFGCL0152E: Attempt to create a reply queue to receive the response has failed. Exception is ''<insert_0>''.
Severity: 20 : Error
Explanation: The command has the -w (wait for completion) parameter set but could not create a reply queue to receive the results.
Response: Run the command again without the -w (wait for completion) parameter or review the agent properties to identify the configuration problem.

BFGCL0153E: An internal error has occured. There was an attempt to wait on a reply queue before initialization has occurred has resulted in this command failing.
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.

BFGCL0154I: The file transfer request has been cancelled.
Severity: 0 : Information
Explanation: The command has been cancelled and none of the requested files have been transfered to the destination.
Response: No action is required.

BFGCL0155E: An internal error has occurred. 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.

BFGCL0156E: The -w (wait for completion) parameter can not be used in conjunction with the schedule parameters.
Severity: 20 : Error
Explanation: A file transfer request was issued with both a deferred schedule request and a wait for completion parameter. The wait for completion parameter is valid only for immediate transfers. This command has not been completed.
Response: Review the fteCreateTransfer parameters and remove either the schedule or the wait complete parameters.

BFGCL0157I: Monitor of the file transfer request has stopped because the associated queue manager is no longer running.
Severity: 0 : Information
Explanation: The command is monitoring for a reply message from the agent on its queue manager. This queue manager has been stopped and monitoring can no longer continue. The original file transfer request might still be continuing if its queue manager is still operational. Otherwise the request will have been suspended awaiting restart of the queue manager. In either case, monitoring for completion can no longer be preformed.
Response: Investigate why queue manager has been stopped.

BFGCL0158I: The file transfer request has failed because the trigger was not successful.
Severity: 0 : Information
Explanation: The command has failed and none of the requested files have been transferred to the destination because the trigger conditions have not been successfully matched.
Response: No action is required.

BFGCL0159E: Either the transfer definition property ''<insert_0>'' or one of the destination file specification properties:(''<insert_1>'') must be specified.
Severity: 20 : Error
Explanation: The command has been issued without any one of the specified properties present. The command requires that exactly one of these properties is specified.
Response: Refer to the command line help or to the product documentation to determine which property to specify. Reissue the command supplying exactly one of the properties.

BFGCL0160E: Additional properties were supplied but were not expected: ''<insert_0>''.
Severity: 20 : Error
Explanation: The command does not require additional properties.
Response: Refer to the command line help or to the product documentation to determine which property to specify. Reissue the command omitting the additional properties.

BFGCL0161E: The parameter ''<insert_0>'' cannot be used if the transfer definition file parameter (''<insert_1>'') is specified.
Severity: 20 : Error
Explanation: When a transfer definition file is specified on the command line, some parameters must not be used because they are specified in the transfer definition file contents.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command omitting the additional parameter.

BFGCL0162E: The transfer definition file specified by the path ''<insert_0>'' does not exist.
Severity: 20 : Error
Explanation: The supplied file path does not correspond with a valid file. The directory or file name might not be correct.
Response: Reissue the command providing a path to a file that exists.

BFGCL0163E: The transfer definition file path ''<insert_0>'' is not a file.
Severity: 20 : Error
Explanation: The supplied file path does not correspond with a valid file. The path might be referring to a directory. A path including the file name is expected.
Response: Reissue the command providing a path to a file.

BFGCL0164E: The transfer definition file ''<insert_0>'' cannot be read.
Severity: 20 : Error
Explanation: The transfer definition file does not have read permission granted.
Response: Set the permission on the transfer definition file to allow read operations. Reissue the command.

BFGCL0165E: The command is unable to complete because of an SSL issue. <insert_0>.
Severity: 20 : Error
Explanation: The command could not be processed due to an SSL configuration issue. This problem prevented the command from being run.
Response: Resolve the problem and rerun the command. Otherwise contact the IBM support center if you need further assistance.

BFGCL0166E: The command is unable to complete because of an SSL issue. <insert_0>.
Severity: 20 : Error
Explanation: The command could not be processed because of an SSL configuration issue. This problem prevented the command from being run.
Response: Resolve the problem and rerun the command. Otherwise contact the IBM support center if you need further assistance.

BFGCL0167E: The agent <insert_0> is not valid because the agent does not have a defined set of properties.
Severity: 20 : Error
Explanation: The command could not clean the agent because the agent name supplied does not have a defined agent.properties file.
Response: Review the agent name given and rerun the command. Otherwise contact the IBM support center if you need further assistance.

BFGCL0168E: The ''<insert_0>'' command line parameter cannot be specified at the same time as the ''<insert_1>'' command line property.
Severity: 20 : Error
Explanation: The two specified parameters cannot be specified together. A maximum of one of the specified parameters can be present for a single invocation of the command.
Response: Refer to the command line help or to the product documentation to determine the correct set of command line parameters required. Reissue the command using a corrected set of command line parameters.

BFGCL0169E: An internal error has occurred while attempting to configure the XML parser. The exception message was: ''<insert_0>''
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: This exception is unexpected. The cause is not immediately known.

BFGCL0170E: An internal error has occurred. The transfer definition document content does not comply with its XML schema.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: This exception is unexpected. The cause is not immediately known.

BFGCL0171E: The XML schema validator for transfer definition documents reports the following problem ''<insert_0>''
Severity: 20 : Error
Explanation: The transfer definition document specified by a create transfer request has failed its XML schema validation.
Response: Validate the content of the transfer definition document against its XML schema.

BFGCL0172E: An internal error has occurred relating to the decoding of an XML message. 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.

BFGCL0173E: The XML parser has detected the following error in an XML message ''<insert_0>''.
Severity: 20 : Error
Explanation: A received XML message has failed to match the defined schema.
Response: Review the XML message and correct the message as necessary to match the schema.

BFGCL0174E: The XML parser has detected the following error in an XML message ''<insert_0>''.
Severity: 20 : Error
Explanation: A received XML message has failed to match the defined schema with an unrecoverable error.
Response: Review the XML message and correct the message as necessary to match the schema.

BFGCL0175E: The XML parser has detected the following error in an XML message ''<insert_0>''.
Severity: 20 : Error
Explanation: A received XML message has failed to match the defined schema and reported a warning.
Response: Review the XML message and correct the message as necessary to match the schema.

BFGCL0176E: While cleaning the queues for agent ''<insert_0>'' an MQRC of ''<insert_1>'' was received. Check that your agent is not running. If your agent is running, issue the fteStopAgent command.
Severity: 20 : Error
Explanation: While cleaning the agent queues, the specified MQRC was received. Check that your agent is not running. If your agent is running, issue the fteStopAgent command.
Response: Ensure that the agent you want to clean is not running. Reissue the fteCleanAgent command.

BFGCL0177E: One or more unexpected parameters were supplied before a transfer definition parameter ''<insert_0>'' or one of the destination file specification parameters (''<insert_1>''). The unexpected parameters were: ''<insert_2>''. Another cause of this error is that neither the ''<insert_0>'' parameter nor one of the ''<insert_1>'' parameters was specified.
Severity: 20 : Error
Explanation: The command cannot process the additional parameters and so cannot complete successfully.
Response: Refer to the command-line help or to the product documentation to determine the correct syntax for the command. Reissue the command omitting the additional parameter.

BFGCL0178E: The agent name ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: You have specified an agent name that is longer than 28 characters or that contains characters other than 'A-Z', 'a-z', '0-9', '.' or '_'.
Response: Reissue the command with a valid agent name.

BFGCL0179E: The end schedule date occurs before the start schedule date. No transfer will be submitted.
Severity: 20 : Error
Explanation: The given end date for the schedule will occur before the given start date of the schedule. This would result in no transfers being generated.
Response: Review the start and end date of the schedule, then reissuethe command again.

BFGCL0180E: An internal error has occurred relating to parsing the schedule parameters. 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.

BFGCL0181E: The file transfer request has failed because an error occurred while sending a message to the destination agent's command queue.
Severity: 20 : Error
Explanation: The command has failed and none of the requested files have been transferred to the destination as it could not be reached.
Response: Check the configuration for the destination agent and queue manager and reissue the command.

BFGCL0182I: The request is now waiting to be processed by the agent.
Severity: 0 : Information
Explanation: The command has successfully been submitted and is waiting for the agent to process it.
Response: If progress monitoring is required, the transfer should be watched via the coordination publications.

BFGCL0183E: The mandatory parameters <insert_0> are missing.
Severity: 20 : Error
Explanation: The parameters -mn monitorname, -ma agent name, -md monitor directory, -mt XML task are mandatory parameters and are required for the command.
Response: Identify the required parameter and reissue the command with these additional parameter.

BFGCL0184E: The -mq queue manager name parameter is required.
Severity: 20 : Error
Explanation: The agent queue manager is required when to enable this command to communciate the request to the agent.
Response: Reissue the command again supplying the -mq parameter.

BFGCL0185E: The file specifying the task XML can not be accessed. The error reported was <insert_0>.
Severity: 20 : Error
Explanation: The file containing the XML task information could not be accessed. This could either be it was not present or that this command did not have permission to access it.
Response: Review the error report and ensure that the file is present and this command has permission to access it.

BFGCL0186E: The parent directory <insert_0> for the given output file can not be accessed.
Severity: 20 : Error
Explanation: The output file specified to received the generate XML Monitor request could not be generated as the parent directory does not exist or this command did not have permission to access it.
Response: Review the output file name and ensure that its parent directory exists and this command has write permission to create the output file.

BFGCL0187I: The XML monitor definition has been generated and written to <insert_0>.
Severity: 0 : Information
Explanation: The XML monitor request has been successfully been generated.
Response: No action required.

BFGCL0188I: The request to create a monitor has been submitted with a request id of <insert_0>.
Severity: 0 : Information
Explanation: The command has successfully generated and submitted the create monitor request.
Response: No action is required.

BFGCL0189E: The mandatory parameters <insert_0> are missing.
Severity: 20 : Error
Explanation: The parameters -ma agent name and -mm queue manager are mandatory parameters and are required for the command.
Response: Identify the required missing parameter and reissue the command with these additional parameter

BFGCL0190E: Could not find file ''<insert_0>''.
Severity: 20 : Error
Explanation: The command could not find the specified file. The command to start the agent requires that the command is able to open this file. The agent has not been started.
Response: Determine why the file is not present in the expected location. If possible, restore the file from a backup or re-create the agent configuration using the supplied tools.

BFGCL0191E: A following file system exception has occurred. Exception: <insert_0>
Severity: 20 : Error
Explanation: A problem occurred trying to access the named file in the exception. The file may not exist, its parent directory does not exist or this command does not have permission to access it.
Response: Examine the name and permissions of the named file and ensure it has the correct values.

BFGCL0192I: A request to delete monitor <insert_0> has been issued.
Severity: 0 : Information
Explanation: The command has successfully completed generating the monitor deletion request and transferred to the agent.
Response: No action is required.

BFGCL0193I: The request has been received by the agent.
Severity: 0 : Information
Explanation: The command has successfully been received and is waiting for the agent to process it.
Response: No action is required.

BFGCL0194I: The scheduled transfer was successfully deleted.
Severity: 0 : Information
Explanation: The agent delete the scheduled transfer.
Response: None.

BFGCL0195E: The requested schedule id could not be deleted as it was not possible to locate it.
Severity: 20 : Error
Explanation: An attempt to delete a schedule from the schedule queue failed because the schedule could not be located.
Response: Use the fteListScheduledTransfers command to review the current schedule queue and reissue the fteDeleteScheduledTransfer command if needed.

BFGCL0196I: The transfer was successfully cancelled.
Severity: 0 : Information
Explanation: The agent processed the cancellation request successfully.
Response: n/a

BFGCL0197E: The request to cancel the transfer failed as the given transfer id could not be found.
Severity: 20 : Error
Explanation: The agent could not find the transfer. 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. In any case, the cancel request has been ignored.
Response: If the transfer has already completed no action is required. If an incorrect ID was given to the fteCancelTransfer command, reissue the command with the correct transfer ID.

BFGCL0198I: The agent has processed the stop request and will end when all current transfers have completed.
Severity: 0 : Information
Explanation: The agent has received the stop request and will shutdown when all current transfers have completed.
Response: n/a

BFGCL0199I: The agent has processed the stop request and will end immediately.
Severity: 0 : Information
Explanation: The agent has received the stop request and is starting to shutdown.
Response: n/a

BFGCL0200E: The agent has failed to process the stop request successfully.
Severity: 20 : Error
Explanation: The agent received the stop request but failed to act on it accordingly.
Response: Review the agent logs and check for FFDCs or other problems. If necessary, manually kill the agent process.

BFGCL0201E: The request has failed because this command is not able to write the generated template to the file: <insert_0>.
Severity: 20 : Error
Explanation: The request to generate the output template file has failed as the command does not have write permission to change or create the named output file.
Response: Review the file and parent directory permissions and issue the command again.

BFGCL0202E: The request has failed as this command received the following exception <insert_0>.
Severity: 20 : Error
Explanation: The request to generate the output template file has failed as the parent directory could not be located.
Response: Review the reported exception and check that the directory for the output file is present and this command has write permission.

BFGCL0203E: The request has failed as this command received the following exception <insert_0>.
Severity: 20 : Error
Explanation: The request to generate the output template file has failed with an input/output error. This could due to no space being available on the storage device or another program is accessing the output file.
Response: Review the reported exception and check that there is sufficient space on the storage device and that no other program is accessing the output file.

BFGCL0204I: Transfer request has been output to <insert_0>
Severity: 0 : Information
Explanation: The command has successfully generated the transfer request to the named file.
Response: No action is required.

BFGCL0205E: No build file specified.
Severity: 20 : Error
Explanation: The -f, -file, or -buildfile option is required to specify the build file. fteAnt does not support a default build.xml.
Response: Specify the required build file option.

BFGCL0206I: <insert_0>
Severity: 0 : Information
Explanation: Debug message output from Apache Ant.
Response: Refer to the Apache Ant documentation for an explanation of the message.

BFGCL0207E: <insert_0>
Severity: 20 : Error
Explanation: Error message output from Apache Ant.
Response: Refer to the Apache Ant documentation for an explanation of the message.

BFGCL0208I: <insert_0>
Severity: 0 : Information
Explanation: Info message output from Apache Ant.
Response: Refer to the Apache Ant documentation for an explanation of the message.

BFGCL0209I: <insert_0>
Severity: 0 : Information
Explanation: Verbose message output from Apache Ant.
Response: Refer to the Apache Ant documentation for an explanation of the message.

BFGCL0210W: <insert_0>
Severity: 10 : Warning
Explanation: Warning message output from Apache Ant.
Response: Refer to the Apache Ant documentation for an explanation of the message.

BFGCL0211I: <insert_0>
Severity: 0 : Information
Explanation: Message output from Apache Ant.
Response: Refer to the Apache Ant documentation for an explanation of the message.

BFGCL0212I: Issuing ping request to agent <insert_0>
Severity: 0 : Information
Explanation: The ping request is about to be issued to the agent.
Response: No action is required.

BFGCL0213I: agent <insert_0> responded to ping in <insert_1> seconds.
Severity: 0 : Information
Explanation: A ping request has successfully responded to by the agent.
Response: No action is required.

BFGCL0214I: agent <insert_0> didn''t respond to ping after <insert_1> seconds.
Severity: 0 : Information
Explanation: A ping request did not get a response from the agent within the specified timeout.
Response: No action is required.

BFGCL0215I: call of command id <insert_0> from agent <insert_1> was successful.
Severity: 0 : Information
Explanation: A ping request has successfully responded to by the agent.
Response: No action is required.

BFGCL0216I: call of command id <insert_0> from agent <insert_1> failed with reason: <insert_2>.
Severity: 0 : Information
Explanation: The command failed. See the event log for details of the failure.
Response: Correct the problem as identified by the error message, and retry if required.

BFGCL0217I: Issuing call request to agent <insert_0>
Severity: 0 : Information
Explanation: The call request is about to be issued to the agent.
Response: No action is required.

BFGCL0218I: Call request issued. The request ID is: <insert_0>
Severity: 0 : Information
Explanation: The call request was successfully issued to the agent.
Response: No action is required.

BFGCL0219E: Call request was not acknowledged by the agent
Severity: 20 : Error
Explanation: The call request was successfully issued to the agent but the agent did not respond
Response: Check that the agent is running and accepting messages.

BFGCL0220E: The parameter <insert_0> is not a valid argument for this command.
Severity: 20 : Error
Explanation: A parameter supplied to the create monitor request command has been rejected as it was not recognized.
Response: Run the command again with the -h help option and review the parameters supported.

BFGCL0221I: The request to cancel call ''<insert_0>'' issued to agent ''<insert_1>''.
Severity: 0 : Information
Explanation: The command has successfully issued a cancel call request to the specified agent. When the agent receives this request, the agent will cancel the call.
Response: No action is required.

BFGCL0222I: The call was successfully cancelled.
Severity: 0 : Information
Explanation: The agent processed the cancellation request successfully.
Response: No action is required.

BFGCL0223E: The request to cancel the call failed as the given call id could not be found.
Severity: 20 : Error
Explanation: The agent could not find the call. This might be because the call completed before the cancel request was processed by the agent. It might also be caused because you supplied an incorrect call ID to the fteCancelCall command. In any case, the cancel request has been ignored.
Response: If the transfer has already completed no action is required. If an incorrect ID was given to the fteCancelCall command, reissue the command with the correct transfer ID.

BFGCL0224E: The call identifier ''<insert_0>'' is not valid
Severity: 20 : Error
Explanation: The command has been issued with a call identifier parameter that is not a 48-character hexadecimal string. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the call identifier as a 48-character hexadecimal string.

BFGCL0225E: A maximum of one call identifier can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as a call identifier. The command requires that exactly one call identifier parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one call identifier parameter.

BFGCL0226E: A call identifier parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no call identifier parameter. The command requires that exactly one call identifer parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one call identifier parameter.

BFGCL0227E: The parameter <insert_0> is not a valid argument for this command.
Severity: 20 : Error
Explanation: A parameter supplied to the create monitor request command has been rejected as not be recognised.
Response: Run the command again with the -h help option and review the parameter required.

BFGCL0228E: An internal error has occurred. The XML schema checker reports the following problem "<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.

BFGCL0229E: An internal error has occurred. The XML schema checker reports the following IO problem "<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.

BFGCL0230E: An internal error has occurred. The XML schema checker reports the following parser problem "<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.

BFGCL0231E: An internal error has occurred. The XML schema checker reports the following xpath problem "<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.

BFGCL0232E: A command parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The call command has been issued with no command parameter.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying a command parameter.

BFGCL0233E: The value <insert_0> is invalid for parameter <insert_1>
Severity: 20 : Error
Explanation: The given value has invalid characters for use with the parameter. Only character 0 through 9,A through Z and '.','_' and '%' can be used for defining a name.
Response: Review the given name and change it to match the valid characters that can be used.

BFGCL0234E: The root element <insert_0> was unexpected for the supplied transfer XML document.
Severity: 20 : Error
Explanation: A transfer definition document must conform with the FileTransfer schema, and contain a root element of 'request' or 'transferSpecifications'.
Response: Review the content of the transfer definition XML document according to its schema.

BFGCL0235E: The content of the supplied task definition is not valid.
Severity: 20 : Error
Explanation: A task definition document must conform with the FileTransfer schema, and contain a root element of 'request'.
Response: Review the content of the task definition XML document according to its schema.

BFGCL0236E: A transfer definition with root element <insert_0> was supplied but a task definition was expected.
Severity: 20 : Error
Explanation: A monitor definition takes a task definition XML document which must conform with the FileTransfer schema, and contain a root element of 'request'. Providing a transfer definition XML document with a root of 'transferSpecifications' will not work.
Response: Review the content of the task definition XML document according to its schema.

BFGCL0237I: Stop request issued to logger command queue <insert_0> on <insert_1>.
Severity: 0 : Information
Explanation: The command has successfully issued a stop request to the logger. When the logger receives this request, the logger will stop.
Response: No action is required.

BFGCL0238I: The request has been received by the logger.
Severity: 0 : Information
Explanation: The command has successfully been received and is waiting for the logger to process it.
Response: No action is required.

BFGCL0239I: The request is now waiting to be processed by the logger.
Severity: 0 : Information
Explanation: The command has successfully been submitted and is waiting for the logger to process it.
Response: No action is required.

BFGCL0240I: The logger has processed the stop request and will end immediately.
Severity: 0 : Information
Explanation: The logger has received the stop request and is starting to shutdown.
Response: No action is required.

BFGCL0241E: The logger has failed to process the stop request successfully.
Severity: 20 : Error
Explanation: The logger received the stop request but failed to act on it.
Response: Review the logger log file and check for FFDCs or other problems. If necessary, manually kill the logger process.

BFGCL0242W: No monitors exist that match the current selection criteria.
Severity: 10 : Warning
Explanation: The command has completed successfully but no monitor information can be listed. This is either because no monitors are registered with the coordination queue manager or because the pattern specified as part of the command did not match any monitors that are registered with the coordination queue manager.
Response: If a pattern was specified, consider reissuing the command with a more inclusive pattern.

BFGCL0243E: An internal error has occurred. 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.

BFGCL0244E: The dataDirectory property of ''<insert_0>'', specified in the install.properties, is not a valid absolute path.
Severity: 20 : Error
Explanation: The dataDirectory given in the install.properties must specify a valid absolute path.
Response: Update the install.properties file, in the MQMFT installation root directory, to specify a valid absolute path for the dataDirectory property.

BFGCL0245I: The file ''<insert_0>'' has been created successfully.
Severity: 0 : Information
Explanation: fteSetupCommands completed successfully, creating the required command.properties file.
Response: No action required.

BFGCL0246E: The command has failed to start logger due to: <insert_0>
Severity: 20 : Error
Explanation: The command has failed to start the specified logger process due to the specified problem.
Response: Use the information in the message to investigate the problem. Resolve the problem, if possible, and reissue the start agent command. If this does not resolve the problem, contact the IBM support center for assistance.

BFGCL0247E: Could not find file ''<insert_0>''.
Severity: 20 : Error
Explanation: The command could not find the specified file. The command to start the logger requires that the command is able to open this file. The logger has not been started.
Response: Determine why the file is not present in the expected location. If possible, restore the file from a backup or re-create the agent configuration using the supplied tools.

BFGCL0248W: No command response from agent within timeout.
Severity: 10 : Warning
Explanation: The agent has successfully acknowledged receipt of the command but did not indicate completion within the timeout period. It could be the case that the command did actually complete but either the agent took longer than the timeout to reply or was unable to reply.
Response: Check the agent event log to see if there are any errors. Check the transfer log to see if the command did actually complete.

BFGCL0249E: The monitor could not be created as one already exists with the given name on that agent.
Severity: 20 : Error
Explanation: The requested monitor could not be created as one already exists within the agent. Therefore the monitor was not created.
Response: Run the fteListMonitors command to validate the monitor name given.

BFGCL0250E: The monitor could not be found on the given agent.
Severity: 20 : Error
Explanation: The requested monitor could not be located within the agent. Therefore the monitor was not deleted.
Response: Run the fteListMonitors command to validate the monitor name given.

BFGCL0251I: The request has successfully completed.
Severity: 0 : Information
Explanation: The command has successfully completed.
Response: No action is required.

BFGCL0252E: The request has failed to complete successfully.
Severity: 20 : Error
Explanation: The command has failed to complete successfully.
Response: No action is required.

BFGCL0253W: No acknowledgement to command from agent within timeout.
Severity: 10 : Warning
Explanation: The command was successfully placed on the agent's command queue, but the agent did not acknowledge receipt within the timeout period. The agent may not be running or responding to commands.
Response: Check that the agent is running and accepting commands. If the agent is running then check the agent event log to see if there are any errors. Check the transfer log to see if the command did actually complete.

BFGCL0254I: Agent configured successfully. The agent has not been registered with the coordination queue manager.
Severity: 0 : Information
Explanation: Agent configured successfully. The agent has not been registered with the coordination queue manager. This may be due to the coordination queue manager being inaccessible.
Response: Check that the coordination queue manager is running and that the coordination queue manager properties have been configured correctly in the coordination.properties file. The agent will be registered with the coordination queue manager when the agent is started.

BFGCL0255E: An internal error has occurred. The exception was: ''<insert_0>''. Caused by: ''<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.

BFGCL0256E: The agent <insert_0> was specified in the template, but its associated queue manager cannot be determined. Use the -sm or -dm option to specify the queue manager for this agent.
Severity: 20 : Error
Explanation: Templates can be created with or without specifying agents. However, if a source or destination agent is specified, the agent queue manager for that agent must be resolved at the time that the template is created. If the queue manager is not specified the fteCreateTemplate command will attempt to resolve it from the local properties files, but if it cannot be resolved in this way then the information must be explicitly provided on the command line.
Response: If the agent mentioned in the message is the source agent, use the -sm option to provide the name of its queue manager. If the agent is the destination agent, use the -dm option.

BFGCL0257E: An internal error has occurred. 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.

BFGCL0258E: No name was provided for the template.
Severity: 20 : Error
Explanation: Each template must have a name, by which it can be recalled for use as a transfer. No name was provided to the command.
Response: Use the -tn option to provide a templatename.

BFGCL0259E: The -tn option is not valid for this command.
Severity: 20 : Error
Explanation: The -tn option is used to provide a name for a transfer template. The current command does not create a transfer template and so the option is superfluous.
Response: Remove the -tn option and reissue the command.

BFGCL0260E: The -tl option is not valid for this command.
Severity: 20 : Error
Explanation: The -tl option is not supported for templates. If you are combining triggers with schedules in order to initiate a transfer when a condition is met, consider using monitors instead.
Response: Remove the -tl option and reissue the command.

BFGCL0261E: A messaging problem prevented the command from completing successfully. The command attempted to publish a message to the coordination queue manager <insert_0>, via a direct connection to the command queue manager <insert_1>. The reported error was <insert_2> (MQ reason code <insert_3>).
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The reason code specified in the message corresponds to the type of problem encountered. The problem occurred while trying to establish a bindings transport mode connection to the specified queue manager.
Response: Consult the IBM MQ product documentation to understand the MQ reason code. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0262E: A messaging problem prevented the command from completing successfully. The command attempted to publish a message to the coordination queue manager <insert_0>, via a client connection to the command queue manager <insert_1> on host <insert_2>, port <insert_3> and using MQ channel <insert_4>. The reported error was <insert_5> (MQ reason code <insert_6>).
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The reason code specified in the message corresponds to the type of problem encountered. The problem occurred while trying to establish a client transport mode connection to the specified queue manager.
Response: Consult the IBM MQ product documentation to understand the MQ reason code. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0263I: A template has been created and sent to the coordination queue manager for publication.
Severity: 0 : Information
Explanation: Transfer templates are stored as retained publications on the coordination queue manager. fteCreateTemplate has generated an appropriate message describing your template, and sent it to the coordination queue manager to be published. All connected GUIs will then be able to obtain a copy of this template and use it to create transfers.
Response: No action is required.

BFGCL0264E: Missing mandatory parameter <insert_0>
Severity: 20 : Error
Explanation: A mandatory parameter is missing from the entered command and the request can not be performed.
Response: Review the parameter and either correct and add the missing parameter.

BFGCL0265E: Missing mandatory parameter <insert_0>
Severity: 20 : Error
Explanation: A mandatory parameter is missing from the entered command and the request can not be performed.
Response: Review the parameter and either correct and add the missing parameter.

BFGCL0266E: The value <insert_0> is invalid for parameter <insert_1>. The last invalid character is: ''<insert_2>''.
Severity: 20 : Error
Explanation: The given value has invalid characters for use with the parameter. Cannot contain '*' , '%', '"' or '?' characters in the name.
Response: Review the given name and change it to match the valid characters that can be used.

BFGCL0267E: This user is not authorized to perform the operation.
Severity: 20 : Error
Explanation: The user that submitted the command is not authorized to perform the operation. The operation has not been carried out.
Response: Confirm that the command was submitted in the context of the correct user and switch user if necessary. Alternatively, contact your systems administrator and ask for the user that submitted to command to be authorized for the operation being carried out.

BFGCL0268E: The agent is already acting as the source agent for the maximum number of file transfer operations.
Severity: 20 : Error
Explanation: 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 its queued transfer limit being reached. 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.

BFGCL0269E: A protocol file server type (-bt) must be specified when creating an agent.
Severity: 20 : Error
Explanation: We cannot create a bridge agent without specifying the protocol type.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0270E: A server host must be specified when creating a bridge agent.
Severity: 20 : Error
Explanation: We cannot create a bridge agent without specifying the protocol file server host.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0271E: A server platform type must be specified when creating a bridge agent.
Severity: 20 : Error
Explanation: We cannot create a bridge agent without specifying the server platform type.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0272E: A server time zone must be specified when creating an bridge agent.
Severity: 20 : Error
Explanation: We cannot create a bridge agent without specifying the server time zone.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0273E: A server locale must be specified when creating a bridge agent.
Severity: 20 : Error
Explanation: We cannot create a bridge agent without specifying the server locale.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0274E: A server file encoding must be specified when creating a bridge agent.
Severity: 20 : Error
Explanation: We cannot create a bridge agent without specifying the server file encoding.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0275E: The default credential exit class has been select however no credential configuration has been specified.
Severity: 20 : Error
Explanation: The credential exit class parameter has not been specified therefore the default credntial exit class will be used. This default requires the credential configuration to be present and specify the file path to the credential configuration file.
Response: Review the MQMFT info center for information regarding configurating the default credential exit class for bridge agent.

BFGCL0276I: An existing credential XML file for agent ''<insert_0>'' has been detected and has not been updated.
Severity: 0 : Information
Explanation: The credentialXML file is already present for the agent and has not been changed.
Response: No action required.

BFGCL0277I: A credential XML file has been created. This file must be completed with credential details for accessing the protocol file server before the bridge agent can be brought into service. The file can be found here: ''<insert_0>''.
Severity: 0 : Information
Explanation: A credential XML file has been generated at the locationgiven. This XML file defines credential information for accessing the protocol file server.
Response: Update this file to include the necessary credential information so that the bridge agent can login to the protocol file server.

BFGCL0278W: The standby connection value ''<insert_0>'' given for property ''<insert_1>'' is not valid and has been ignored.
Severity: 10 : Warning
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 value will be ignored if the standby connection name is incorrectly specified.
Response: Modify the appropriate properties file so that the value assigned to the given property is a valid standby connection name before retrying the command.

BFGCL0279W: The standby connection value ''<insert_0>'' given for property ''<insert_1>'' specifies a port number which is not valid and has been ignored.
Severity: 10 : Warning
Explanation: The specified standby connection name specifies a port number which is not valid. Port numbers must be a non-negative numeric valid. If the connection name specifies a port number which is not valid, then it will be ignored.
Response: Modify the appropriate properties file so that the value assigned to the given property is a valid standby connection name before retrying the command.

BFGCL0280W: The standby connection value ''<insert_0>'' given for property ''<insert_1>'' duplicates the primary connection details and has been ignored.
Severity: 10 : Warning
Explanation: The specified standby connection name specifies the same host and port as the primary connection details and so it has been ignored.
Response: Modify the appropriate properties file so that the value assigned to the given property does not duplicate the primary connection details before retrying the command.

BFGCL0281E: Command was sent to the wrong MQMFT agent.
Severity: 20 : Error
Explanation: The command was successfully placed on an MQMFT agent's command queue but the agent specified as the source, for the command, did not match the agent that was actually processing the command queue.
Response: Either resend the message to the correct agent command queue or update the message to specify the correct agent and resend the command.

BFGCL0282I: A request to deregister the agent was sent to the coordination queue manager. We can also delete the agent's queues.
Severity: 0 : Information
Explanation: A message has been sent to the coordination queue manager which will remove the retained publication representing the agent. Nothing has been done to remove the agent's queues on its agent queue manager. If required, we can remove these queues manually. See the product documentation for a list of queues used by each agent.
Response: No action is required. We can optionally delete the agent's queues.

BFGCL0283E: Failed to create the ProtocolBridgeCredentials.xml with exception <insert_0>
Severity: 20 : Error
Explanation: Attempted to create the sample credential file ProtocolBridgeCredentials.xml, but failed to generate the relevant file. Without this file created and configured the bridge agent cannot perform any transfers.
Response: Check that we have permission to write the sample file into the agents directory.

BFGCL0284E: Triggers are not supported on a protocol bridge agent.
Severity: 20 : Error
Explanation: It is not supported to create a transfer request with a trigger specified on a protocol bridge agent.
Response: No user action is required.

BFGCL0285E: Resource monitors are not supported by the agent.
Severity: 20 : Error
Explanation: It is not supported to create or delete a resource monitor on a protocol bridge or Web Gateway MQMFT agent.
Response: Resubmit the request to an agent that supports resource monitors, such as a standard MQMFT agent.

BFGCL0287I: The request to start the logger on this machine has been submitted.
Severity: 0 : Information
Explanation: The request to start the logger has been successfully submitted.
Response: No action is required.

BFGCL0288E: An internal error has occurred during parsing the monitor task XML file. 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.

BFGCL0289I: A user sandbox XML file for agent ''<insert_0>'' is already present and will not be overwritten.
Severity: 0 : Information
Explanation: The user sandbox XML file is already present for the agent and has not been overwritten or changed.
Response: No action required.

BFGCL0290E: Failed to create the user sandbox XML file with exception: <insert_0>
Severity: 20 : Error
Explanation: An attempt was made to create the sample user sandbox file UserSandboxes.xml, but failed to generate the relevant file. Without this file created and configured the agent cannot be configured with per-user sandboxes.
Response: Check that we have permission to write the sample file into the agents directory.

BFGCL0292E: An internal error has occurred. Command fteShowDetailAgent has found an agent status message which has an incorrect format.
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.

BFGCL0293E: The agent name of ''<insert_0>'' specified in the ''<insert_1>'' properties file must be given in the uppercase form in the agent properties file.
Severity: 20 : Error
Explanation: The specified agent name in the properties file has lowercase characters. The agent name must be in uppercase. The agent has not been started.
Response: Modify the agent name in the specified properties file so that no lower case characters are used.

BFGCL0294E: No template names have been given in the command arguments.
Severity: 20 : Error
Explanation: The command requires one or more template names to be specified as command arguments for them to be deleted.
Response: Review the usage information for this command. Execute the command again with the template names to delete.

BFGCL0295W: There are no templates present on the given coordination queue manager.
Severity: 10 : Warning
Explanation: The specified coordination queue manager does not have any templates currently registered. Therefore this command cannot delete the requested templates.
Response: Review the usage information for this command and verify the correct coordination queue manager has been specified.

BFGCL0296W: There are no templates present on the given coordination queue manager that match those specified in the arguments.
Severity: 10 : Warning
Explanation: The coordination queue manager does have templates registered but none of them match the specified names given in the command arguments.
Response: Review the given templates name in the previous. Correct as necessary and repeat command.

BFGCL0297E: Could not find coordination queue manager details for ''<insert_0>''. Properties file ''<insert_1>'' is not present.
Severity: 20 : Error
Explanation: The configuration details for the requested coordination queue manager could not be located.
Response: Check the named coordination queue manager is correct and that its configuration is present in the MQMFT data directory. When corrected retry the command again.

BFGCL0298I: Command has completed and deleted <insert_0> templates from coordination queue manager <insert_1>.
Severity: 0 : Information
Explanation: The delete template command completed successful and one or more templates have been deleted.
Response: No action is required.

BFGCL0299I: Command has completed but failed to delete any templates.
Severity: 0 : Information
Explanation: The delete template command has completed but due to error conditions it failed to perform the delete template action requested.
Response: Review associated error message and follow guidance.

BFGCL0300E: The command was run without a traceAgent parameter. Run the command with the -h parameter to see usage information.
Severity: 20 : Error
Explanation: The trace request was not processed because the command was run without a traceAgent parameter. Run the command with the -h parameter to see usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0301E: The trace specification ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The value passed to the command is not supported.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying a valid trace specification.

BFGCL0302E: Output file <insert_0> cannot be generated as it is already present and forced overwrite has not been selected.
Severity: 20 : Error
Explanation: The specified output file is already present and cannot be replaced as the forced overwrite has not been specified. This template cannot be listed.
Response: Correct the current files present in the specified output directory. Remove existing file or specified the force overwrite option in command line before re-issuing the command.

BFGCL0303E: Internal error has occurred. Not able to create output file <insert_0> due to exception <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.

BFGCL0304E: Internal error has occurred. Not able to use file encoding <insert_0> due to reported exception <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.

BFGCL0305E: One or more templates have failed to be listed.
Severity: 20 : Error
Explanation: One or more templates requested to be listed in the command have failed to be listed due to previously given errors.
Response: Review previously given error messages.

BFGCL0306E: Internal error has occurred. Xpath could not process <insert_0> due to reported exception <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.

BFGCL0307I: No templates have been matched.
Severity: 0 : Information
Explanation: The named templates were not present in the coordination queue manager. Therefore no templates have been shown.
Response: No action is required

BFGCL0308E: Command line arguments '-o' and '-O' cannot be used together.
Severity: 20 : Error
Explanation: The arguments '-o' and '-O' each define where output is stored. Only one of these arguments can be specified as only one output location can be defined.
Response: Review where the output from the command should be stored and remove the unnecessary arguments before retrying the command again.

BFGCL0309E: The output directory of <insert_0> is present, but not a directory.
Severity: 20 : Error
Explanation: The list template command cannot complete the request as the specified output directory is present, but not a directory.
Response: Check the specified output directory and ensure the path is correct and is a directory. Reissue the command.

BFGCL0310E: The output directory of <insert_0> is not present.
Severity: 20 : Error
Explanation: The list template can not locate the specified output directory and cannot complete the command.
Response: Check the specified output directory and ensure the path is correct and present. Reissue the command.

BFGCL0311W: Tracing has not been enabled due to previously reported errors.
Severity: 10 : Warning
Explanation: A request to enable tracing for this command line tool could not be processed due to a previously reported error. As a result tracing has not been enabled.
Response: Evaluate and correct the previous error before re-issuing this command again.

BFGCL0312W: Tracing has not been enabled due to previously reported error.
Severity: 10 : Warning
Explanation: A request to enable tracing for this command line tool could not be processed due to a previously reported error. As a result tracing has not been enabled.
Response: Evaluate and correct the previous error before re-issuing this command again.

BFGCL0313E: Error occurred whilst attempting to validate agent startup. reason: <insert_0>
Severity: 20 : Error
Explanation: The agent process was started but an error occurred whilst attempting to determine the status.
Response: Examine the reported error information and take the appropriate action. If the problem can not be resolved, contact the IBM support center.

BFGCL0314W: Agent process is running, but unable to confirm it started successfully.
Severity: 10 : Warning
Explanation: The agent process was started and is running, but there was no confirmation from the agent.
Response: The agent may be running successfully, in which case no action is required. If this is not the case then examine any error information that may have been output and examine the files in the agent log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0315E: Agent startup failed.
Severity: 20 : Error
Explanation: The agent process was started but there was an error that may have caused it to terminate.
Response: Examine any error information that has been output and examine the files in the agent log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0316E: Agent was started successfully but is no longer running.
Severity: 20 : Error
Explanation: The agent process was started successfully but has ended due to an error.
Response: Examine any error information that may have been output and examine the files in the agent log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0317W: arguments: <insert_0> did not match any templates present on the given coordination queue manager.
Severity: 10 : Warning
Explanation: The coordination queue manager does have templates registered but none of them match the specified names given in the command arguments.
Response: Review the given templates name in the previous. Correct as necessary and repeat command.

BFGCL0318E: <insert_0> invalid templates have been detected but not listed.
Severity: 20 : Error
Explanation: The list template command was unable to get information on one or more templates as the information given in those template was either missing or invalid.
Response: Use the fteDeleteTemplate command with option -R to remove the invalid templates.

BFGCL0319I: Specify the '-h' command line parameter to see more usage information.
Severity: 0 : Information
Explanation: Specify the '-h' parameter to display usage information about the command.
Response: No action required.

BFGCL0320E: There were unknown parameter on the command line: ''<insert_0>''
Severity: 20 : Error
Explanation: You are specifying parameters that do not work with this command.
Response: The command displays more usage information if we use the '-h' parameter.

BFGCL0321I: The given ''<insert_0>'' parameter will currently have no effect as the functionality is not yet supported by the agent.
Severity: 0 : Information
Explanation: You are specifying parameters that do not yet work with the agent.
Response: No action required.

BFGCL0322E: The binary delimiter option ''<insert_0>'' is not valid unless the transfer is in binary mode.
Severity: 20 : Error
Explanation: You are specifying a parameter that depends on another being set to a particular value.
Response: Specify the '-h' command line parameter to see more usage information and modify your command to submit a binary transfer.

BFGCL0323E: The text delimiter option ''<insert_0>'' is not valid unless the transfer is in text mode.
Severity: 20 : Error
Explanation: You are specifying a parameter that depends on another being set to a particular value.
Response: Specify the '-h' command line parameter to see more usage information and modify your command to submit a text transfer.

BFGCL0324E: The specified message splitting command line options, <insert_0>, are mutually exclusive and cannot be used together.
Severity: 20 : Error
Explanation: A maximum of one of the specified options can be present for a single invocation of the command.
Response: Reissue the command specifying one or none of the message splitting options.

BFGCL0325E: The specified command line options, <insert_0>, are only supported when transferring to a queue.
Severity: 20 : Error
Explanation: You are specifying command line options that depend on another command line option also being specified.
Response: Either reissue the command with the specified options removed, or with a queue as the destination.

BFGCL0326E: Only a single queue name can be specified as the trailing source arguments when transferring using the ''-<insert_0>'' option.
Severity: 20 : Error
Explanation: When you include the given option in your command line arguments, you must only specify a single queue name as the source specification.
Response: Run the command with the -h parameter to see more usage information and modify your command appropriately.

BFGCL0327E: An input/output error occurred when reading the status information from the agent. The error was: <insert_0>
Severity: 20 : Error
Explanation: Agent information is obtained from a message published by the agent and stored on the coordination queue manager. A Java IO Exception occurred while reading the message.
Response: Retry the command in case the error is a transient one. If this does not resolve the problem, contact the IBM Support Center for assistance.

BFGCL0328E: A messaging problem prevented the command from completing successfully. The MQ code for the problem was <insert_0> (<insert_1>).
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The reason code specified in the message corresponds to the type of problem encountered.
Response: Consult the IBM MQ product documentation to understand the MQ reason code. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0329E: An input/output error occurred when reading the status information from an agent. The error was: <insert_0>
Severity: 20 : Error
Explanation: Agent information is obtained from a message published by the agent and stored on the coordination queue manager. A Java IO Exception occurred while reading the message.
Response: Retry the command in case the error is a transient one. If this does not resolve the problem, contact the IBM Support Center for assistance.

BFGCL0330E: The specified command line options, <insert_0>, are only supported when transferring from a queue.
Severity: 20 : Error
Explanation: You are specifying command line options that depend on another command line option also being specified.
Response: Either reissue the command with the specified options removed, or with a queue as the source.

BFGCL0331E: Text file encoding specifications are not valid on a binary transfer.
Severity: 20 : Error
Explanation: Binary mode was selected for the transfer, either by specifying "-t binary" or by omitting the "-t" parameter. Another parameter was used to specify how the source or destination file is encoded or what kind of line-ending character it uses. These characteristics only apply to text files, not binary files.
Response: If you meant to perform a text transfer with character or line-ending conversion, specify "-t text". If you meant to perform a binary transfer, or to transfer a text file with no conversions, remove the "-dle", "-dce" or "-sce" parameters.

BFGCL0332E: The specified monitor resource command line options, <insert_0>, are mutually exclusive and cannot be used together.
Severity: 20 : Error
Explanation: A maximum of one of the specified options can be present for a single invocation of the command.
Response: Reissue the command specifying exactly one of the monitor resource options.

BFGCL0333E: Missing '-wgn' command line argument.
Severity: 20 : Error
Explanation: The '-wgn' (or '-webGatewayName') command line argument was not specified on the command line of the 'fteCreateWebAgent' command. The command has not created a web agent.
Response: Reissue the command specifying the '-wgn' option.

BFGCL0334E: Exactly one of the command line options that are available for specifying the resource to be monitored, (<insert_0>), must be provided.
Severity: 20 : Error
Explanation: One of the specified options must be provided when issuing the fteCreateMonitor command.
Response: Reissue the command specifying exactly one of the monitor resource options.

BFGCL0335E: The Web Gateway name ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: You have specified a Web Gateway name that is longer than 28 characters or that contains characters other than 'A-Z', 'a-z', '0-9', '.' or '_'.
Response: Reissue the command with a valid Web Gateway name.

BFGCL0336E: The default substitution variable parameter <insert_0> is incorrectly formatted because it is missing an equals sign (=).
Severity: 20 : Error
Explanation: The default substitution variable parameter does not have the correct format and the name and data pairs cannot be identified correctly. The command cannot be completed.
Response: Review this default substitution variable parameter, ensuring that the parameter follows the format of = and that each pair is separated by a comma. Reissue the command.

BFGCL0337E: Default substitution variables are not supported by directory resources.
Severity: 20 : Error
Explanation: Directory monitoring was selected using the "-md" parameter and one or more default substitution variables were specified using the the "-dv" parameter.
Response: If you intended to monitor a directory, remove the "-dv" parameter and then submit the transfer again.If you intended to monitor a queue, remove the "-md" parameter and specify the queue to monitor using the "-mq" parameter. Then submit the transfer again.

BFGCL0338E: The Windows service name ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: You have specified a Windows service name that is longer than 256 characters or that contains characters other than 'A-Z', 'a-z' or '0-9'.
Response: Reissue the command with a valid Windows service name.

BFGCL0339E: Only one of the arguments '-s' and '-n' can be specified.
Severity: 20 : Error
Explanation: Arguments '-s' and '-n' are mutually exclusive, so only one of them can be specified.
Response: Reissue the command with either the '-s' or '-n' argument removed.

BFGCL0340I: Agent modified successfully.
Severity: 0 : Information
Explanation: The modification to the agent has completed successfully.
Response: No action required.

BFGCL0341E: The arguments: (<insert_0>) can only be specified when the ''-s'' (-service) Windows service option is specified.
Severity: 20 : Error
Explanation: Arguments '-su', '-sp', and '-sj' are additional options to be specified when the '-s', Windows service, option is specified. These arguments are not permitted without the '-s' option.
Response: Reissue the command, either specifying the '-s' option or with the invalid arguments removed.

BFGCL0342E: The agent ''<insert_0>'' is still running. Before modifying the agent, you must run fteStopAgent to stop the agent.
Severity: 20 : Error
Explanation: The agent you want to modify is still running. An agent cannot be modified until it has been stopped.
Response: Run the fteStopAgent command for the agent you want to modify. Reissue the fteModifyAgent command when the agent has stopped.

BFGCL0343I: The Windows service ''<insert_0>'' has been stopped for agent ''<insert_1>''.
Severity: 0 : Information
Explanation: The command has successfully stopped the specified agent's Windows service.
Response: No action is required.

BFGCL0344E: The specified message splitting command line option ''<insert_0>'', requesting inclusion of delimiters in the output, cannot be used together with the split-by-size option (<insert_1>).
Severity: 20 : Error
Explanation: The specified options cannot be used together.
Response: Reissue the command without the 'include delimiters' message splitting option.

BFGCL0345E: Both the -disableOnAnyFFDC and -disableOnFFDC parameters have been specified on the command line. Only one of these parameters can be specified.
Severity: 20 : Error
Explanation: The parameters -disableOnAnyFFDC and -disableOnFFDC are mutually exclusive and only one can be specified on the command line.
Response: If you want to stop trace when a particular FFDC event occurs then use the -disableOnFFDC parameter. Otherwise use -disableOnAnyFFDC to stop trace when any FFDC occurs.

BFGCL0346E: The argument supplied with the -disableOnFFDC parameter is invalid.
Severity: 20 : Error
Explanation: The -disableOnFFDC parameter requires an argument that defines which FFDC event generates a stop trace event. The value supplied was invalid and could not be used as a stop trace event.
Response: Use the fteSetAgentTraceLevel -h option to review the command usage. Correct the argument before reissuing the command.

BFGCL0347E: It is not valid to specify both the '-sq' and '-dq' parameters together.
Severity: 20 : Error
Explanation: Either the source or destination of a transfer may be a WebSpehere MQ queue but not both.
Response: Reissue the command with either the source or destination not an IBM MQ queue.

BFGCL0348I: Logger modified successfully.
Severity: 0 : Information
Explanation: The modification to the logger has completed successfully.
Response: No action required.

BFGCL0349E: The logger ''<insert_0>'' is still running. Before modifying the logger, you must run the fteStopLogger command to stop the logger.
Severity: 20 : Error
Explanation: The logger to modify is still running. A logger cannot be modified until it has been stopped.
Response: Run the fteStopLogger command for the logger to modify. Run the fteModifyLogger command again when the logger has stopped.

BFGCL0350I: The Windows service ''<insert_0>'' has been stopped for the logger with properties set ''<insert_1>''
Severity: 0 : Information
Explanation: The command has successfully stopped the specified logger Windows service.
Response: No action is required.

BFGCL0351E: The Windows service name ''<insert_0>'' already exists.
Severity: 20 : Error
Explanation: The specified service name cannot be used because a Windows service with the same name already exists.
Response: Reissue the command with a different Windows service name.

BFGCL0352E: The -su command-line parameter must be specified, with a non-blank user account name, whenever the -s command-line parameter is specified.
Severity: 20 : Error
Explanation: Whenever a Windows service is required, the service user (-su) command-line parameter must be specified. The value for the -su command-line parameter cannot be blank.
Response: Reissue the command, specifying a valid user account name for the -su command-line parameter.

BFGCL0353I: The -sp command-line parameter has not been specified. The password is required to start the service.
Severity: 0 : Information
Explanation: The command has modified or created a Windows service to run under a named user account. A password was not specified on the command line for the user account. Before the service can be started, the password for the user account must be set using available Windows system or other vendor tools. If the password is not set to the correct value the service cannot start.
Response: Either reissue the command specifying a valid password or use an available Windows system or other vendor tool to set the password.

BFGCL0354E: The -dqdp parameter is only applicable if either the -dqdb or -dqdt parameter has been specified.
Severity: 20 : Error
Explanation: The destination delimiter position parameter is only applicable if either a binary or text delimiter parameter has been specified for the destination.
Response: Either remove the -dqdp parameter from the command, or add the -dqdb or -dqdt parameter to the command. Then reissue the command.

BFGCL0355E: The -sqdp parameter is only applicable if either the -sqdb or -sqdt parameter has been specified.
Severity: 20 : Error
Explanation: The source delimiter position parameter is only applicable if either a binary or text delimiter parameter has been specified for the source.
Response: Either remove the -sqdp parameter from the command, or add the -sqdb or -sqdt parameter to the command. Then reissue the command.

BFGCL0358E: The -coordinationQMgr parameter must be specified.
Severity: 20 : Error
Explanation: The -coordinationQMgr parameter is a required parameter for the fteSetupCoordination command.
Response: Reissue the command, ensuring that the -coordinationQMgr parameter is specified.

BFGCL0359E: Monitor of the request has stopped because the associated queue manager returned an empty response message and reconnection was not possible.
Severity: 20 : Error
Explanation: The command was waiting for a reply message from the agent, but it received an empty response. This usually means that the temporary reply queue has been removed from the remote queue manager.
Response: Investigate why the temporary reply queue might have been removed.

BFGCL0363E: Missing '-cdNode' command-line argument.
Severity: 20 : Error
Explanation: The '-cdNode' command-line argument was not specified for the 'fteCreateCDAgent' command. The command has not created a Connect:Direct bridge agent.
Response: Reissue the command, specifying the '-cdNode' option.

BFGCL0364I: The Windows service ''<insert_0>'' is already stopped for agent ''<insert_1>''.
Severity: 0 : Information
Explanation: No action was taken as the agent's Windows service is already stopped.
Response: No action is required.

BFGCL0365I: The Windows service ''<insert_0>'' is already stopped for the logger with properties set ''<insert_1>''
Severity: 0 : Information
Explanation: No action was taken as the loggers Windows service is already stopped.
Response: No action is required.

BFGCL0366E: Failed to create the ConnectDirectCredentials.xml file with exception <insert_0>
Severity: 20 : Error
Explanation: Attempted to create the sample credential file ConnectDirectCredentials.xml, but failed to generate the relevant file. Without this file created and configured the Connect:Direct bridge agent cannot perform any transfers.
Response: Check that we have permission to write the sample file into the agents directory.

BFGCL0367I: A credential XML file has been created. This file must be completed with credential details for accessing the Connect:Direct node before the Connect:Direct bridge agent can be used.The file is located here: ''<insert_0>''.
Severity: 0 : Information
Explanation: A credential XML file has been generated at the locationgiven. This XML file defines credential information for accessing the Connect:Direct node.
Response: Update this file to include the necessary credential information so that the Connect:Direct bridge agent can access the Connect:Direct node.

BFGCL0368I: An existing credential XML file for agent ''<insert_0>'' has been detected and has not been updated.
Severity: 0 : Information
Explanation: The credential XML file is already present for the agent and has not been changed.
Response: No action required.

BFGCL0369W: The agent ''<insert_0>'' has been cleaned. Some files may not have been removed from the Connect:Direct bridge agent temporary directory ''<insert_1>''.
Severity: 10 : Warning
Explanation: The command has successfully cleaned the queues for the specified agent. Some files could not be removed from the Connect:Direct bridge agent temporary directory.
Response: Check the agent temporary directory and remove any files which still exist in the directory.

BFGCL0370E: The -cdu parameter has been specified but the agent being cleaned is not a Connect:Direct bridge agent.
Severity: 20 : Error
Explanation: The -cdu parameter is valid on the fteCleanAgent command only if the agent being cleaned is a Connect:Direct bridge agent.
Response: Run the command again without the -cdu parameter.

BFGCL0371E: The -cdp parameter has been specified without the -cdu parameter.
Severity: 20 : Error
Explanation: The -cdp parameter is valid with the fteCleanAgent command only if the -cdu parameter has been specified.
Response: Run the command again without the -cdp parameter or specifying the -cdu parameter.

BFGCL0372E: You do not have permission to read files that are in, or write files to, the Connect:Direct bridge agent temporary directory ''<insert_0>''.
Severity: 20 : Error
Explanation: The user who runs the fteCleanAgent command must have read and write permission for the Connect:Direct bridge agent temporary directory to delete temporary files from the directory.
Response: Ensure that the user ID you are using to run the fteCleanAgent command has read and write permission for the Connect:Direct bridge temporary directory.

BFGCL0373E: Failed to authenticate with the Connect:Direct bridge agent node.
Severity: 20 : Error
Explanation: The clean agent command failed to authenticate with the Connect:Direct bridge agent node using the specified user name and password.
Response: Check the user name and password are correct and run the command again.

BFGCL0374E: Failed to create file <insert_0> due to error: <insert_1>
Severity: 20 : Error
Explanation: An attempt was made to create the sample configuration file, but failed to generate the relevant file. Without this file created the agent will not start.
Response: Check that we have permission to write the sample file into the agent's directory.

BFGCL0375I: A Connect:Direct process definitions XML file for agent ''<insert_0>'' is already present and will not be overwritten.
Severity: 0 : Information
Explanation: The Connect:Direct process definitions XML file is already present for the agent and has not been overwritten or changed.
Response: No action required.

BFGCL0376I: A Connect:Direct process definitions XML file has been created. The file is located here: ''<insert_0>''.
Severity: 0 : Information
Explanation: A Connect:Direct process definitions XML file has been generated at the location given. This XML file defines Connect:Direct process definition information for customizing the Connect:Direct processes that are generated for file transfers to and from Connect:Direct nodes.
Response: Update this file to include the necessary customization.

BFGCL0377I: A Connect:Direct node properties XML file for agent ''<insert_0>'' is already present and will not be overwritten.
Severity: 0 : Information
Explanation: The Connect:Direct node properties XML file is already present for the agent and has not been overwritten or changed.
Response: No action required.

BFGCL0378I: A Connect:Direct node properties XML file has been created. The file is located here: ''<insert_0>''.
Severity: 0 : Information
Explanation: A Connect:Direct node properties XML file has been generated at the location given. This XML file defines Connect:Direct node properties information for defining information to MQMFT that is not available, or appropriate, from the Connect:Direct network map.
Response: Update this file to include the necessary node properties.

BFGCL0379E: A truststore must be specified when creating a protocol bridge agent with a protocol file server type of FTPS.
Severity: 20 : Error
Explanation: We cannot create a protocol bridge agent with a protocol file server type of FTPS without specifying a truststore.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0380E: A truststore password must be specified when creating a protocol bridge agent with a protocol file server type of FTPS.
Severity: 20 : Error
Explanation: We cannot create a protocol bridge agent with a protocol file server type of FTPS without specifying a truststore password.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0381E: A truststore can only be specified when creating a protocol bridge agent with a protocol file server type of FTPS.
Severity: 20 : Error
Explanation: We cannot create a protocol bridge agent with a truststore when the protocol file server type is not FTPS.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0382E: A truststore password can only be specified when creating a protocol bridge agent with a protocol file server type of FTPS.
Severity: 20 : Error
Explanation: We cannot create a bridge agent with a truststore when the protocol file server type is not FTPS.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0383E: The source and destination agents for the transfer have different 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 different 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 have the same value. Restart the agents so that the changes take effect. Retry the transfer.

BFGCL0384E: One or more unexpected parameters were supplied before a transfer definition parameter ''<insert_0>'' or one of the parameters (''<insert_1>''). The unexpected parameters were: ''<insert_2>''. Another cause of this error is that neither the ''<insert_0>'' parameter nor one of the ''<insert_1>'' parameters was specified.
Severity: 20 : Error
Explanation: The command cannot process the additional parameters and so cannot complete successfully.
Response: Refer to the command-line help or to the product documentation to determine the correct syntax for the command. Reissue the command omitting the additional parameter.

BFGCL0385E: The specified combination of the -trs, -ms, -ss, -all and -ims parameters is invalid.
Severity: 20 : Error
Explanation: The -all parameter cannot be specified with the -trs, -ms -ss or -ims parameters and the -ims parameter cannot be specified with the -trs, -ms -ss or -all parameters.
Response: For further information refer to the command-line help. Correct the command by specifying a valid combination of parameters and run the command again.

BFGCL0386E: The -cdu parameter has been specified without the -trs or -all parameters.
Severity: 20 : Error
Explanation: The -cdu parameter is valid with the fteCleanAgent command only if the -trs or -all parameters have been specified.
Response: For further information refer to the command-line help. Run the command again without the -cdu parameter or by specifying the -trs or -all parameters.

BFGCL0387E: The -tracePath parameter has been specified without the -trace parameter.
Severity: 20 : Error
Explanation: The -tracePath parameter is only allowed if the -trace parameter is also specified.
Response: Run the command again either without the -tracePath parameter or with the -trace parameter specified.

BFGCL0388E: The directory path specified as the value of the -tracePath parameter is not accessible.
Severity: 20 : Error
Explanation: The value of the -tracePath parameter must be an existing directory to which the command has write access.
Response: Ensure that the specified directory exists and the command has write permission to access it. Run the command again.

BFGCL0389W: The agent trace specification <insert_0> contains an incorrect character.
Severity: 10 : Warning
Explanation: The agent trace specification defined in the agent.propertries file did not match the required format. An incorrect character was used. The trace specified was invalid and could not be used to start trace.
Response: To enable trace, correct the trace specification in agent.properties file and restart the agent. Consult the product documentation for the correct trace specification format.

BFGCL0390E: An error occurred accessing the directory path specified as the value of the -tracePath parameter. The reason is: <insert_0>
Severity: 20 : Error
Explanation: An error occurred accessing the directory to which the trace output is to be written.
Response: Check the reason for the error and make any necessary changes. Run the command again.

BFGCL0391E: Failed to create the ProtocolBridgeProperties.xml file with exception <insert_0>
Severity: 20 : Error
Explanation: Attempted to create the sample protocol bridge properties file ProtocolBridgeProperties.xml, but failed to create the file. Unless this file is created and configured, the protocol bridge agent cannot transfer files.
Response: Check that we have permission to write the sample file into the agents directory.

BFGCL0392I: A protocol bridge properties XML file has been created. This file contains details for the protocol file server specified at protocol bridge agent creation. You must add further details and servers manually. The file can be found here: ''<insert_0>''.
Severity: 0 : Information
Explanation: A protocol bridge properties XML file has been generated at the locationgiven. This XML file defines protocol file server information for transfers.
Response: Update this file to add additional servers so that the protocol bridge agent can transfer to multiple protocol file servers.

BFGCL0393I: An existing protocol bridge properties XML file for agent ''<insert_0>'' has been detected and has not been updated.
Severity: 0 : Information
Explanation: The protocol bridge properties XML file already exists for the agent and has not been changed.
Response: No action required.

BFGCL0394E: The arguments: (<insert_0>) are invalid for the protocol file server type SFTP.
Severity: 20 : Error
Explanation: An SFTP protocol file server type does not support the additional arguments.
Response: Refer to the command line help or to the product documentation to determine which property to specify. Reissue the command omitting the additional arguments.

BFGCL0395E: An error occurred attempting to parse the given monitor definition file XML. The error was: <insert_0>
Severity: 20 : Error
Explanation: An error occurred attempting to parse the given monitor definition file XML.
Response: Check the reason for the error and make any necessary changes to the XML before running the command again.

BFGCL0396E: Cannot export a monitor definition XML file unless both the ''<insert_0>'' and ''<insert_1>'' commandline arguments have also been specified.
Severity: 20 : Error
Explanation: Monitor defininition XML can only be exported for a single unique monitor.
Response: Specify an agent and monitor name and resubmit the command.

BFGCL0397I: Monitor definition XML for ''<insert_0>'' written to <insert_1>.
Severity: 0 : Information
Explanation: n/a
Response: No action required.

BFGCL0398W: An empty protocol bridge properties XML file has been created. At least one protocol server must be defined before the protocol bridge agent can be used for transfers. The file can be found here: ''<insert_0>''
Severity: 10 : Warning
Explanation: A protocol bridge properties XML file has been generated at the locationgiven. This XML file defines protocol file server information for transfers.
Response: Update this file with server definitions so that the protocol bridge agent can be used for transfers.

BFGCL0399E: The -srdp parameter is applicable only if we have specified the -srdb parameter.
Severity: 20 : Error
Explanation: The source delimiter position parameter is applicable only if we have specified a binary delimiter parameter for the source.
Response: Either remove the -srdp parameter from the command, or add the -srdb parameter to the command. Then reissue the command.

BFGCL0400E: The specified command line options, <insert_0>, are supported only when transferring from a record-oriented file.
Severity: 20 : Error
Explanation: You are specifying command line options that are not appropriate for the specified source.
Response: Either reissue the command after removing the specified options or specify an appropriate source.

BFGCL0401E: The -skeep parameter is not valid unless the transfer is in text mode.
Severity: 20 : Error
Explanation: You are specifying a parameter that depends on another parameter being set to a particular value.
Response: Specify the '-h' command line parameter to see more usage information and modify your command to submit a text transfer.

BFGCL0402E: The monitor resource has been asked to scan a denied path.
Severity: 20 : Error
Explanation: The resource directory being monitored will not scan directories which have been listed as denied access.
Response: Review agent properties 'sandBoxRoot' and 'commandPath' and ensure they are not on the resource path of any monitors.

BFGCL0403E: Queue operations have not been enabled by the monitor agent. The queue monitor has been created but has not been started.
Severity: 20 : Error
Explanation: The agent property enableQueueInputOutput must be set to "true" for queue monitors to be started.
Response: Set the agent property enableQueueInputOutput to "true" in the agent.properties file. Then restart the monitor agent.

BFGCL0404E: Queue manager ''<insert_0>'' and agent ''<insert_1>'' are not associated with this installation of IBM MQ Managed File Transfer. They are currently associated with installation ''<insert_2>''.
Severity: 20 : Error
Explanation: The queue manager for this agent is associated with a different installation of IBM MQ Managed File Transfer.
Response: Start the agent using the commands from the correct installation of IBM MQ Managed File Transfer.

BFGCL0405E: Agent ''<insert_0>'' is configured to connect to queue manager ''<insert_1>'' in bindings mode but the IBM MQ installation located at ''<insert_2>'' does not contain an IBM MQ Server installation.
Severity: 20 : Error
Explanation: To connect an agent to a queue manager in bindings mode, the IBM MQ Server component must be installed in the installation of IBM MQ that owns the agent.
Response: Install the IBM MQ Server component in the installation of IBM MQ that owns the specified agent. If you want to connect the agent to a queue manager owned by a different IBM MQ installation, configure the agent to use a client mode connection instead of a bindings mode connection.

BFGCL0406E: The IBM MQ Managed File Transfer installation associated with queue manager ''<insert_0>'' and agent ''<insert_1>'' is unknown.
Severity: 20 : Error
Explanation: The agent's queue manager must be associated with an installation of IBM MQ Managed File Transfer.
Response: Associate the queue manager for this agent with an installation of IBM MQ Managed File Transfer. Ensure the queue manager is started.

BFGCL0407E: Queue manager ''<insert_0>'' is not associated with this installation of IBM MQ Managed File Transfer. It is currently associated with installation ''<insert_1>''.
Severity: 20 : Error
Explanation: The specified queue manager is associated with a different installation of IBM MQ Managed File Transfer.
Response: Run the command from the correct installation of IBM MQ Managed File Transfer.

BFGCL0408E: Unable to obtain IBM MQ installation information for queue manager ''<insert_0>''. Reason <insert_1>
Severity: 20 : Error
Explanation: The command checks the IBM MQ installation information for the required queue manager to ensure that the queue manager is associated with the required IBM MQ installation. This check failed for the reason given. The most likely cause of the failure is that the required queue manager does not exist.
Response: Examine the reason given for the error and take the necessary corrective action. Then retry the command.

BFGCL0409E: The IBM MQ Managed File Transfer installation associated with queue manager ''<insert_0>'' is unknown.
Severity: 20 : Error
Explanation: The specified queue manager must be associated with an installation of IBM MQ Managed File Transfer.
Response: Associate the specified queue manager with an installation of IBM MQ Managed File Transfer. Ensure the queue manager is started.

BFGCL0410E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, the reason code was <insert_1> and diagnostic message code was <insert_2>. A connection could not be established to the default queue manager on host ''<insert_3>'' using port <insert_4> and channel <insert_5>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code, reason code and diagnostic message specified in the message correspond to the type of problem encountered. The problem occurred while trying to establish a client transport mode connection to the default queue manager, using the specified connection information.
Response: Consult the IBM MQ product documentation to determine the cause of the problem. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0411E: A messaging problem prevented the command from completing successfully. The IBM MQ completion code was <insert_0>, the reason code was <insert_1> and diagnostic message code was <insert_2>. A connection could not be established to queue manager <insert_3>, on host ''<insert_4>'' using port <insert_5> and channel <insert_6>.
Severity: 20 : Error
Explanation: The command could not complete because IBM MQ detected a problem. The completion code, reason code and diagnostic message specified in the message correspond to the type of problem encountered. The problem occurred while trying to establish a client transport mode connection to the specified queue manager, using the specified connection information.
Response: Consult the IBM MQ product documentation to determine the cause of the problem. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM support center.

BFGCL0412E: Unable to determine the logger name.
Severity: 20 : Error
Explanation: It is not possible to determine the name of the logger to send the stop request to.
Response: Ensure the name of the logger to be stopped is specified in the command.

BFGCL0413E: Unable to determine the logger name.
Severity: 20 : Error
Explanation: It is not possible to determine the name of the logger to start.
Response: Ensure the name of the logger to be started is specified in the command.

BFGCL0414E: Unable to determine the logger name.
Severity: 20 : Error
Explanation: It is not possible to determine the name of the logger to be modified.
Response: Ensure the name of the logger to be modified is specified in the command.

BFGCL0415I: Logger configured successfully.
Severity: 0 : Information
Explanation: Logger configured successfully.
Response: No action required.

BFGCL0416E: The '-loggerType' parameter has been specified without a value.
Severity: 20 : Error
Explanation: The '-loggerType' parameter requires a value of DATABASE or FILE to be specified.
Response: Specify a value for the '-loggerType' parameter and retry the command.

BFGCL0417E: The value of the '-loggerType' parameter is invalid.
Severity: 20 : Error
Explanation: The '-loggerType' parameter requires a value of DATABASE or FILE to be specified.
Response: Specify a valid value for the '-loggerType' parameter and retry the command.

BFGCL0418E: The logger directory ''<insert_0>'' could not be created.
Severity: 20 : Error
Explanation: It was not possible to create a configuration directory for the logger.
Response: Ensure the user running the command has sufficient permissions to create the specified directory, and that the directory doesn't exist already. Retry the command.

BFGCL0419E: The logger directory ''<insert_0>'' already exists and the ''-f'' parameter was not specified on the command.
Severity: 20 : Error
Explanation: If the logger directory already exists and the '-f' parameter has not been specified the command is not able to recreate the directory.
Response: Delete the directory and retry the command. Alternatively specify the '-f' parameter to overwrite the existing directory.

BFGCL0420E: The logger properties file ''<insert_0>'' already exists and the ''-f'' parameter was not specified on the command.
Severity: 20 : Error
Explanation: If the logger properties file already exists and the '-f' parameter has not been specified the command is not able to recreate the file.
Response: Delete the properties file and retry the command. Alternatively specify the '-f' parameter to overwrite the existing file.

BFGCL0421E: The logger properties file ''<insert_0>'' could not be created.
Severity: 20 : Error
Explanation: It was not possible to create a properties file for the logger.
Response: Ensure the user running the command has sufficient permissions to create the specified file, and that the file doesn't exist already. Retry the command.

BFGCL0422E: The logger MQSC script ''<insert_0>'' already exists and the ''-f'' parameter was not specified on the command.
Severity: 20 : Error
Explanation: If the logger MQSC script already exists and the '-f' parameter has not been specified the command is not able to recreate the file.
Response: Delete the MQSC script and retry the command. Alternatively specify the '-f' parameter to overwrite the existing file.

BFGCL0423E: The logger MQSC script ''<insert_0>'' already exists and the ''-f'' parameter was not specified on the command.
Severity: 20 : Error
Explanation: If the logger MQSC script already exists and the '-f' parameter has not been specified the command is not able to recreate the file.
Response: Delete the MQSC script and retry the command. Alternatively specify the '-f' parameter to overwrite the existing file.

BFGCL0424I: A file has been created containing the MQSC definitions to create your logger. The file can be found here: ''<insert_0>''.
Severity: 0 : Information
Explanation: Use the MQSC definitions to configure the logger queues if we have not already done so.
Response: Use the MQSC definitions as input to runmqsc, if available. Alternatively, on z/OS, the commands can be used as input to CSQUTIL. Refer to the topic "Installing > Installing on z/OS > After we have installed on z/OS" in the product documentation for an example of how to do this. The product documentation is available online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCL0425I: A file has been created containing the MQSC definitions to delete your logger. The file can be found here: ''<insert_0>''.
Severity: 0 : Information
Explanation: Use the MQSC definitions to remove the logger queues if we have not already done so.
Response: Use the MQSC definitions as input to runmqsc, if available. Alternatively, on z/OS, the commands can be used as input to CSQUTIL. Refer to the topic "Installing > Installing on z/OS > After we have installed on z/OS" in the product documentation for an example of how to do this. The product documentation is available online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCL0426I: Direct the following MQSC definitions for logger ''<insert_0>'' to queue manager ''<insert_1>''.
Severity: 0 : Information
Explanation: Direct the following MQSC definitions for the specified logger to the specified queue manager.
Response: Direct the following MQSC definitions for the specified logger to the specified queue manager.

BFGCL0427E: A logger type must be specified when creating a logger.
Severity: 20 : Error
Explanation: We cannot create a logger without specifying a logger name.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0428E: A logger database type must be specified when creating a database logger.
Severity: 20 : Error
Explanation: We cannot create a database logger without specifying a logger database type.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0429E: A logger database name must be specified when creating a database logger.
Severity: 20 : Error
Explanation: We cannot create a database logger without specifying a database name.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0430E: A logger database driver must be specified when creating a database logger.
Severity: 20 : Error
Explanation: We cannot create a database logger without specifying a database driver.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0431E: A maximum file size must be specified when creating a file logger.
Severity: 20 : Error
Explanation: We cannot create a file logger without specifying a maximum file size.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0432E: A maximum file count must be specified when creating a file logger.
Severity: 20 : Error
Explanation: We cannot create a file logger without specifying a maximum file count.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0433E: The data directory ''<insert_0>'' does not exist.
Severity: 20 : Error
Explanation: The product has been configured to use a data directory that does not exist.
Response: Check that the specified data directory exists.

BFGCL0434E: Unable to determine the logger name.
Severity: 20 : Error
Explanation: It is not possible to determine the name of the logger to create.
Response: Ensure the name of the logger to be created is specified in the command.

BFGCL0435E: Unable to determine the logger name.
Severity: 20 : Error
Explanation: It is not possible to determine the name of the logger to delete.
Response: Ensure the name of the logger to be deleted is specified in the command.

BFGCL0436I: The logger has been deleted but no logger.properties file was found.
Severity: 0 : Information
Explanation: The logger was successfully deleted. A logger.properties file could not be found but the configuration directory was deleted because the -f option was used to force deletion.
Response: None.

BFGCL0437E: The command was unable to delete the logger ''<insert_0>'' because the logger does not exist. Check spelling and try again.
Severity: 20 : Error
Explanation: The command did not complete because the command could not find the logger.
Response: Check the spelling of the logger name and reissue the command.

BFGCL0438E: The logger is currently running and cannot be deleted.
Severity: 20 : Error
Explanation: You must stop the logger before attempting to delete it.
Response: Stop the logger and reissue the command.

BFGCL0439E: There was an error when trying to find the file: ''<insert_0>''.
Severity: 20 : Error
Explanation: The command failed to create the file. Check we have the required permissions and retry.
Response: The command failed to create the file. Check we have the required permissions and retry.

BFGCL0440E: There was an input/output error when trying to use the file: ''<insert_0>''.
Severity: 20 : Error
Explanation: The command failed to create the file. Check we have the required permissions and retry.
Response: The command failed to create the file. Check we have the required permissions and retry.

BFGCL0441I: Use the following MQSC commands to clear and delete the logger''s queues on queue manager ''<insert_0>''.
Severity: 0 : Information
Explanation: A file has been created that contains the required MQSC commands to complete the deletion of a logger.
Response: Use the file generated to delete the local queues for the logger.

BFGCL0442E: The command was unable to delete the directory: ''<insert_0>''. Check that we have the required permissions and retry.
Severity: 20 : Error
Explanation: The command failed to delete the directory.
Response: Check that we have the required permissions to delete directories. Reissue the command.

BFGCL0443E: The command was unable to delete the directory: ''<insert_0>''. Check that we have the required permissions and retry.
Severity: 20 : Error
Explanation: The command failed to delete the directory.
Response: Check that we have the required permissions to delete directories. Reissue the command.

BFGCL0444E: The logger name ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: You have specified a logger name that is longer than 28 characters or that contains characters other than 'A-Z', 'a-z', '0-9', '.' or '_'.
Response: Reissue the command with a valid logger name.

BFGCL0445E: Internal error : Attempted to create a wmqfte.properties file in ''<insert_0>'' failed because ''<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.

BFGCL0446E: Internal error : Attempted to write to wmqfte.properties file in ''<insert_0>'' failed because ''<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.

BFGCL0447E: The attempt to delete agent ''<insert_0>'' could not be completed because the property file was missing. Use the -f parameter to force the deletion of the agent.
Severity: 20 : Error
Explanation: The delete agent command could not successfully remove the named agent because the configuration file for that agent was missing or inaccessible.
Response: Check that the agent is present and that the fteDeleteAgent command has permission to access the files. If the properties file is missing, we can force the deletion of the agent using the -f parameter.

BFGCL0448E: An error occurred while reading the standard output stream. The reason is: <insert_0>
Severity: 20 : Error
Explanation: An error occurred while reading the standard output stream of an agent or logger running in the foreground.
Response: Check the reason for the error and make any changes required. Then restart the agent or logger. Otherwise contact the IBM support center if you need further assistance.

BFGCL0449E: An error occurred while reading the standard error stream. The reason is: <insert_0>
Severity: 20 : Error
Explanation: An error occurred while reading the standard error stream of an agent or logger running in the foreground.
Response: Check the reason for the error and make any changes required. Then restart the agent or logger. Otherwise contact the IBM support center if you need further assistance.

BFGCL0450E: The attempt to create the ''<insert_0>'' properties file has failed with exception <insert_1>.
Severity: 20 : Error
Explanation: A IBM MQ Managed File Transfer data configuration failed to create one of the components. As a result, the creation of the IBM MQ Managed File Transfer configuration has failed.
Response: Review the associated error message and check that this command can access the directory to create the file and has permission to write to that directory.

BFGCL0451E: A file logger mode must be specified when creating a file logger.
Severity: 20 : Error
Explanation: We cannot create a file logger without specifying a file logger mode.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0452E: The '-fileLoggerMode' parameter has been specified without a value.
Severity: 20 : Error
Explanation: The '-fileLoggerMode' parameter requires a value of CIRCULAR or LINEAR to be specified.
Response: Specify a value for the '-fileLoggerMode' parameter and retry the command.

BFGCL0453E: The value of the '-fileLoggerMode' parameter is invalid.
Severity: 20 : Error
Explanation: The '-fileLoggerMode' parameter requires a value of CIRCULAR or LINEAR to be specified.
Response: Specify a valid value for the '-fileLoggerMode' parameter and retry the command.

BFGCL0454E: The attempt to stop agent <insert_0> has failed because the agent command properties could not be located.
Severity: 20 : Error
Explanation: To stop the agent, the fteStopAgent command must send a stop request to the agent's command queue manager. These values are read from the properties file command.properties in the agent's coordination directory.
Response: Review the agent configuration and ensure that the associated coordination configuration has a command.properties file and that the file contains the necessary properties.

BFGCL0455E: The '-fileCount' parameter is not valid when the '-fileLoggerMode' is set to LINEAR.
Severity: 20 : Error
Explanation: Linear file loggers cannot specify how many files to log messages to. The '-fileSize' parameter should be used instead to specify the size of the individual log files.
Response: Remove the '-fileCount' parameter and rerun the command.

BFGCL0456E: The parameter ''<insert_0>'' is not valid for the fteCreateLogger command.
Severity: 20 : Error
Explanation: A parameter was specified that is not supported on the fteCreateLogger command.
Response: Remove the specified parameter and rerun the command. Use the '-h' flag to show the correct syntax for the command.

BFGCL0457E: Missing or corrupt installation configuration. Use the fteSetupCoordination command to correct this condition. Additional information might be contained in the this exception <insert_0>
Severity: 20 : Error
Explanation: An attempt to change the default coordination name for this installation has failed because the installation configuration is either missing or corrupted.
Response: If this is a new installation, use the fteSetupCoordination command to define the first set of coordination details because this command also defines the installation configuration for IBM MQ Managed File Transfer. Otherwise, review any previous commands and ensure that they completed correctly.

BFGCL0459E: Unable to determine default coordination property set from installation configuration. Issue the fteSetupCoordination or fteChangeDefaultConfigurationOptions commands as appropriate to resolve this problem.
Severity: 20 : Error
Explanation: An attempt to create an agent without specifying a specific property set has failed. The default coordination property set could not be determined because the installation configuration is either missing or corrupted.
Response: If this is a new installation, use the fteSetupCoordination command to create the first set of coordination details and the installation configuration for IBM MQ Managed File Transfer. Otherwise, use the fteChangeDefaultConfigurationOptions command to select a default property set.

BFGCL0460E: The attempt to delete logger ''<insert_0>'' could not be completed because the property file was missing.
Severity: 20 : Error
Explanation: The delete logger command could not successfully remove the named logger because the configuration file for that logger was missing or inaccessible.
Response: Check that the logger is present and that the fteDeleteLogger command has permission to access the files.

BFGCL0461E: An attempt to create a logger associated with coordination <insert_0> has failed because coordination <insert_0> is not present.
Severity: 20 : Error
Explanation: When creating a new logger it must be associated with a coordination. The named coordination is not present so the command cannot complete.
Response: Check that the named coordination is correct and if so ensure it is present in the configuration, and that the user issuing the command has at least read access.

BFGCL0462W: Agent ''<insert_0>'' is not running on the local system or we do not have sufficient privileges to run this command.
Severity: 10 : Warning
Explanation: To run the command the agent must be running on the local system and you must have sufficient privileges to run the command against the specified agent.
Response: If the agent is running on the local system, run the command from the user ID that the agent is running under. Alternatively if the agent is running on Windows, run the specified command as an administrator. If the agent is running on a remote system use the '-m' parameter to specify the queue manager to send the command to.

BFGCL0464E: Failed to stop agent ''<insert_0>''. Reason: <insert_1>
Severity: 20 : Error
Explanation: The stop request failed for the reason given.
Response: Examine the reason given for the stop request failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0465I: Agent ''<insert_0>'' has been stopped.
Severity: 0 : Information
Explanation: The command has successfully stopped the specified agent.
Response: No action is required.

BFGCL0466E: An attempt to stop logger <insert_0> associated with coordination <insert_1> has failed as the configuration could not be located.
Severity: 20 : Error
Explanation: When stopping a logger its configuration needs to be accessed for properties. The logger configuration could not be located for the given name and as a result the command could not be completed successfully.
Response: Check the that named logger is correct and associate with the expected coordination.

BFGCL0467I: Issuing immediate stop request to agent ''<insert_0>''. The command will wait for the agent to stop.
Severity: 0 : Information
Explanation: The command is requesting that the local agent stops immediately. The command will wait until the agent has stopped. Any transfers that are currently running will be interrupted and recovered the next time the agent is started.
Response: No action is required.

BFGCL0468I: Issuing stop request to agent ''<insert_0>''. The command will wait for the agent to stop. The agent will stop only when all current transfers have completed.
Severity: 0 : Information
Explanation: The command is requesting that the local agent stops. The command will wait until the agent has stopped. The agent will stop only when all current transfers have completed.
Response: No action is required.

BFGCL0469E: Another instance of logger ''<insert_0>'' is already running.
Severity: 20 : Error
Explanation: Another instance of the logger is already running. Only a single instance of any given logger can run at one time. A second instance of the logger has not been started.
Response: No action required.

BFGCL0470E: The migrate program has not been initiated through the correct script. As a result it is missing a number of configuration items.
Severity: 20 : Error
Explanation: The migration problem has not been initiated via the fteAgentMigration or the fteLoggerMigration.
Response: Review how the migration has been started and correct as necessary.

BFGCL0471E: The agent to be migrated has not been specified. Use the -agentName to define which agent to migrate.
Severity: 20 : Error
Explanation: The mandatory parameter -agentName has not been given and as a result no migration can be performed.
Response: Resubmit the command with a -agentName parameter.

BFGCL0472E: The agent name ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: You have specified an agent name that is longer than 28 characters or that contains characters other than 'A-Z', 'a-z', '0-9', '.', '_' or wildcard '*'.
Response: Reissue the command with a valid agent name.

BFGCL0473E: The source config to migrate from has not been specified. Use the -config to define which root source configuration to migrate from.
Severity: 20 : Error
Explanation: The required parameter -config has not been given and as a result no migration can be performed.
Response: Resubmit the command with a -config parameter.

BFGCL0474E: An error has occurred whilst validating the original configuration or environment. As a result the migration cannot proceed.
Severity: 20 : Error
Explanation: An error has occurred whilst validating the original configuration or environment of the migration. As a result the required information is not available and the migration cannot complete successfully.
Response: Review the previous errors and correct as necessary.

BFGCL0475E: The -agentName parameter "<insert_0>" has been supplied with a wildcard value which does not match to any agent name within the property set. As a result no migration will be performed.
Severity: 20 : Error
Explanation: The supplied -agentName parameter had a wildcard character, this has not matched to any agent within the property set.
Response: Review the parameter value for -agentName and correct as necessary.

BFGCL0476E: An error has occurred whilst validating the configuration. As a result the migration cannot proceed.
Severity: 20 : Error
Explanation: An error has occurred whilst validating the property set of the migration. As a result the required information is not available and the migration cannot complete successfully.
Response: Review the previous errors and correct as necessary.

BFGCL0477E: A warning has occurred whilst validating the configuration. As the -f (force) is not present, the migration will not proceed.
Severity: 20 : Error
Explanation: A warning has occurred whilst validating the configuration. The -f (force) parameter is not present and as a result the migration will not proceed.
Response: Review the previous warning and if expected then resubmit the command with the -f parameter.

BFGCL0478I: Migration of <insert_0> has been completed.
Severity: 0 : Information
Explanation: The migration of the end point (agent or loggers) has been complete.
Response: No action required.

BFGCL0479E: An error occurred configuring the SSL properties. The reason is: <insert_0>
Severity: 20 : Error
Explanation: SSL has been specified for connection to the command or coordination queue manager. The configuration of the SSL properties has failed.
Response: Correct the problem with the SSL properties. Then issue the command again.

BFGCL0480E: The logger to be migrated has not been specified. Use the -loggerName to define which logger to migrate.
Severity: 20 : Error
Explanation: The mandatory parameter -loggerName has not been given and as a result no migration can be performed.
Response: Resubmit the command with a -loggerName parameter.

BFGCL0481E: The logger name ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: You have specified an logger name that is longer than 28 characters or that contains characters other than 'A-Z', 'a-z', '0-9', '.', '_'.
Response: Reissue the command with a valid logger name.

BFGCL0482E: An error has occurred whilst validating the configuration. As a result the migration cannot proceed.
Severity: 20 : Error
Explanation: An error has occurred whilst validating the property set of the migration. As a result the required information is not available and the migration cannot complete successfully.
Response: Review the previous errors and correct as necessary.

BFGCL0483E: A warning has occurred whilst validating the configuration. As the -f (force) is not present, the migration will not proceed.
Severity: 20 : Error
Explanation: A warning has occurred whilst validating the configuration. The -f (force) parameter is not present and as a result the migration will not proceed.
Response: Review the previous warning and if expected then resubmit the command with the -f parameter.

BFGCL0484E: Attempt to create queue generation scripts has failed with <insert_0>
Severity: 20 : Error
Explanation: The fteMigrationLogger could not create the MQ script for generating the queues in the queue manager. The migration will have been completed but does not include the MQ scripts.
Response: Review the exception reported and ensure underlying problem has been removed and repeat this command with the -f (force) parameter.

BFGCL0485E: The installed Windows service for the agent is at version <insert_0>, the required version is <insert_1>. The agent cannot be started.
Severity: 20 : Error
Explanation: You have attempted to start an agent that is configured as a Windows service for an earlier version of the product. This is incompatible with the current product version and the agent cannot be started.
Response: Migrate the agent to the IBM MQ Managed File Transfer product version or run the fteModifyAgent command with the -s parameter to replace the existing Windows service with the new version. Then attempt to start the agent again.

BFGCL0486E: The installed Windows service program is for a different IBM MQ Managed File Transfer product installation from the command.
Severity: 20 : Error
Explanation: The installed Windows service program must be for the same product installation image as the command requesting the agent to start.
Response: Run the command for the IBM MQ Managed File Transfer product installation that is associated with the installed Windows service program. Alternatively, move the Windows service program to the IBM MQ Managed File Transfer product installation associated with the command by running the fteModifyAgent command with the -s parameter to replace the existing Windows service with the version required.

BFGCL0487E: Missing or corrupt installation configuration. Use the fteSetupCoordination command to correct this condition. Additional information might be contained in this exception <insert_0>
Severity: 20 : Error
Explanation: An attempt to create an agent has failed because the installation configuration is either missing or corrupted.
Response: If this is a new installation, use the fteSetupCoordination command to define the first set of coordination details because this command also defines the installation configuration for IBM MQ Managed File Transfer. Otherwise, review any previous commands and ensure that they completed correctly.

BFGCL0488E: Missing or corrupt installation configuration. Use the fteSetupCoordination command to correct this condition. Additional information might be contained in this exception <insert_0>
Severity: 20 : Error
Explanation: An attempt to create an agent has failed because the installation configuration is either missing or corrupted.
Response: If this is a new installation, use the fteSetupCoordination command to define the first set of coordination details because this command also defines the installation configuration for IBM MQ Managed File Transfer. Otherwise, review any previous commands and ensure that they completed correctly.

BFGCL0489I: The attempt to stop the agent failed because of a problem connecting to MQ. It may be possible to stop the agent locally. To do so you must run the fteStopAgent command as the same user who started the agent.
Severity: 0 : Information
Explanation: If an attempt to stop an agent fails because of an MQ messaging problem, MQMFT will attempt to stop the local agent process. This is only possible if the user who runs the fteStopAgent command is the same as the user who started the agent.
Response: Correct the MQ messaging problem and rerun the command. Alternatively run the command as the user who started the agent.

BFGCL0490E: There is no default set of configuration options because of missing or corrupt installation configuration. Use the -p parameter to specify the set of configuration options on the fteSetupCoordination command to correct this condition.
Severity: 20 : Error
Explanation: An attempt to read the default set of configuration options has failed because the installation configuration is either missing or corrupted.
Response: If this is a new installation, use the fteSetupCoordination command to define the first set of coordination details because this command also defines the installation configuration for IBM MQ Managed File Transfer. Otherwise, review any previous commands and ensure that they completed correctly.

BFGCL0491E: Missing or corrupt command.properties file. Use the fteSetupCommands command to correct this condition. Additional information might be contained in this exception <insert_0>
Severity: 20 : Error
Explanation: An attempt to create an agent has failed because the command properties are either missing or corrupted.
Response: If this is a new installation, use the fteSetupCommands command to define the command properties. Otherwise, review any previous commands and ensure that they completed correctly.

BFGCL0492E: Missing or corrupt installation configuration. Use the fteSetupCoordination command to correct this condition. Additional information might be contained in this exception <insert_0>
Severity: 20 : Error
Explanation: An attempt to create an agent has failed because the installation configuration is either missing or corrupted.
Response: If this is a new installation, use the fteSetupCoordination command to define the first set of coordination details because this command also defines the installation configuration for IBM MQ Managed File Transfer. Otherwise, review any previous commands and ensure that they completed correctly.

BFGCL0493E: An attempt to access the IBM MQ Managed File Transfer configuration at "<insert_0>" has failed. This might be because the command does not have sufficient authority to read the configuration, that the configuration has been not been created, or that the configuration has been removed.
Severity: 20 : Error
Explanation: The fteDisplayVersion command was not able to access the IBM MQ Managed File Transfer configuration and as a result could not continue.
Response: Check that the given configuration path exists and that this command has the correct authority to access the path and then run the fteDisplayVersion command again.

BFGCL0494W: Agent ''<insert_0>'' is not running on the local system or we do not have sufficient privileges to run this command.
Severity: 10 : Warning
Explanation: To run the command the agent must be running on the local system and you must have sufficient privileges to run the command against the specified agent.
Response: If the agent is running, run the command from the user ID that the agent is running under. Alternatively if the agent is running on Windows, run the specified command as an administrator.

BFGCL0495W: Agent ''<insert_0>'' is not running on the local system or we do not have sufficient privileges to run this command.
Severity: 10 : Warning
Explanation: To run the command the agent must be running on the local system and you must have sufficient privileges to run the command against the specified agent.
Response: If the agent is running, run the command as the user that the agent is running as. Alternatively if the agent is running on Windows, run the specified command as an administrator.

BFGCL0496E: The -jc parameter must not be used with other trace parameters.
Severity: 20 : Error
Explanation: The -jc parameter can only be used when other trace parameters are not specified on the command.
Response: Remove other trace parameters from the command and rerun the command.

BFGCL0497E: The -jc parameter must not be used with other trace parameters.
Severity: 20 : Error
Explanation: The -jc parameter can only be used when other trace parameters are not specified on the command.
Response: Remove other trace parameters from the command and rerun the command.

BFGCL0498I: The javacore request was successfully sent to agent ''<insert_0>'' but the system was unable to determine the javacore output file name.
Severity: 0 : Information
Explanation: The javacore request was successfully sent to the specified agent. The agent could not determine the file name of the output javacore file. However, the javacore file name should have been output to the console. For a background agent, the console output is directed to file stderr.log, which is located in the agent's logs directory.
Response: No action is required.

BFGCL0499E: Agent ''<insert_0>'' is not running on the local system.
Severity: 20 : Error
Explanation: The command can only be run against an agent that is running on the local system.
Response: If the agent is running on another system, rerun the command on that system.

BFGCL0500I: The file ''<insert_0>'' has been obfuscated successfully.
Severity: 0 : Information
Explanation: The fteObfuscate command has completed successfully.
Response: No action required.

BFGCL0501E: Credentials file ''<insert_0>'' could not be accessed for obfuscation.
Severity: 20 : Error
Explanation: The supplied credentials file could not be accessed by the fteObfuscate command. This could be because the file is not present in the specified location or the fteObfuscate process does not have sufficient privileges to read and write to the file.
Response: Correct the access problem and run the command again.

BFGCL0502E: You are not authorized to perform the requested operation.
Severity: 20 : Error
Explanation: The command can only be run by IBM MQ administrators. To be a IBM MQ administrator, you must be a member of a special group called the mqm group (or a member of the Administrators group, or the SYSTEM account, on Windows systems).
Response: The mqm group is created automatically when IBM MQ is installed; add further users to the group to allow them to perform administration.

BFGCL0503E: The configuration for IBM MQ Managed File Transfer cannot be determined. Reason: <insert_0>
Severity: 20 : Error
Explanation: The configuration for IBM MQ Managed File Transfer cannot be determined for the reason given, which has prevented the command from completing.
Response: Check that any previous command that might have changed the configuration has completed correctly.

BFGCL0504E: The set of configuration options "<insert_0>" already exists and cannot be replaced.
Severity: 20 : Error
Explanation: The named set of configuration options is already present and as a result the migration cannot take place.
Response: Check that we have provided the correct name of the set of configuration options to the migrate command.

BFGCL0505E: The required parameter -configurationOptions is missing.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command requires the parameter -configurationOptions because this parameter defines which set of configuration options are migrated.
Response: Review the help information and repeat the command with the required parameters.

BFGCL0506E: An error has occurred while validating the configuration options. As a result the migration cannot proceed.
Severity: 20 : Error
Explanation: An error has occurred while validating the set of configuration options for migration. As a result the migration cannot complete successfully.
Response: Review the previous errors and correct as necessary.

BFGCL0507E: No configuration options matching <insert_0> were discovered in <insert_1>.
Severity: 20 : Error
Explanation: The command was given a wilcard for the -configurationOptionsName parameter However, no configuration options were found matching that name.
Response: Review the -configurationOptionsName parameter and check that the correct value has been given.

BFGCL0508E: The topic queue <insert_0> could not be located on the coordination queue manager. The IBM MQ reason code was <insert_1>. No agent publications could be retrieved.
Severity: 20 : Error
Explanation: The specified coordination queue manager has not been correctly configured and so the agent publications could not be retrieved.
Response: Ensure that the coordination queue manager has been correctly configured using the MQSC scripts produced by the fteSetupCoordination command.

BFGCL0509E: The topic queue <insert_0> could not be located on the coordination queue manager. The IBM MQ reason code was <insert_1>. No monitor publications could be retrieved.
Severity: 20 : Error
Explanation: The specified coordination queue manager has not been correctly configured and so the monitor publications could not be retrieved.
Response: Ensure that the coordination queue manager has been correctly configured using the MQSC scripts produced by the fteSetupCoordination command.

BFGCL0510E: Error occurred whilst attempting to validate logger startup. Reason: <insert_0>
Severity: 20 : Error
Explanation: The logger process was started but an error occurred whilst attempting to determine the status.
Response: Examine the reported error information and take the appropriate action. If the problem can not be resolved, contact the IBM support center.

BFGCL0511E: Logger was started successfully but is no longer running.
Severity: 20 : Error
Explanation: The logger process was started successfully but has ended due to an error.
Response: Examine any error information that may have been output and examine the files in the logger log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0512W: Logger process is running, but unable to confirm it started successfully.
Severity: 10 : Warning
Explanation: The logger process was started and is running, but there was no confirmation from the logger.
Response: The logger may be running successfully, in which case no action is required. If this is not the case then examine any error information that may have been output and examine the files in the logger log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0513E: Logger startup failed.
Severity: 20 : Error
Explanation: The logger process was started but there may have been an error that caused it to terminate.
Response: Examine any error information that has been output and examine the files in the logger log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0514E: The command was specified with no logger name. Run the command with the -h parameter to see the usage information.
Severity: 20 : Error
Explanation: You must specify a logger name for this command. Run the command with the -h parameter to see usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0515E: Only one logger name can be specified as an argument. Run the command with the -h parameter to see usage information.
Severity: 20 : Error
Explanation: You must specify a single logger name for this command. Run the command with the -h parameter to see the usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0516E: The -jc parameter must not be used with other trace parameters.
Severity: 20 : Error
Explanation: The -jc parameter can only be used when other trace parameters are not specified on the command.
Response: Remove other trace parameters from the command and rerun the command.

BFGCL0517E: The traceLogger value specified ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The value passed to the command is not supported.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying a valid traceLogger value.

BFGCL0518E: The command was run without a traceLogger parameter. Run the command with the -h parameter to see usage information.
Severity: 20 : Error
Explanation: The trace request was not processed because the command was run without a traceLogger parameter. Run the command with the -h parameter to see usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0519E: Both the -disableOnAnyFFDC and -disableOnFFDC parameters have been specified on the command line. Only one of these parameters can be specified.
Severity: 20 : Error
Explanation: The parameters -disableOnAnyFFDC and -disableOnFFDC are mutually exclusive and only one can be specified on the command line.
Response: If you want to stop trace when a particular FFDC event occurs then use the -disableOnFFDC parameter. Otherwise use -disableOnAnyFFDC to stop trace when any FFDC occurs.

BFGCL0520E: The argument supplied with the -disableOnFFDC parameter is invalid.
Severity: 20 : Error
Explanation: The -disableOnFFDC parameter requires an argument that defines which FFDC event generates a stop trace event. The value supplied was invalid and could not be used as a stop trace event.
Response: Use the fteSetLoggerTraceLevel -h option to review the command usage. Correct the argument before reissuing the command.

BFGCL0521E: Logger ''<insert_0>'' is not running on the local system.
Severity: 20 : Error
Explanation: The command can only be run against a logger that is running on the local system.
Response: If the logger is running on another system, rerun the command on that system.

BFGCL0522W: Logger ''<insert_0>'' is not running on the local system or we do not have sufficient privileges to run this command.
Severity: 10 : Warning
Explanation: To run the command the logger must be running on the local system and you must have sufficient privileges to run the command against the specified logger.
Response: If the logger is running, run the command as the user that the logger is running as. Alternatively if the logger is running on Windows, run the specified command as an administrator.

BFGCL0523I: The javacore request was successfully sent to logger ''<insert_0>''.
Severity: 0 : Information
Explanation: The javacore request was successfully sent to the specified logger. The logger will receive the request and generate a javacore file. The location of the javacore file will be written to the logger's log file.
Response: No action is required.

BFGCL0524I: The trace request was successfully sent to logger ''<insert_0>''.
Severity: 0 : Information
Explanation: The trace request was successfully sent to the specified logger. The logger will receive the request and update its trace specification based on that request. Any trace information will be generated in the directory that the logger outputs its logs to.
Response: No action is required. We can confirm that the logger has processed the request by looking for a corresponding entry in the logger's log file.

BFGCL0525E: An internal error has occurred. 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.

BFGCL0526I: Logger log files located at: <insert_0>
Severity: 0 : Information
Explanation: The logger process, started by this command, is recording logging information to the specified location.
Response: No action is required.

BFGCL0527I: The attempt to stop the logger failed because of a problem connecting to MQ. It may be possible to stop the logger locally. To do so you must run the fteStopLogger command as the same user who started the logger.
Severity: 0 : Information
Explanation: If an attempt to stop an logger fails because of an MQ messaging problem, MQMFT will attempt to stop the local logger process. This is only possible if the user who runs the fteStopLogger command is the same as the user who started the logger.
Response: Correct the MQ messaging problem and re-run the command. Alternatively run the command as the user who started the logger.

BFGCL0528I: Issuing stop request to logger ''<insert_0>''. The command will wait for the logger to stop.
Severity: 0 : Information
Explanation: The command is requesting that the local logger stops. The command will wait until the logger has stopped.
Response: No action is required.

BFGCL0529I: Logger ''<insert_0>'' has been stopped.
Severity: 0 : Information
Explanation: The command has successfully stopped the specified logger.
Response: No action is required.

BFGCL0530E: Failed to stop logger ''<insert_0>''. Reason: <insert_1>
Severity: 20 : Error
Explanation: The stop request failed for the reason given.
Response: Examine the reason given for the stop request failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0531W: Logger ''<insert_0>'' is not running on the local system.
Severity: 10 : Warning
Explanation: The specified logger could not be stopped because it was not running on the local system.
Response: If the logger is running on another system, rerun the command specifying the -m parameter.

BFGCL0532I: For this agent to function an additional credentials file must be created manually. By default this file is called <insert_0> and is located in the home directory of the user who starts the agent. For example, if this user started the agent the location would be: <insert_1>
Severity: 0 : Information
Explanation: A bridge agent requires a credentials file to function correctly. After creating the agent, a credentials file of the correct type must be created manually. Sample credentials files can be found in the samples directory of the product installation. More information on how to create a credentials file can be found in the documentation.
Response: Create a credentials file before attempting to start and use the new bridge agent.

BFGCL0533E: The trace specification ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The value passed to the command is not supported.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Run the command again and supply a valid trace specification.

BFGCL0534E: Failed to start agent ''<insert_0>''. Reason: <insert_1>
Severity: 20 : Error
Explanation: The start request failed for the reason given.
Response: Examine the reason given for the start request failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0535I: A request has been sent to the process controller to start the agent ''<insert_0>''.
Severity: 0 : Information
Explanation: The command has found that the process controller for the agent is running but the agent is not running. This can occur if the agent has failed too many times or if the process controller is waiting for the queue manager to become available. A request has been sent to the process controller to immediately start the agent. Refer to the command line help or to the product documentation for further information.
Response: No action is required.

BFGCL0536E: A request to start the agent ''<insert_0>'' in the foreground has been issued but a process controller for the agent is already running for the agent.
Severity: 20 : Error
Explanation: To start an agent in the foreground the agent must be in the stopped state.
Response: To start the agent in the foreground, stop the agent and then run the fteStartAgent command again.

BFGCL0537E: The path to migrate the credentials to has not been specified. Use the -credentialPath to define the location of the credentials directory.
Severity: 20 : Error
Explanation: The required parameter -credentialPath has not been specified and as a result no migration can be performed.
Response: Run the command again with a -credentialPath parameter.

BFGCL0538E: The credentials path of <insert_0> is not present.
Severity: 20 : Error
Explanation: The credential path specified in the -credentialPath parameter does not exist or the user does not have access to the path.
Response: Review the -credentialPath parameter and ensure 1) we have specified a directory 2) the directory path exist 3) the userid has write permissions to that directory.

BFGCL0539E: Because the -credentialPath is not present, no credentials information will be merged.
Severity: 20 : Error
Explanation: The migrate command was run without the -credentialPath parameter, but with the -force parameter. This means the migration will proceed but will not include any credentials information.
Response: No action provided that no credentials information needs to be migrated.

BFGCL0540I: Migrated files will be stored under <insert_0>
Severity: 0 : Information
Explanation: The root directory for storing of the migrated files.
Response: No action required.

BFGCL0541E: Failed to start logger ''<insert_0>''. Reason: <insert_1>
Severity: 20 : Error
Explanation: The start request failed for the reason given.
Response: Examine the reason given for the start request failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0542I: A request has been sent to the process controller to start the logger ''<insert_0>''.
Severity: 0 : Information
Explanation: The command has found that the process controller for the logger is running but the logger is not running. This can occur if the logger has failed too many times or if the process controller is waiting for the queue manager to become available. A request has been sent to the process controller to immediately start the logger. Refer to the command line help or to the product documentation for further information.
Response: No action is required.

BFGCL0543E: A request to start the logger ''<insert_0>'' in the foreground has been issued but a process controller for the logger is already running for the logger.
Severity: 20 : Error
Explanation: To start a logger in the foreground the logger must be in the stopped state.
Response: To start the logger in the foreground, stop the logger and then run the fteStartLogger command again.

BFGCL0544E: The trace specification ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The value passed to the command is not supported.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Run the command again and supply a valid trace specification.

BFGCL0545E: A maximum of one logger name must be specified as the final argument to this command.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as a logger name. The command requires that exactly one logger name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one logger name parameter.

BFGCL0546E: The IBM MQ Managed File Transfer installation appears to be corrupt or is not accessible. The process controller executable ''<insert_0>'' does not exist.
Severity: 20 : Error
Explanation: The process controller executable file was not found for the product installation or is not accessible. The IBM MQ Managed File Transfer installation might be corrupt.
Response: Check the IBM MQ Managed File Transfer installation for the process controller executable file and check that the file is accessible. If necessary, reinstall the IBM MQ Managed File Transfer product. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0547E: The agent is configured as a Windows service and requires the process controller.
Severity: 20 : Error
Explanation: The -npc parameter was specified to start an agent that is configured as a Windows service. This is not permitted.
Response: Run the command again without the -npc parameter. Alternatively, use the fteModifyAgent command to modify the agent to no longer be run as a Windows service, and then run the fteStartAgent command again.

BFGCL0548E: The logger is configured as a Windows service and requires the process controller.
Severity: 20 : Error
Explanation: The -npc parameter was specified to start a logger that is configured as a Windows service. This is not permitted.
Response: Run the command again without the -npc parameter. Alternatively, use the fteModifyLogger command to modify the logger to no longer be run as a Windows service, and then run the fteStartLogger command again.

BFGCL0549I: The javacore request was successfully sent to agent ''<insert_0>''. The created javacore file name is: <insert_1>
Severity: 0 : Information
Explanation: The javacore request was successfully sent to the specified agent. The agent has generated a javacore file.
Response: No action is required.

BFGCL0550W: A request has been sent to stop the agent process but MQMFT was unable to confirm that the process stopped successfully.
Severity: 10 : Warning
Explanation: The agent process was requested to stop but there was no confirmation from the agent.
Response: The agent may have stopped successfully, in which case no action is required. If this is not the case then examine any error information that may have been output and examine the files in the agent log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0551W: The logger process has been started but MQMFT was unable to confirm that the process started successfully.
Severity: 10 : Warning
Explanation: The logger process was started and may be running, but there was no confirmation from the logger.
Response: The logger may be running successfully, in which case no action is required. If this is not the case then examine any error information that may have been output and examine the files in the logger log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0552W: A request has been sent to stop the logger process but MQMFT was unable to confirm that the process stopped successfully.
Severity: 10 : Warning
Explanation: The logger process was requested to stop but there was no confirmation from the logger.
Response: The logger may have stopped successfully, in which case no action is required. If this is not the case then examine any error information that may have been output and examine the files in the logger log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0553I: The agent has processed the stop request and will end when all current transfers have completed.
Severity: 0 : Information
Explanation: The agent has received the stop request and will shutdown when all current transfers have completed.
Response: n/a

BFGCL0554W: The agent process has been started but MQMFT was unable to confirm that the process started successfully.
Severity: 10 : Warning
Explanation: The agent process was started and may be running, but there was no confirmation from the agent.
Response: The agent may be running successfully, in which case no action is required. If this is not the case then examine any error information that may have been output and examine the files in the agent log directory for any error information. If the problem can not be resolved, contact the IBM support center.

BFGCL0555E: The libraries for performing bindings mode connections to the command queue manager or coordination queue manager are not present in this installation.
Severity: 20 : Error
Explanation: If we have installed only the 'MFT Agent' or 'MFT Tools' components and have configured your MFT commands to connect to the command or coordination queue manager in bindings mode, the commands will be unable to run.
Response: Configure the MFT commands to use a client mode connection to the command and coordination queue manager. Alternatively, install the bindings libraries for IBM MQ.

BFGCL0556E: The supplied -fileSize value of ''<insert_0>'' does not include a valid unit suffix.
Severity: 20 : Error
Explanation: The -fileSize parameter requires a unit to be included as part of the supplied value. Supported units are: GB, MB, KB, m (minutes), h (hours), d (days), w (weeks).
Response: Specify a valid unit as part of the value defined for the -fileSize parameter when you retry the fteCreateLogger command.

BFGCL0557I: For this database logger to function it may be necessary to provide security credentials to access your database server. These credentials can be specified in a credentials file that we can configure your logger to use using the ''wmqfte.database.credentials.file'' property. By default this file is called <insert_0> and is located in the home directory of the user who starts the logger. For example, if this user started the logger the location would be: <insert_1>
Severity: 0 : Information
Explanation: Depending on the location and type of your database server this new logger may need to use a user ID and password in order to access its tables. The only configuration where a user ID and password do not need to be explicitly specified is when the logger is connecting to a local DB2 over a type 2 JDBC connection. In all other cases you need to specify the correct user ID and password to use using a credentials file. More information on how to create a credentials file can be found in the documentation.
Response: Determine if you need to create a credentials file and, if required, do so before attempting to start and use the new database logger.

BFGCL0558E: A logger name parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with no logger name parameter. The command requires that exactly one logger name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one logger name parameter.

BFGCL0559E: A maximum of one logger name can be specified as an argument.
Severity: 20 : Error
Explanation: The command has been issued with more than one parameter that has been interpreted as a logger name. The command requires that exactly one logger name parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying exactly one logger name parameter.

BFGCL0560E: The attempt to stop the agent failed because of a problem connecting to the agent. To stop an agent running on the local system you must run the fteStopAgent command as the same user who started the agent.
Severity: 20 : Error
Explanation: An attempt to stop an agent is only possible if the user who runs the fteStopAgent command is the same as the user who started the agent.
Response: Run the command as the user who started the agent.

BFGCL0561E: An attempt to connect to the agent has failed as a result of one of the following reasons: 1. The user ID running the command was not the same user ID the agent was started with. 2. The user ID running the command was not a member of the group specified by the agent property "adminGroup" on z/OS. 3. A communication failure. The report exception was: <insert_0>
Severity: 20 : Error
Explanation: The command received a communication failure when attempting to connect to an agent. The agent has been confirmed to be local and running, however a connection to the agent could not be made. This may be due to the command being run with a different user ID to the one the agent was started with or possibly a problem with the operating system configuration.
Response: Check that the user ID that started the agent is the same user ID as the one performing this command. On z/OS, check that the user ID performing the command is a member of the group specified by the agent property "adminGroup". Otherwise review the exception report with this message.

BFGCL0562E: An internal error has occurred. 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.

BFGCL0563E: Failed to stop agent ''<insert_0>'' because the interprocess communications mechanism is not available. Reason: <insert_1>
Severity: 20 : Error
Explanation: The stop request uses an interprocess communications mechanism to stop an agent that is running on the local system. The command fails because the interprocess communications mechanism is not available. The most likely reason for the interprocess communications mechanism not being available is that the agent has been started with the -npc parameter.
Response: Examine the reason given for the stop request failure and take action as appropriate. Try running the command again specifying the -m parameter, to prevent the stop request from using the interprocess communications mechanism. If the problem persists, and the agent was not started with the -npc parameter, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0564E: Failed to stop logger ''<insert_0>'' because the interprocess communications mechanism is not available. Reason: <insert_1>
Severity: 20 : Error
Explanation: The stop request uses an interprocess communications mechanism to stop a logger that is running on the local system. The command fails because the interprocess communications mechanism is not available. The most likely reason for the interprocess communications mechanism not being available is that the logger has been started with the -npc parameter.
Response: Examine the reason given for the stop request failure and take action as appropriate. Try running the command again specifying the -qm parameter, to prevent the stop request from using the interprocess communications mechanism. If the problem persists, and the logger was not started with the -npc parameter, contact the IBM MQ Managed File Transfer product support team for assistance.

BFGCL0565E: A maximum of one file path can be specified as an argument.
Severity: 20 : Error
Explanation: The ftecfg command has been issued with more than one parameter that has been interpreted as a file path. The command requires that only one file path parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying only one file path parameter.

BFGCL0566E: A file path parameter must be specified as an argument.
Severity: 20 : Error
Explanation: The ftecfg command has been issued without a file path parameter. The command requires one file path parameter. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying one file path parameter.

BFGCL0567E: The Managed File Transfer installation root directory ''<insert_0>'' was not found.
Severity: 20 : Error
Explanation: Managed File Transfer must be installed on the system before running the ftecfg command.
Response: Install Managed File Transfer on the system. Then run the ftecfg command again. Refer to the IBM MQ product documentation for further information.

BFGCL0568E: An error occurred creating the ''config'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'config' subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0569E: An error occurred creating the ''<insert_1>'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating a subdirectory during the extraction of the Managed File Transfer configuration compressed file.
Response: Verify the format of the configuration compressed file. Refer to the IBM MQ product documentation for further information. Make any corrections and rerun the ftecfg command.

BFGCL0570E: A ''config'' file exists in the ''<insert_0>'' directory but it is not a directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'config' subdirectory because a 'config' file already exists but is not a directory. The 'config' file must be a directory.
Response: Copy the existing 'config' file to another location and delete the original 'config' file. Then rerun the ftecfg command.

BFGCL0571E: An error occurred while deleting the directory ''<insert_0>''.
Severity: 20 : Error
Explanation: An error occurred while deleting a directory which is part of an existing Managed File Transfer configuration.
Response: Ensure that the directory is not locked and the user executing the ftecfg command has sufficient access to run the delete. Rerun the ftecfg command.

BFGCL0572E: An error occurred while deleting file ''<insert_0>''.
Severity: 20 : Error
Explanation: An error occurred while deleting a file which is part of an existing Managed File Transfer configuration.
Response: Ensure that the file is not locked and the user executing the ftecfg command has sufficient access to run the delete. Rerun the ftecfg command.

BFGCL0573E: The name of the coordination queue manager could not be found in the coordination.properties file contained in the compressed file.
Severity: 20 : Error
Explanation: The coordination.properties file in the compressed file must contain a value for the coordinationQMgr property specifying the name of the coordination queue manager to be used by the agents.
Response: Modify the compressed file so that it conforms to the required format. Refer to the IBM MQ product documentation for further information. Rerun the ftecfg command.

BFGCL0574E: No Managed File Transfer agent configuration directories were found in the compressed file.
Severity: 20 : Error
Explanation: There must be at least one agent configuration directory present in the compressed file.
Response: Modify the compressed file so that it conforms to the required format. Refer to the IBM MQ product documentation for further information. Rerun the ftecfg command.

BFGCL0575E: The directory name ''<insert_0>'' in the compressed file is not valid.
Severity: 20 : Error
Explanation: All directories in the compressed file must conform to the required format. The identified directory name is invalid for a Managed File Transfer configuration directory structure.
Response: Modify the compressed file so that it conforms to the required format. Refer to the IBM MQ product documentation for further information. Rerun the ftecfg command.

BFGCL0576E: The compressed configuration file ''<insert_0>'' passed as a parameter does not exist.
Severity: 20 : Error
Explanation: The compressed configuration file must exist.
Response: Rerun the ftecfg command passing a valid path to the compressed configuration file as the first parameter.

BFGCL0577E: The file path ''<insert_0>'' in the compressed configuration file is duplicated.
Severity: 20 : Error
Explanation: Each file path in the compressed configuration file must be unique.
Response: Modify the compressed file so that it conforms to the required format. Refer to the IBM MQproduct documentation for further information. Rerun the ftecfg command.

BFGCL0578E: The file path ''<insert_0>'' was not found in the compressed configuration file.
Severity: 20 : Error
Explanation: The file path must exist in the compressed configuration file for it to be valid.
Response: Modify the compressed file so that it conforms to the required format. Refer to the IBM MQproduct documentation for further information. Rerun the ftecfg command.

BFGCL0579W: The file path ''<insert_0>'' in the compressed file was unexpected.
Severity: 10 : Warning
Explanation: The configuration is typically only expected to contain file paths in a certain format. An unexpected file path was found that may be required for the configuration. This file is written to the output configuration directory.
Response: Review the referenced file path, and if this is not required then remove it from the compressed file. Refer to the IBM MQ product documentation for further information. Rerun the ftecfg command if required.

BFGCL0580E: The coordination queue manager name ''<insert_0>'' found in the compressed configuration file is not a valid queue manager name.
Severity: 20 : Error
Explanation: The coordination queue manager name must be a valid queue manager name.
Response: Modify the compressed file so that the coordination queue manager name is valid. Refer to the IBM MQ product documentation for further information. Rerun the ftecfg command.

BFGCL0581E: The agent name ''<insert_0>'' found in the compressed configuration file is not a valid Managed File Transfer agent name when running on 4690 OS.
Severity: 20 : Error
Explanation: The agent name must only contain characters that are valid in a Managed File Transfer agent name and must be less than the maximum length supported on the 4690 platform.
Response: Modify the compressed file so that the agent name conforms to the naming conventions and then rerun the command. Refer to the IBM MQ product documentation for further information.

BFGCL0583E: An error occurred creating the ''installations'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'installations' subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0584E: An ''installations'' file exists in the ''<insert_0>'' directory but it is not a directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'installations' subdirectory because an 'installations' file already exists but is not a directory. The 'installations' file must be a directory.
Response: Copy the existing 'installations' file to another location and delete the original 'installations' file. Rerun the ftecfg command.

BFGCL0585E: An error occurred creating the ''installation1'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'installation1' subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0586E: An error occurred creating the ''logs'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'logs' subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0587E: A ''logs'' file exists in the ''<insert_0>'' directory but it is not a directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'logs' subdirectory because a 'logs' file already exists but is not a directory. The 'logs' file must be a directory.
Response: Copy the existing 'logs' file to another location and delete the original 'logs' file. Rerun the ftecfg command.

BFGCL0588E: An error occurred creating the ''agents'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the 'agents' subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0589E: An error occurred creating the ''<insert_1>'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the agent name subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0590E: The start agent response file template ''<insert_0>'' was not found or cannot be read.
Severity: 20 : Error
Explanation: The start agent response file template is used to construct a response file for each agent. This file is missing or inaccessible.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0591E: An error occurred creating the ''<insert_1>'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating the coordination subdirectory.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCL0592E: A ''<insert_1>'' file exists in the ''<insert_0>'' directory but it is not a directory.
Severity: 20 : Error
Explanation: An error occurred creating the coordination subdirectory because a file of the same name already exists but is not a directory. The coordination file must be a directory.
Response: Copy the existing coordination file to another location and delete the original coordination file. Rerun the ftecfg command.

BFGCL0593E: The directory name ''<insert_0>'' in the compressed file is not valid for coordination ''<insert_1>''. A single coordination root directory must exist in the compressed file.
Severity: 20 : Error
Explanation: All directories in the compressed file must conform to the required format. The first root directory found in the compressed file is taken to be the coordination queue manager name. Any other root directory in the compressed file will result in this error.
Response: Modify the compressed file so that it conforms to the required format. Refer to the IBM MQproduct documentation for further information. Rerun the ftecfg command.

BFGCL0594E: Error reading compressed file ''<insert_0>''. Either this file is not a valid .zip file or it has been corrupted. The error message returned was ''<insert_1>''.
Severity: 20 : Error
Explanation: An error occurred attempting to read from the provided .zip file.
Response: Provide an alternative .zip file from which to read.

BFGCL0595E: The destination attribute ''<insert_0>'' is incorrectly formatted.
Severity: 20 : Error
Explanation: A supplied destination attribute does not conform to the correct format. A destination attribute can be specified as a name only or with a value. A value should be supplied inside parentheses for example, ATTRIBUTE1(VALUE1). If using the name only format then no parentheses are required. For example, ATTRIBUTE2. Multiple attributes can be supplied using either a semicolon separated string or multiple -dfa parameters. For example, a semicolon separated value would look like: ATTR1(VALUE);ATTR2;ATTR3(VALUE) or the same values could be specified using multiple parameters like this: -dfa ATTR1(VALUE) -dfa ATTR2 -dfa ATTR3(VALUE).
Response: Check the format of the supplied destination attributes to see that they are formatted correctly and reissue the command.

BFGCL0596E: The -disableOnAnyFFDC or -disableOnFFDC parameters can only be specified if the -traceAgent parameter is also specified.
Severity: 20 : Error
Explanation: The parameters -disableOnAnyFFDC and -disableOnFFDC only apply to the setting of the agent trace level and therefore only apply when the -traceAgent parameter is also specified.
Response: Either remove the -disableOnAnyFFDC or -disableOnFFDC parameter, or add the -traceAgent parameter.

BFGCL0597W: The diagnostics request was successfully sent to agent ''<insert_0>'' but the system was unable to determine the diagnostics output file name.
Severity: 10 : Warning
Explanation: The diagnostics request was successfully sent to the specified agent. The agent could not determine the file name of the output diagnostics file. However, the diagnostics file name should have been output to the console. For a background agent, the console output is directed to file stderr.log, which is located in the agent's logs directory.
Response: No action is required.

BFGCL0598I: The diagnostics request was successfully sent to agent ''<insert_0>''. The created diagnostics file name is: <insert_1>
Severity: 0 : Information
Explanation: The diagnostics request was successfully sent to the specified agent. The agent has generated a diagnostics file.
Response: No action is required.

BFGCL0599E: The trace request has failed. Reason: <insert_0>
Severity: 20 : Error
Explanation: The trace request failed for the reason given.
Response: Examine the reason given for the failure, and taken action as appropriate.

BFGCL0600E: The javacore request has failed. Reason: <insert_0>
Severity: 20 : Error
Explanation: The javacore request failed for the reason given.
Response: Examine the reason given for the failure, and taken action as appropriate.

BFGCL0601E: The agent diagnostics request has failed. Reason: <insert_0>
Severity: 20 : Error
Explanation: The agent diagnostics request failed for the reason given.
Response: Examine the reason given for the failure, and taken action as appropriate.

BFGCL0602E: The agent status request has failed. Reason: <insert_0>
Severity: 20 : Error
Explanation: The agent status request failed for the reason given.
Response: Examine the reason given for the failure, and taken action as appropriate.

BFGCL0603I: Running <insert_0>.
Severity: 0 : Information
Explanation: The fteRAS command is running the specified collector.
Response: No action is required.

BFGCL0604I: fteRAS command completed successfully. Output is stored in <insert_0>.
Severity: 0 : Information
Explanation: The fteRAS command completed successfully and the output is stored in the specified file.
Response: Send the .zip file specified to the IBM support center.

BFGCL0605E: A maximum of one output path can be specified.
Severity: 20 : Error
Explanation: The fteRAS command can take only a single output path parameter.
Response: Check the fteRAS command parameters and ensure that there is only one output path parameter.

BFGCL0606I: fteRAS command is compressing the output.
Severity: 0 : Information
Explanation: The fteRAS command compresses the output that is to be sent to IBM to a .zip file.
Response: No action is required.

BFGCL0607E: An unexpected exception has occurred running <insert_0>: <insert_1>
Severity: 20 : Error
Explanation: The named collector has encountered the exception specified.
Response: If the details with this message do not help resolve the problem, contact the IBM support center.

BFGCL0608E: The path <insert_0> is not suitable for the fteRAS command.
Severity: 20 : Error
Explanation: The path specified for the RAS output cannot be written to, is not a directory, or already has a subdirectory called fteRAS.
Response: Specify a valid directory path, ensure that the user running the fteRAS command has write access, and that a subdirectory called fteRAS does not exist. If no path was specified, make sure the current user's home directory is valid.

BFGCL0609W: An unexpected return code of <insert_0> was received by <insert_1> when running <insert_2>. The output of the command is in the generated fteRAS.zip file in file: <insert_3>
Severity: 10 : Warning
Explanation: A non-zero return code was returned from the command. The command may have failed or the output may be incomplete.
Response: Check the output of the command for any errors or warnings. If required take appropriate action to resolve the problem.

BFGCL0610I: Agent <insert_0> successfully configured. ADXCHAIN.386 response file: <insert_1>
Severity: 0 : Information
Explanation: Configuration data for the specified agent has been successfully created. The agent can be configured to run as a 4690 OS permanent background application by specifying ADXCHAIN.386 as the program and the specified response file, prefixed with an at sign (@), as the parameter. Note that the response file format must be written exactly as specified for the parameter.
Response: Configure the agent to be run as a permanent background application. Refer to the IBM MQ Managed File Transfer product documentation for a detailed description of how to configure an agent to be run as a permanent background application on the 4690 OS.

BFGCL0611E: The supplied directory ''<insert_0>'' does not exist.
Severity: 20 : Error
Explanation: The directory supplied to the fteBundleConfiguration command cannot be found.
Response: Check that the correct directory was supplied to the command and that it exists. Rerun the fteBundleConfiguration command.

BFGCL0612E: The supplied directory ''<insert_0>'' is not a directory.
Severity: 20 : Error
Explanation: The directory supplied to the fteBundleConfiguration is not a directory.
Response: Check that the correct directory was supplied to the command and that it is a directory and not a file. Rerun the fteBundleConfiguration command.

BFGCL0613E: A command.properties file could not be found in directory ''<insert_0>''.
Severity: 20 : Error
Explanation: The directory supplied to the fteBundleConfiguration does not contain a command.properties file. This file is required for a working configuration so the fteBundleConfiguration command cannot continue.
Response: Correct the configuration in the directory supplied to the command. Rerun the fteBundleConfiguration command.

BFGCL0614E: A coordination.properties file could not be found in directory ''<insert_0>''.
Severity: 20 : Error
Explanation: The directory supplied to the fteBundleConfiguration does not contain a coordination.properties file. This file is required for a working configuration so the fteBundleConfiguration command cannot continue.
Response: Correct the configuration in the directory supplied to the command. Rerun the fteBundleConfiguration command.

BFGCL0615W: An agent.properties file could not be found for agent ''<insert_0>'' in directory ''<insert_1>''. Configuration for this agent will not be included in the bundle.
Severity: 10 : Warning
Explanation: The fteBundleConfiguration command attempted to add the agent.properties file for the referenced agent to the bundle, but it could not be found. This file is required for a working configuration so the configuration for this agent will not be included in the bundle.
Response: Correct the configuration in the directory supplied to the command. Rerun the fteBundleConfiguration command.

BFGCL0616E: An unexpected error was encountered by the fteBundleConfiguration command. Error: <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.

BFGCL0617E: The supplied destination directory ''<insert_0>'' is not empty.
Severity: 20 : Error
Explanation: The directory supplied to the fteBundleConfiguration command when using the -d parameter must be empty so that the contents of the bundle can be extracted into it.
Response: Check that the supplied directory is empty. Rerun the fteBundleConfiguration command.

BFGCL0618E: The supplied bundle file ''<insert_0>'' could not be accessed.
Severity: 20 : Error
Explanation: The bundle file supplied to the fteBundleConfiguration command cannot be accessed.
Response: Check that the bundle file name given in the command is correct and that the user running the command has read access. Rerun the fteBundleConfiguration command.

BFGCL0619W: The agent name ''<insert_0>'' found in the specified directory is not a valid Managed File Transfer agent name when running on 4690 OS. Configuration for this agent will not be included in the bundle.
Severity: 10 : Warning
Explanation: The agent name must only contain characters that are valid in a Managed File Transfer agent name and must be less than the maximum length supported on the 4690 platform.
Response: If you want the specified agent to be a part of your configuration bundle you must modify the configuration so that the agent name conforms to the naming conventions and then rerun the command. Refer to the IBM MQ product documentation for further information.

BFGCL0620I: The bundle ''<insert_0>'' has been successfully created from the configuration in directory ''<insert_1>''.
Severity: 0 : Information
Explanation: The fteBundleConfiguration command completed the creation of a new bundle successfully.
Response: No action required.

BFGCL0621I: The contents of the bundle ''<insert_0>'' have been successfully extracted to directory ''<insert_1>''.
Severity: 0 : Information
Explanation: The fteBundleConfiguration command completed the extraction of a bundle successfully.
Response: No action required.

BFGCL0622E: An error occurred creating the ''<insert_1>'' subdirectory of the ''<insert_0>'' directory.
Severity: 20 : Error
Explanation: An error occurred creating a subdirectory during the extraction of the Managed File Transfer configuration compressed file.
Response: Verify the format of the configuration compressed file. Verify that the user running the fteBundleConfiguration command has the correct access to write to the specified directory. Refer to the IBM MQ product documentation for further information. Make any corrections and rerun the fteBundleConfiguration command.

BFGCL0623E: Too many parameters were passed to the command.
Severity: 20 : Error
Explanation: The fteBundleConfiguration command has been issued with more parameters than expected. The command requires that only one bundle file name and one directory path parameter is specified. The command cannot complete successfully.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the correct number of parameters.

BFGCL0624E: Insufficient parameters were passed to the command. File path parameters must be specified for both the bundle .zip file and the directory path.
Severity: 20 : Error
Explanation: The fteBundleConfiguration command has been issued with insufficient parameters. The command requires that exactly two are specified.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying the correct number of parameters.

BFGCL0625E: The supplied command line parameter ''<insert_0>'' is not a valid option for this command.
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.

BFGCL0626W: Ignoring invalid path ''<insert_0>'' within agents subdirectory of the source tree.
Severity: 10 : Warning
Explanation: The given path has not been accepted as a valid agent subdirectory and will not be included in the bundle.
Response: Investigate the source path to determine if the configuration is required and recreate it using the supplied tooling if necessary.

BFGCL0627E: The configuration could not be read from directory ''<insert_0>''
Severity: 20 : Error
Explanation: The fteBundleConfiguration command was attempting to create a new configuration bundle, but could not read the configuration in the supplied directory. The command cannot complete successfully.
Response: Check the user running the fteBundleConfiguration command has read access to the supplied directory. Rerun the fteBundleConfiguration command.

BFGCL0628E: No valid agent configurations found in directory ''<insert_0>''. The bundle cannot be created.
Severity: 20 : Error
Explanation: The fteBundleConfiguration command was attempting to create a configuration bundle, but could not find any valid agent directories in the supplied directory. The command cannot complete successfully.
Response: Refer to previous messages to determine why no valid agent directories were found. Fix any problems and rerun the fteBundleConfiguration command.

BFGCL0629E: The contents of the agent.properties file for agent ''<insert_0>'' are not valid. Configuration for this agent will not be included in the bundle.
Severity: 20 : Error
Explanation: The fteBundleConfiguration command was attempting to create a configuration bundle, but found properties in the agent.properties file for the specified agent that are not valid.
Response: Refer to previous messages to determine why the contents of the agent.properties file for the specified agent was not valid. Fix any problems and rerun the fteBundleConfiguration command.

BFGCL0630E: An I/O exception occurred while attempting to read the agent.properties file for agent ''<insert_0>''. Configuration for this agent will not be included in the bundle. Exception: <insert_1>
Severity: 20 : Error
Explanation: The fteBundleConfiguration command was attempting to create a configuration bundle, but an I/O exception occurred when an attempt was made to access the agent.properties file for the specified agent.
Response: Refer to the supplied exception message to determine why the contents of the agent.properties file for the specified agent could not be validated. Fix any problems and rerun the fteBundleConfiguration command.

BFGCL0631E: The contents of the coordination.properties file in directory ''<insert_0>'' are not valid. The bundle cannot be created.
Severity: 20 : Error
Explanation: The fteBundleConfiguration command was attempting to create a configuration bundle, but found that the coordination.properties file in the supplied directory is not valid. The command cannot complete successfully.
Response: Refer to previous messages to determine why the contents of the coordination.properties file is not valid. Fix any problems and rerun the fteBundleConfiguration command.

BFGCL0632E: The property ''<insert_0>'' required in the coordination.properties file is missing or has no value. The bundle cannot be created.
Severity: 20 : Error
Explanation: The supplied property is required in the coordination.properties file for the correct operation of the configuration bundle. The command cannot complete successfully.
Response: Ensure that the supplied property is included in the coordination.properties file and has a valid value. Rerun the fteBundleConfiguration command.

BFGCL0633E: Configuration failed for agent ''<insert_0>'' because of a bad properties file.
Severity: 20 : Error
Explanation: The configuration for the specified agent cannot be successfully completed because of an error in the agent properties file.
Response: Examine the reason for the failure given in the previous message, and correct the agent properties file as appropriate on the source system. Re-create the configuration bundle on the source system with the fteBundleConfiguration command. Then transfer the configuration bundle to the target 4690 system and rerun this command specifying the new bundle.

BFGCL0634W: Diagnostics were requested, but agent ''<insert_0>'' is either not running, not located on the local system, or we do not have sufficient privileges to run this command.
Severity: 10 : Warning
Explanation: To run the command the agent must be both running and located on the local system. You must also have sufficient privileges to run the command against the specified agent.
Response: If the agent is running, run the command as the user that the agent is running as. Alternatively if the agent is running on Windows, run the specified command as an administrator.

BFGCL0635E: Failed to create the Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The command has failed for the reason given by the previous message. The Managed File Transfer configuration has not been created.
Response: Examine the reason for the failure and take the appropriate action.

BFGCL0636E: Unexpected arguments: <insert_0>
Severity: 20 : Error
Explanation: The provided arguments were not expected by the uninstall command and so it cannot continue.
Response: Run the uninstall command again with the unexpected arguments omitted.

BFGCL0637E: No argument was specified to the uninstall command.
Severity: 20 : Error
Explanation: The uninstall command requires a single argument of either -a or -c to specify what type of uninstall should be carried out. For descriptions of the -a and -c arguments see the command line help.
Response: Run the uninstall command again with either the -a or -c argument specified.

BFGCL0638E: A unexpected exception was encountered during the uninstall process. Exception: <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.

BFGCL0639E: The IBM IBM MQ File Transfer uninstall failed.
Severity: 20 : Error
Explanation: The uninstall process encountered a problem and could not continue.
Response: Check for previous messages in the log to determine why the uninstall failed.

BFGCL0640W: Directory ''<insert_0>'' could not be deleted during the uninstall process.
Severity: 10 : Warning
Explanation: When the uninstall process attempted to delete the specified directory the file system reported that it could not be deleted.
Response: If required delete the directory manually.

BFGCL0641W: File ''<insert_0>'' could not be deleted during the uninstall process.
Severity: 10 : Warning
Explanation: When the uninstall process attempted to delete the specified file the file system reported that it could not be deleted.
Response: If required delete the file manually.

BFGCL0642I: IBM IBM MQ File Transfer uninstalled successfully.
Severity: 0 : Information
Explanation: The uninstall completed successfully. Please consult the product documentation for information on any further action that may be required.
Response: No action is required.

BFGCL0643I: The maximum number of configuration backups has been reached. The oldest backup will be deleted.
Severity: 0 : Information
Explanation: The maximum number of existing backups has been reached on disk. The oldest backup files will be deleted to ensure that disk space used for backups does not continue to increase.
Response: No action is required.

BFGCL0644I: The backup file ''<insert_0>'' has been deleted.
Severity: 0 : Information
Explanation: The supplied file has been deleted because the maximum number of backups has been reached. This message will be output twice each time the oldest backup is deleted: once for the configuration backup file and once for the logs backup file.
Response: No action is required.

BFGCL0645I: A backup of the product configuration has been created in file ''<insert_0>''.
Severity: 0 : Information
Explanation: The existing product configuration has been backed up in the file specified before it was replaced by the new configuration.
Response: No action is required.

BFGCL0646I: A backup of the product logs has been created in file ''<insert_0>''.
Severity: 0 : Information
Explanation: The existing product logs have been backed up in the file specified.
Response: No action is required.

BFGCL0647I: No existing configuration found. No backup will be created.
Severity: 0 : Information
Explanation: No existing configuration files were found so the ftecfg tool will not make a backup. This is most likely because this is the first time the ftecfg tool has been run after installation of the product.
Response: No action is required.

BFGCL0648W: A background application definition with parameters <insert_0> is no longer valid and should be manually removed using the background application screen, if it has been defined.
Severity: 10 : Warning
Explanation: During the configuration process an agent was found that existed in the previous configuration but not in the new configuration. If a background application was previously defined for this agent it will no longer function correctly so should be removed.
Response: Check the background application screen to see if a definition exists with parameters matching those supplied. If a matching entry is found then it should be removed.

BFGCL0649E: A problem occurred creating backup file ''<insert_0>''. Exception: <insert_1>
Severity: 20 : Error
Explanation: An I/O problem occurred when creating the specified backup file. The backup file might not have been created successfully. The command will not continue. The most common reason for this is a lack of disk space available for the backup files to be created.
Response: Check the supplied exception message to determine the reason for the problem to avoid the problem recurring the next time the configuration is updated.

BFGCL0650E: A backup of the previous configuration could not be created. The command cannot continue.
Severity: 20 : Error
Explanation: A problem occurred when creating a backup of the previous configuration.
Response: Check for previous messages in the log to determine the cause of the failure.

BFGCL0651E: An internal error occurred. Exit code: <insert_0>
Severity: 20 : Error
Explanation: An unexpected error occurred in the License Acceptance Program.
Response: CMSG002

BFGCL0652E: Agreement declined: Installation will not complete successfully unless the license agreement is accepted.
Severity: 20 : Error
Explanation: The license agreement must be accepted before installation can proceed.
Response: No action is required.

BFGCL0653I: Agreement accepted: Proceed with installation.
Severity: 0 : Information
Explanation: The license agreement has been accepted and installation can proceed.
Response: No action is required.

BFGCL0654E: An invalid parameter was supplied to the command.
Severity: 20 : Error
Explanation: An invalid command-line parameter was supplied to the command.
Response: Consult the command usage to determine the valid command-line parameters.

BFGCL0655E: 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

BFGCL0658E: No matching conditions or defaults found for agent ''<insert_0>'' in substitution file ''<insert_1>''.
Severity: 20 : Error
Explanation: When determining the set of substitution variables to use for the specified agent, no matching conditions were found. This combined with no default values means that an agent supplied with a substitution.xml file does not have any substitution variable values to use during substitution. This can lead to incorrectly formatted agent.properties files so the command will not continue. The most likely reason for this error is that the machine where the ftecfg command was run does not match any of the conditions in the substitution.xml file provided for the named agent.
Response: Check the configuration for the specified agent to make sure that its supplied susbstitution.xml file will match the properties of the machine where the ftecfg command was run.

BFGCL0659E: The local absolute path ''<insert_0>'' supplied for property ''<insert_1>'' is outside the configuration directory being bundled.
Severity: 20 : Error
Explanation: When a local absolute path is used to specify a value for a property, the file specified must be located in the configuration directory tree supplied to the fteBundleConfiguration command. This ensures that the file is included in the bundle and will be correctly located by the agent when the bundle is deployed to a 4690 system.
Response: Check whether the property should refer to a local absolute file. If you intended to use a local absolute file, change the location of the file so that it is in the configuration directory tree supplied for inclusion in the bundle.

BFGCL0660I: The local absolute path ''<insert_0>'' supplied for property ''<insert_1>'' was converted to relative path ''<insert_2>'' for inclusion in the bundle.
Severity: 0 : Information
Explanation: The value for the supplied property was modified from the absolute path supplied to a relative path. This allows the file specified by the path to be found when the bundle is deployed to a 4690 system.
Response: No action is required.

BFGCL0661E: The relative path ''<insert_0>'' supplied for property ''<insert_1>'' does not refer to a file located in the configuration directory.
Severity: 20 : Error
Explanation: The value for the supplied property was determined to be a relative path but the file that the path refers to could not be located in the configuration directory being bundled. The bundle cannot be created because this would lead to an error when starting an agent using this configuration, if deployed on 4690.
Response: Ensure that the file referred to by the property exists in the configuration directory supplied to the fteBundleConfiguration command.

BFGCL0662W: It could not be determined if the absolute path ''<insert_0>'' referred to a local file or a 4690 file, so the path will be left unchanged.
Severity: 10 : Warning
Explanation: Because of the the similarity in path formats between Microsoft Windows and IBM OS 4690, it is not always possible to determine if an absolute path refers to a location on the machine where the fteBundleConfiguration command is being run or a 4690 machine where the bundle is intended for use. This warning means that the supplied path value was treated as a 4690 path because the referenced path could not be resolved on the local system.
Response: If you intended the supplied file path to refer to a file on the system where fteBundleConfiguration is being run, ensure that the file exists in the expected location and run the command again. If the supplied file path refers to a location on a 4690 system, no further action is required.

BFGCL0663E: The local absolute path ''<insert_0>'' supplied in credentials file ''<insert_1>'' is outside the configuration directory being bundled.
Severity: 20 : Error
Explanation: When a local absolute path is used to specify a value for the path attribute of a file element in a credentials file, the file specified must be located in the configuration directory tree supplied to the fteBundleConfiguration command. This ensures that the file is included in the bundle and will be correctly located by the agent when the bundle is deployed to a 4690 system.
Response: Check whether the path attribute should be referring to a local absolute file. If you intended to use a local absolute file, change the location of the file so that it is in the configuration directory tree supplied for inclusion in the bundle.

BFGCL0664E: The relative path ''<insert_0>'' supplied in credentials file ''<insert_1>'' does not refer to a file located in the configuration directory.
Severity: 20 : Error
Explanation: The value for the path attribute of a file element in the supplied credentials file was determined to be a relative path but the file that the path refers to could not be located in the configuration directory being bundled. The bundle cannot be created because this would lead to an error when starting an agent using this configuration, if deployed on 4690.
Response: Ensure that the file referred to by the path attribute exists in the configuration directory supplied to the fteBundleConfiguration command.

BFGCL0665I: The local absolute path ''<insert_0>'' supplied in credentials file ''<insert_1>'' was converted to relative path ''<insert_2>'' for inclusion in the bundle.
Severity: 0 : Information
Explanation: The value for the path attribute of a file element in the supplied credentials file was modified from the absolute path supplied to a relative path. This allows the file specified by the path to be found when the bundle is deployed to a 4690 system.
Response: No action is required.

BFGCL0666E: The relative path ''<insert_0>'' supplied for property ''<insert_1>'' does not refer to a file located in the configuration bundle.
Severity: 20 : Error
Explanation: The value for the supplied property was determined to be a relative path but the file that the path refers to could not be located in the configuration bundle being processed. Because this would lead to an error when starting an agent using this configuration, the bundle cannot be extracted.
Response: Ensure that the file referred to by the property exists in the configuration bundle supplied to the ftecfg command.

BFGCL0667E: The relative path ''<insert_0>'' supplied in credentials file ''<insert_1>'' does not refer to a file located in the configuration bundle.
Severity: 20 : Error
Explanation: The value for the path attribute of a file element in the supplied credentials file was determined to be a relative path but the file that the path refers to could not be located in the configuration bundle being processed. Because this would lead to an error when starting an agent using this configuration, the bundle cannot be extracted.
Response: Ensure that the file referred to by the path attribute exists in the configuration bundle supplied to the ftecfg command.

BFGCL0668E: The absolute path ''<insert_0>'' supplied for property ''<insert_1>'' does not refer to an existing local file.
Severity: 20 : Error
Explanation: An absolute path was provided for the supplied property but the path does not exist on the local file system. Because this would lead to an error when starting an agent using this configuration, the bundle cannot be extracted.
Response: Ensure that the file referred to by the path exists on the local file system and run the ftecfg command again.

BFGCL0669E: The absolute path ''<insert_0>'' supplied in credentials file ''<insert_1>'' does not refer to an existing local file.
Severity: 20 : Error
Explanation: An absolute path was provided in the supplied credentials file but the path does not exist on the local file system. Because this would lead to an error when starting an agent using this configuration, the bundle cannot be extracted.
Response: Ensure that the file referred to by path exists on the local file system and run the ftecfg command again.

BFGCL0670E: An error occurred processing the credentials file ''<insert_0>'' in the bundle. Exception: <insert_1>
Severity: 20 : Error
Explanation: An error occurred processing the supplied credentials file contained in the bundle supplied to the ftecfg command. The most likely cause of this is a problem with the format of the credentials file.
Response: Use the supplied exception message to determine the cause of the problem.

BFGCL0671E: An error occurred processing the agent.properties file ''<insert_0>'' in the bundle. Exception: <insert_1>
Severity: 20 : Error
Explanation: An error occurred processing the supplied agent.properties file in the bundle supplied to the ftecfg command.
Response: Use the supplied exception message to determine the cause of the problem.

BFGCL0672E: The resource monitor request could not be accepted because of the following error condition.
Severity: 20 : Error
Explanation: The command submitted a resource monitor create request which was not accepted because of an invalid condition within the agent.
Response: Review the subsequent error message and follow the guidance.

BFGCL0673E: After substitution was carried out the contents of the agent.properties file for agent ''<insert_0>'' are not valid. Configuration for this agent will not be included in the bundle.
Severity: 20 : Error
Explanation: The fteBundleConfiguration command found a substitution.xml file when attempting to create a configuration bundle for the specified agent. The command carried out substitution using all possible variable values to validate the outcome of the agent properties file. A set of substitution variable values give an agent.properties file that is not valid. This is probably because a substitution variable is not expanded in the agent properties because a condition or default does not have a value for that variable.
Response: Refer to previous messages to determine why the contents of the agent.properties post subsitution for the specified agent was not valid. Check the contents of the agent.properties and substitution.xml files for the agent in the bundle directory and fix any problems before attempting to run the fteBundleConfiguration command again.

BFGCL0674E: No substitution variable values were found in the substitution.xml file supplied for agent ''<insert_0>''. Configuration for this agent will not be included in the bundle.
Severity: 20 : Error
Explanation: Processing of the substitution.xml file included in the bundle configuration directory for the specified agent found no variable values. If the agent.properties file for this agent contains substitution variables it could lead to an error when the configuration bundle is deployed, so this agent's configuration is not included in the bundle.
Response: Check the contents of the substitution.xml file included for the specified agent before running the fteBundleConfiguration command again.

BFGCL0675E: An exception occurred while attempting to read the substitution.xml file for agent ''<insert_0>''. Configuration for this agent will not be included in the bundle. Exception: <insert_1>
Severity: 20 : Error
Explanation: The fteBundleConfiguration command attempted to create a configuration bundle, but an exception occurred when attempting to access the substitution.xml file for the specified agent.
Response: Refer to the supplied exception message to determine why the substitution.xml file for the specified agent could not be processed. Fix any problems and run the fteBundleConfiguration command again.

BFGCL0676E: The local absolute path ''<insert_0>'' supplied for property ''<insert_1>'' does not refer to a file located in the configuration directory.
Severity: 20 : Error
Explanation: The value for the supplied property was determined to be an absolute path on the local system but the file that the path refers to was not found in the configuration directory being bundled. The bundle cannot be created because this would cause an error when starting an agent using this configuration, if deployed on 4690.
Response: Ensure the file referenced by the property exists in the configuration directory supplied to the fteBundleConfiguration command.

BFGCL0677E: The local absolute path ''<insert_0>'' supplied in credentials file ''<insert_1>'' does not refer to a file located in the configuration directory.
Severity: 20 : Error
Explanation: The value for the path attribute of a file element in the supplied credentials file was determined to be an absolute path on the local system. However, the file that the path refers to could not be located in the configuration directory being bundled. The bundle cannot be created because this would cause an error when starting an agent using this configuration, if deployed on 4690.
Response: Ensure that the file referenced by the path attribute exists in the configuration directory supplied to the fteBundleConfiguration command.

BFGCL0678E: The bundle has not been created because of an error during the creation of the bundle.
Severity: 20 : Error
Explanation: An error has occurred that has caused the creation of the bundle to be stopped.
Response: Review the previous error and take appropriate action.

BFGCL0679E: After substitution was carried out, the agent.properties file for agent ''<insert_0>'' has the doNotUseTempOutputFile property set to true.
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 and substitution.xml files for the agent in the bundle directory and ensure that the doNotUseTempOutputFile property is always set to false or defaulted to false.

BFGCL0680E: The agent.properties file for agent ''<insert_0>'' has the doNotUseTempOutputFile property set to true.
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 in the bundle directory and ensure that the doNotUseTempOutputFile property is set to false or defaulted to false.

BFGCL0681E: The agent.properties file for agent ''<insert_0>'' has the doNotUseTempOutputFile property set to true.
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.

BFGCL0682E: Unable to create the output directory ''<insert_0>'' that was specified on the <insert_1> commandline argument.
Severity: 20 : Error
Explanation: The command must be able to create and/or write to the given output directory for it to be used.
Response: Specify an alternative output directory, or perform the necessary filesystem steps in order to make the desired directory accessible to the command.

BFGCL0683E: The mandatory commandline argument ''<insert_0> '' has not been specified.
Severity: 20 : Error
Explanation: The type argument is required to be present.
Response: Consult the commandline help to determine the correct format and re-run the modified command.

BFGCL0684E: An I/O exception occurred while trying to resolve the relative path ''<insert_0>'' supplied for property ''<insert_1>'' within the bundle. Exception: <insert_2>
Severity: 20 : Error
Explanation: An exception was caught when the bundle was being searched for the relative path supplied.
Response: Use the supplied exception message to determine the cause of the problem and run the command again.

BFGCL0685E: An I/O exception occurred while trying to resolve the relative path ''<insert_0>'' supplied in credentials file ''<insert_1>'' within the bundle. Exception: <insert_2>
Severity: 20 : Error
Explanation: An exception was caught when the bundle was being searched for the relative path supplied.
Response: Use the supplied exception message to determine the cause of the problem and run the command again.

BFGCL0686E: Both the -a and -c parameter were specified for the uninstall command.
Severity: 20 : Error
Explanation: The uninstall command requires a single parameter of either -a or -c to specify which type of uninstall should be carried out. For descriptions of the -a and -c parameters, see the command line help.
Response: Run the uninstall command again with either the -a or -c parameter specified.

BFGCL0687E: This command does not have write access to the credential directory <insert_0>
Severity: 20 : Error
Explanation: This command is performing a migration and either needs to create or update a file in the credential directory, but the command does not have the necessary file access permission.
Response: Review the -credentialPath parameter and ensure 1) we have specified a directory. 2) the directory path exist. 3) the userid has write permissions to that directory.

BFGCL0688E: One or more trigger content parameters have been specified but the trigger content parameter is missing. Using either -tcr or -tcc requires the -tc parameter to be present.
Severity: 20 : Error
Explanation: One of the trigger content parameters (-tcr or -tcc) has been specified without including the trigger content parameter (-tc). The request is ambiguous and cannot be completed.
Response: Review the fteCreateMonitor request and if the trigger content facility is required, add the -tc parameter to enable the function. Otherwise remove the -tcr or -tcc parameters before trying this command again.

BFGCL0689E: The trigger content capture order group parameter (-tcc) has been specified but the associated regular expression parameter (-tcr) is missing.
Severity: 20 : Error
Explanation: The trigger content facility has been enabled by specifying the capture group order parameter but no supporting pattern (-tcr) has been specified.
Response: Review the fteCreateMonitor command and if trigger content with a redefine of capture is required, add the (-tcr) parameter and pattern. Otherwise remove the -tcc parameter before trying this command again.

BFGCL0690E: The trigger content parameter (-tc) does not support the batch size parameter (-bs).
Severity: 20 : Error
Explanation: The monitor specification has both trigger content enabled and batch size specified. This combination is not supported.
Response: Review the fteCreateMonitor command and either remove the trigger content or the batch size parameter before trying the command again.

BFGCL0691E: The trigger content parameter (-tc) is supported for file-based resource monitoring only.
Severity: 20 : Error
Explanation: The monitor specification is using a non-file base trigger and trigger contents. This combination is not supported.
Response: Review the fteCreateMonitor command and either change the resource triggeror remove the trigger content parameter (-tc) before trying the command again.

BFGCL0692E: The trigger content parameter (-tc) does not support the given file base trigger type. The only file-based triggers supported are "match" or "noSizeChange".
Severity: 20 : Error
Explanation: The monitor specification is using a file based trigger type which does not support trigger content facility.
Response: Review the fteCreateMonitor command and either change the trigger type (-tr) to either "match" or "noSizeChange" or otheriwse remove the trigger content parameter (-tc) before retrying the command.

BFGCL0693E: An attempt to import a monitor template has failed because of <insert_0>
Severity: 20 : Error
Explanation: An attempt to import a existing monitor from a template has failed because that template has configuration errors.
Response: Review the associated error message and correct the template before trying the command again.

BFGCL0694E: The -dtr parameter is not valid unless the transfer is in text mode.
Severity: 20 : Error
Explanation: You are specifying a parameter that depends on another parameter being set to a particular value.
Response: Specify the '-h' command line parameter to see more usage information and modify your command to submit a text transfer.

BFGCL0695E: The -dtr parameter is not valid unless the destination of the transfer is a data set or a partitioned data set.
Severity: 20 : Error
Explanation: You are specifying a parameter that depends on another parameter being set to a particular value.
Response: Specify the '-h' command line parameter to see more usage information and modify your command to submit a transfer that has a destination of a data set or a partitioned data set.

BFGCL0696E: The fteSetupCoordination command could not complete because <insert_0>
Severity: 20 : Error
Explanation: The command has failed to create a coordination configuration due to the specified problem.
Response: Use the information in the message to investigate the problem. Resolve the problem, if possible, and reissue the fteSetupCoordination command. If this does not resolve the problem, contact the IBM support center for assistance.

BFGCL0697E: The logger type of ''<insert_0>'' is not supported on this platform.
Severity: 20 : Error
Explanation: The attempt to create a logger of the given type cannot be completed on this platform because the configuration is not supported.
Response: Review which logger configurations are supported for this platform in the IBM MQ product documentation.

BFGCL0698E: The LIBRARY environment variable has not been specified or is set to a blank value.
Severity: 20 : Error
Explanation: The LIBRARY environment variable must be defined to specify the name of the PDSE LIBRARY that contains the command template scripts. The environment variable is also required to generate commands scripts.
Response: Update the BFGCUSTM PDSE member in the command library to specify the LIBRARY environment variable. For more information, refer to the IBM MQ Information Center.

BFGCL0699W: Line <insert_0> - Unexpected comment continuation line characters ''<insert_1>''. Assuming a comment continuation line.
Severity: 10 : Warning
Explanation: A comment continuation line was expected in the JCL script, at the specified line. The line does not start with characters: '//'. The line will be assumed to be a comment continuation line.
Response: Correct the template JCL script as required. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0700W: Line <insert_0> - Unexpected character ''<insert_1>'' at column 3 on continuation line. Assuming a valid continuation line.
Severity: 10 : Warning
Explanation: A continuation line was expected in the JCL script, at the specified line. The line does not start with characters: '// '. The line will be assumed to be a continuation line.
Response: Correct the template JCL script as required. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0701W: Line <insert_0> - Unexpected character ''<insert_1>'' at column <insert_2> on continuation line. Assuming a valid continuation line with data starting at column 16.
Severity: 10 : Warning
Explanation: A continuation line was expected in the JCL script, at the specified line. The line does not start with characters: '//', followed by 14 space characters. The line will be assumed to be a valid continuation line with data starting at column 16.
Response: Correct the template JCL script as required. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0702E: Line <insert_0> - Unexpected continuation line, which starts with characters ''<insert_1>''. Line will be ignored.
Severity: 20 : Error
Explanation: A continuation line was expected in the JCL script, at the specified line. The line does not start with characters: '// '. The line will be ignored.
Response: Correct the template JCL script as required. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0703E: Line <insert_0> - Unexpected end of file. A continuation line was expected.
Severity: 20 : Error
Explanation: A continuation line was expected in the JCL script, at the specified line. The end of file was reached.
Response: Correct the template JCL script as required. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0704E: Output line <insert_0> - Too long and has been incorrectly split.
Severity: 20 : Error
Explanation: When writing to a JCL script, the identified line was too long and could not be correctly split over to a continuation line.
Response: Examine the JCL script generated from the template, and correct as appropriate. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0705E: BFGSTDIN DD statement line <insert_0> - Syntax error. ''<insert_1>'' is not a valid parameter section specifier.
Severity: 20 : Error
Explanation: The identified parameter section specifier in the BFGSTDIN DD statement has been specified incorrectly, as it does not end with a ']' character.
Response: Correct the BFGSTDIN DD statement in the BFGCUSTM JCL script, and resubmit the job.

BFGCL0706E: BFGSTDIN DD statement line <insert_0> - Syntax error. ''<insert_1>'' is not a valid parameter specification.
Severity: 20 : Error
Explanation: The identified line in the BFGSTDIN DD statement is expected to be in format: =, but the equals ('=') character is missing.
Response: Correct the BFGSTDIN DD statement in the BFGCUSTM JCL script, and resubmit the job.

BFGCL0707E: Unexpected end of file while parsing first line for a parameter specification.
Severity: 20 : Error
Explanation: The script file defines the start of a parameter on the first line. The end of file was encountered before the parameter was complete.
Response: Correct the template script as required. If the template script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0708E: Script file is empty.
Severity: 20 : Error
Explanation: The script file has no content.
Response: Correct the template script as required. If the template script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0709E: Output Line <insert_0> is too long and has been truncated.
Severity: 20 : Error
Explanation: When writing text to a script, the identified line is too long (maximum supported line length is 80 characters).
Response: Examine the script generated from the template, and correct as appropriate. If the template script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0710E: Line <insert_0> - Unexpected blank continuation line. Line will be ignored.
Severity: 20 : Error
Explanation: A continuation line was expected in the JCL script, at the specified line. The line does not start with characters: '// '. The line will be ignored.
Response: Correct the template JCL script as required. If the template JCL script has been supplied with the product then contact the IBM support center for assistance.

BFGCL0711E: The BFG_DATA variable has not be defined, or is set to a blank value.
Severity: 20 : Error
Explanation: The BFG_DATA variable must be set in the BFGSTDIN DD statement to specify the data directory value.
Response: Correct the BFGSTDIN DD statement in the BFGCUSTM JCL script, and resubmit the job.

BFGCL0712E: The coordinationQMgr variable has not been defined, or is set to a blank value.
Severity: 20 : Error
Explanation: The coordinationQMgr variable must be set in the BFGSTDIN DD statement to specify the required coordination queue manager for the configuration data.
Response: Correct the BFGSTDIN DD statement in the BFGCUSTM JCL script, and resubmit the job.

BFGCL0713W: Unable to update configuration properties for coordination queue manager ''<insert_0>''. Reason: <insert_1>
Severity: 10 : Warning
Explanation: The coordination queue manager configuration properties could not be updated for the reason given. It is likely that the coordination queue manager has not been setup yet.
Response: Examine the reason given and take the appropriate action. It may be necessary to run the BFGCFCR JCL script to setup the coordination queue manager.

BFGCL0714W: Unable to update command properties for coordination queue manager ''<insert_0>''. Reason: <insert_1>
Severity: 10 : Warning
Explanation: The command configuration properties could not be updated for the reason given. It is likely that the commands have not been setup yet.
Response: Examine the reason given and take the appropriate action. It may be necessary to run the BFGCMCR JCL script to setup the commands.

BFGCL0715W: Unable to update configuration properties for agent ''<insert_0>'' and coordination queue manager ''<insert_1>''. Reason: <insert_2>
Severity: 10 : Warning
Explanation: The agent configuration properties could not be updated for the reason given. It is likely that the agent has not been created yet.
Response: Examine the reason given and take the appropriate action. It may be necessary to run the BFGAGCR JCL script to create the agent configuration properties.

BFGCL0716W: Unable to update configuration properties for logger ''<insert_0>'' and coordination queue manager ''<insert_1>''. Reason: <insert_2>
Severity: 10 : Warning
Explanation: The logger configuration properties could not be updated for the reason given. It is likely that the logger has not been created yet.
Response: Examine the reason given and take the appropriate action. It may be necessary to run the BFGLGCR JCL script to create the logger configuration properties.

BFGCL0717E: The SERVICE_TYPE variable has not been defined or is invalid.
Severity: 20 : Error
Explanation: The SERVICE_TYPE variable must be set in the BFGSTDIN DD statement, in property section [Variables], to either AGENT or LOGGER.
Response: Correct the BFGSTDIN DD statement in the BFGCUSTM JCL script and submit the job again.

BFGCL0718E: Variable ''<insert_0>'' does not appear to have been set, as its value is: ''<insert_1>''
Severity: 20 : Error
Explanation: The value for the identifier variable starts with '++' and ends with '++' . This implies that the variable value has not been set.
Response: Update the BFGCUSTM JCL script to ensure that all variable values that start with '++', and end with '++', are replaced with the required value.

BFGCL0719I: Variable ''<insert_0>'' has not been set. Line will be removed.
Severity: 0 : Information
Explanation: The value for the identified variable has not been set in the BFGCUSTM JCL script. The template script being customized defines the variable on a line that is to be removed if the variable's value is missing. The line will be removed for the created command script.
Response: Update the BFGCUSTM JCL script to ensure that the required variable is set with an appropriate value, and submit the job again.

BFGCL0720W: Variable ''<insert_0>'' has not been set.
Severity: 10 : Warning
Explanation: The value for the identified variable has not been set in the BFGCUSTM JCL script. The template script being customized defines the variable. The variable will be replaced with a blank value for the created command script.
Response: Update the BFGCUSTM JCL script to ensure that the required variable is set with an appropriate value, and submit the job again.

BFGCL0721E: Unable to access PDS library ''<insert_0>''. Reason: <insert_1>.
Severity: 20 : Error
Explanation: The PDS library identified by the LIBRARY variable value, in the BFGCUSTM JCL script, could not be accessed for the reason given.
Response: Ensure that the LIBRARY variable value, in the BFGCUSTM JCL script, correctly references the PDS library that contains the script and submit the job again.

BFGCL0722E: fteCustom has been invoked with an invalid argument.
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.

BFGCL0723E: The credential path of <insert_0> is referencing a data set but this data set must be a PDSE.
Severity: 20 : Error
Explanation: The -credentialPath parameter supports standard USS and PDSE only. The given value references a data set, but it is not a partitioned data set extended.
Response: Review the -credentialPath parameter and ensure that the parameter refers to a partitioned data set extended.

BFGCL0724E: The credential path of <insert_0> is referencing a PDSE that does not exist.
Severity: 20 : Error
Explanation: The -credentialPath parameter is referencing a PDSE that does not exist. The migrate command can work only with a partitioned data set extended that already exists.
Response: Review the -credentialPath parameter and ensure that the partitioned data set extended is present.

BFGCL0725E: This command does not have write access to the stored credential information in the PDSE <insert_0>.
Severity: 20 : Error
Explanation: The -credentialPath parameter is referencing an existing PDSE, but the command is not able to create a member.
Response: Review the -credentialPath parameter. Ensure that the partitioned data set extended exists, that the command has permission to write to the data set and that the data set is not locked by another process before trying this command.

BFGCL0726E: This command could not be completed because <insert_0>
Severity: 20 : Error
Explanation: The command could not be completed due to the underlying reason given.
Response: Review the underlying error given and correct as necessary before retrying this command.

BFGCL0727E: The credential path of <insert_0> is an invalid PDSE name.
Severity: 20 : Error
Explanation: The -credentialPath parameter is referencing an invalid PDSE name. The migrate command can work only with a valid partitioned data set extended name that already exists.
Response: Review the -credentialPath parameter and ensure that the partitioned data set extended name is correct.

BFGCL0728E: The PDSE <insert_0> is configured for fixed record length which is not supported to hold MFT credentials.
Severity: 20 : Error
Explanation: The PDSE that holds the credentials for MFT cannot be of fixed record length. The PDSE specified is of fixed record length and cannot be used for this operation as a result the command cannot be successfully complete.
Response: Review the PDSE and replace with one that is not of fixed record length and before trying this command again.

BFGCL0729E: The <insert_0> is not a PDSE, and not suitable for storing MQMFT credentials.
Severity: 20 : Error
Explanation: MQMFT only supports data set type PDSE for storage of its credentials. The given data set is not of type partition, and therefore cannot be used to store the MQMFT credentials
Response: Review the given storage location for the credentials and change to a PDSE and retry this command again.

BFGCL0730E: The value <insert_0> supplied for parameter <insert_1> is too long. The maximum length for this property is 256 characters.
Severity: 20 : Error
Explanation: The given value is too long The maximum length for this property is 256 characters.
Response: Review the given name and creduce it to 256 characters.

BFGCL0731W: The request to cancel the transfer failed because the transfer has already completed sending the data.
Severity: 10 : Warning
Explanation: The transfer was not cancelled because the transfer had already completed sending the data.
Response: No action is required.

BFGCL0732E: An mquserid parameter is required when supplying an mqpassword parameter.
Severity: 20 : Error
Explanation: The command has been supplied with a password parameter but no associated user ID has been supplied.
Response: Review the command and either remove the password parameter or supply an mquserid.

BFGCL0733E: An attempt to collect an IBM MQ password has failed because the command is not running in an interactive mode.
Severity: 20 : Error
Explanation: The command is being run in an environment where the user cannot be asked for a password to connect to the queue manager. As a result the command could not successfully be completed.
Response: Review the environment that the command is being run in and allow interactive mode, or supply the credentials using a different method.

BFGCL0734E: An attempt to connect to queue manager <insert_0> has been rejected because of invalid authentication details. If this queue manager has authentication enabled, user ID and password details must be supplied.
Severity: 20 : Error
Explanation: The attempted connection to the queue manager has failed with an MQRC 2035. This indicates the connection has been rejected because of invalid authentication details and the command cannot be completed.
Response: Check the required authentication for connection to this queue manager before attempting this command again. Refer to the IBM MQ product documentation for more information on this subject.

BFGCL0735E: The request to add a credential value cannot be performed as the ''-<insert_0>'' required parameter has not been given.
Severity: 20 : Error
Explanation: This command can optional create or append a new credential details to a MQMFT Credential file. The present of the -credentialsFile parameter indicate a value is to be added but one or more other required parameters are missing.
Response: Decide whether to adding a credential is desired and supply the required missing parameter or remove the -credentialsFile parameter before trying the command again.

BFGCL0736E: The two given password are either invalid or do not match.
Severity: 20 : Error
Explanation: The user being interactively asked to assign a password for a MQ credential. The password is asked for twice and they do not match indicating either validate password has not been given or the two passwords do not match.
Response: Re-enter the two matching passwords.

BFGCL0737W: Diagnostics were requested, but agent ''<insert_0>'' is running on an older version of the product that does not support the request for diagnostics.
Severity: 10 : Warning
Explanation: Agent diagnostic information is supported only for agents running at MQMFT V7.5, or higher.
Response: No action is required.

BFGCL0738E: No user ID specified for the mquserid parameter.
Severity: 20 : Error
Explanation: The command has been supplied with a mquserid parameter but no associated user ID has been supplied.
Response: Review the command and either remove the mquserid parameter or supply an mquserid.

BFGCL0739W: The PDS library name option (-l) was specified, but this is only supported on z/OS. The option will be ignored.
Severity: 10 : Warning
Explanation: The -l option was specified, but it is not supported for the current platform.
Response: No action is required.

BFGCL0740E: The specified coordination queue manager name ''<insert_1>'' in the BFGCFCR JCL script was not the expected coordination queue manager name of ''<insert_0>''.
Severity: 20 : Error
Explanation: The coordination queue manager configured when the BFGCUSTM JCL script was run is not the same as the coordination queue manager specified in the BFGCFCR JCL script. This means that the BFGCFCR JCL script has been updated in an invalid way because the coordination queue manager name should only be changed in the BFGCUSTM JCL script.
Response: Update the coordinationQMgrName property in the BFGCUSTM JCL script to the required name and submit the BFGCUSTM job again. Finally, submit the BFGCFCR job again.

BFGCL0741W: The -jn option is not supported by the fteCreateMonitor command, and will be ignored.
Severity: 10 : Warning
Explanation: The -jn option given as an argument to the fteCreateMonitor is not supported, and will be ignored. The job reference only relates to the transfer generated by the monitor.
Response: Ensure the relevant job reference has been given in the transfer template as specified in the -mt argument. Refer to the fteCreateTransfer help for more information.

BFGCL0742E: The javacore request was successfully sent to logger ''<insert_0>'' but the system was unable to determine the javacore output file name. Reason: <insert_1>
Severity: 20 : Error
Explanation: The javacore request was successfully sent to the specified logger. The logger could not determine the file name of the output javacore file. However, the javacore file name or an error message should have been output to the console. For a background logger, the console output is directed to file stderr.log, which is located in the logger's logs directory.
Response: No action is required.

BFGCL0743I: The javacore request was successfully sent to logger ''<insert_0>'' but the system was unable to determine the javacore output file name.
Severity: 0 : Information
Explanation: The javacore request was successfully sent to the specified logger. The logger could not determine the file name of the output javacore file. However, the javacore file name should have been output to the console. For a background agent, the console output is directed to file stderr.log, which is located in the logger's logs directory.
Response: No action is required.

BFGCL0744E: The javacore request was successfully sent to agent ''<insert_0>'' but the system was unable to determine the javacore output file name. Reason: <insert_1>
Severity: 20 : Error
Explanation: The javacore request was successfully sent to the specified agent. The agent could not determine the file name of the output javacore file. However, the javacore file name or an error message should have been output to the console. For a background agent, the console output is directed to file stderr.log, which is located in the agent's logs directory.
Response: No action is required.

BFGCL0745E: Creation of Web agent is not supported.
Severity: 20 : Error
Explanation: The creation of Web agent cannot be performed. The Web agent and Web Gateway components are not supported from IBM MQ Managed File Transfer v9.
Response: No action is required.

BFGCL0746E: The command was run without a logAgent parameter. Run the command with the -h parameter to see usage information.
Severity: 20 : Error
Explanation: The log request was not processed because the command was run without a logAgent parameter. Run the command with the -h parameter to see usage information.
Response: Refer to the command line help or to the product documentation to determine the correct command line arguments.

BFGCL0747E: The log specification ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: The value passed to the command is not valid.
Response: Refer to the command line help or to the product documentation to determine the correct syntax for the command. Reissue the command supplying a valid trace specification.

BFGCL0748I: The log request was successfully sent to agent ''<insert_0>''.
Severity: 0 : Information
Explanation: The log request was successfully sent to the specified agent. The agent will receive the request and update its log specification based on that request. Any log information will be generated in the directory that the agent outputs its logs to.
Response: No action is required. We can confirm that the agent has processed the request by looking for a corresponding entry in the agent's log file.

BFGCL0749E: Migration of a Web agent ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The migration of a Web agent cannot be performed. The Web agent and Web Gateway components are not supported from IBM MQ Managed File Transfer v9.
Response: No action required.

BFGCL0752E: The fteCleanAgent command requires additional parameters to be specified, run fteCleanAgent -h for more details.
Severity: 20 : Error
Explanation: Insufficient parameters were specified to run fteCleanAgent.
Response: To allow the command to run specifying only the AgentName parameter, set the failCleanAgentWithNoArguments property to false in the command.properties configuration file.

BFGCL0753E: A productId must be specified when setting the productId.
Severity: 20 : Error
Explanation: We cannot set the productId without specifying the value to which you want to set it.
Response: Specify the '-h' parameter to display usage information about the command.

BFGCL0754I: The specified productId ''<insert_0>'' is already being used. No changes have been made.
Severity: 0 : Information
Explanation: The specified productId is already being used. No changes have been made.
Response: No action required.

BFGCL0755I: The specified productId ''<insert_0>'' has been set.
Severity: 0 : Information
Explanation: The specified productId has been set.
Response: No action required.

BFGCL0757E: The command is only valid on z/OS.
Severity: 20 : Error
Explanation: An attempt has been made to run a command which is only valid on z/OS on a different platform.
Response: Consult the product documentation.

BFGCL0761E: The Windows service ''<insert_0>'' could not be modified. No changes have been made.
Severity: 20 : Error
Explanation: The command could not delete the original Windows service definition and so could not recreate it with the updated configuration options.
Response: Review the error message describing why the original Windows service could not be deleted it. Correct the error condition and reissue the command.

BFGCL0762E: An error occurred modifying the Windows service ''<insert_0>''. The Windows service definition has been deleted.
Severity: 20 : Error
Explanation: The original Windows service definition was deleted but an exception was thrown creating the replacement with the new configuration options. The IBM MQ Managed File Transfer process being modified will not run as a Windows service if started.
Response: Review the error message describing why the replacement Windows service could not be created. Correct the error condition and reissue the command to create the Windows service definition.

BFGCL0763E: An exception occurred processing a previous error thrown while modifying the Windows service ''<insert_0>''. The exception that occurred accompanies this message. The configuration of the IBM MQ Managed File Transfer process may now be inconsistent with the state of the Windows service definition, should it exist.
Severity: 20 : Error
Explanation: The original Windows service definition was deleted but an exception was thrown creating the replacement with the new configuration options. The properties for the IBM MQ Managed File Transfer process being modified could not be updated to reflect the new state.
Response: Review the Windows service definitions using the Windows operating system tooling and ensure that if one is not defined for the process being modified, the Windows service properties (windowsService and windowsServiceVersion) are not specified in the properties configuration file for the process.

BFGCL0764I: The agent has been modified to run as a Windows service. The name of the Windows service associated with the agent is ''<insert_0>''. The arguments supplied to the fteModifyAgent command to create the Windows service were ''<insert_1>''.
Severity: 0 : Information
Explanation: An IBM MQ Managed File Transfer administrator issued the fteModifyAgent command that resulted in the agent being configured to run as a Windows service.
Response: No action required. This message is informational.

BFGCL0765I: The agent has been modified to no longer run as a Windows service. The name of the Windows service definition that was previously associated with the agent and has now deleted was ''<insert_0>''. The arguments supplied to the fteModifyAgent command to delete the Windows service were ''<insert_1>''.
Severity: 0 : Information
Explanation: An IBM MQ Managed File Transfer administrator issued the fteModifyAgent command that resulted in the Windows service definition, which was associated with the agent, being deleted.
Response: No action required. This message is informational.

BFGCL0766I: The agent''s Windows service definition has been modified. The name of the Windows service associated with the agent is ''<insert_0>''. The arguments supplied to the fteModifyAgent command to modify the Windows service were ''<insert_1>''.
Severity: 0 : Information
Explanation: An IBM MQ Managed File Transfer administrator issued the fteModifyAgent command that resulted in a modification of the Windows service definition associated with the agent.
Response: No action required. This message is informational.

BFGCL0767I: The logger has been modified to run as a Windows service. The name of the Windows service associated with the logger is ''<insert_0>''. The arguments supplied to the fteModifyLogger command to create the Windows service were ''<insert_1>''.
Severity: 0 : Information
Explanation: An IBM MQ Managed File Transfer administrator issued the fteModifyLogger command that resulted in the logger being configured to run as a Windows service.
Response: No action required. This message is informational.

BFGCL0768I: The logger has been modified to no longer run as a Windows service. The name of the Windows service definition that was previously associated with the logger and has now deleted was ''<insert_0>''. The arguments supplied to the fteModifyLogger command to delete the Windows service were ''<insert_1>''.
Severity: 0 : Information
Explanation: An IBM MQ Managed File Transfer administrator issued the fteModifyLogger command that resulted in the Windows service definition, which was associated with the agent, being deleted.
Response: No action required. This message is informational.

BFGCL0769I: The logger''s Windows service definition has been modified. The name of the Windows service associated with the logger is ''<insert_0>''. The arguments supplied to the fteModifyLogger command to modify the Windows service were ''<insert_1>''.
Severity: 0 : Information
Explanation: An IBM MQ Managed File Transfer administrator issued the fteModifyLogger command that resulted in a modification of the Windows service definition associated with the logger.
Response: No action required. This message is informational.

BFGCL0770W: The fteModifyAgent command was unable to access the eventlog file associated with the IBM MQ Managed File Transfer agent due to the exception ''<insert_0>''. The agent''s event log will not record the outcome of this command.
Severity: 10 : Warning
Explanation: An exception prevented the fteModifyAgent command from updating the agent''s event log with details of the modification performed by the command.
Response: No action required. This message is informational.

BFGCL0771W: The fteModifyLogger command was unable to access the eventlog file associated with the IBM MQ Managed File Transfer logger due to the exception ''<insert_0>''. The logger''s event log will not record the outcome of this command.
Severity: 10 : Warning
Explanation: An exception prevented the fteModifyLogger command from updating the logger''s event log with details of the modification performed by the command.
Response: No action required. This message is informational.

BFGCL0772I: The fteModifyAgent command has completed with reason code ''<insert_0>''.
Severity: 0 : Information
Explanation: A return code of zero indicates the fteModifyAgent command successfully completed. A non-zero return code indicates an error occurred.
Response: If the return code from the fteModifyAgent command was non-zero, review the accompanying error messages to determine why, correct the error condition and reissue the command.

BFGCL0773I: The fteModifyLogger command has completed with reason code ''<insert_0>''.
Severity: 0 : Information
Explanation: A return code of zero indicates the fteModifyLogger command successfully completed. A non-zero return code indicates an error occurred.
Response: If the return code from the fteModifyLogger command was non-zero, review the accompanying error messages to determine why, correct the error condition and reissue the command.

BFGCL9999E: <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.