Telemetry (AMQXR) messages

AMQXR0001I: Client <insert_0> disconnected normally.
Explanation: An MQTT disconnect flow was received and processed.
Response: No action is required.

AMQXR0002E: On channel <insert_2>, a throwable <insert_1> resulted when the service received a message from client <insert_0>.
Explanation: Bad data was received from a network connection and could not be processed, the connection is closed by the server.
Response: Determine why the client sent the uninterpretable data.

AMQXR0003I: MQXR JAAS <insert_0> : <insert_1>.
Explanation: The JAAS callback in the service requested that the message is displayed to the user.
Response: Determine the cause of the security problem described in the text of the message issued by JAAS.

AMQXR0004E: MQSeries verb=<insert_0>(String) returned cc=<insert_1>(int) <insert_2> rc=<insert_3>(int) <insert_4>.
Explanation: The IBM MQ verb returned an unexpected reason and completion code.
Response: Look up the reason code to determine what caused the error.

AMQXR0005I: Running <insert_0> version <insert_1>.
Explanation: The command is running.
Response: No action is required.

AMQXR0006E: Invalid argument <insert_0> Usage: runMQXRService -m <queueManagerName> -d <Qmgr Data Directory> -g <MQ Global Data directory>
Explanation: The runMQXRService command arguments are incorrect.
Response: Correct the command.

AMQXR0007E: Invalid argument <insert_0> Usage: endMQXRService -m <queueManagerName> -d <Qmgr Data Directory> -g <MQ Global Data directory>
Explanation: The endMQXRService command arguments are incorrect.
Response: Correct the command.

AMQXR0008E: Exception during start up of <insert_0> service: <insert_1>
Explanation: The service was starting up but encountered a problem. Earlier errors or FDCs will provide more detail.
Response: Use earlier errors or FDCs to diagnose and address the problem then restart the service.

AMQXR0009E: Exception during shutdown of service: <insert_0>
Explanation: The service was shutting down but encountered a problem. Earlier errors or FDCs will provide more detail.
Response: Use earlier errors or FDCs to diagnose and address the problem

AMQXR0010E: An invalid ClientIdentifier <insert_0> was received from <insert_1> in an MQTT CONNECT packet on channel <insert_2>.
Explanation: The service received a ClientIdentifier that is not valid because it contains too few, or too many characters, or the characters are not valid in a queue manager name.
Response: Change the ClientIdentifier to use valid characters.

AMQXR0011E: An error occurred during a publish on topic <insert_3> from ClientIdentifier <insert_0> UserName <insert_1> on channel <insert_2>. A reason code of <insert_5> <insert_6> was received during an <insert_4> operation for object <insert_7>.
Explanation: The publication from the client was not able to be completed
Response: Using the reason code, diagnose the cause of the problem, alter the configuration (of the client or the server as appropriate) and then retry the publish.

AMQXR0012E: An error occurred whilst subscribing on topic(s) <insert_3> for ClientIdentifier <insert_0> UserName <insert_1> on channel <insert_2>. A reason code of <insert_5> <insert_6> was received during an <insert_4> operation for object <insert_7>.
Explanation: The subscription from the client was not able to be completed
Response: Using the reason code, diagnose the cause of the problem, alter the configuration (of the client or the server as appropriate) and then reconnect the client and retry the subscription.

AMQXR0013E: Error starting channel <insert_0> (on host: <insert_1> and port <insert_2>). Reason: <insert_3>
Explanation: The service was unable to listen for connections on the specified port
Response: Use the exception to diagnose and rectify the problem then restart the affected channel.

AMQXR0015I: <insert_0> Service started successfully (<insert_1> channels running, <insert_2> channels stopped). PID(<insert_3>).
Explanation: The service has completed the processing that occurs on startup
Response: No action is required.

AMQXR0016I: Channel <insert_0> has started
Explanation: This channel is now available for client connections
Response: No action is required

AMQXR0017I: A new channel (called <insert_0>) has been created
Explanation: In response to a request from a user, a new channel has been created
Response: No action is required

AMQXR0018I: Channel <insert_0> has been altered
Explanation: In response to a request from a user, some settings on the channel were changed. Some settings do not take effect until the channel is restarted.
Response: No action is required

AMQXR0019I: Channel <insert_0> has been deleted
Explanation: In response to a request from a user, a new channel has been deleted
Response: No action is required

AMQXR0020I: Channel <insert_0> has been purged
Explanation: Clients have been disconnected from this channel and state associated with them has been removed
Response: No action is required

AMQXR0021W: Client <insert_0> at network address <insert_1> disconnected abnormally with exception <insert_2>.
Explanation: An MQTT client was disconnected from the network for the reason shown by the exception.
Response: Look into the exception cause to determine what action is required.

AMQXR0022I: Client <insert_0> previously connected at network address <insert_1> now connected at <insert_2>.
Explanation: A new connection has been made for the client taking over from an existing one.
Response: None, if this was intentional.

AMQXR0023I: Unsupported MQTT protocol version on channel <insert_1>, the exception <insert_0> was thrown.
Explanation: An MQTT client attempted to connect using an unsupported protocol version, the connection is closed by the server.
Response: Re-configure the client to use a supported protocol version.

AMQXR0024I: A Telemetry Daemon for devices attempted to connect using its private protocol on channel <insert_1>, the exception <insert_0> was thrown.
Explanation: The Telemetry daemon for devices has a private protocol for communication. This protocol is not supported and the connection has been closed by the server.
Response: No user action is required, the daemon should reconnect with a supported protocol. To remove this message, re-configure the Telemetry daemon for devices to not use the private protocol for this connection.

AMQXR0025E: ClientIdentifier <insert_0> used an invalid destination name <insert_1>.
Explanation: The publication from the client was not able to be completed because the destination name was not valid.
Response: Change the destination name so that it is valid.

AMQXR0026E: Unsupported application data type <insert_0> character <insert_1>.
Explanation: The server does not support a message body of the type reported.
Response: Change the message body to be one of the supported types.

AMQXR0027E: Unsupported AMQP settle mode <insert_0>.
Explanation: The server does not support the given settle mode.
Response: Change the application to use one of the supported settle modes.

AMQXR0028E: Unsupported AMQP terminus expiry policy of <insert_0> .
Explanation: The server does not support the given expiry policy when supplying a time-to-live.
Response: Change the application to use the link-detach expiry policy.

