BFGIP0001 - BFGIP9999
- BFGIP0001E
- An internal error has occurred. Native support is unavailable. Reason: <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.
- BFGIP0002E
- An internal error has occurred. The interprocess communications mechanism has been shut 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.
- BFGIP0003E
- Failed to open 4690 pipe ''<insert_1>'' for service ''<insert_0>''. Reason: <insert_2>
- Severity
- 20 : Error
- Explanation
- The 4690 pipe required for the interprocess communications mechanism cannot be opened for the reason given.
- Response
- Examine the reason given and taken action as appropriate.
- BFGIP0004E
- Failed to open 4690 pipe ''<insert_1>'' for service ''<insert_0>''. 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.
- BFGIP0005E
- Failed to read interprocess communications message from pipe. Reason: <insert_0>
- Severity
- 20 : Error
- Explanation
- An attempt to read an interprocess communications message failed.
- Response
- Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
- BFGIP0006E
- Failed to read from 4690 pipe. Reason: <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.
- BFGIP0007E
- Failed to open 4690 pipe ''<insert_1>'' for service ''<insert_0>''. Reason: <insert_2>
- Severity
- 20 : Error
- Explanation
- The 4690 pipe required for the interprocess communications mechanism cannot be opened for the reason given.
- Response
- Examine the reason given and taken action as appropriate.
- BFGIP0008E
- Failed to open 4690 pipe ''<insert_1>'' for service ''<insert_0>''. 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.
- BFGIP0009E
- Interprocess communications message of length <insert_0> bytes is too long. The maximum permitted length for an interprocess communications message is <insert_1> bytes.
- 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.
- BFGIP0010E
- Failed to serialize interprocess communications message. Reason: <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.
- BFGIP0011E
- Failed to open 4690 pipe ''<insert_0>''. Reason: <insert_1>
- Severity
- 20 : Error
- Explanation
- The 4690 pipe required for the interprocess communications mechanism cannot be opened for the reason given.
- Response
- Examine the reason given and taken action as appropriate.
- BFGIP0012E
- Failed to open 4690 pipe ''<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.
- BFGIP0013E
- Failed to write interprocess communications message to pipe ''<insert_0>''. Reason: <insert_1>
- Severity
- 20 : Error
- Explanation
- An attempt to write an interprocess communications message failed.
- Response
- Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
- BFGIP0014E
- No response to command within <insert_0> seconds.
- Severity
- 20 : Error
- Explanation
- There was no response to the command within the required timeout.
- Response
- Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
- BFGIP0015E
- Failed to read interprocess communications reply message. Reason: <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.
- BFGIP9999E
- <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.