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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity
20 : Error
Explanation
The command could not complete because WebSphere MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered.
Response
Consult the WebSphere 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 WebSphere MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity
20 : Error
Explanation
The command could not complete because WebSphere MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered.
Response
Consult the WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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
You 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
You 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
You 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 you 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 WebSphere MQ. The reason code was: ''<insert_0>''.
Severity
20 : Error
Explanation
There was a problem connecting to WebSphere MQ described by the specified reason code.
Response
Check the MQRC reason codes and take appropriate action.

BFGCL0062E
There was a problem connecting to WebSphere MQ. The reason code was: ''<insert_0>''.
Severity
20 : Error
Explanation
There was a problem connecting to WebSphere 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.

BFGCL0067I
If you have not already done so, direct the following MQSC definitions for your coordination queue manager ''<insert_0>'' to an MQSC session.
Severity
0 : Information
Explanation
If you have not already done so, direct the following MQSC definitions for your coordination queue manager to an appropriate MQSC session.
Response
No action required.

BFGCL0068I
A file has been created that contains the MQSC definitions for your coordination queue manager. The file can be found here: ''<insert_0>''.
Severity
0 : Information
Explanation
A file has been created that contains the MQSC definitions for your coordination queue manager.
Response
No action required.

BFGCL0069I
A file has been created containing the MQSC definitions to create your agent. The file can be found here: ''<insert_0>''.
Severity
0 : Information
Explanation
A file has been created containing the MQSC definitions to create your agent.
Response
No action required.

BFGCL0070I
A file has been created containing the MQSC definitions to delete your agent. The file can be found here: ''<insert_0>''.
Severity
0 : Information
Explanation
A file has been created containing the MQSC definitions to delete your agent.
Response
No action required.

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

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 WebSphere MQ File Transfer Edition 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 WebSphere MQ File Transfer Edition 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 you have the required permissions and retry.
Response
The command failed to create the file. Check you 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 you have the required permissions and retry.
Response
The command failed to create the file. Check you 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 you have the required permissions and retry.
Severity
20 : Error
Explanation
The command was unable to create the file. Check that you have the required permissions and retry.
Response
The command was unable to create the file. Check that you have the required permissions and retry.

BFGCL0082E
The command was unable to create the file: ''<insert_0>''. Check that you have the required permissions and retry.
Severity
20 : Error
Explanation
The command was unable to create the file. Check that you have the required permissions and retry.
Response
The command was unable to create the file. Check that you 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 you have the required permissions and retry.
Severity
20 : Error
Explanation
The command failed to delete the directory.
Response
Check that you 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. You 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
You 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 WebSphere MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity
20 : Error
Explanation
The command could not complete because WebSphere MQ detected a problem. The completion code and reason code specified in the message correspond to the type of problem encountered.
Response
Consult the WebSphere 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 FTE_CONFIG environment variable is set to ''<insert_0>'' before issuing further commands.
Severity
0 : Information
Explanation
The FTE_CONFIG 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 FTE_CONFIG environment variable to the specified value. For more information, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCL0126I
You can optionally delete the WebSphere MQ objects used by this agent from queue manager <insert_0>.
Severity
0 : Information
Explanation
The WebSphere MQ objects used by the agent are no longer required. You can delete the object definitions from the specified queue manager.
Response
Optionally, delete the WebSphere 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/.

BFGCL0127I
Ensure that the coordination queue manager (<insert_0>) has the required WebSphere MQ objects defined.
Severity
0 : Information
Explanation
The coordination queue manager must have a specific set of WebSphere MQ objects defined. These objects must be defined before you use the specified queue manager as a coordination queue manager for the first time.
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. If the specified queue manager does not have the required objects defined, define these objects for the queue manager.

BFGCL0128I
The agent requires a number of WebSphere 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 WebSphere MQ objects to be defined to the specified queue manager. These definitions are required for the agent process to function correctly. Ensure that you have defined the appropriate WebSphere 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 you have defined these objects, start the agent.