AMQXR0029I: Unsupported MQTT V3.1.1 protocol version on channel <insert_1>, the exception <insert_0> was thrown.
Explanation: An MQTT client attempted to connect using an MQTT V3.1.1 protocol version, the connection is closed by the server.
Response: Re-configure the client to use a supported protocol version, or modify the channel definition to allow the MQTT V3.1.1 protocol.

AMQXR0030W: Invalid Will Message.
Explanation: The Will Message in the Connect packet is malformed, the client connection is closed by the server.
Response: Check the client application and make sure the will message has a non zero length topic name, and a valid Qos.

AMQXR0031E: Invalid application data, type <insert_0> value <insert_1>.

AMQXR0032E: ClientIdentifier <insert_0> has not specified an address to obtain the destination name.
Explanation: The publication from the client was not able to be completed because the to address property was not present.
Response: Set the to address property and ensure that it contains a valid destination name.

AMQXR0033E: A connection from <insert_1> for client identifier <insert_2> was rejected for channel <insert_0> because of CONNAUTH or CHLAUTH rule configuration. <insert_3>
Explanation: The AMQP channel rejected a connection attempt that failed to pass one or more CONNAUTH or CHLAUTH rules.
Response: View the reason for the authorization failure in the queue manager error logs. Examine the client eligibility and the CONNAUTH or CHLAUTH definitions and alter as appropriate.

AMQXR0034E: A connection from <insert_0> was rejected for channel <insert_1> because of CHLAUTH rule configuration.
Explanation: The AMQP channel rejected a connection attempt that failed to pass one or more CHLAUTH rules.
Response: View the reason for the CHLAUTH failure in the queue manager error logs. Examine the client eligibility and the CHLAUTH channel definitions and alter as appropriate.

AMQXR0035E: Client <insert_0> already in use.
Explanation: A connection cannot be made because the specified client identifier is already in use.
Response: Choose a different client identifier or contact the system administrator to resolve the problem.

AMQXR0036I: Blocked takeover of client <insert_0> from network address <insert_1> over channel <insert_2> by user <insert_3>. The client identifier is already in use from network address <insert_4> over channel <insert_5> for user <insert_6>.
Explanation: A new connection has been blocked because it specifies a client identifier that is already in use and the connection does not meet the configured criteria for client takeover.
Response: No action is required.

AMQXR0037E: Connection not possible because the maximum number of permitted clients are already connected.
Explanation: A connection cannot be made because the configured maximum number of client connections for the channel has already been reached.
Response: Either try again later or attempt to connect on a different channel.

AMQXR0038E: ClientIdentifier <insert_0> used an invalid reply-to address <insert_1>.
Explanation: The publication from the client was not able to be completed because the value of the reply-to address was not valid.
Response: Change the reply-to value to a plain topic string or a valid AMQP URL.

AMQXR0039E: An invalid client identifier <insert_0> was received from <insert_1> on channel <insert_2>.
Explanation: The AMQP service received a client identifier that is not valid because it contains too few, or too many characters, or the characters are not valid in a queue manager name.
Response: Change the client identifier to be less than 257 characters in length and to use valid characters.

AMQXR0040E: Connection to the queue manager has broken.
Explanation: The connection to the queue manager has been broken. This has most likely been caused by the queue manager being shutdown.
Response: Examine the logs to determine why the connection to the queue manager has been broken, and take any appropriate action. If the problem cannot be resolved contact your IBM support center.

AMQXR0041E: A connection from <insert_1> was rejected for channel <insert_0> because of CONNAUTH or CHLAUTH rule configuration. <insert_3>
Explanation: The service rejected a connection attempt that failed to pass one or more CONNAUTH or CHLAUTH tests
Response: View the reason for the authorization failure in the queue manager error logs. Examine the client eligibility and the CONNAUTH or CHLAUTH definitions and alter as appropriate.

AMQXR0042E: A subscribe request was not authorized for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The AMQP service rejected a subscription attempt that failed to pass one or more MQ authority checks.
Response: Ensure the queue manager authority records are set up to allow the MQ identity to subscribe to the specific topic. See the MQ error logs for detail of the MQ authority check that caused the connection to fail.

AMQXR0043E: An MQ object required by AMQP channel <insert_0> for a subscribe request from client <insert_1> could not be found. <insert_2>
Explanation: One of the MQ objects the AMQP channel expects to exist when creating or resuming a subscription could not be found.
Response: Ensure the system objects required exist on the queue manager. Check the MQ and AMQP error logs for detail of the missing object.

AMQXR0044E: A publish request was not authorized for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The AMQP service rejected a publish attempt that failed to pass one or more MQ authority checks.
Response: Ensure the queue manager authority records are set up to allow the MQ identity to publish to the specific topic. See the MQ error logs for detail of the MQ authority check that caused the connection to fail.

AMQXR0045E: A subscription request failed for channel <insert_0> received from <insert_1> because the combination of topic pattern and client ID exceeded 10230 characters. <insert_2>
Explanation: When a subscription request is made to an AMQP channel an MQ managed subscription is defined. The subscription name takes the format ':private:<client-id>:<topic-pattern>'. The maximum length of the MQ subscription name is 10240 characters. Reserved characters take up 10 characters of the subscription name. The combination of the topic pattern and the client ID must be less than 10230 characters.
Response: Reduce the length of the topic pattern or the client ID that the application uses and retry the operation.

AMQXR0046E: A shared subscription request failed for channel <insert_0> received from <insert_1> because the combination of topic pattern and share name exceeded 10232 characters. <insert_2>
Explanation: When a shared subscription request is made to an AMQP channel an MQ managed subscription is defined. The subscription name takes the format ':share:<share-name>:<topic-pattern>'. The maximum length of the MQ subscription name is 10240 characters. Reserved characters take up 8 characters of the subscription name. The combination of the topic pattern and the share name must be less than 10232 characters.
Response: Reduce the length of the topic pattern or the share name that the application uses and retry the operation.

AMQXR0047E: A subscription request failed for channel <insert_0> received from <insert_1> because a zero-length topic pattern was specified. <insert_2>
Explanation: A topic pattern must be specified when subscribing to a destination.
Response: Ensure your application specifies a topic pattern to subscribe to and retry the operation.

AMQXR0048E: An unknown error occurred during a subscription request for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The queue manager failed to handle the subscribe request from an AMQP client.
Response: Check the MQ return code included in the error message. Check the MQ logs or FFDC files for more information.

