BFGBS0001 - BFGBS9999
- BFGBS0001E
- An internal error has occurred. An insufficient number of arguments were supplied to "<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.
- BFGBS0002E
- An internal error has occurred. The "<insert_0>" system property is not set.
- 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.
- BFGBS0003E
- An internal error has occurred. The "<insert_0>" directory 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.
- BFGBS0004E
- An internal error has occurred. "<insert_0>" is not a directory.
- 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.
- BFGBS0005E
- An internal error has occurred. The exception details follow this 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.
- BFGBS0006E
- Unable to find library "<insert_0>" on the library path "<insert_1>". A potential library "<insert_2>" was found, with the correct name, but has the wrong bit mode.
- Severity
- 20 : Error
- Explanation
- A library with the required name was found on the library path, but its directory name or file name suggest that it is not compatible with the bit mode of the running program.
- Response
- Check the library path (LD_LIBRARY_PATH or LIBPATH environment variable) is set correctly and check that the identified library is in the correct location.
- BFGBS0007E
- An internal error has occurred. Problem accessing file: "<insert_0>", reason: "<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.
- BFGBS0008E
- An internal error has occurred. File: "<insert_0>" is 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.
- BFGBS0009I
- The application is running in a test environment.
- Severity
- 0 : Information
- Explanation
- The environment has requested that the application is run in a test environment. This means that the application classes will be loaded using the standard Java application class loader from the standard Java CLASSPATH, instead of the IBM MQ Managed File Transfer class loader.
- Response
- No action required.
- BFGBS0010E
- Unable to load classes from the JMQI using the classpath ''<insert_0>''.
- Severity
- 20 : Error
- Explanation
- The classes from the JMQI were not found on the classpath.
- Response
- If you are starting an MFT agent or logger as a windows service check whether 'JAVA_HOME' is set as a user or system environment variable. If it is set the value must be 'MQ_INSTALLATION_PATH/java/jre' where 'MQ_INSTALLATION_PATH' is the directory where IBM MQ was installed. Either change or delete the value of the 'JAVA_HOME' environment variable. Then restart the MFT agent or logger service. Contact the IBM support center if you need further assistance.