BFGCL0129E
This command requires the FTE_CONFIG environment variable to be set.
Severity
20 : Error
Explanation
The FTE_CONFIG environment variable must be set for this command to function correctly. The command cannot continue and will end without performing any actions.
Response
Set the FTE_CONFIG environment variable. Refer to the product documentation to determine a valid value for the parameter. Reissue the command.

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 WebSphere MQ completion code was <insert_0>, and the reason code was <insert_1>.
Severity
20 : Error
Explanation
The command could not complete because WebSphere MQ detected a problem. The completion code and reason code specified in the message indicate the type of problem encountered.
Response
Consult the WebSphere 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 transfer result 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
Monitoring 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 property ''<insert_0>'' or one of the destination file specification properties:(''<insert_1>'') could be detected. The unexpected parameters were: ''<insert_2>''.
Severity
20 : Error
Explanation
The command does not understand the additional parameters and 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.

BFGCL0181I
The file transfer request has failed because the destination queue manager is unreachable.
Severity
0 : Information
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 once all current transfers have completed.
Severity
0 : Information
Explanation
The agent has received the stop request and will shutdown once 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 database logger command queue <insert_0> on <insert_1>.
Severity
0 : Information
Explanation
The command has successfully issued a stop request to the database logger. When the database logger receives this request, the logger will stop.
Response
No action is required.

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

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

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

BFGCL0241E
The database logger has failed to process the stop request successfully.
Severity
20 : Error
Explanation
The database logger received the stop request but failed to act on it.
Response
Review the database logger log file and check for FFDCs or other problems. If necessary, manually kill the database 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 FTE 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 database logger due to: <insert_0>
Severity
20 : Error
Explanation
The command has failed to start the specified database 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 database logger requires that the command is able to open this file. The database 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 WebSphere 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 WebSphere 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 WebSphere 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 WebSphere 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
You 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
You 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
You 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
You 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
You 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
You 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 FTE 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 FTE agent.
Severity
20 : Error
Explanation
The command was successfully placed on an FTE 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. You 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, you can remove these queues manually. See the product documentation for a list of queues used by each agent.
Response
No action is required. You 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 you 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 WMQFTE agent.
Response
Resubmit the request to an agent that supports resource monitors, such as a standard WMQFTE agent.

BFGCL0286W
By configuring a connection to a queue manager on the same machine, you might have configured this agent in a manner not permitted by product licensing terms. (<insert_0>)
Severity
10 : Warning
Explanation
This agent is licensed as a WebSphere MQ File Transfer Edition client. This agent may not be used with a WebSphere MQ queue manager running on the same system.
Response
Determine whether the agent has been configured to connect to a WebSphere MQ queue manager on the same system. If the agent has been configured to connect to a queue manager on the same system, either obtain an appropriate Server license for the agent or reconfigure the agent to use a queue manager running on a different system.

BFGCL0287I
The request to start the database logger on this machine has been submitted.
Severity
0 : Information
Explanation
The request to start the database 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 you have permission to write the sample file into the agents directory.

BFGCL0291E
WebSphere MQ File Transfer Edition does not support communication between bridge agents on a z/OS platform and an SFTP protocol file server.
Severity
20 : Error
Explanation
An attempt was made to start a bridge agent on a z/OS platform, which has been configured to communicate with an SFTP protocol file server. This configuration is not supported.
Response
Review the bridge configuration you require and where possible use an FTP protocol file server.

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 FTE data directory. Once 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 traceAgent 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 traceAgent value.

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 their was an error that may have caused it to terminate.
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.

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 you 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 WebSphere MQ detected a problem. The reason code specified in the message corresponds to the type of problem encountered.
Response
Consult the WebSphere 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 a WebSphere MQ queue.

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

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

BFGCL0350I
The Windows service ''<insert_0>'' has been stopped for the database logger with properties set ''<insert_1>''
Severity
0 : Information
Explanation
The command has successfully stopped the specified database 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.

