BFGMQ0001 - BFGMQ9999
- BFGMQ0001E
- An internal error has occurred. setWMQApi can only be called for unit testing.
- 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.
- BFGMQ1000E
- Unable to convert parameter ''<insert_0>'' to UTF-8 encoding.
- Severity
- 20 : Error
- Explanation
- This message is issued when the given string cannot be converted to UTF-8 encoding.
- Response
- Reissue command with valid input string.
- BFGMQ1001E
- At least one of the <insert_0> and <insert_1> parameters must not be empty.
- Severity
- 20 : Error
- Explanation
- This message is issued when the publish method is invoked with empty values for both Topic and Topic String.
- Response
- Reissue command with valid parameters.
- BFGMQ1002E
- An internal error has occurred. The WMQSyncPoint object is being shared between WMQConnection objects.
- 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.
- BFGMQ1003E
- An internal error has occurred. The WMQSyncPoint object has already been completed.
- 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.
- BFGMQ1004E
- An internal error has occurred. This WMQConnection already has a WMQSyncPoint object that has not been completed.
- 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.
- BFGMQ1005I
- An internal error has occurred.
- 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.
- BFGMQ1006W
- The specified coordination queue manager host name <insert_0> cannot be resolved to an external address. The agent''s presence will not be published.
- Severity
- 10 : Warning
- Explanation
- The specified coordination queue manager cannot be resolved using DNS. The agent's presence will not be published.
- Response
- Ensure that the specified host name is valid.
- BFGMQ1007W
- The coordination queue manager cannot be contacted or has refused a connection attempt. The IBM MQ reason code was <insert_0>. The agent''s presence will not be published.
- Severity
- 10 : Warning
- Explanation
- The specified coordination queue manager cannot be contacted so the agent's presence will not be published.
- Response
- Check the IBM MQ documentation for information relating to the specified reason code. Ensure that the coordination queue manager is available and is correctly configured.
- BFGMQ1008E
- An internal error occurred: <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.
- BFGMQ1009I
- An internal error has occurred.
- 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.
- BFGMQ1010E
- An internal error occurred.
- 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.
- BFGMQ1011E
- An error occurred while accessing the specified key store: <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command could not be processed because of an SSL configuration issue relating to the specified key store. This problem prevented the command from being run.
- Response
- Resolve the problem and rerun the command. Otherwise contact the IBM support center if you need further assistance.
- BFGMQ1012E
- An error occurred while accessing the specified trust store: <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command could not be processed because of an SSL configuration issue relating to the specified trust store. This problem prevented the command from being run.
- Response
- Resolve the problem and rerun the command. Otherwise contact the IBM support center if you need further assistance.
- BFGMQ1013E
- An error occurred while accessing the specified key store: <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command could not be processed because of an SSL configuration issue relating to the specified key store. This problem prevented the command from being run.
- Response
- Resolve the problem and rerun the command. Otherwise contact the IBM support center if you need further assistance.
- BFGMQ1014E
- An error occurred while accessing the specified trust store: <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command could not be processed because of an SSL configuration issue relating to the specified trust store. This problem prevented the command from being run.
- Response
- Resolve the problem and rerun the command. Otherwise contact the IBM support center if you need further assistance.
- BFGMQ1015W
- A IBM MQ message with message type Report has been received on queue "<insert_0>".
- Severity
- 10 : Warning
- Explanation
- Report messages are not allowed on MQMFT Queues. The message has been rejected.
- Response
- No user action is required.
- BFGMQ1016W
- A IBM MQ message with message type Report has been received on queue "<insert_0>".
- Severity
- 10 : Warning
- Explanation
- Report messages are not allowed on MQMFT Queues. The message has been rejected.
- Response
- No user action is required.
- BFGMQ1017E
- An internal error occurred. Operation ''<insert_0>'' not allowed on a queue list
- 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.
- BFGMQ1018W
- Unable to convert message coded character set identifier ''<insert_0>'' to a known encoding. Exception information: <insert_1>.
- Severity
- 10 : Warning
- Explanation
- A message was unable to be decoded due to it having an unknown coded character set identifier. UTF-8 encoding will have been assumed but may yield an invalid interpretation of the message; if this is the case then another error will be reported. The cause of this error is likely to be a newer version of IBM MQ being used than the MQMFT version.
- Response
- To resolve the problem ensure your MQMFT installation is at the latest version. If the problem persists contact the IBM support center.
- BFGMQ1019E
- The ''<insert_0>'' property has been assigned an incorrect value of ''<insert_1>''. Valid values are ''none'' or ''java''. The default value of ''none'' will be used.
- Severity
- 20 : Error
- Explanation
- An incorrect value has been assigned to the specified property. The process will continue, but will use the specified default value.
- Response
- Correct the value assigned to the specified property so that it is one of the valid values specified.
- BFGMQ1020E
- Unable to parse the MQRC override property ''<insert_0>''. Failed to interpret ''<insert_1>''.
- Severity
- 20 : Error
- Explanation
- An incorrect value has been assigned to the MQRC override property. The process will continue, but at least part of the MQRC override property will be ignored.
- Response
- Correct the value assigned to the MQRC override property.
- BFGMQ1021E
- MQPUT to <insert_0> failed as the message size of <insert_1> exceeds the maximum that was negotiated for the channel.
- Severity
- 20 : Error
- Explanation
- Either the IBM MQ channel configuration has specified too small a maximum message size or the advanced agent size properties resulted in too large a message being generated.
- Response
- Either alter the IBM MQ channel configuration to ensure the maximum message size is big enough to accommodate the message being sent, or alter the advanced agent size properties so that a smaller message is generated.
- BFGMQ1022E
- An error occurred while configuring a FIPS enabled provider: <insert_0>.
- Severity
- 20 : Error
- Explanation
- The command could not be processed because of an SSL configuration issue relating to the configuration of the FIPS enabled provider. This problem prevented the command from being run. The cause is likely down to no IBM JSSE support included in the JVM in use.
- Response
- Ensure a JVM with IBM JSSE support is used. Otherwise contact the IBM support center if you need further assistance.
- BFGMQ1023E
- A FIPS enabled provider has been requested on an unsupported platform.
- Severity
- 20 : Error
- Explanation
- The command could not be processed because FIPS has been requested on a platform that does not support it.
- Response
- Disable the SSL FIPS property.
- BFGMQ1024I
- The coordination queue manager cannot be contacted or has refused a connection attempt. The IBM MQ reason code was <insert_0> and diagnostic message code was <insert_1>. The agent''s presence will not be published.
- Severity
- 0 : Information
- Explanation
- The specified coordination queue manager cannot be contacted so the agent's presence will not be published.
- Response
- Check the IBM MQ documentation for information relating to the specified reason code. Ensure that the coordination queue manager is available and is correctly configured.
- BFGMQ1025E
- Internal error: the associated IBM MQ command 'dspmqver' does not specify its installation name.
- 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.
- BFGMQ1026E
- Internal error: the associated IBM MQ command 'dspmqver' does not specify its IBM MQ configuration data path.
- 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.
- BFGMQ1027I
- The topic queue <insert_0> could not be located on the coordination queue manager. The IBM MQ reason code was <insert_1>. The agent''s presence will not be published.
- Severity
- 0 : Information
- Explanation
- The specified coordination queue manager has not been correctly configured and so the agent's presence will not be published.
- Response
- Ensure that the coordination queue manager has been correctly configured using the MQSC scripts produced by the fteSetupCoordination command.
- BFGMQ1029E
- The environment variable BFG_DATA is not present but is required to define the location of the MQMFT data and configuration.
- Severity
- 20 : Error
- Explanation
- An attempt to run an MQMFT command failed because the required data and configuration information should be specified in the environment variable BFG_DATA but this variable cannot be located.
- Response
- Refer to the information center and define the BFG_DATA environment variable to reference the relevant data and configuration.
- BFGMQ1030E
- The data directory ''<insert_1>'' specified in the environment variable <insert_0> does not exist or is not a directory.
- Severity
- 20 : Error
- Explanation
- An attempt to run an MQMFT command has failed because the MQMFT data directory specified in the environment variable BFG_DATA or FTE_CONFIG does not reference an existing directory.
- Response
- Ensure that the value in the BFG_DATA or FTE_CONFIG environment variable references an existing directory.
- BFGMQ1031E
- The environment variable <insert_0> references data directory <insert_1>, which does not have the correct configuration because ''<insert_2>'' cannot be located.
- Severity
- 20 : Error
- Explanation
- An attempt to run an MQMFT command has failed because the MQMFT data directory specified in the environment variable BFG_DATA or FTE_CONFIG does not reference an MQMFT data configuration.
- Response
- Ensure that the value in the BFG_DATA or FTE_CONFIG environment variable is referencing the correct MQMFT data configuration and that configuration is complete as specified in the product information center.
- BFGMQ1032E
- The environment variable <insert_0> references <insert_1> which exists but is not a directory.
- Severity
- 20 : Error
- Explanation
- The MQMFT data path must be a directory.
- Response
- Either delete the referenced MQMFT data path, or set the BFG_DATA or FTE_CONFIG environment variable to reference an existing directory that does not contain mqft or that contains an mqft that is a directory.
- BFGMQ1033E
- The current user is unable to access the MQMFT data directory ''<insert_1>'' as referenced by environment variable <insert_0>.
- Severity
- 20 : Error
- Explanation
- The MQMFT data directory does not have write access for the current user, and cannot be used.
- Response
- Change the permissions of the MQMFT data directory to be writable by the current user. Alternatively, change the setting of the BFG_DATA or FTE_CONFIG environment variable to reference a writable empty directory, or a directory that contains a writable mqft subdirectory.
- BFGMQ1034E
- The attempt to create directory <insert_1> as referenced by environment variable <insert_0> was not successful.
- Severity
- 20 : Error
- Explanation
- The command could not complete successfully because the specified directory could not be created. The current user might not have permission to create a directory under the specified parent directory.
- Response
- Check that the user has permission to create a directory under the specified parent directory.
- BFGMQ1035E
- Failed to set file permissions for directory <insert_1> as referenced by environment variable <insert_0> for reason: <insert_2>.
- Severity
- 20 : Error
- Explanation
- The file permissions could not be set for the reason given.
- Response
- Examine the reason given and correct the problem if possible. If the problem persists, contact the IBM support center.
- BFGMQ1036E
- The environment variable <insert_0> references data directory <insert_1>, which does not have the correct configuration because ''<insert_2>'' cannot be read.
- Severity
- 20 : Error
- Explanation
- An attempt to run an MQMFT command has failed because the MQMFT data directory specified in the environment variable BFG_DATA or FTE_CONFIG does not reference an MQMFT data configuration.
- Response
- Ensure that the value in the BFG_DATA or FTE_CONFIG environment variable is referencing the correct MQMFT data configuration and that configuration is complete and accessible for the user as specified in the product information center.
- BFGMQ1037E
- The environment variable <insert_0> references data directory <insert_1>, which does not have the correct configuration because ''<insert_2>'' is a file when a directory was expected.
- Severity
- 20 : Error
- Explanation
- An attempt to run an MQMFT command has failed because the MQMFT data directory specified in the environment variable BFG_DATA or FTE_CONFIG does not reference an MQMFT data configuration.
- Response
- Ensure that the value in the BFG_DATA or FTE_CONFIG environment variable is referencing the correct MQMFT data configuration and that configuration is complete as specified in the product information center.
- BFGMQ1038E
- The environment variable <insert_0> references data directory <insert_1>, which does not have the correct configuration because ''<insert_2>'' is a directory when a file was expected.
- Severity
- 20 : Error
- Explanation
- An attempt to run an MQMFT command has failed because the MQMFT data directory specified in the environment variable BFG_DATA or FTE_CONFIG does not reference an MQMFT data configuration.
- Response
- Ensure that the value in the BFG_DATA or FTE_CONFIG environment variable is referencing the correct MQMFT data configuration and that configuration is complete as specified in the product information center.
- BFGMQ1039E
- Cannot interpret the content of a message that is encoded using character set identifier ''<insert_0>'' (encoding: ''<insert_1>''). Reason: <insert_2>
- Severity
- 20 : Error
- Explanation
- Cannot interpret the content of a message encoded with the specified character set identifier because the character set identifier is not supported. The message will not be processed. The character set identifier associated with a message is set by the program that produces the message. The character set identifier can also be changed by IBM MQ, for example by routing the message using IBM MQ channels that perform data conversion.
- Response
- Determine the reason that the Coded Character Set Identifier field of IBM MQ Message Descriptor has been set to the specified value. Resolve this issue to ensure that the Coded Character Set Identifier is not changed or is only changed to a value that is supported by the agent. If required, refer to the IBM MQ Managed File Transfer product documentation to determine the character sets that an agent process supports.
- BFGMQ1040E
- Unable to convert the character set ''<insert_0>'' to a coded character set ID. 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.
- BFGMQ1041E
- An attempt to connect to queue manager ''<insert_0>'' with user ID ''<insert_1>'' has been rejected because of invalid authentication details. Valid user ID and password details must be supplied in the credentials file.
- Severity
- 20 : Error
- Explanation
- The attempted connection to the queue manager has failed with an MQRC 2035. This indicates the connection has been rejected because of invalid authentication details and the command cannot be completed.
- Response
- Check the required authentication for connection to this queue manager before attempting this command again. Refer to the IBM MQ product documentation for more information on this subject.
- BFGMQ1042E
- An attempt to publish agent information on SYSTEM.FTE topic has been rejected because user ID ''<insert_0>'' has insufficient authority.
- Severity
- 20 : Error
- Explanation
- The publish attempt on SYSTEM.FTE topic has failed with an MQRC 2035. This indicates the publication has been rejected because of insufficient authority and the command cannot be completed.
- Response
- Check if the user has required publish authority on SYSTEM.FTE topic before attempting this command again. Refer to the IBM MQ product documentation for more information on this subject.
- BFGMQ1043W
- An attempt to publish agent''s presence to the coordination queue manager failed. The IBM MQ reason code was ''<insert_0>''.
- Severity
- 10 : Warning
- Explanation
- The publish attempt on SYSTEM.FTE topic has failed so the agent's presence will not be published.
- Response
- Check the IBM MQ documentation for information relating to the specified reason code. Ensure that the coordination queue manager is correctly configured.
- BFGMQ1044E
- Agent client connection on z/OS must be to a queue manager on z/OS
- Severity
- 20 : Error
- Explanation
- Agent running on z/OS attempted a client connection to a queue manager running on a different platform. This is not allowed.
- Response
- Update the agent configuration to connect to a queue manager running on z/OS.
- BFGMQ1045I
- Agent''s system queue ''<insert_0>'' is configured as either NOSHARE or DEFSOPT(EXCL).
- Severity
- 0 : Information
- Explanation
- Agent's system queue is configured as NOSHARE or default input open option as Exclusive.Agent's system queues must be configured as SHARE and DEFSOPT(SHARED).
- Response
- Stop the agent, ensure that agent's system queue is configured as SHARE and DEFSOPT(EXCL)and restart agent.
- BFGMQ1046I
- Fetching messages from subscription to topic string ''<insert_0>''. Number of messages received: ''<insert_1>''.
- Severity
- 0 : Information
- Explanation
- This message shows the number of messages received by the current command from the coordination queue manager.
- Response
- No action is required.
- BFGMQ9999E
- <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.