BFGAP0001 - BFGAP9999

BFGAP0001W: 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 host name immediately followed by a port number enclosed in parentheses, 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 trying the command again.

BFGAP0002W: 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 value. 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 trying the command again.

BFGAP0003W: 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 trying the command again.

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

BFGAP0006E: The properties file <insert_0> could not be read due to: <insert_1>.
Severity: 20 : Error
Explanation: The specified properties file could not be read for the specified reason. As a result, the current command could not be completed.
Response: Use the information present in the message to identify why the specified properties file could not be read. If possible correct the problem, otherwise contact the IBM support center for further assistance.

BFGAP0007E: An internal error has occurred. The ''<insert_0>'' properties file does not contain a ''<insert_1>'' property.
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.

BFGAP0008E: An internal error has occurred. The product data directory value ''<insert_0>'' could not be resolved due to: <insert_1>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

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

BFGAP0010W: The properties file <insert_0> could not be read due to: <insert_1>.
Severity: 10 : Warning
Explanation: The specified properties file could not be read for the specified reason. As a result, the current command could not be completed.
Response: Use the information present in the message to identify why the specified properties file could not be read. If possible correct the problem, otherwise contact the IBM support center for further assistance.

BFGAP0011E: An internal error has occurred. The ''<insert_0>'' properties file does not contain a ''<insert_1>'' property.
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.

BFGAP0012E: An internal error has occurred. The ''<insert_0>'' directory does not exist in <insert_1>, or does not contain a required properties file.
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.

BFGAP0013E: An internal error has occurred. The ''<insert_0>'' properties file does not exist in <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.

BFGAP0014E: The configuration options directory ''<insert_0>'' does not exist, or does not contain a required properties file.
Severity: 20 : Error
Explanation: The specified configuration options directory does not exist. The command cannot be completed.
Response: Verify that the configuration options directory specified is correct. Reissue the command with a corrected configuration options parameter. If this does not resolve the problem, contact the IBM Support Center for further assistance.

BFGAP0015E: An internal error has occurred. The properties file ''<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.

BFGAP0016E: The properties file <insert_0> could not be read due to: <insert_1>.
Severity: 20 : Error
Explanation: The specified properties file could not be read for the specified reason. As a result, the current command could not be completed.
Response: Use the information present in the message to identify why the specified properties file could not be read. If possible correct the problem, otherwise contact the IBM support center for further assistance.

BFGAP0017E: An internal error has occurred. Unable to complete the command because the agent 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.

BFGAP0018E: Unable to complete the command because the agent directory ''<insert_0>'' does not exist.
Severity: 20 : Error
Explanation: The agent directory must exist for a validly configured agent.
Response: Check that the agent name has been specified correctly on the command and that the agent exists. Run the command again with a valid agent name. If this information is not sufficient to resolve the problem, contact the IBM Support Center.

BFGAP0019E: An 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.

BFGAP0020E: A messaging problem prevented the command from completing successfully. The reason was: <insert_0>. A connection could not be established to the default queue manager.
Severity: 20 : Error
Explanation: The command could not complete because the JMS subsystem for connecting to IBM MQ detected a problem. The reason 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 default queue manager.
Response: Consult the IBM MQ product documentation to interpret the reason. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM Support Center.

BFGAP0021E: A messaging problem prevented the command from completing successfully. The reason was: <insert_0>. A connection could not be established to queue manager <insert_1>.
Severity: 20 : Error
Explanation: The command could not complete because the JMS subsystem for connecting to IBM MQ detected a problem. The reason 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: Refer to the IBM MQ product documentation to interpret the reason. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM Support Center.

BFGAP0022E: A messaging problem prevented the command from completing successfully. The reason was: <insert_0>. A connection could not be established to the default queue manager on host ''<insert_1>'' using port <insert_2> and channel <insert_3>.
Severity: 20 : Error
Explanation: The command could not complete because the JMS subsystem for connecting to IBM MQ detected a problem. The reason 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 default queue manager, using the specified connection information.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM Support Center.

BFGAP0023E: A messaging problem prevented the command from completing successfully. The JMS error is: <insert_0>. A connection could not be established to queue manager <insert_1>, on host ''<insert_2>'' using port <insert_3> and channel <insert_4>.
Severity: 20 : Error
Explanation: The command could not complete because the JMS subsystem for connecting to IBM MQ detected a problem. The reason 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, using the specified connection information.
Response: Consult the IBM MQ product documentation to interpret the information. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM Support Center.

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