BFGCL0356E
The database logger has been requested to run as a 32-bit process, however it has been started in a 64-bit JVM runtime.
Severity
20 : Error
Explanation
The database logger has been requested to run as a 32-bit process, however the JVM runtime used is a 64-bit process. The database logger will now end. This problem occurs when the database logger is instructed to run as a 32-bit process either using the -b command line parameter or the FTE_BITMODE environment variable, however the JVM selected by the FTE_JAVA_HOME environment variable is a 64-bit JVM.
Response
Determine whether the database logger should run as a 32-bit or a 64-bit process. If the database logger should run as a 32-bit process then change the JVM selected by the FTE_JAVA_HOME environment variable to select a 32-bit JVM, or unset the FTE_JAVA_HOME environment variable. If the database logger should run as a 64-bit process then either specify a value of 64 for the -b command line parameter or set the FTE_BITMODE environment variable to a value of 64.

BFGCL0357E
The database logger has been requested to run as a 64-bit process, however it has been started in a 32-bit JVM runtime.
Severity
20 : Error
Explanation
The database logger has been requested to run as a 64-bit process, however the JVM runtime used is a 32-bit process. The database logger will now end. This problem occurs when the database logger is instructed to run as a 64-bit process either using the -b command line parameter or the FTE_BITMODE environment variable, however the JVM selected by the FTE_JAVA_HOME environment variable is a 32-bit JVM.
Response
Determine whether the database logger should run as a 32-bit or a 64-bit process. If the database logger should run as a 64-bit process then change the JVM selected by the FTE_JAVA_HOME environment variable to select a 64-bit JVM, or unset the FTE_JAVA_HOME environment variable. If the database logger should run as a 32-bit process then either specify a value of 32 for the -b command line parameter or set the FTE_BITMODE environment variable to a value of 32.

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
Monitoring 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.

BFGCL0360W
Ignoring invalid FTE_BITMODE environment variable value: <insert_0>
Severity
10 : Warning
Explanation
The FTE_BITMODE environment variable is set to the specified value, which is not valid. Valid values are '32' and '64'. The FTE_BITMODE environment variable will be ignored. The database logger will use the -b (-bitMode) command-line parameter to determine whether to run as a 32-bit or 64-bit process. If the -b parameter is not specified, the default behaviour is to run as a 32-bit process.
Response
Correct the value of the FTE_BITMODE environment variable so that it is either '32' or '64'.

BFGCL0361W
Ignoring FTE_BITMODE environment variable value of 32 because the -b command-line parameter specifies that the database logger should run as a 64-bit process.
Severity
10 : Warning
Explanation
The FTE_BITMODE environment variable has been set to a value of 32, indicating that the database logger should run as a 32-bit process. However the -b (-bitMode) command-line parameter specifies that the database logger is to run as a 64-bit process. The -b parameter takes precedence over the FTE_BITMODE environment variable.
Response
Confirm whether the database logger should run as a 64-bit process. If the database logger should run as a 64-bit process then no action is required, however you might want to update the value of the FTE_BITMODE environment variable to prevent this message being displayed in the future. If the database logger should run as a 32-bit process then stop the database logger and restart it without specifying the -b or -bitMode command-line parameter.

BFGCL0362W
Ignoring FTE_BITMODE environment variable value of 64 because the -b command-line parameter specifies that the database logger should run as a 32-bit process.
Severity
10 : Warning
Explanation
The FTE_BITMODE environment variable has been set to a value of 64, indicating that the database logger should run as a 64-bit process. However the -b (-bitMode) command-line parameter specifies that the database logger is to run as a 32-bit process. The -b parameter takes precedence over the FTE_BITMODE environment variable.
Response
Confirm whether the database logger should run as a 32-bit process. If the database logger should run as a 32-bit process then no action is required, however you might want to update the value of the FTE_BITMODE environment variable to prevent this message being displayed in the future. If the database logger should run as a 64-bit process then stop the database logger and restart it without specifying the -b or -bitMode command-line parameter.

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 database logger with properties set ''<insert_1>''
Severity
0 : Information
Explanation
No action was taken as the database 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 you 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 you 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 WMQFTE 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
You 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
You 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
You 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
You 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
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.

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 you 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 you have specified the -srdb parameter.
Severity
20 : Error
Explanation
The source delimiter position parameter is applicable only if you 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.

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.

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.