The trace specification has changed to "<insert_0>".
Severity
0 : Information
Explanation
The trace specification has changed to the value specified in the message. This affects the amount of diagnostic information that is generated.
Response
No action required.
BFGUT0002E
An internal error has occurred. Product failure data was captured in file "<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.
BFGUT0003E
An internal error has occurred. An unexpected condition has occurred that has resulted in the abnormal end of this process. Failure data was captured in file "<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.
BFGUT0004E
An internal error has occurred. An unexpected condition has occurred that has resulted in the abnormal end of this process. Failure data could not be captured.
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.
BFGUT0005E
An internal error has prevented the process from shutting down.
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.
BFGUT0006E
The system is unable to output log messages to the agent event log file in directory <insert_0> (reason: <insert_1>). Agent event log messages will be output to the console.
Severity
20 : Error
Explanation
An error occurred whilst attempting to write a message to the agent event log file. The event log file or containing directory may be inaccessible or the event log file is being used exclusively by another application.
Response
Ensure the agent event log file and directory are accessible and not being used by another application.
BFGUT0007E
The system is unable to access the current trace file: (ErrorManager code: <insert_0>) <insert_1> <insert_2>
Severity
20 : Error
Explanation
An error occurred whilst attempting to access the agent's current trace log file. The trace log file or containing directory may be inaccessible or the disk is full.
Response
Examine the reason given for the error and take the appropriate action.
BFGUT0008E
The system is unable to access the current event log file: (ErrorManager code: <insert_0>) <insert_1> <insert_2>
Severity
20 : Error
Explanation
An error occurred whilst attempting to access the agent's current event log file. The event log file or containing directory may be inaccessible or the disk is full.
Response
Examine the reason given for the error and take the appropriate action.
BFGUT0009E
The system is unable to access the console: (ErrorManager code: <insert_0>) <insert_1> <insert_2>
Severity
20 : Error
Explanation
An error occurred whilst attempting to access the agent's console.
Response
Examine the reason given for the error and take the appropriate action.
BFGUT0010E
The process has attempted to shut itself down by issuing command <insert_0>. This failed with error status <insert_1> reason <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.
BFGUT0011E
The process has attempted to shut itself down by issuing a system kill and super kill. This has failed to complete within a reasonable time period.
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.
BFGUT0012E
The supplied FFDC rule is invalid and cannot be used. The rule is <insert_0>
Severity
20 : Error
Explanation
The FFDC rule supplied in the agent properties file is not valid and cannot be used. The default FFDC rule will be used.
Response
Review the FFDC rule stored in the agent properties file, refer to the agent properties section of the IBM MQ Managed File Transfer documentation, correct the FFDC rule, and restart
BFGUT0013E
An internal problem occurred while validating a FFDC rule. The rule 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.
BFGUT0014I
<insert_2> FFDC reports from class <insert_0> and probe ID <insert_1> have been suppressed.
Severity
0 : Information
Explanation
The agent has implemented an FFDC suppression rule and a number of FFDC reports have been suppressed. The message is reporting how many FFDC reports have been suppressed.
Response
This is an information message and no action is required.
BFGUT0015I
Issuing a stop trace because an FFDC event of class <insert_0> and probe <insert_1> has occurred.
Severity
0 : Information
Explanation
A matching FFDC event previously defined in an fteSetAgentTraceLevel command has occurred and a stop trace event has been issued.
Response
No action is required.
BFGUT0016I
Trace will be turned off if the following FFDCs occur: <insert_0>.
Severity
0 : Information
Explanation
A trace request has been processed that included a trace disable FFDC specification. If any of the FFDCs specified occurs then the trace will be turned off.
Response
No action is required.
BFGUT0017I
Trace will be turned off if any FFDC occurs.
Severity
0 : Information
Explanation
A trace request has been processed that included a trace disable FFDC specification. If any FFDC occurs then the trace will be turned off.
Response
No action is required.
BFGUT0018I
Encoding for output log set to "<insert_0>".
Severity
0 : Information
Explanation
The encoding used to write information to the output log has been changed to the value specified in the message.
Response
No action required.
BFGUT0019W
The requested output log encoding "<insert_0>" is unsupported by this platform. Reverting to platform default.
Severity
10 : Warning
Explanation
The requested encoding for the output log is unsupported by the platform.
Response
Select an encoding for the output log which is supported by the platform, or use the platform default.
BFGUT0020E
The agent trace property value specified ''<insert_0>'' is not supported.
Severity
20 : Error
Explanation
The value passed to the agent trace property is not supported.
Response
Refer to the product documentation to determine the correct syntaxfor the agent trace property. Modify the agent property and restart the agent.
BFGUT0021I
A request to generate JVM diagnostic information has been submitted. The generated JVM diagnostic output file is: <insert_0>
Severity
0 : Information
Explanation
A request to generate JVM diagnostic information has been submitted to the JVM process. The diagnostic information will be output to the working directory of the process.
Response
No user action is necessary.
BFGUT0022I
Diagnostic information written to: <insert_0>
Severity
0 : Information
Explanation
Diagnostic information was written to the specified file.
Response
No user action is necessary.
BFGUT0023E
Unable to generate diagnostic information: <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.
BFGUT0024E
Javacore file not found in directory <insert_0>
Severity
20 : Error
Explanation
The javacore file has been generated but was not found in the expected directory.
Response
If the problem persists, see problem determination information in the product documentation.
BFGUT0025I
Protocol bridge agent log specification has changed to "<insert_0>".
Severity
0 : Information
Explanation
Protocol bridge agent log specification has changed to the value specified in the message.
Response
No action required.
BFGUT0026E
Invalid Protocol bridge agent log specification. The log specified is "<insert_0>".
Severity
20 : Error
Explanation
Protocol bridge agent log specification has unrecognised key value pairs.
Response
Correct the log specification and retry.
BFGUT0027E
The system is unable to log protocol bridge command/response messages to the protocol bridge agent event log file in directory <insert_0> (reason: <insert_1>). Agent event log messages will be output to the console.
Severity
20 : Error
Explanation
An error occurred whilst attempting to write a message to the protocol bridge agent event log file. The event log file or containing directory may be inaccessible or the event log file is being used exclusively by another application.
Response
Ensure the agent event log file and directory are accessible and not being used by another application.
BFGUT0028E
The system is unable to access the current protocol bridge agent event log file: (ErrorManager code: <insert_0>) <insert_1> <insert_2>
Severity
20 : Error
Explanation
An error occurred whilst attempting to access the protocol bridge agent's current event log file. The event log file or containing directory may be inaccessible or the disk is full.
Response
Examine the reason given for the error and take the appropriate action.
BFGUT0029I
Protocol bridge agent log filter specification has changed to "<insert_0>".
Severity
0 : Information
Explanation
Protocol bridge agent log filter specification has changed to the value specified in the message.
Response
No action required.
BFGUT0030E
Invalid Protocol bridge agent log filter specified. The filter specified is "<insert_0>".
Severity
20 : Error
Explanation
Protocol bridge agent log filter specification has unrecognised key value pairs.
Response
Correct the log filter specification and retry.
BFGUT0031E
Failed to set protocol bridge agent log filter. The filter specified is "<insert_0>".
Severity
20 : Error
Explanation
Protocol bridge agent failed to set log filter due to internal exception.
Response
Correct the log filter specification and retry.
BFGUT0032I
Resource monitor event log level has changed to "<insert_0>".
Severity
0 : Information
Explanation
Resource monitor event log level has changed to the value specified in the message.
An invalid option was specified as resource monitor event log level.
Response
Correct the specification and resubmit.
BFGUT0034E
The system is unable to access the current resource monitor event log file: (ErrorManager code: <insert_0>) <insert_1> <insert_2>
Severity
20 : Error
Explanation
An error occurred whilst attempting to access the resource monitor event log file. The event log file or containing directory may be inaccessible or the disk is full.
Response
Examine the reason given for the error and take the appropriate action.
BFGUT0035E
The system is unable to write resource monitor logs to the resource monitor event log file in directory <insert_0> (reason: <insert_1>). Resource monitor event log messages will be output to the console.
Severity
20 : Error
Explanation
An error occurred whilst attempting to write a message to the resource monitor event log file. The event log file or containing directory may be inaccessible or the event log file is being used exclusively by another application.
Response
Ensure the agent event log file and directory are accessible and not being used by another application.
BFGUT0036I
Resource monitor event log level has changed to "<insert_0>" for all resource monitors of this agent.
Severity
0 : Information
Explanation
Resource monitor event log level has changed to the value specified in the message.
Response
No action required.
BFGUT9999E
<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, refer to the problem determination information on the product Web site.