BFGAP0025W: The value supplied for the ''<insert_0>'' property in the ''<insert_1>'' properties file is outside the range of valid numerical values for this property. The range is <insert_2> - <insert_3>.
Severity: 10 : Warning
Explanation: The value supplied for the property in the specified properties file is outside the specified range of acceptable values. The value will be ignored.
Response: Refer to the product documentation to determine a vaild value for the parameter. Update the specified properties file to correct the value of the specified property.

BFGAP0026W: The value supplied for the ''<insert_0>'' property in the ''<insert_1>'' properties file is not a valid numerical value.
Severity: 10 : Warning
Explanation: The value supplied for the specified property in the specified properties file is not a valid numerical value. As a result, the property will be ignored.
Response: Refer to the product documentation to determine a valid value for the parameter. Update the specified properties file to correct the value of the specified property.

BFGAP0027W: The value supplied for the ''<insert_0>'' property in the ''<insert_1>'' property file is too long. The maximum length for this property value is 48 characters.
Severity: 10 : Warning
Explanation: The value supplied for the specified property in the specified properties file is longer than 48 characters. The maximum length permitted for values of this property is 48 characters. As a result, the property will be ignored.
Response: Correct the value of the specified property in the specified properties file.

BFGAP0028W: The value supplied for the ''<insert_0>'' property in the ''<insert_1>'' property file contains characters that are not permitted in an IBM MQ object name.
Severity: 10 : Warning
Explanation: The value supplied for the specified property in the specified properties file contains characters that are not permitted in an IBM MQ object name. The property will be ignored.
Response: Refer to the IBM MQ product documentation to determine the rules for naming IBM MQ objects. Correct the value of the specified property in the specified properties file.

BFGAP0029E: The value supplied for the ''<insert_0>'' property in the ''<insert_1>'' property file is in a format that has not been recognized.
Severity: 20 : Error
Explanation: The value supplied for the specified property is in a format that has not been recognized. As a result, the command cannot be completed.
Response: Reissue the command with a value for the specified property that conforms to the following format: yyyy-MM-ddThh:mm or hh:mm.

BFGAP0030E: The value ''<insert_0>'' is not valid for argument ''<insert_1>''.
Severity: 20 : Error
Explanation: The value given in the command argument is not a valid option for the argument.
Response: Review the possible options from the usage information, then correct and resubmit the command.

BFGAP0031E: The value ''<insert_0>'' is not valid for argument ''<insert_1>''.
Severity: 20 : Error
Explanation: The value given in the command argument is not a valid option for the argument.
Response: Review the possible options from the usage information, then correct and resubmit the command.

BFGAP0032E: The value ''<insert_0>'' is not a valid locale for argument ''<insert_1>''.
Severity: 20 : Error
Explanation: The value given in the command argument is not a valid locale option for the argument.
Response: Review the possible options from the usage information, then correct and resubmit the command.

BFGAP0033E: The value ''<insert_0>'' is not a valid time zone for argument ''<insert_1>''.
Severity: 20 : Error
Explanation: The value given in the command argument is not a valid time zone option for the argument.
Response: Review the possible options from the usage information, then correct and resubmit the command.

BFGAP0034E: The value ''<insert_0>'' is not a valid file encoding for argument ''<insert_1>''.
Severity: 20 : Error
Explanation: The value given in the command argument is not a valid file encoding option for the argument.
Response: Review the possible options from the usage information, then correct and resubmit the command.

BFGAP0035E: The value ''<insert_0>'' is not a valid port reference for argument ''<insert_1>''.
Severity: 20 : Error
Explanation: The given value is not a valid port reference. The port must be an integer in the range of 0 to 65534.
Response: Review the possible options from the usage information, then correct the argument and resubmit the command.

BFGAP0036E: The configuration options directory name is blank.
Severity: 20 : Error
Explanation: The specified configuration options directory must be a valid, non-blank name. The command cannot be completed.
Response: Correct the configuration options to specify a valid directory. Reissue the command with a corrected configuration options parameter. If this does not resolve the problem, contact the IBM Support Center for further assistance.

BFGAP0037E: The specified agent name is blank.
Severity: 20 : Error
Explanation: The specified agent name must be a valid, non-blank name. The command cannot be completed.
Response: Correct the agent name to specify a valid name. Reissue the command with a corrected agent name parameter. If this does not resolve the problem, contact the IBM Support Center for further assistance.

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

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

