BFGCU0001 - BFGCU9999
- BFGCU0001E
- The value supplied for the ''<insert_0>'' command line property is outside the range of valid numerical values for this property. The range is from <insert_1> to <insert_2>.
- Severity
- 20 : Error
- Explanation
- The value supplied for the specified command line property is outside the specified range of acceptable values. As a result, the command cannot be issued.
- Response
- Refer to the command line help or to the product documentation to determine a valid value for the parameter that is within the specified range. Reissue the command using this value.
- BFGCU0002E
- The value supplied for the ''<insert_0>'' command line property is not a valid numerical value.
- Severity
- 20 : Error
- Explanation
- The value supplied for the specified command line property is not a valid numerical value. As a result, the command cannot be issued.
- Response
- Reissue the command with a numerical value for the specified property.
- BFGCU0003W
- 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.
- BFGCU0004W
- 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 vaild value for the parameter. Update the specified properties file to correct the value of the specified property.
- BFGCU0005E
- The value supplied for the ''<insert_0>'' command line property is too long. The maximum length for this property is 48 characters.
- Severity
- 20 : Error
- Explanation
- The value supplied for the specified property is longer than 48 characters. The maximum length permitted for values of this property is 48 characters. As a result, the command cannot be completed.
- Response
- Reissue the command with a value for the specified property that is no greater than 48 characters in length.
- BFGCU0006E
- The value supplied for the ''<insert_0>'' command line property contains characters that are not permitted in a WebSphere MQ object name.
- Severity
- 20 : Error
- Explanation
- The value supplied for the specified property contains characters that are not permitted in a WebSphere MQ object name. As a result, the command cannot be completed.
- Response
- Refer to the WebSphere MQ product documentation to determine the rules for naming WebSphere MQ objects. Reissue the command with a value for the specified property that conforms to WebSphere MQ object naming rules.
- BFGCU0007W
- 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.
- BFGCU0008W
- The value supplied for the ''<insert_0>'' property in the ''<insert_1>'' property file contains characters that are not permitted in a WebSphere 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 a WebSphere MQ object name. As a result, the property will be ignored.
- Response
- Refer to the WebSphere MQ product documentation to determine the rules for naming WebSphere MQ objects. Correct the value of the specified property in the specified properties file.
- BFGCU0009E
- FTE_CONFIG environment variable is not set or the ''<insert_0>'' file cannot be located in the product installation directory ''<insert_1>''.
- Severity
- 20 : Error
- Explanation
- The FTE_CONFIG environment variable must be set or the installation properties file must exists for this command to function correctly. The command cannot continue and will end without performing any action.
- Response
- Set the FTE_CONFIG environment variable or check your configuration. For distributed platforms the installation properties file should have been laid down as part of the installation. Refer to the product documentation to determine a valid value for the parameter. Reissue the command.
- BFGCU0010E
- 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.
- BFGCU0011E
- 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.
- BFGCU0012E
- 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.
- BFGCU0013E
- 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.
- BFGCU0014W
- 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.
- BFGCU0015E
- 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.
- BFGCU0016E
- 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.
- BFGCU0017E
- 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.
- BFGCU0018E
- The configuration options directory ''<insert_0>'' does not exist.
- 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.
- BFGCU0019E
- 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.
- BFGCU0020E
- 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.
- BFGCU0021E
- 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.
- BFGCU0022E
- 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.
- BFGCU0023E
- 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 known valid option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0024E
- 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 known valid option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0025E
- 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.
- BFGCU0026E
- The Java Runtime Environment (Version: <insert_0>) is not compatible. Run with Version: <insert_1> or higher.
- Severity
- 20 : Error
- Explanation
- The agent requires Java Runtime Environment {1} or higher.
- Response
- Upgrade the system Java Runtime Environment.
- BFGCU0027E
- The value supplied for the ''<insert_0>'' command line property 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 standard: yyyy-MM-ddThh:mm or hh:mm.
- BFGCU0028E
- 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 standard: yyyy-MM-ddThh:mm or hh:mm.
- BFGCU0029E
- 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 action.
- Response
- Set the FTE_CONFIG environment variable. Refer to the product documentation to determine a valid value for the parameter. Reissue the command.
- BFGCU0030E
- The trigger parameter ''<insert_0>'' has an unknown condition value.
- Severity
- 20 : Error
- Explanation
- The condition part of the trigger parameter of the transfer request is not recognized and therefore the fteCreateTransfer command cannot be completed.
- Response
- Review the help options for the trigger parameter and update the condition part of the trigger parameter as necessary. Refer to the fteCreateTransfer command documentation if you need further clarification.
- BFGCU0031E
- The trigger parameter ''<insert_0>'' has an unknown condition value.
- Severity
- 20 : Error
- Explanation
- The condition part of the trigger parameter of the transfer request is not recognized and therefore the fteCreateTransfer command cannot be completed.
- Response
- Review the help options for the trigger parameter and update the condition part of the trigger parameter as necessary. Refer to the fteCreateTransfer command documentation if you need further clarification.
- BFGCU0032E
- The trigger parameter ''<insert_0>'' has an unknown condition value.
- Severity
- 20 : Error
- Explanation
- The condition part of the trigger parameter of the transfer request is not recognized and therefore the fteCreateTransfer command cannot be completed.
- Response
- Review the help options for the trigger parameter and update the condition part of the trigger parameter as necessary. Refer to the fteCreateTransfer command documentation if you need further clarification.
- BFGCU0033E
- The trigger parameter ''<insert_0>'' has an unknown condition value.
- Severity
- 20 : Error
- Explanation
- The condition part of the trigger parameter of the transfer request is not recognized and therefore the fteCreateTransfer command cannot be completed.
- Response
- Review the help options for the trigger parameter and update the condition part of the trigger parameter as necessary. Refer to the fteCreateTransfer command documentation if you need further clarification.
- BFGCU0034E
- The trigger parameter ''<insert_0>'' has an unknown condition value.
- Severity
- 20 : Error
- Explanation
- The condition part of the trigger parameter of the transfer request is not recognized and therefore the fteCreateTransfer command cannot be completed.
- Response
- Review the help options for the trigger parameter and update the condition part of the trigger parameter as necessary. Refer to the fteCreateTransfer command documentation if you need further clarification.
- BFGCU0035E
- The trigger parameter ''<insert_0>'' has an unknown condition value.
- Severity
- 20 : Error
- Explanation
- The value supplied as the qualifier for the trigger parameter is invalid for the check value of the filesize option. As a result, the command cannot be completed.
- Response
- Review the help options for the trigger parameter and update the condition part of the trigger parameter as necessary. Refer to the fteCreateTransfer command documentation if you need further clarification.
- BFGCU0036E
- The trigger parameter ''<insert_0>'' has an incorrectly-formatted list of file specifications.
- Severity
- 20 : Error
- Explanation
- The list of file specifications supplied to the trigger parameter is incorrectly formatted and it is not clear what the file names are. As a result, the command cannot be completed.
- Response
- Reissue the command with a list of file specifications formed of either a single file name or multiple file names each separated by a single comma.
- BFGCU0037E
- The trigger parameter ''<insert_0>'' has an incorrectly-formatted list of file specifications.
- Severity
- 20 : Error
- Explanation
- The list of file specifications supplied to the trigger parameter is incorrectly formatted and it is not clear what the file names are. As a result, the command cannot be completed
- Response
- Reissue the command with a list of file specifications formed of either a single file name or multiple file names each separated by a single comma.
- BFGCU0038E
- The trigger parameter ''<insert_0>'' is incorrectly formatted.
- Severity
- 20 : Error
- Explanation
- The trigger parameter does not conform to any of the correct formats.
- Response
- Use the command help option to review possible options and then reissue the command.
- BFGCU0039E
- An internal error has occurred. Trigger parameter ''<insert_0>'' is incorrectly formatted. The subdivided elements were <insert_1>
- Severity
- 20 : Error
- Explanation
- CMSG001
- Response
- CMSG002
- BFGCU0040E
- The trigger parameter ''<insert_0>'' is not a supported condition when monitoring a <insert_1> resource.
- Severity
- 20 : Error
- Explanation
- The trigger parameter must conform to one of the formats supported by the resource being monitored.
- Response
- Consult the command line help to review the available options and then reissue the command.
- BFGCU0041E
- The trigger parameter ''<insert_0>'' is not valid as it does not match the required format for any of the conditions supported by the command.
- Severity
- 20 : Error
- Explanation
- The trigger parameter must conform to one of the formats supported by the command.
- Response
- Consult the command line help to review the available options and then reissue the command.
- BFGCU0042E
- 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 known valid option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0043E
- 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 known valid option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0044E
- 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 known valid locale option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0045E
- The value ''<insert_0>'' is not a valid timezone for argument ''<insert_1>''.
- Severity
- 20 : Error
- Explanation
- The value given in the command argument is not a known valid timezone option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0046E
- 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 known valid file encoding option for the argument.
- Response
- Review the possible options from the usage information, then correct and resubmit the command.
- BFGCU0047E
- An internal error has occurred. Missing long name required for property key in <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.
- BFGCU0048E
- The value ''<insert_0>'' is not a valid port reference for argument ''<insert_1>''.
- Severity
- 20 : Error
- Explanation
- The given value was not a valid port reference which should be an integer in the range of 0 and 65534.
- Response
- Review the possible options from the usage information, then correct the argument and resubmit the command.
- BFGCU0049E
- The destination queue parameter ''<insert_0>'' is incorrectly formatted.
- Severity
- 20 : Error
- Explanation
- The destination queue parameter is not in the correct format.
- Response
- Ensure the destination queue parameter is specified either as QUEUE or QUEUE@QUEUEMANAGER and in both cases conforms to valid WebSphere MQ object names.
- BFGCU0050E
- The value of ''<insert_0>'' for the size by which to split messages is not valid.
- Severity
- 20 : Error
- Explanation
- The size by which to split messages must be specified in a supported format.
- Response
- Review the possible options from the usage information, then correct the message splitting size value.
- BFGCU0051E
- The value of ''<insert_0>'' for the delimiter by which to split binary messages is not valid.
- Severity
- 20 : Error
- Explanation
- The delimiter by which to split binary messages must be specified in a supported format.
- Response
- Review the possible options from the usage information, then correct the binary delimiter value.
- BFGCU0052E
- The regular expression given as a value for the ''-<insert_0>'' property is not specified in a valid syntax (<insert_1>).
- Severity
- 20 : Error
- Explanation
- The command line value must be formatted as a valid regular expression.
- Response
- Correct the argument value and submit the request again.
- BFGCU0053E
- The value specified using the ''-<insert_0>'' parameter is not valid. The value must be either ''32'' or ''64''.
- Severity
- 20 : Error
- Explanation
- The value specified is not valid for the parameter given in the error message. The value must be either '32' or '64'.
- Response
- Correct the value and submit the request again.
- BFGCU0054E
- The value of ''<insert_0>'' for the delimiter to split binary records with is not valid.
- Severity
- 20 : Error
- Explanation
- You must specify the delimiter to split binary records with in a supported format.
- Response
- Review the possible options from the usage information, then correct the binary delimiter value.
- BFGCU9999E
- <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.