MQWB0100E: The CSRF header <insert_0> was omitted from the request.
Explanation
The REST API request cannot be completed because the CSRF header was omitted.
Response
Resubmit the request with the correct CSRF header.
MQWB0102E
MQWB0102E: Object <insert_1> type <insert_0> is damaged.
Explanation
The object is damaged.
Response
The object must be deleted or, if the queue manager supports media recovery, recreated from its media image.
MQWB0103E
MQWB0103E: Not authorized.
MQWB0103E: Not authorized to alter <insert_0>.
MQWB0103E: Not authorized to browse from <insert_0>.
MQWB0103E: Not authorized to clear <insert_0>.
MQWB0103E: Not authorized to create <insert_0>.
MQWB0103E: Not authorized to delete <insert_0>.
MQWB0103E: Not authorized to display <insert_0>.
MQWB0103E: Not authorized to get from <insert_0>.
MQWB0103E: Not authorized to open <insert_0>.
MQWB0103E: Not authorized to ping <insert_0>.
MQWB0103E: Not authorized to publish to <insert_0>.
MQWB0103E: Not authorized to purge <insert_0>.
MQWB0103E: Not authorized to put to <insert_0>.
MQWB0103E: Not authorized to refresh <insert_0>.
MQWB0103E: Not authorized to reset <insert_0>.
MQWB0103E: Not authorized to resolve <insert_0>.
MQWB0103E: Not authorized to resume <insert_0>.
MQWB0103E: Not authorized to set <insert_0>.
MQWB0103E: Not authorized to start <insert_0>.
MQWB0103E: Not authorized to inquire status for <insert_0>.
MQWB0103E: Not authorized to stop <insert_0>.
MQWB0103E: Not authorized to suspend <insert_0>.
Explanation
The authenticated principal is not authorized to perform the requested REST API operation.
Response
Obtain the necessary authorization to perform the operation and resubmit the request.
MQWB0104E
MQWB0104E: The REST API request is not authenticated.
MQWB0104E: The REST API request to <insert_0> is not authenticated.
Explanation
The REST API request cannot be completed because credentials were omitted from the request. On z/OS, if the mqweb server has been configured for SAF authentication, this can be caused by the Liberty angel process not being active.
Response
Provide credentials using a client certificate, LTPA security token, or username and password via HTTP basic authentication header. On z/OS, if the mqweb server has been configured for SAF authentication, check the messages.log file for messages indicating that SAF authentication is not available. Start the Liberty angel process if it is not already running. You might need to restart the mqweb server for any changes to take effect.
The REST API request failed due to incorrect username and password credentials.
Response
Provide valid credentials or use another form of authentication such as a client certificate.
MQWB0106E
MQWB0106E: The attribute <insert_0> is incorrect or unexpected.
Explanation
The REST API request failed as an unexpected or incorrect attribute was included in the request.
Response
Resubmit the request omitting the attribute.
MQWB0107E
MQWB0107E: Unable to parse the request data.
MQWB0107E: Unable to parse the request data due to exception <insert_0>.
Explanation
The REST API request failed as the data in the request payload could not be parsed.
Response
Resubmit the request using the correct format and syntax.
MQWB0108E
MQWB0108E: The authenticated principal <insert_0> is not granted access to any of the required roles: <insert_1>.
Explanation
The REST API request failed as the authenticated principal is not associated with any of the roles. On z/OS, if the mqweb server has been configured for SAF authentication, this can be caused by the Liberty angel process not being active.
Response
Map one or more of the indicated roles to the principal and resubmit the request. On z/OS, if the mqweb server has been configured for SAF authentication, check the messages.log file for messages indicating that SAF authentication is not available. Start the Liberty angel process if it is not already running. You might need to restart the mqweb server for any changes to take effect.
MQWB0109E
MQWB0109E: Login failed as the principal <insert_0> is already logged in.
Explanation
The REST API login request failed as the request is already authenticated.
Response
Continue to use the existing credentials, or logout and resubmit the login request.
MQWB0110E
MQWB0110E: Unable to process the REST API request as HTTP basic authentication and <insert_0> authentication token cookie were both provided.
Explanation
A HTTP Basic Authentication header and an authentication token were provided, only one authentication mechanism must be provided.
Response
Omit either the HTTP Basic authentication header or the authentication token cookie from the request and resubmit.
MQWB0111E
MQWB0111E: REST API queues are not defined.
MQWB0111E: REST API queue <insert_0> is not defined.
MQWB0111E: REST API queue <insert_0> is not defined on queue manager <insert_1>.
Explanation
The REST API request failed as a queue required to handle PCF requests is not defined on the queue manager.
Response
Define the required queues on the target queue manager and resubmit the request.
MQWB0112E
MQWB0112E: The <insert_0> authentication token cookie failed verification.
Explanation
The REST API request cannot be completed because the authentication token failed verification.
Response
Login to the REST API to obtain a valid authentication cookie.
MQWB0113E
MQWB0113E: User <insert_0> does not have a suitable role. The <insert_1> role permits only read-only operations.
Explanation
The REST API request cannot be completed because the authenticated principals role permits only read-only operations.
Response
Resubmit the request using a principal that is not restricted to read-only operations.
MQWB0114E
MQWB0114E: User <insert_0> is unable to use the <insert_1> role because the principal name is longer than 12 characters.
Explanation
The REST API request cannot be completed because the principal name is too long to be authenticated by the queue manager.
Response
Resubmit the request using a shorter principal name, or a principal with administrative privileges.
MQWB0115E
REST115E: Unable to process REST API request as <insert_0> is not a valid 'ibm-mq-rest-request-timeout' header value.
Explanation
The REST API request cannot be completed because an invalid value was specified by the header 'ibm-mq-rest-request-timeout'.
Response
Resubmit the request using a valid 'ibm-mq-rest-request-timeout' header value. Valid values must be positive integers.
MQWB0116E
MQWB0116E: The URI cannot be invoked as it does not correspond to an existing REST interface.
Explanation
There is no corresponding REST interface on the provided URI.
Response
Resubmit the request using a valid URI.
MQWB0117E
MQWB0117E: Remote users are not authorized to perform this action in the current environment.
Explanation
Some objects and attributes are restricted for remote users in the current environment.
Response
Refer to the MQ documentation to see which actions and attributes are restricted and omit them from the request.
MQWB0118E
MQWB0118E: Not authorized to open <insert_0>.
Explanation
The authenticated principal is not authorized to perform the requested REST API operation.
Response
Obtain the necessary authorization to perform the operation and resubmit the request. Check queue name resolution, and consult the queue manager error logs for further details.
MQWB0119E
MQWB0119E: The command <insert_0> is not supported.
Explanation
An unsupported command was supplied.
Response
Resubmit the request with a supported command.
MQWB0120E
MQWB0120E: The attribute <insert_0> is invalid.
Explanation
The REST API request failed as an invalid attribute was specified.
Response
Ensure that the attribute is correct and that all required attributes are specified, then resubmit the request.
MQWB0121E
MQWB0121E: The value <insert_0> is not valid for the attribute <insert_1>.
Explanation
An inappropriate value was provided for an attribute.
Response
Resubmit the request with an appropriate value for the attribute. Ensure that all required attributes are specified.