AMQXR0049E: A connection from <insert_0> was rejected because the connection could not be authenticated.
Explanation: The AMQP channel rejected a connection attempt that failed to pass a JAAS authentication step.
Response: Review the queue manager logs and check that your JAAS configuration is correct.

AMQXR0050E: A connection from <insert_0> was rejected because no MQ identity could be found.
Explanation: When a client connects to an AMQP channel, an MQ identity is required to check that the client has authority to publish and subscribe. No MQ identity has been configured for the AMQP channel.
Response: Ensure an MQ identity is set for the AMQP channel. Configure one or more of the following MQ features: the MCAUSER of the AMQP channel; the USECLTID attribute of the AMQP channel; a channel authentication rule that sets the MQ identity to use for the channel.

AMQXR0051E: A connection from <insert_0> was rejected for channel <insert_1> because the SSL distinguished name <insert_2> does not match the channel's peer name <insert_3>.
Explanation: The AMQP channel rejected a connection attempt because the distinguished name contained in the SSL certificate for the client end of the channel does not match the local SSL peer name for the channel.
Response: If the client should be allowed to connect, either change the channel SSL peer name specification so that it matches the distinguished name in the SSL certificate for the client, or obtain the correct certificate for the client end of the channel.

AMQXR0063I: The AMQP channel that the client is connected to has been stopped.
Explanation: The system administrator has stopped the AMQP channel that the client was connected to. As a result the client connection has been terminated.
Response: If this was unexpected, contact the MQ system administrator to understand why AMQP channel was stopped.

AMQXR0064I: The AMQP channel that the client is connected to is being restarted.
Explanation: The system administrator is restarting the AMQP channel that the client was connected to. As a result the client connection has been terminated. The AMQP channel might be being restarted because of a configuration change.
Response: If this was unexpected, contact the MQ system administrator to understand why AMQP channel is being restarted.

AMQXR0065E: Supplied AMQP source timeout of <insert_0> is greater than the permitted server maximum of <insert_1>.
Explanation: The server does not permit the given timeout.
Response: Change the application to supply a shorter timeout value.

AMQXR0066E: sasl mechanisms of client and server must match.
Explanation: The remote sasl mechanism does not match the server mechanism.
Response: Change the application to use the same sasl mechanism as the server.

AMQXR0082E: Authentication failure. The user name or client identifier <insert_0> received from <insert_2> on channel <insert_3>, exceeds the maximum supported length of <insert_1> characters.
Explanation: The server cannot support the supplied user name or client identifier because it exceeds the maximum supported length. If the channel has the USERCLTID parameter set to YES then it is the supplied client identifier that exceeds the maximum supported length. If the channel has the MCAUSER parameter set to a nonblank value then this is the user name that exceeds the maximum supported length. Otherwise it is the user name supplied to the connection request that exceeds the maximum supported length.
Response: Either reconfigure the channel as appropriate or attempt to reconnect with a different user name or client identifier that does not exceed the maximum supported length.

AMQXR0083E: Channel parameter MCAUSER exceeds the maximum supported length of <insert_0> characters.
Explanation: The server cannot support the specified value for the MCAUSER channel parameter because it exceeds the maximum supported length.
Response: Reconfigure the channel to specify a MCAUSER channel parameter value that is 12 characters or less.

AMQXR0084E: An attempt to alter a subscription to topic <insert_2> was not authorized for channel <insert_0> received from <insert_1>. <insert_3>
Explanation: The AMQP service rejected an attempt to alter a subscription to a topic.
Response: Ensure the queue manager authority records are set up to allow the MQ identity to subscribe to the specific topic. See the MQ error logs for detail of the MQ authority check that caused the alter to fail.

AMQXR0100E: A connection from <insert_0> was not authorized.
Explanation: An attempt to connect to an AMQP channel was rejected because the connection failed one or more authentication or authorization checks.
Response: A detailed explanation of the reason why the connection was refused can be found in the queue manager logs. Contact the system administrator to determine the cause of the failure.

AMQXR0101E: A request by client <insert_0> to subscribe to topic <insert_1> was not authorized. <insert_2>
Explanation: An attempt to connect to an AMQP channel was rejected because the connection failed one or more authentication or authorization checks.
Response: A detailed explanation of the reason why the connection was refused can be found in the queue manager logs. Contact the system administrator to determine the cause of the failure.

AMQXR0102E: A request by client <insert_0> to publish to topic <insert_1> was not authorized. <insert_2>
Explanation: An attempt to connect to an AMQP channel was rejected because the connection failed one or more authentication or authorization checks.
Response: A detailed explanation of the reason why the connection was refused can be found in the queue manager logs. Contact the system administrator to determine the cause of the failure.

AMQXR0103I: The service has shut down because the QM process is no longer available.
Explanation: The service was unable to communicate with the queue manager and has shut down as a result.
Response: No action is required.

AMQXR0104E: A client attempted to unsubscribe but an active subscription could not be found.
Explanation: An AMQP client attempted to unsubscribe from a topic it is not subscribed to.
Response: Check that the application logic is correct, and check for earlier errors that could have caused the application to get into an inconsistent state. If the client is using the JMS API ensure it is not calling unsubscribe for a non-durable subscription.

AMQXR0105E: AMQP filters not supported (<insert_0>).
Explanation: The server does not support AMQP source filters.
Response: Change the application so that it does not specify an AMQP source filter. Alternatively set the system property com.ibm.mq.MQXRService.ignoreamqpunsupported=true to ignore the filter.

AMQXR0106E: The user ID and password for the client application <insert_0> running on host <insert_1> cannot be checked by the queue manager.
Explanation: The user ID and password for the client application cannot be checked. The channel authentication (CHLAUTH) record for the connection requires an authentication check, but the queue manager is not configured to use connection authentication for clients.
Response: Change the CHLAUTH configuration so that client authentication is not required, or alter the queue manager connection authority (CONNAUTH) configuration to enable client authentication checks.

AMQXR0107E: The queue manager is not available.
Explanation: The queue manager is not available for AMQP connections. The most likely reason is because the queue manager is still being started.
Response: Wait a few seconds to allow the queue manager to complete startup, then retry the connection.

AMQXR0108E: The client user ID <insert_0> is unsupported. The maximum supported user ID length is <insert_1>
Explanation: The client application user ID is greater then length of maximum supported user ID length
Response: Ensure that the client application user ID length is within the supported range.

AMQXR1002E: MQTTV5Exception message=<insert_0>(String).
Explanation: An instance of com.ibm.mqtt.encoding.internal.MQTTException has been caught and wrapped.
Response: Contact your IBM support center.