BFGAP0040E: The SSL cipher specification <insert_0> is not supported.
Severity: 20 : Error
Explanation: A SSL cipher specification that was read from the MQMFT connection properties is not supported.
Response: Update the MQMFT connection properties to specify a valid SSL cipher specification, or specify a valid SSL cipher suite.

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

BFGAP0042E: An attempt to create a reply queue to receive the command result has failed. Exception is ''<insert_0>''.
Severity: 20 : Error
Explanation: The command needs to wait for a reply but could not create a reply queue to receive it, because the JMQI subsystem for connecting to IBM MQ detected a problem.
Response: Consult the IBM MQ product documentation to interpret the completion and reason codes. Use this information to correct the problem, if possible. If this information is not sufficient to resolve the problem, contact the IBM Support Center.

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

BFGAP0044E: An internal error has occurred. There was an attempt to wait on a reply queue before initialization had occurred, which caused the command to fail.
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.

BFGAP0045E: Monitoring of the request has stopped because the associated queue manager is no longer running.
Severity: 20 : Error
Explanation: The command is monitoring for a reply message on its queue manager. This queue manager has been stopped and monitoring can no longer continue. The original 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 performed.
Response: Investigate why the queue manager has been stopped.

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

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

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

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

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

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

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

BFGAP0053E: An internal error has occurred. No connection for command to queue: <insert_0> on queue manager: <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.

BFGAP0055E: CCSID: <insert_0> is unsupported.
Severity: 20 : Error
Explanation: The CCSID specified for publishing a message to the coordination queue manager is unsupported.
Response: Correct the MQMFT Web Gateway configuration to specify a valid CCSID. Consult the IBM MQ product documentation for more information.

BFGAP0056E: The properties file <insert_0> could not be written due to: <insert_1>.
Severity: 20 : Error
Explanation: The specified properties file could not be written for the specified reason. As a result, the current command could not be completed.
Response: Use the information present in the message to identify why the specified properties file could not be written. If possible correct the problem, otherwise contact the IBM Support Center for further assistance.

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

BFGAP0058W: The local communications address ''<insert_0>'' given for property ''<insert_1>'' is not valid and has been ignored.
Severity: 10 : Warning
Explanation: The specified local communications address is not valid. The format of this address is: [ip-addr][(low-port[,high-port])], where square brackets ([ ]) denote optional information, for example: HOST.IBM.COM(5000,5999). The value will be ignored if the address is incorrectly specified.
Response: Modify the appropriate properties file so that the value assigned to the given property is a valid local communications address before retrying the command.

BFGAP0059E: An internal error has occurred. The product logging directory ''<insert_0>'' does not exist or cannot be read.
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.

BFGAP0060E: The logging options directory name is blank.
Severity: 20 : Error
Explanation: The specified configuration options directory must be a valid, non-blank name. The command cannot be completed.
Response: Correct the configuration options to specify a valid directory. Reissue the command with a corrected configuration options parameter. If this does not resolve the problem, contact the IBM Support Center for further assistance.

BFGAP0061E: The configuration logging directory ''<insert_0>'' does not exist.
Severity: 20 : Error
Explanation: The specified configuration logging directory does not exist. The command cannot be completed.
Response: Verify that the configuration logging directory specified is correct. Reissue the command with a corrected configuration options parameter. If this does not resolve the problem, contact the IBM Support Center for further assistance.

BFGAP0062E: It was not possible to read the passwordfrom the console.
Severity: 20 : Error
Explanation: An error occurred reading the password fromthe console.
Response: Ensure you are using a Java SE 6.0 Runtime.Alternatively specify the password using the '-dbPassword' command line parameter.

BFGAP0063I: Using first available coordination property set ''<insert_0>'' as the default.
Severity: 0 : Information
Explanation: Because a suitable default coordination property set could not be found, the first available valid one will be used.
Response: Explicitly select a default coordination property set by consulting the supplied documentation.

BFGAP0064E: The specified logger name is blank.
Severity: 20 : Error
Explanation: The specified logger name must be a valid, non-blank name. The command cannot be completed.
Response: Correct the logger name to specify a valid name. Reissue the command with a corrected logger name parameter. If this does not resolve the problem, contact the IBM Support Center for further assistance.

BFGAP0065E: An internal error has occurred. Unable to complete the command because the logger 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.

BFGAP9999E: <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 website.