REST API messages

MQWB0201E

MQWB0201E: Could not find the subscription <insert_0>.

Explanation

The MQ REST API was invoked specifying a subscription name which cannot be located.

Response

Resubmit the request with the name of an existing subscription, or with no name to retrieve a list of subscriptions.

MQWB0202E

MQWB0202E: Could not find the subscription with the id <insert_0> - the queue manager reason code is <insert_1> : <insert_2>.

Explanation

The MQ REST API was invoked specifying a subscription id which cannot be located.

Response

Resubmit the request with the id of an existing subscription, or with no id to retrieve a list of subscriptions.

MQWB0203E

MQWB0203E: The value <insert_0> is an invalid hex string.

Explanation

Hex strings can consist only of hexadecimal characters 0-9,A-F and have an even length.

Response

Resubmit the request with a valid hex string.

MQWB0204E

MQWB0204E: The value <insert_0> is incorrectly encoded.

Explanation

If the value contains a literal asterisk or percentage then the provided string must be URL encoded an additional time.

Response

Resubmit the request with a string with valid encoding.

MQWB0205E

MQWB0205E: The value <insert_0> for <insert_1> is not a valid boolean.

Explanation

A boolean value can only consist of either 'true', 'false' or blank (false).

Response

Resubmit the request with a valid boolean string.

MQWB0206E

MQWB0206E: <insert_0> is not a valid value for query parameter 'name'.

Explanation

The query parameter 'name' must either be blank or contain a single wildcard character.

Response

Resubmit the request with an appropriate set of parameters.

MQWB0207E

MQWB0207E: The subscription URI cannot be invoked as it does not correspond to a valid subscription REST interface.

Explanation

Any slashes intended to be part of the subscription name in the URI must be encoded.

Response

Resubmit the request using a valid URI.

MQWB0208E

MQWB0208E: An internal error <insert_0> has occurred.

Explanation

An internal MQ REST API error has occurred.

Response

If necessary, seek assistance from IBM support.