AMQXR1003E: An invalid message type=<insert_0>(byte) was received.
Explanation: An invalid MQTT message type was received. The connection is disconnected.
Response: The client connected to the service is sending invalid MQTT messages. Find out what client has connected to the service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the IBM MQ installation, contact your IBM support center.

AMQXR1004E: An invalid message version=<insert_0>(byte) subVersion=<insert_1>(byte)was received.
Explanation: An invalid MQTT message version was received. The connection is disconnected.
Response: The client connected to the service is sending invalid MQTT messages. Find out what client has connected to the service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the IBM MQ installation, contact your IBM support center.

AMQXR1005E: An invalid message was received. first fixed header byte=<insert_0>(Hex) remaining length=<insert_1>(Decimal) message=<insert_2>(Hex)
Explanation: An invalid MQTT message was received. The connection is disconnected.
Response: The client connected to the service is sending invalid MQTT messages. Find out what client has connected to the service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the IBM MQ installation, contact your IBM support center.

AMQXR1006E: An MQTT message with an invalid MultiByteLength=<insert_0>(long) was received.
Explanation: An invalid MQTT message containing an invalid multi-byte length was received. The connection is disconnected.
Response: The MQTT client application might have sent incorrect data, which is interpreted as an incorrect length. Check your MQTT client application, and verify that it is sending correct data. Contact the provider of the client code. If you are using a client provided in the IBM MQ installation, contact your IBM support center.

AMQXR1007E: An invalid Attribute type=<insert_0>(int) was found.
Explanation: An invalid MQTT attribute was found processing of this message is abandoned and the connection closed.
Response: Gather diagnostics and contact your IBM support center.

AMQXR1008E: An invalid mapped message was detected because of <insert_0>(String).
Explanation: An invalid Mapped message was found, it cannot be processed.
Response: Determine where the message came from and correct the messages so that they are not mapped messages or are created with the correct format.

AMQXR1009E: An invalid WebSocket message was detected because of <insert_0>(String).
Explanation: An invalid WebSocket message was found, it cannot be processed.
Response: Determine where the message came from and correct the messages so that they are correctly formed.

AMQXR1010E: An invalid message qos=<insert_0>(int) was received.
Explanation: An invalid MQTT qos was received.
Response: The client connected to the service is sending invalid MQTT messages. Find out what client has connected to the service and what data it has sent. Contact the provider of the client code. If you are using a client provided in the IBM MQ installation, contact your IBM support center.

AMQXR1011E: MQTTV3Exception message=<insert_0>(String).
Explanation: An instance of com.ibm.mqttv3.internal.MQTTException has been caught and wrapped.
Response: Contact your IBM support center.

AMQXR1013E: An attempt was made by <insert_0>(Object) to use name <insert_1>(String) when it is already in use by <insert_2>(Object).
Explanation: The attempt is rejected.
Response: Use a different name or delete the existing object that uses the name.

AMQXR1014E: Method=<insert_0>(String) cannot be invoked on object=<insert_1>(String) while in state=<insert_2>(String).
Explanation: An invalid action was attempted in the state.
Response: Do not attempt the operation in the state shown.

AMQXR1015E: Argument=<insert_0>(String) is not valid for method=<insert_1>.
Explanation: An illegal argument was passed to the method.
Response: Examine the argument and provide a correct value.

AMQXR1016W: <insert_0>(Object) discovered that most of the available memory has been used.
Explanation: The XRService will attempt to shed load, typically by disconnecting some clients.
Response: Reduce the workload or provide more memory.

AMQXR1017E: MQTTV311Exception message=<insert_0>(String).
Explanation: An instance of com.ibm.mqttv311.internal.MQTTException has been caught and wrapped.
Response: Contact your IBM support center.

AMQXR2001E: The command to end the service failed connecting to queue manager <insert_0>. Exception: <insert_1>
Explanation: The administrative layer could not connect to the queue manager.
Response: If the queue manager is no longer running, no action is required. If the queue manager is still running, check why the administrative layer is unable to connect.

AMQXR2002E: The command to end the service failed opening queue <insert_0>. Exception: <insert_1>
Explanation: The administrative layer could not open the queue that is required to send a request end the service.
Response: Determine why the queue could not be opened and retry stopping the service.

AMQXR2003E: The command to end the service failed: Failed Operation: <insert_0> Exception (<insert_1>): <insert_2>
Explanation: The administrative layer failed to put or get a message that is required to stop the service.
Response: Correct the problem and then try stopping the service again.

AMQXR2004E: An error occurred while stopping the service. Completion Code: <insert_0> Reason: <insert_1>
Explanation: An error occurred while the service was shutting down.
Response: Use the reason code to diagnose the problem.

AMQXR2005E: An error occurred while releasing queue manager resources. Object: <insert_0> Exception: <insert_1>
Explanation: While cleaning up resources the EndMQXRService command encountered a transient problem.
Response: No action is required.

AMQXR2010E: The service could not access the file: <insert_0>. Exception: <insert_1>
Explanation: The file is invalid, has an invalid format, or incorrect permissions.
Response: Check the file permissions and ensure the file is valid.

AMQXR2011I: Property <insert_0> value <insert_1>
Explanation: The runMQXRService command has read a property with the assigned value.
Response: No action is required.

AMQXR2012E: Invalid property key=<insert_0> value=<insert_1>
Explanation: The runMQXRService command read an incorrect properties file.
Response: Look at the property in error, correct it, and reissue the command.

AMQXR2013E: Duplicate authentication methods specified for channel=<insert_0>, previous=<insert_1> duplicate=<insert_2>
Explanation: The runMQXRService command read a properties file that specifies two authentication methods, only one is allowed.
Response: Look at the properties file and locate the definition of the named channel. Correct the file to specify a single authentication method and restart the channel.

AMQXR2014E: The following error occurred during the starting of an MQXR channel, channelName = <insert_0> : <insert_1>
Explanation: An MQXR channel was starting up but encountered a problem. Earlier errors or FDCs will provide more detail.
Response: Use earlier errors or FDCs to diagnose and address the problem then restart the MQXR channel.

AMQXR2015E: The following error occurred during the stopping of an MQXR channel, channelName = <insert_0> : <insert_1>
Explanation: An MQXR channel was stopping but encountered a problem. Earlier errors or FDCs will provide more detail.
Response: Use earlier errors or FDCs to diagnose and address the problem then restart the MQXR channel.

