MQWB03xx: REST API messages
- MQWB0300E
- MQWB0300E: Cannot create messaging connection to <insert_0> on <insert_1>.
- Explanation
- The queue manager or destination might not be created or active.
- Response
- Resubmit the request, correcting any issues.
- MQWB0301E
- MQWB0301E: Cannot create message.
- Explanation
- The message could not be created.
- Response
- Resubmit the request, correcting any issues.
- MQWB0302E
- MQWB0302E: The <insert_0> request header cannot be set as <insert_1> is not a valid request header value.
- Explanation
- The API request cannot be completed because an invalid value was specified for a request header.
- Response
- Resubmit the request using a valid header value.
- MQWB0303E
- MQWB0303E: An unforeseen error occurred while sending, publishing, receiving, or browsing the message.
- Explanation
- An underlying error occurred while sending, publishing, receiving, or browsing the message.
- Response
- Resubmit the request, correcting any issues.
- MQWB0304E
- MQWB0304E: The <insert_0> response header cannot be set in the HTTP response.
- Explanation
- The required response header could not be set in the HTTP response.
- Response
- Resubmit the request, correcting any issues.
- MQWB0305E
- MQWB0305E: The character set <insert_0> is not acceptable for the request.
- Explanation
- The request is encoded using an unacceptable character set.
- Response
- Resubmit the request, correcting any issues.
- MQWB0306E
- MQWB0306E: The media type is unsupported for this type of request.
- Explanation
- The request attempted to use an unsupported media type.
- Response
- Resubmit the request using a valid media type.
- MQWB0307E
- MQWB0307E: The mqweb server received an invalid response from connected services.
- Explanation
- The mqweb server received an invalid response when acting as a proxy or gateway from connected services. This might be due to the underlying services being unavailable or inhibited.
- Response
- Resubmit the request ensuring that the mqweb server and connected services meet requirements.
- MQWB0308E
- MQWB0308E: The mqweb server was unable to successfully process the message body.
- Explanation
- The mqweb server successfully received an MQ message, but was unable to process the HTTP response. This might be due to an unsupported encoding of the message.
- Response
- Resubmit the request, correcting any issues.
- MQWB0309E
- MQWB0309E: The received or browsed message type is unsupported by the mqweb server.
- Explanation
- The mqweb server successfully received an MQ message, but was of an unsupported message type.
- Response
- Resubmit the request, correcting any issues.
- MQWB0310E
- MQWB0310E: Queue <insert_0> cannot be accessed as it is <insert_1> inhibited.
- Explanation
- An MQ message could not be sent or received as the queue is not available.
- Response
- Ensure that the necessary queue is available before retrying the operation.
- MQWB0311E
- MQWB0311E: The value <insert_0> must be <insert_1> character
- Explanation
- The value supplied for the attribute or parameter is the incorrect length.
- Response
- Resubmit the request with the value at the expected length.
- MQWB0312E
- MQWB0312E: The queue type <insert_0> is unsupported for this type of request.
- Explanation
- An MQ message could not be sent or received as the queue is an unsupported type.
- Response
- Resubmit the request using a valid queue.
- MQWB0313E
- MQWB0313E: The messaging REST API is not enabled.
- Explanation
- Messaging is not permitted as the service is not enabled.
- Response
- Enable the messaging REST API and resubmit the request.
- MQWB0314E
- MQWB0314E: The administrative REST API gateway is not supported by this operation.
- Explanation
- The administrative REST API gateway was specified, but is not supported by this operation.
- Response
- Resubmit the operation without specifying a gateway. Check the queue manager state.
- MQWB0315E
- MQWB0315E: Unable to allocate a messaging connection to <insert_0> on <insert_1>.
- Explanation
- No messaging connection could be allocated as the pool has exceeded its configured limits.
- Response
- Configure the messaging REST API to wait for available connections, overflow, or increase the maximum pool size.
- MQWB0316E
- MQWB0316E: Topic <insert_0> cannot be accessed as it is <insert_1> inhibited.
- Explanation
- An MQ message could not be published as the topic is not available.
- Response
- Ensure that the necessary topic is available before retrying the operation.
- MQWB0317E
- MQWB0317E: The request header <insert_0> is incorrect or unexpected.
- Explanation
- The REST API request failed as an unexpected or incorrect header was included in the request.
- Response
- Resubmit the request omitting the header. Refer to IBM Documentation for applicable request headers.
- MQWB0318I
- MQWB0318I: The mqweb server is configured for <insert_0> queue manager REST messaging.
- Explanation
- The mqweb server can be configured for either local or remote REST messaging exclusively.
- Response
- Modify the associated property and restart the mqweb server to switch connection modes.
- MQWB0319I
- MQWB0319I: A change to the remote queue manager global configuration has been detected.
- Explanation
- The mqweb server has detected a change to the remote queue manager global configuration and has closed all connections. Connections will be re-established with the new configuration when the next REST request is received.
- Response
- No action required.
- MQWB0320E
- MQWB0320E: Invalid or unknown remote queue manager definition <insert_0>.
- Explanation
- The remote queue manager definition specified is invalid, hidden from the messaging REST API, or does not exist.
- Response
- Ensure that the correct unique name for the remote queue manager is specified in the request URL. The unique name that is specified in the remote queue manager configuration might be different to the name of the remote queue manager. If necessary, correct the remote queue manager definition and resubmit the request.
- MQWB0321E
- MQWB0321E: A security error occurred when connecting to the remote queue manager <insert_0>. The root MQ error message was <insert_1>.
- Explanation
- An error occurred when connecting to a remote queue manager using SSL/TLS. This error might indicate that the remote definition or associated CCDT are invalid or that the user does not have the required authorization.
- Response
- Examine the associated MQ message to determine the cause. Ensure that configuration is correct and the user has the correct privileges. Correct any other problems and resubmit the request.
- MQWB0322E
- MQWB0322E: Password decryption failed.
- Explanation
- A password in the remote queue manager configuration cannot be decrypted.
- Response
- Check the mqweb server logs for more details of the failure.
- MQWB0323E
- MQWB0323E: Incompatible group attributes for remote queue manager definition <insert_0>.
- Explanation
- The specified remote queue manager definition is configured as a queue manager group and can be used only with the messaging REST API.
- Response
- Correct the remote queue manager definition and resubmit the request.
- MQWB0324I
- MQWB0324I: The remote queue manager definition <insert_0> has been modified.
- Explanation
- The mqweb server has detected a change to the specified remote queue manager definition and has closed any connections to the queue manager. Connections will be re-established with the modified definition when the next REST request is received.
- Response
- No action required.
- MQWB0325E
- MQWB0325E: The remote queue manager configuration file <insert_0> cannot be read or is invalid.
- Explanation
- The mqweb server cannot read the remote configuration file and has closed all connections.
- Response
- Correct the remote queue manager configuration definitions. Ensure the file structure and data is valid and resubmit the request.
- MQWB0326E
- MQWB0326E: The client channel definition table
- Explanation
- The associated client channel definition table (CCDT) cannot be found or contains an invalid structure or data.
- Response
- Correct the remote queue manager configuration definition and associated CCDT. Ensure the file structures and data are valid and resubmit the request.
- MQWB0327I
- MQWB0327I: The user that is logged into the REST API is being used for MQ authorization: <insert_0>
- Explanation
- This message indicates whether it is the user that is logged into the REST API or the user ID that started the mqweb server that is used for MQ object authorization.
- Response
- No action required.
- MQWB0328I
- MQWB0328I: The remote queue manager definition <insert_0> was removed.
- Explanation
- The specified remote queue manager definition was removed and any connections to the queue manager have been closed.
- Response
- No action required.