BFGPR0001 - BFGPR9999

BFGPR0001E
Could not load properties file ''<insert_0>'' due to exception: <insert_1>
Severity
20 : Error
Explanation
The specified properties file could not be loaded because of the specified exception.
Response
Use the exception information from the message to diagnose the problem. Resolve the problem if possible, otherwise contact the IBM Support Center for further assistance.

BFGPR0008W
Audit publication is disabled.
Severity
10 : Warning
Explanation
No audit message will be published because the coordination queue manager has not been specified.
Response
Correctly specify the coordination queue manager.

BFGPR0009E
An empty expression was used as the success return code for a command invocation.
Severity
20 : Error
Explanation
An empty expression has been specified for use when evaluating the return code for a command invocation. It is not valid to specify an empty expression for the expression used to evaluate a command invocation.
Response
Correct the place where the expression has been specified so that a non-empty expression is specified.

BFGPR0010E
The success return code expression ''<insert_0>'', is malformed as it ends with a logical operator.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because it ends with either the '|' or '&' logical operators which are intended to join expressions.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.

BFGPR0011E
The success return code expression ''<insert_0>'' is malformed as it contains the symbol ''<insert_1>'' where either the logical operators ''|'' or ''&'' are expected.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because the specified symbol was encountered where either the '|' or '&' logical operators were expected.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.

BFGPR0012E
The success return code expression ''<insert_0>'' is malformed as it contains the symbol ''<insert_1>'' where a numeric value is expected.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because the specified symbol was encountered where a numeric value was expected.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.

BFGPR0013E
The success return code expression ''<insert_0>'' is malformed as it contains the symbol ''<insert_1>'' where a comparison operator of ''!'', ''<'' or ''>'' is expected.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because the specified symbol was encountered where a comparison operator was expected.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.

BFGPR0014E
The country and language format of <insert_0> is not valid.
Severity
20 : Error
Explanation
The given country and language parameter could not be validated against the expected format. The expected format is cc-ll, where cc is the two letter country code and ll is the two letter language code.
Response
Review the given parameter and correct the format as necessary.

BFGPR0015E
The language code of <insert_0> does not match any of the know values.
Severity
20 : Error
Explanation
The language element of the given country and language parameter does not match any of the know values and has been rejected.
Response
Review the given parameter and correct the language element as necessary.

BFGPR0016E
The country code of <insert_0> does not match any of the know values.
Severity
20 : Error
Explanation
The country element of the given country and language parameter does not match any of the know values and has been rejected.
Response
Review the given parameter and correct the country element as necessary.

BFGPR0017E
The given property value for ''<insert_0>'' is not valid as it contains control characters. This usually occurs if the backslash character has not been escaped.
Severity
20 : Error
Explanation
When inputting property values that contain a backslash character (e.g., a Windows path name), these values must be escaped to ensure they are passed through as expected.
Response
Replace all occurrences of the backslash '\\' with a double-backslash '\\\\' in the referenced property value.

BFGPR0018E
An incomplete transfer template has been detected in either the Id or name missing.
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.

BFGPR0019E
An invalid transfer template has been detected and the parser has reported <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.

BFGPR0020E
Internal error has occurred and a <insert_0> exception has been reported with description <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.

BFGPR0021E
Internal error has occurred with an unsupported encoding.
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.

BFGPR0022E
The command received MQI reason code <insert_0> when connecting to coordination queue ''<insert_1>''. The requested action cannot be completed.
Severity
20 : Error
Explanation
The command cannot access transfer template information because the command cannot establish a binding mode connection to the specified queue manager because of the specified MQI reason code. The requested action cannot be completed.
Response
Consult the WebSphere MQ product documentation to determine the cause of the problem. Resolve the problem.

BFGPR0023E
The command received MQI reason code <insert_0> when connecting to coordination queue ''<insert_1>'' on host <insert_2>, port <insert_3> using channel <insert_4>. The requested action cannot be completed.
Severity
20 : Error
Explanation
The command cannot access transfer template information because the command cannot establish a client mode connection to the specified queue manager because of the specified MQI reason code. The requested action cannot be completed.
Response
Consult the WebSphere MQ product documentation to determine the cause of the problem. Resolve the problem.

BFGPR0024E
Internal error has occurred with a report JMQI exception of <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.

BFGPR0025E
Internal error has occurred with a report JMQI exception of <insert_0>.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.

BFGPR0026E
MQ returned reason code <insert_0> when attempting to read the <insert_2> topic string from queue <insert_1> on queue manager <insert_3>.
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.