AMQXR2016E: Failed to rename <insert_0> to <insert_1>
Explanation: The file could not be renamed
Response: Look at the permissions on the target file and directory and alter them if necessary

AMQXR2017E: The service could not synchronize with the backing store preferences. Reason: <insert_0>
Explanation: The loaded service preferences have been updated, but it has not been possible to synchronize with the store (typically the source properties file).
Response: Check the file permissions on the properties file and ensure that it can be read and written to. If the problem persists, contact your IBM support center.

AMQXR2018W: The service could not set the group for service configuration file to mqm. Exception: <insert_0>
Explanation: There was an error setting the group of the files to mqm.
Response: Check that the mqm group exists on the system.

AMQXR2019W: Unable to reply to MQ command <insert_0> because the reply queue has been deleted.
Explanation: A reply to an MQ command will not be waited on indefinitely. Hence if an MQ command is not replied to in a timely manner then the reply queue may have been deleted, resulting in a MQRC_Q_DELETED error. This normally should not cause an error as the invoking application would have already given up waiting for the reply.
Response: Check the queue manager logs and error logs for any unexpected errors and take the necessary action. Also this problem maybe the result of a command issued from an application, such as runmqsc. Check any application output or logs for errors that may have been caused by the reply not being received.

AMQXR2020E: Client <insert_0> attempted to unsubscribe from the topic <insert_1> which it is not subscribed to.
Explanation: An MQTT client attempted to unsubscribe from a topic it is not subscribed to.
Response: Check that the application logic is correct, and check for earlier errors that could have caused the application to get into an inconsistent state.

AMQXR2021E: Client <insert_0> attempted to unsubscribe from the queue <insert_1> which it is not subscribed to.
Explanation: An MQTT client attempted to unsubscribe from a queue it is not subscribed to.
Response: Check that the application logic is correct, and check for earlier errors that could have caused the application to get into an inconsistent state.

AMQXR2022S: Client <insert_0> failed to commit a transaction.
Explanation: The queue manager failed to commit a unit of work, and FFDC will have been written but the client is disconnected.
Response: Determine the cause of the transaction commit failure, correct it and reconnect the client.

AMQXR2023S: Failed to commit a transaction for client connection.
Explanation: The queue manager failed to commit a unit of work, and FFDC will have been written but the client will not have been connected.
Response: Determine the cause of the transaction commit failure, correct it and attempt to connect the client again.

AMQXR2050E: Unable to load JAAS config: <insert_0>. The following exception occurred <insert_1>
Explanation: The JAAS configuration tried to authenticate a user on a connection that was unable to load
Response: Check that the JAAS config selected by the channel exists in the jaas.config file and is valid.

AMQXR2051E: Login failed for ClientIdentifier <insert_0> with exception <insert_1>.
Explanation: The JAAS login failed with the exception shown.
Response: Check that the username and password sent by the client are correct.

AMQXR2052E: The TPROOT attribute for channel <insert_0> specifies topic name: <insert_1>, which is not a local topic. This is not supported.
Explanation: The topic specified for the channel's TPROOT attribute is not a local topic. Only local topics can be used for the TPROOT attribute.
Response: The MQ system administrator should update the channel's TPROOT attribute value to specify a valid local topic and restart the channel.

AMQXR2053E: Error in a trace factory. The following exception occurred <insert_1>
Explanation: There was a problem starting or stopping trace.
Response: Use the exception to diagnose and rectify the problem and then restart trace.

AMQXR2054E: Login failed on channel <insert_0>, no MCA user identity could be resolved.
Explanation: The AMQP channel is not configured with an MQ user identity. An MCA user identity is required so that MQ can complete the relevant authority checks.
Response: Configure one or more of the following MQ features: the MCAUSER of the AMQP channel; the USECLTID attribute of the AMQP channel; a channel authentication rule that sets the MQ identity to use for the channel.

AMQXR2055E: The TPROOT attribute for channel <insert_0> specifies an unknown topic name: <insert_1> (MQ reason code: <insert_2> <insert_3>)
Explanation: The configured TPROOT attribute for the AMQP channel does not reference a known topic or the topic could not be accessed. Use the given MQ reason code information to understand the actual cause of the error.
Response: The MQ system administrator should update the channel's TPROOT attribute value to specify a valid topic name and restart the channel.

AMQXR2056E: The connection to the queue manager has been terminated.
Explanation: The connection to the queue manager has been terminated by the system administrator or has been terminated because of a queue manager connection issue.
Response: If this was unexpected the MQ system administrator should be contacted to understand why the connection to the queue manager was terminated. If this was not a deliberate action, the MQ system administrator should examine the queue manager logs to understand the reason.

AMQXR2057E: The AMQP channel that the client is connected to has been purged.
Explanation: The system administrator has purged the AMQP channel that the client was connected to and as a result the client connection has been terminated.
Response: If this was unexpected, contact the MQ system administrator to understand why AMQP channel was purged.

AMQXR2058E: A message from client <insert_0> has been rejected. Reason: <insert_1>
Explanation: A message from the identified client was rejected because of an illegal state.
Response: Examine the reason for the error and take appropriate action. If the problem cannot be resolved contact your IBM support center.

AMQXR2059E: A message from client <insert_0> has been rejected because of a message decoding problem. Reason: <insert_1>
Explanation: A message from the identified client was rejected because the message could not parsed because of the given reason.
Response: Examine the reason for the error and take appropriate action.

AMQXR2060E: A message from client <insert_0> has been rejected because the specified AMQP message-id property <insert_1> has been specified with a data type of <insert_2>, which is not supported.
Explanation: A message from the identified client was rejected because the message contains an AMQP message-id property with a data type that is not supported. Only an AMQP message-id property with a data type of String or Binary is currently supported.
Response: Examine the reason for the error and take appropriate action.

AMQXR2061E: A message from client <insert_0> has been rejected because the specified AMQP correlation-id property <insert_1> has been specified with a data type of <insert_2>, which is not supported.
Explanation: A message from the identified client was rejected because the message contains an AMQP correlation-id property with a data type that is not supported. Only an AMQP correlation-id property with a data type of String or Binary is currently supported.
Response: Examine the reason for the error and take appropriate action.

AMQXR2062E: The following exception was thrown whilst refreshing SSL security: <insert_0>
Explanation: The MQXR Listener was requested to refresh SSL security but an error was encountered.
Response: Examine the reason for the error and take appropriate action. Then attempt the SSL refresh security operation again. If the problem cannot be resolved contact your IBM support center.

