BFGRP0001 - BFGRP9999
- BFGRP0001E
- Duplicate supplements with matching indexes.
- Severity
- 20 : Error
- Explanation
- Creation of an audit message has failed due to supplement entries having duplicated indexes.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0002E
- Received a WMQAPI Exception - cause code "<insert_0>" and result Code "<insert_1>".
- Severity
- 20 : Error
- Explanation
- An attempt to connect to coordination queue manager for publishing an audit message has failed.
- Response
- Review the result code to analyze the problem further.
- BFGRP0003E
- An internal error has occurred. Received a JMQI 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.
- BFGRP0004E
- Received a WMQAPI exception - cause code "<insert_0>" and result Code "<insert_1>".
- Severity
- 20 : Error
- Explanation
- An attempt to publish an audit message has failed.
- Response
- Review the result code to analyze the problem further.
- BFGRP0005E
- Received a JMQI exception - cause code "<insert_0>" and result Code "<insert_1>".
- Severity
- 20 : Error
- Explanation
- An attempt to disconnect from WebSphere MQ after publishing an audit message has failed.
- Response
- Review the result code to analyze the problem further.
- BFGRP0006E
- An internal error has occurred. Missing XML data to create element Instigator.
- Severity
- 20 : Error
- Explanation
- A mandatory element for the audit message is missing from the underlying data.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0007E
- An internal error has occurred. An XML message failed parsing with "<insert_0>".
- Severity
- 20 : Error
- Explanation
- The XML parser has rejected an XML message as not being valid.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0008E
- An XML message failed parsing with "<insert_0>".
- Severity
- 20 : Error
- Explanation
- An XML parser has rejected an XML message as not being valid.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0009E
- An internal error has occurred. JAXP Support reported an illegal argument "<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.
- BFGRP0010E
- An internal error has occurred. Document build has reported a factory parsing error "<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.
- BFGRP0011E
- An internal error has occurred. Parsing an audit message has failed with "<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.
- BFGRP0012E
- An internal error has occurred. Can not locate schema to parse XML message with "<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.
- BFGRP0013E
- An internal error has occurred. XML message failed parsing with "<insert_0>".
- Severity
- 20 : Error
- Explanation
- The XML parser has rejected an XML message as not being valid.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0014E
- An internal error has occurred. An audit message could not be generated because the Action element was not defined.
- 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.
- BFGRP0015E
- An internal error has occurred. There is missing XML data to create element Source.
- Severity
- 20 : Error
- Explanation
- A mandatory element for the audit message is missing from the underlying data.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0016E
- An internal error has occurred. There is missing XML data to create element Destination.
- Severity
- 20 : Error
- Explanation
- A mandatory element for the audit message is missing from the underlying data.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0017E
- There is missing XML data to create element Transfer.
- Severity
- 20 : Error
- Explanation
- A mandatory element for the audit message is missing from the underlying data.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0018E
- An internal error has occurred. Parsing an audit message has failed with "<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.
- BFGRP0019E
- Received a WMQAPI exception - cause code "<insert_0>" and result code "<insert_1>".
- Severity
- 20 : Error
- Explanation
- An attempt to publish an audit message has failed.
- Response
- Review the Result Code to analyse the problem further
- BFGRP0020E
- Received a WMQAPI exception - cause code "<insert_0>" and result code "<insert_1>".
- Severity
- 20 : Error
- Explanation
- An attempt to disconnect from coordination queue manager after publishing an audit message has failed.
- Response
- Review the result code to analyze the problem further
- BFGRP0021E
- An internal error has occurred. Repeat attempt to send an audit Started 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.
- BFGRP0022E
- An internal error has occurred. Attempt to send an audit Completed message before an audit Started 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.
- BFGRP0023E
- An internal error has occurred. Repeat attempt to send an audit Completed 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.
- BFGRP0024E
- An internal error has occurred. Attempt to send an audit Progress before an audit Started 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.
- BFGRP0025E
- An internal error has occurred. Attempt to send an audit Progress message after an audit Complete 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.
- BFGRP0026E
- An internal error has occurred. Factory requires initialization before use.
- 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.
- BFGRP0027E
- An internal error has occurred. Calls to this factory method is not supported in current mode.
- 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.
- BFGRP0028I
- An internal error has occurred. Unknown agent role <insert_0>.
- Severity
- 0 : Information
- Explanation
- This exception is unexpected. The cause is not immediately known.
- Response
- If the problem persists, see problem determination information in the product documentation.
- BFGRP0029E
- An internal error has occurred. Unknown agent role when creating XML audit message 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.
- BFGRP0030E
- An internal error has occurred. Unknown value for attribute EOL for a file element of a log message. Value 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.
- BFGRP0031E
- An internal error has occurred. IOException message: <insert_0>
- Severity
- 20 : Error
- Explanation
- CMSG00001
- Response
- CMSG00002
- BFGRP0032I
- The file transfer request has successfully completed.
- Severity
- 0 : Information
- Explanation
- The requested file transfer has completed with all required files transferring successfully.
- Response
- None.
- BFGRP0033I
- The file transfer request has completed with partial success.
- Severity
- 0 : Information
- Explanation
- The requested file transfer has completed but not all files were transferred successfully. See FTE log for details of the failures.
- Response
- Review the FTE log and resubmit the transfer request with appropriate modifications, as required.
- BFGRP0034I
- The file transfer request has completed with no files being transferred.
- Severity
- 0 : Information
- Explanation
- The requested file transfer has completed but none of the requested files were transferred successfully. See FTE log for details of the failure.
- Response
- Review the FTE log and resubmit the transfer request with appropriate modifications, as required.
- BFGRP0035E
- An internal error has occurred. Publishing a progress audit with an invalid item result code 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.
- BFGRP0036I
- The transfer request has successfully completed, although no files were transferred.
- Severity
- 0 : Information
- Explanation
- No files were transferred, but the agent believes this to be a successful outcome. This may be, for example, due to a source wildcard that didn't match any files, or some similar reason.
- Response
- None.
- BFGRP9999E
- <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.