BFGPR0027E
MQ returned reason code <insert_0> when attempting to delete template name <insert_1> with Id <insert_2>.
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.

BFGPR0028E
Internal error has occurred. Xpath reported exception <insert_1> when processing <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.

BFGPR0029E
Internal error has occurred. Xpath reported exception <insert_1> when processing <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.

BFGPR0030E
The trace request has the following XML errors: <insert_0>.
Severity
20 : Error
Explanation
A request to change trace settings has been received. However it contains XML syntax errors and could not be processed.
Response
Review the XML request and correct as necessary. If this was generated by a supplied command then contact the IBM Support Center for further assistance.

BFGPR0031E
The XML trace request contains mixed triggers. The -disableOnAnyFFDC parameter cannot be combined with the -disableOnFFDC parameter.
Severity
20 : Error
Explanation
A request for changing trace settings has been received, but contains mixed FFDC triggers. It contains requests to disable on both any FFDC and a specific FFDC. This is ambiguous and the request could not be completed.
Response
Review the XML request and correct as necessary. If this was generated by a supplied command then contact the IBM Support Center for further assistance.

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

BFGPR0033E
Log capture could not be enabled due to the following exception: <insert_0>
Severity
20 : Error
Explanation
Log capturing has been configured to be enabled but was not initialized due to an exception. Log capturing has been disabled.
Response
Review the exception and take any necessary action before restarting the agent.

BFGPR0034E
The tag filter for log capturing has the following syntax errors: <insert_0>.
Severity
20 : Error
Explanation
The supplied tag filter for log capture contains a syntax error and cannot be used for filtering the log capture. Log capture will be enabled but filtering will not be used.
Response
Review the syntax errors and correct the regular expression as necessary before restarting the agent.

BFGPR0035E
Internal error. The capture log file name of <insert_0> is missing the ''%d'' sequence for substituting the index value.
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.

BFGPR0036E
Failed to write capture log information to <insert_0> due to the following exception: <insert_1>
Severity
20 : Error
Explanation
Writing to the capture log file has failed due to a problem with the storage device. Capture logging has been disabled.
Response
Check that the directory that the capture logs are written to has the correct permissions for the agent to write to the directory, and that there is sufficient file space. Make any necessary changes and restart the agent.

BFGPR0037E
Failed to delete capture log file <insert_0>
Severity
20 : Error
Explanation
An attempt to delete the oldest capture log file has failed. Capture logging has been disabled.
Response
Check that the agent has permission to delete this file and then restart the agent.

BFGPR0038E
Failed to rename capture log file <insert_0> to <insert_1>
Severity
20 : Error
Explanation
An attempt to rename the capture log file has failed. Capture logging has been disabled.
Response
Check that the agent has permission to rename these files and then restart the agent.

BFGPR0039E
The capture log directory of <insert_0> does not exist or the agent does not have permission to write files to the directory.
Severity
20 : Error
Explanation
The agent is unable to access the specified directory, either because the directory does not exist or because the agent does not have permission to write to the directory. Capture logging has been disabled.
Response
Check that the directory does exist and the agent has write permission for the directory. Restart the agent.

BFGPR0040E
Failed to write capture log information to <insert_0> due to the exception <insert_1>
Severity
20 : Error
Explanation
Writing to the capture log file has failed due to a problem with the storage device. Capture logging has been disabled.
Response
Check that the directory that the capture logs are written to has the correct permissions for the agent to write to the directory, and that there is sufficient file space. Make any necessary changes and restart the agent.

BFGPR0041W
Using default value of ''<insert_1>'' for property ''<insert_0>''. The specified value ''<insert_2>'' is invalid. The value must be an integer in the range <insert_3> to <insert_4>.
Severity
10 : Warning
Explanation
An invalid value was specified for an integer property. The system will use the default value.
Response
Update the property definition to specify a valid value.

BFGPR0042W
Invalid logCapture property value: ''<insert_0>''. Valid values are ''true'' or ''false''.
Severity
10 : Warning
Explanation
The value specified for the logCapture property is not valid. Valid values are 'true' and 'false'. The default value of 'false' will be used.
Response
Correct the value of the logCapture property.

BFGPR0043W
Invalid logCaptureFileSize property value: <insert_0>
Severity
10 : Warning
Explanation
The value specified for the logCaptureFileSize property is not valid. The value must be a positive integer that specifies a size in megabytes. The default value for the logCaptureFileSize property (10 MB) will be used.
Response
Correct the value of the logCaptureFileSize property.