AMQXR2065E: A message from client <insert_0> has been rejected because it exceeds the maximum message size of <insert_1>.
Explanation: A message from the identified client was rejected because it exceeds the MAXMSGL attribute of the channel, the queue manager or the destination queue.
Response: If you wish to allow messages of this size to be sent by AMQP clients, ensure that the MAXMSGL attribute of the channel, the queue manager and the destination queue (which may be the model queue used to create subscription destinations) is increased to a large enough value. Some of the MQ message is taken up message properties so the MAXMSGL may need to be larger than the size of the message data.

AMQXR2066E: A message for client <insert_0> could not be delivered because it is too big.
Explanation: When the AMQP client attached a link to subscribe for messages it specified a value for max-message-size. The value is too small to receive one or more messages published on the topic.
Response: If the client cannot consume messages larger than the size set for the max-message-size attribute, ensure publishing applications do not publish messages greater than that size. Alternatively increase the value of max-message-size.

AMQXR2067E: An attempt to publish a last will and testament message from Client Identifier <insert_0> on channel <insert_1> failed as the user identifier <insert_2> performing the operation was not authorized to access the topic <insert_3>.
Explanation: The last will and testament message could not be published.
Response: Ensure that the user id used to publish the message is authorized to access the last will and testament topic.

AMQXR2068W: Channel <insert_0> attribute MCAUSER has not been set.
Explanation: The MCAUSER attribute for the channel specifies the user for authorization to access IBM MQ resources. If this is not set then the user for authorization to access IBM MQ resources will be determined by the client identity.
Response: To improve channel security it is recommended to configure the MCAUSER channel attribute to specify an authorized user with suitably restricted access.

AMQXR2069W: No required authentication method set for channel <insert_0>. Client connections might be unauthenticated.
Explanation: The channel is configured to not authenticate, or optionally authenticate, clients on connection.
Response: To improve channel security it is recommended to configure the JAASCFG channel attribute (MQTT channels only) or, with SSL/TLS enabled, set the SSLCAUTH channel attribute to REQUIRED.

AMQXR2070W: No SSL/TLS configuration set for channel <insert_0>. Client data over the channel will not be encrypted.
Explanation: The channel is configured to not encrypt data when communicating with clients.
Response: To communicate securely with clients it is recommended to configure SSL/TLS for the channel by setting the SSLCIPH, SSLKEYR and SSLKEYP channel attributes appropriately.

AMQXR2071W: Unable to set collection usage threshold to <insert_1> for memory pool <insert_0>. Maximum allowed value for the pool is <insert_2>
Explanation: The system monitors memory usage such that if it becomes low on available memory some client connections are automatically terminated in an attempt to free memory resource and allow the system to continue operation. For the named memory pool it has not been possible to set a collection usage threshold, which is the mechanism required to enable the memory monitoring function for a pool.
Response: If the problem persists then contact your IBM support center.

AMQXR2072E: The AMQP service task scheduler limit has been exceeded.
Explanation: The AMQP service only queues up a certain number of asynchronous tasks. When that limit is reached, new tasks are rejected. This can occur if too many client applications attempt to connect at the same time.
Response: Try the client connection attempt again at a later time.

AMQXR2073E: No password has been specified to access the TLS key repository. Specify the password using the queue manager attribute 'KEYRPWD'.
Explanation: A password has not been provided to access the TLS key repository.
Response: Provide the password to access the TLS key repository using the queue manager attribute 'KEYRPWD'.

AMQXR2074E: A TLS key repository has not been specified to configure SSL. Specify the TLS key repository using the queue manager attribute 'SSLKEYR'.
Explanation: A TLS key repository has not been specified to configure SSL.
Response: Provide the key repository to configure SSL using the queue manager attribute 'SSLKEYR'.

AMQXR2080E: Required channel parameter <insert_0> is missing.
Explanation: The identified channel parameter must be set for a valid channel configuration.
Response: Ensure the identified channel parameter is set. If the problem persists then contact your IBM support center.

AMQXR2081E: Channel parameter USECLTID is set to YES and MCAUSER is nonblank. This is not permitted.
Explanation: Channel authentication is performed using either the client user identifier (when channel parameter USECLTID is set to YES), the MCA user identifier (when channel parameter MCAUSER is set to a nonblank value), or the default for the channel. Hence if USECLTID is set to YES and MCAUSER is nonblank it causes a conflict.
Response: Change either of the USECLTID or MCAUSER channel parameters as required, and restart the channel.

AMQXR2085E: A message received from Client Identifier <insert_0> on channel <insert_1> contained invalid UTF-8 encoded textual data. The client has been disconnected.
Explanation: The message contains textual data, UTF-8 encoded, using a character set that is invalid within the MQTT specification.
Response: Work with the user running the MQTT client application, and ensure that the messages that it sends are valid within the MQTT specification. For more information on valid and not valid characters, please refer to the MQTT documentation.

AMQXR2086I: Topic string of a message received from user identifier <insert_0> contained invalid UTF-8 encoded textual data. The message has been discarded.
Explanation: The Topic of the message contains code points that are not valid within the MQTT specification.
Response: Work with the user running the publishing client application, and ensure that the messages that it sends are valid within the MQTT specification. For more information on valid and not valid characters, please refer to the MQTT documentation.

AMQXR2087I: Client with identifier <insert_0> at network address <insert_1> sent an unexpected MQTT packet causing a protocol error: state: <insert_2> previousState: <insert_3>
Explanation: The MQTT client sent a MQTT protocol message when it was not expected, based on the specification.
Response: Use a version of the MQTT client that does not send MQTT protocol messages at unexpected times.

AMQXR2090E: An unexpected error has occurred on the server.
Explanation: The server has encountered an unexpected error and written details to the error log.
Response: Contact the MQ system administrator for further investigation. If the problem cannot be resolved contact your IBM support center.

AMQXR2091E: An error occurred putting a message to queue <insert_3> from ClientIdentifier <insert_0> UserName <insert_1> on channel <insert_2>. A reason code of <insert_5> <insert_6> was received during an <insert_4> operation for object <insert_7>.
Explanation: The put from the client was not able to be completed.
Response: Using the reason code, diagnose the cause of the problem, alter the configuration (of the client or the server as appropriate) and then retry the operation.

AMQXR2092E: Put message request was not authorized for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The AMQP service rejected a put attempt that failed to pass one or more MQ authority checks.
Response: Ensure the queue manager authority records are set up to allow the MQ identity to put to the specific queue. See the MQ error logs for detail of the MQ authority check that caused the connection to fail.

AMQXR2093E: A request by client <insert_0> to put a message to queue <insert_1> was not authorized. <insert_2>
Explanation: An attempt to connect to an AMQP channel was rejected because the connection failed one or more authentication or authorization checks.
Response: A detailed explanation of the reason why the connection was refused can be found in the queue manager logs. Contact the system administrator to determine the cause of the failure.

AMQXR2094E: An error occurred getting a message from queue <insert_3> for ClientIdentifier <insert_0> UserName <insert_1> on channel <insert_2>. A reason code of <insert_5> <insert_6> was received during an <insert_4> operation for object <insert_7>.
Explanation: The get from the client was not able to be completed.
Response: Using the reason code, diagnose the cause of the problem, alter the configuration (of the client or the server as appropriate) and then reconnect the client and retry the operation.

AMQXR2095E: A get message request from queue <insert_3> was not authorized for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The AMQP service rejected a get attempt that failed to pass one or more MQ authority checks.
Response: Ensure the queue manager authority records are set up to allow the MQ identity to get from the specific queue. See the MQ error logs for detail of the MQ authority check that caused the connection to fail.

AMQXR2096E: A request by client <insert_0> to get a message from queue <insert_1> was not authorized. <insert_2>
Explanation: An attempt to connect to an AMQP channel was rejected because the connection failed one or more authentication or authorization checks.
Response: A detailed explanation of the reason why the connection was refused can be found in the queue manager logs. Contact the system administrator to determine the cause of the failure.

AMQXR2097E: An MQ queue <insert_3> required by AMQP channel <insert_0> for a get message request from client <insert_1> could not be found. <insert_2>
Explanation: One of the MQ objects the AMQP channel expects to exist when creating or resuming a get could not be found.
Response: Ensure the system objects required exist on the queue manager. Check the MQ and AMQP error logs for detail of the missing object.

AMQXR2098E: An unknown error occurred during a get message request for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The queue manager failed to handle the get request from an AMQP client.
Response: Check the MQ return code included in the error message. Check the MQ logs or FFDC files for more information.

AMQXR2099E: An error occurred while creating Temporary Queue from ClientIdentifier <insert_0> UserName <insert_1> on channel <insert_2>. A reason code of <insert_3> <insert_4> was received during an <insert_5> operation.
Explanation: The client failed to create a Temporary Queue.
Response: Using the reason code, diagnose the cause of the problem and as appropriate alter the configuration of the client or contact the MQ system administrator to alter the configuration of the server. Then retry the operation.

AMQXR2100E: CreateTemporaryQueue request was not authorized for channel <insert_0> received from <insert_1>. <insert_2>
Explanation: The AMQP service rejected a CreateTemporaryQueue attempt that failed to pass one or more MQ authority checks.
Response: Ensure the queue manager authority records are set up to allow the MQ identity to create a Temporary Queue. See the MQ error logs for detail of the MQ authority check that caused the connection to fail.

AMQXR2101E: ClientIdentifier <insert_0> rejected the message because the state of the AMQP message was modified.
Explanation: The client had rejected the message and marked it as undeliverableHere, because of an invalid attribute value in the AMQP message.
Response: If the problem persists then contact your IBM support center.

AMQXR2102E: An MQ message for client <insert_0> did not have the required MQHRF2 header, and has been discarded.
Explanation: The MQ message received by the AMQP service for the specified client did not contain an MQHRF2 header. As the header was not available, the AMQP service was unable to build a corresponding AMQP message to send to the client. The MQ message has been discarded.
Response: Contact your IBM support center.

AMQXR2103E: MQ message with message id <insert_0> for client <insert_1> did not have the required MQHRF2 header, and has been discarded.
Explanation: The MQ message received by the AMQP service for the specified client did not contain an MQHRF2 header. As the header was not available, the AMQP service was unable to build a corresponding AMQP message to send to the client. The MQ message has been discarded.
Response: Contact your IBM support center.

AMQXR2104E: An error occurred while starting the <insert_1> service because command queue <insert_0> is in use.
Explanation: The service was unable to open the specified queue. It is likely another service is already running.
Response: Check if another service is already running and stop it first, if this service needs to be started. If no service is running then investigate why the queue is open on another application (the service requires exclusive access to the queue). If the problem cannot be resolved contact your IBM support center.

AMQXR2105E: The TMPMODEL attribute for channel <insert_0> specifies queue name: <insert_1>, which is not a model queue. This is not supported.
Explanation: The queue specified for the channel's TMPMODEL attribute is not a model queue. Only model queues can be used for the TMPMODEL attribute.
Response: The MQ system administrator should update the channel's TMPMODEL attribute value to specify a valid model queue and restart the channel.

AMQXR2106E: The TMPMODEL attribute for channel <insert_0> specifies an unknown model queue name: <insert_1> (MQ reason code: <insert_2> <insert_3>)
Explanation: The configured TMPMODEL attribute for the AMQP channel does not reference a known model queue or the model queue could not be accessed. Use the given MQ reason code information to understand the actual cause of the error.
Response: The MQ system administrator should update the channel's TMPMODEL attribute value to specify a valid model queue name and restart the channel.

AMQXR2107E: Authentication type <insert_0> for authentication information <insert_1> is not supported.
Explanation: The specified authentication type is not supported.
Response: Change the authentication information object so that it uses an authentication type that is supported.

AMQXR2108E: Connection name provided in CRLLDAP authentication information object <insert_0> is not valid.
Explanation: The connection name format provided in the CRLLDAP authentication information object is not correct.
Response: Correct the connection name for the CRLLDAP authentication information object.

AMQXR2109E: URL provided in OCSP authentication information object <insert_0> is not valid.
Explanation: The URL format provided in the OCSP authentication information object is not correct.
Response: Correct the URL for the OCSP authentication information object.

AMQXR2110E: Unable to access the key file <insert_0> for encryption or decryption of channel passphrases. The exception was<insert_1>.
Explanation: The supplied key file for encryption or decryption of channel passphrases could not be accessed by the MQXR service. This could be because the file is not present in the specified location or the process does not have sufficient privileges to read the file.
Response: Ensure the key file for encryption or decryption of channel passphrases is valid and accessible by the MQXR service.