BFGPR0044W
Invalid logCaptureFiles property value: <insert_0>
Severity
10 : Warning
Explanation
The value specified for the logCaptureFiles property is not valid. The value must be a positive integer that specifies the maximum number of log capture files to generate. The default value for the logCaptureFiles property (10) will be used.
Response
Correct the value of the logCaptureFiles property.

BFGPR0045E
A problem has occurred while parsing the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
A SAX parsing error has been encountered while parsing an XML file.
Response
Correct the XML file to resolve the problem.

BFGPR0046E
A problem has occurred while attempting to open the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
The XML file cannot be opened.
Response
Check that the XML file is in the correct location and accessible by the agent.

BFGPR0047E
A problem has occurred while attempting to read the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
The XML file cannot be read.
Response
Check that the XML file is accessible by the agent.

BFGPR0048E
A problem has occurred while attempting to read the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
A SAX error has been encountered while accessing an XML file.
Response
Take appropriate action based on the exception.

BFGPR0049E
An internal error has occurred while creating the XML document builder for the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <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.

BFGPR0050E
An invalid regular expression has been found in the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
When loading an XML file that contains regular expression fields, the contents are validated to ensure they specify a syntactically correct regular expression.
Response
Correct the regular expression fields that are in error in the XML file to resolve the problem.

BFGPR0051E
An invalid data value has been found in the <insert_0> XML file. The internal WMQFTE data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
When loading an XML file the contents are validated to ensure that all data is valid. See the explanation associated with the error for further information.
Response
Correct the values that are in error in the XML file to resolve the problem.

BFGPR0052E
XML file <insert_0> does not exist. The internal WMQFTE data has not been updated.
Severity
20 : Error
Explanation
The XML file cannot be found.
Response
Create the XML file with the correct path and file name.

BFGPR0053I
The <insert_0> file has been updated.
Severity
0 : Information
Explanation
The agent has detected a change in the XML configuration document. The agent has reloaded the XML configuration document and will now operate based on the content of the new document.
Response
No user action is required.

BFGPR0054E
The program specification ''<insert_0>'' does not define the command to be run.
Severity
20 : Error
Explanation
A program specification must contain the name of the command to be called.
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.

BFGPR0055E
Ant script property parameter ''<insert_1>'' is invalid within the program specification ''<insert_0>''.
Severity
20 : Error
Explanation
An Ant script property parameter must be in the form: =, where is 1 or more characters, and is 0 or more characters.
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.

BFGPR0056E
The program specification ''<insert_0>'' defines one or more arguments for a <insert_1> command type. This command type does not support arguments.
Severity
20 : Error
Explanation
Command arguments are not supported for certain command types (such as JCL scripts).
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.

BFGPR0057E
The program specification ''<insert_0>'' is invalid.
Severity
20 : Error
Explanation
A program specification is syntactically incorrect and cannot be parsed.
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.

BFGPR0058E
Internal error during initialization of XPath components. The error 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.

BFGPR0059E
Internal error during parsing of XPath components. The error 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.

BFGPR0060E
A parsing configuration error was reported while parsing an XML message. The error 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.

BFGPR0061E
A SAX error was reported while parsing an XML message. The error 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.

BFGPR0062E
An IO error was reported while parsing an XML message. The error 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.

BFGPR0063E
Schema errors have been detected in the imported XML message. See associated reported data for details.
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.

BFGPR0064W
The value ''<insert_0>'' of the commandMessagePriority property is invalid. The command WebSphere MQ message priority has been set to the default value of -1 (MQPRI_PRIORITY_AS_Q_DEF).
Severity
10 : Warning
Explanation
The value of the commandMessagePriority property must be an integer between -1 and 9.
Response
Set a valid value for the commandMessagePriority property.

BFGPR0065W
The value ''<insert_0>'' for the <insert_1> agent property is invalid.
Severity
10 : Warning
Explanation
The value of the given property must be an integer within the accepted range.
Response
Refer to the documentation to determine the range of accepted values and set the property appropriately.

BFGPR0135W
The value for property ''<insert_0>'' has been altered from ''<insert_1>'' to ''<insert_2>'' because it contained invalid characters for XML conversion.
Severity
10 : Warning
Explanation
The value for this property needed to be XML 1.0 encoded, and contained characters which are not valid in XML 1.0. These characters were therefore removed to allow XML encoding.
Response
Refer to the XML 1.0 specification to determine the acceptable range of characters which can be used, then alter within the FTE configuration file the property stated in the message above to avoid the need for incompatible characters.

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