AMQXR2111W: Channel <insert_0> is using a plain text passphrase.
Explanation: The SSL channel passphase is stored in plain text.
Response: We recommend MQXR SSL channel passphrases be encrypted. Follow the IBM documentation procedure for encrypting the passphrase.

AMQXR2112E: Specified credentials key file <insert_0> is empty or has multiple lines. Credentials key files must contain a valid key.
Explanation: The credentials key file must contain only one line of credential key data.
Response: Correct the credentials key file and restart the MQXR service.

AMQXR2113E: An error occurred while encrypting the passphrase for channel <insert_0>. The exception was <insert_1>.
Explanation: An error occurred while encrypting the passphrase for the channel.
Response: Verify that a valid key file is provided for the MQXR service and try updating the channel passphrase. The channel will then need to be attempted to be started again.

AMQXR2114W: An MQ message contained a SubUserData field in its MQHRF2 header which contained invalid data. The message has been delivered but may have been delivered with an incorrect quality of service, or to a client that specified noLocal publications.
Explanation: MQTT subscriptions store information in the USERDATA field of the subscription. A message was received that contained unexpected data in the USERDATA field of the subscription.
Response: Ensure that the USERDATA field of MQTT subscriptions has not been modified. It may be necessary to recreate the MQTT subscriptions of any where the USERDATA field has been modified.

AMQXR2115W: Attempt to resume subscription <insert_0> failed because the requested topic string <insert_1> did not match the administered sub topic string <insert_2>.
Explanation: Attempt to resume subscription failed because the requested topic string didn't match the administered sub topic string.
Response: Verify that the requested topic string matches the administered sub topic object.

AMQXR2116E: TCP/IP connection request for channel <insert_0> is suppressed.
Explanation: Channel is suppressed as it does not use a secure communications protocol. The queue manager has been configured to only accept TCP/IP communications proposals that use a supported secure communications protocol.
Response: Configure the peer to use a secure protocol by setting a valid CipherSpec value on the channel definition.

AMQXR2117W: Rejected message from client <insert_0> has been deleted. Reason: <insert_1>
Explanation: A message was rejected by client. Rejected Message is deleted from the queue.
Response: Examine the reason for the error and take appropriate action.

AMQXR2118W: Rejected message from client <insert_0> has been released back on queue. Reason: <insert_1>
Explanation: A message was rejected by client. Rejected Message is released back to queue.
Response: Examine the reason for the error and take appropriate action.

AMQXR2119W: The value for property <insert_0> is not valid. The value must be in the range <insert_1> to <insert_2>. The default value <insert_3> will be used.
Explanation: The value of the given property must be an integer within the accepted range.
Response: Update the property value to an integer value in the range given and restart the service.

AMQXR2120I: The value for property <insert_0> is set to <insert_1>.
Explanation: For AMQP consumer application with qos=1, acknowledged messages are removed in batch based on this value.
Response: None

AMQXR2121W: Unable to set MQ message correlation ID from <insert_0>. Reason <insert_1>.
Explanation: Either an attempt was made to specify a correlation ID which starts with the prefix ID but is not followed by a well-formed hexadecimal value, or an attempt was made to receive a message which contains an MQRFH2 property of type bin.hex that does not have a well-formed hexadecimal value.
Response: Ensure that a valid hexadecimal value always follows the ID prefix when setting correlation ID values. Ensure that any MQRFH2 headers generated by non-JMS applications are well-formed.

AMQXR2122E: An unsubscribe request from client <insert_1>(<insert_2>)' failed on channel <insert_0> because the client specified an invalid Topic Filter <insert_3>.
Explanation: A valid topic filter must be specified when unsubscribing to a destination.
Response: Ensure the application specifies a valid topic filter to unsubscribe to and retry the operation.

AMQXR2123E: Exception <insert_0> occurred and the connection to the client <insert_1> at network address <insert_2> connected to channel <insert_3> was closed.
Explanation: The connection to the client has been closed by the server due to an unexpected exception.
Response: Examine the reason for the error and take appropriate action.

AMQXR2124W: Thread <insert_0> was unable to add <insert_1> operations for client <insert_2> to its internal transaction. [Current operations: <insert_3>. Maximum number of operations: <insert_4>. Current subscription operations: <insert_5>. Maximum number of subscription operations: <insert_6>]
Explanation: Internal worker threads have a limit on the number of MQ operations that can be made within a single unit of work or transaction while performing some work for the specified client, the thread detected that its internal transaction did not have enough space for the MQ operations it needed to do.
Response: Increase the value of the properties com.ibm.mq.MQXR.MaximumOperationsPerBatch and com.ibm.mq.MQXR.MaximumSubscriptionOperationsPerBatch to ensure the transaction has enough space for the number of operations that need to be performed. If the issue persists after doing this, contact your IBM support center.

AMQXR2125E: SSLFIPS property is set to YES in the Queue Manager configuration but the FIPS 140-3 JVM system properties -Dsemeru.fips=true and -Dsemeru.customprofile=OpenJCEPlusFIPS are not set in the <insert_0> file.
Explanation: Both the SSLFIPS property and the FIPS 140-3 JVM system properties -Dsemeru.fips=true and -Dsemeru.customprofile=OpenJCEPlusFIPS need to be enabled for FIPS 140-3 support.
Response: Ensure the SSLFIPS property is set on the Queue Manager along with enabling the FIPS 140-3 JVM system properties -Dsemeru.fips=true and -Dsemeru.customprofile=OpenJCEPlusFIPS.

AMQXR2126E: The FIPS 140-3 JVM system properties -Dsemeru.fips=true and -Dsemeru.customprofile=OpenJCEPlusFIPS are set in the <insert_0> file but the SSLFIPS property is not set in the Queue Manager configuration.
Explanation: Both the SSLFIPS property and the FIPS 140-3 JVM system properties -Dsemeru.fips=true and -Dsemeru.customprofile=OpenJCEPlusFIPS need to be enabled for FIPS 140-3 support.
Response: Ensure the SSLFIPS property is set on the Queue Manager along with enabling the FIPS 140-3 JVM system properties -Dsemeru.fips=true and -Dsemeru.customprofile=OpenJCEPlusFIPS.

AMQXR2127E: FIPS 140-3 support is not available on this operating system.
Explanation: The product currently does not support FIPS 140-3 in this environment. However, supported ciphers can still be configured on the channel without enabling FIPS.
Response: Ensure that FIPS configuration is disabled on this queue manager.