MQ Service Provider messages (CSQZ...)

CSQZ0001E: The value of the "{0}" attribute for service "{1}" is either null, blank, or consists entirely of whitespace.
Explanation: The specified property should have a non-blank value.
User action: Set an appropriate value for the property.

CSQZ0002E: The request data for service "{0}" is incorrect for the configured data transformation.
Explanation: The structure of the request data should conform to the data transformation schema.
User action: Ensure the request data conforms to the data transformation schema. Contact the administrator of the service if the schema was not provided.

CSQZ0003E: Service "{0}" is stopped and cannot be invoked.
Explanation: The service is currently stopped and cannot be invoked.
User action: Contact the administrator of the service and ask them to start the service. Then resubmit the request.

CSQZ0004E: The request to service "{0}" resulted in an unexpected internal error.
Explanation: An unexpected internal error occurred.
User action: Contact the IBM® service organization and provide this error message along with any associated information.

CSQZ0005E: A JMS message of unexpected type "{0}" has been received while processing a request for service "{1}".
Explanation: If a data transformation is configured on the service then either a javax.jms.TextMessage or a javax.jms.BytesMessage is supported. Otherwise, only a javax.jms.TextMessage is supported. In either case the message will get rolled back to the configured reply queue.
User action: Ensure that only messages of a supported type are put to the reply queue.

CSQZ0006E: An unexpected JMSException occurred while processing a request for service "{0}".
Explanation: An unexpected JMSException occurred while processing a request.
User action: Use the information accompanying this message to resolve the problem, then resubmit the request.

CSQZ0007E: An exception occurred while looking up the connection factory or one of the destinations used by service "{0}" from JNDI. The JNDI name was "{1}". The exception follows: "{2}"
Explanation: An exception occurred while looking up JMS resources from JNDI.
User action: Use the information in the exception to resolve the problem.

CSQZ0008E: Service "{0}" caught an exception while serializing JSON data. The exception message was "{1}"
Explanation: A failure occurred while serializing JSON data.
User action: Use the information in the exception message to resolve the problem, then resubmit the request.

CSQZ0009E: The request to service "{0}" contains an incorrect ibm-mq-md-expiry value. The value was "{1}".
Explanation: The request contains an incorrect ibm-mq-md-expiry value.
User action: Change the value of the ibm-mq-md-expiry HTTP header to be a valid 32 bit integer, then resubmit the request.

CSQZ0010E: The request to service "{0}" contains an incorrect ibm-mq-md-persistence value. The value was "{1}".
Explanation: The request contains an incorrect ibm-mq-md-persistence value.
User action: Change the value of the ibm-mq-md-persistence HTTP header to be either false, which means that sent messages are non-persistent, or true, which means that sent messages are persistent.

CSQZ0011E: An unexpected JMSException occurred while processing the "ibm-mq-usr" HTTP header of a request for service ''{0}''. The current message is of type "{1}", name "{2}" and value "{3}"
Explanation: An unexpected JMSException occurred while processing the "ibm-mq-usr" HTTP header.
User action: Use the provided information to resolve the problem, then resubmit the request.

CSQZ0012E: Service ''{0}'' was processing the "ibm-mq-usr" HTTP header when a string message was detected which was not surrounded by double quotes. The HTTP header contents were ''{1}''. The error was detected at approximately offset ''{2}''.
Explanation: String message properties in the "ibm-mq-usr" HTTP header should be surrounded by double quotes.
User action: Use the provided offset to locate the string message in the header, and ensure it is surrounded by double quotes, then resubmit the request.

CSQZ0013E: Service ''{0}'' was processing the "ibm-mq-usr" HTTP header when a boolean message property was detected which had an incorrect value. The HTTP header contents were ''{1}''. The message name was ''{2}''. The value was ''{3}''.
Explanation: A boolean message can only have values of ''TRUE'' or ''FALSE''. The specified message property had a different value.
User action: Use the provided information to locate the boolean message with the incorrect value, and change it to either ''TRUE'' or ''FALSE'', then resubmit the request.

CSQZ0014E: Service ''{0}'' was processing the "ibm-mq-usr" HTTP header when a message of an unexpected type was detected. The HTTP header contents were ''{1}''. The message name was ''{2}''. The type was ''{3}''.
Explanation: A message property of an unexpected type was detected.
User action: Ensure that the message property is one of the following types: boolean, i1, i2, i4, i8, r4, r8, string, then resubmit the request.

CSQZ0015E: Service ''{0}'' was processing the "ibm-mq-usr" HTTP header when a numeric message was detected which had an incorrect value. The HTTP header contents were ''{1}''. The message name was ''{2}''. The type was ''{3}''. The value was ''{4}''.
Explanation: The specified value could not be converted into a number of the specified type.
User action: Ensure that the value can be converted into a number of the specified type, then resubmit the request.

CSQZ0016E: Service ''{0}'' was processing the "ibm-mq-usr" HTTP header when an empty message name was detected. The HTTP header contents were ''{1}''. The error was detected at offset ''{2}''.
Explanation: A message with an empty name was detected.
User action: Check that the message has a name, and is correctly formed. Use the provided offset information to locate the message in the header, correct it, then resubmit the request.

CSQZ0017E: Service ''{0}'' was processing the "ibm-mq-usr" HTTP header and could not find a semi-colon when one was expected. The HTTP header contents were ''{1}''. The error was detected at offset ''{2}''.
Explanation: An expected semi-colon could not be located.
User action: Use the provided information to establish the problem and correct it, then resubmit the request.

CSQZ0018E: Service ''{0}'' is configured to use a topic. The HTTP GET and DELETE methods are not supported in this configuration.
Explanation: Only the HTTP POST method is supported with services that use a topic.
User action: Consider using a different, queue based, service.

CSQZ0019E: The request to service ''{0}'' contained an incorrect "ibm-mq-gmo-waitInterval" value. The value was ''{1}''.
Explanation: The request contains an incorrect "ibm-mq-gmo-waitInterval" value.
User action: Change the value of the "ibm-mq-gmo-waitInterval" HTTP header to be a valid 64 bit integer, then resubmit the request.

CSQZ0020E: Service ''{0}'' is configured to use a queue. The "ibm-mq-pmo-retain" HTTP header is not supported with queues.
Explanation: The request contains the "ibm-mq-pmo-retain" HTTP header. This is not supported with services that are configured to use queues.
User action: Delete the "ibm-mq-pmo-retain" HTTP header, then resubmit the request.

CSQZ0021E: The request to service ''{0}'' contained an incorrect ''{1}'' HTTP header. The header value was ''{2}''.
Explanation: The specified header was incorrect. If it was prefixed with ''0x:'' then there should be a 24 byte hexadecimal number after the prefix. Otherwise it should be a string, optionally surrounded with double quotes.
User action: Correct the header so that it is correctly formatted, then resubmit the request.

CSQZ0022E: The code page ''{0}'' corresponding to receiveTextCCSID ''{1}'' for service ''{2}'' is not supported..
Explanation: The code page is not installed on the server.
User action: Either install the code page or use a CCSID corresponding to a different code page.

CSQZ0023E: The request to service ''{0}'' had an unsupported content type of ''{1}''.
Explanation: The service only supports a content type of application json and a character set of utf-8.
User action: Correct either the content type, or character set, of the request and resubmit the request.

CSQZ0024E: The request to service ''{0}'' successfully got a message under a transaction, but the attempt to commit the transaction resulted in the transaction rolling back.
Explanation: HTTP DELETE requests to the service begin a user transaction to minimize the chance of message data being lost. The attempt to commit the transaction failed, resulting in the transaction rolling back.
User action: This is likely to be a temporary error, resubmit the request.

CSQZ0025E: An exception occurred while looking up the connection factory or one of the destinations used by service ''{0}'' from JNDI. The JNDI name was ''{1}''.
Explanation: A failure occurred while looking up JMS resources from JNDI.
User action: Contact the administrator of the service so that they can resolve the problem.

CSQZ0026E: Service ''{0}'' located an object from JNDI, but the object was not of the expected type. The expected type was ''{1}''. The actual type was ''{2}''. The JNDI name was ''{3}''.
Explanation: The object located from JNDI was not of the expected type.
User action: Adjust the configuration of the service so that the correct object can be located.

CSQZ0027E: Service ''{0}'' located an object from JNDI, but the object was not of the expected type. The expected type was ''{1}''. The actual type was ''{2}''. The JNDI name was ''{3}''.
Explanation: The object located from JNDI was not of the expected type.
User action: Contact the administrator of the service so that they can adjust the configuration of the service so that the correct object can be located.

CSQZ0028E: A request to service ''{0}'' resulted in an unexpected internal error.
Explanation: An unexpected internal error occurred.
User action: Contact the IBM service organization, and provide this error message along with the FFDC which will have occurred at the same time.

CSQZ0029E: The receiveTextCCSID ''{0}'' used by service ''{1}'' does not exist, or is not supported.
Explanation: The specified CCSID either does not exist or is not supported on the server.
User action: Set the ''receiveTextCCSID'' attribute of the service to a valid, supported CCSID.

CSQZ0030E: Service ''{0}'' has the "replyDestination" attribute set but the value of the "waitInterval" attribute is 0.
Explanation: The "waitInterval" attribute can not have a value of zero if the "replyDestination" attribute is set.
User action: Change the value of "waitInterval" to a non-zero integer value.

CSQZ0031E: The request to service ''{0}'' failed when performing a data transformation on the request data, prior to sending it to IBM MQ.
Explanation: Data transformation for the request data failed. The data was not sent to IBM MQ.
User action: Check the accompanying stack trace and if the issue cannot be fixed by changing the content of the request data, contact the administrator of the service, as they might need to adjust the configuration of the data transformation.

CSQZ0032E: The request to service ''{0}'' failed when performing a data transformation on the data received from IBM MQ.
Explanation: The data transformation was applied to the data received from IBM MQ, but the transformation failed.
User action: Contact the administrator of the service as they might need to adjust the configuration of the data transformation.

CSQZ0033E: The "password" attribute of service ''{0}'' cannot be decoded.
Explanation: An error occurred when decoding the ''password'' attribute. This might be because it was incorrectly formatted.
User action: Ensure that the ''password'' attribute has been correctly encoded. The securityUtility tool should be used to encode passwords. Use the associated error information in the log file to help resolve the problem.

CSQZ0034E: The combination of ''userName'' and ''password'' attributes of service ''{0}'' is incorrect.
Explanation: Either the ''userName" and ''password'' attributes must both be blank, or they must both be specified.
User action: Ensure that either the ''userName'' and ''password'' attributes are both blank, or both specified.

CSQZ0035E: Service "{0}" is not configured correctly.
Explanation: The service is not configured correctly.
User action: Contact the administrator of the service and ask them to correct the configuration of the service. Then resubmit the request.

CSQZ0036E: The value ''{2}'' of the ''{1}'' attribute of service ''{0}'' can not be converted to the expected type ''{3}''.
Explanation: The attribute of the service has a value of an unexpected type.
User action: Correct the value of the attribute.

CSQZ0037E: The value of the ''mqmdFormat'' attribute of service ''{0}'' exceeds the maximum length of 8.
Explanation: The value of the ''mqmdFormat'' attribute of the service exceeds the maximum length of 8.
User action: Correct the value of the ''mqmdFormat'' attribute.

CSQZ0038E: The value ''{1}'' of the ''replySelection'' attribute of service ''{0}'' is not one of: ''none'', ''msgIDToCorrelID'' or ''correlIDToCorrelID''.
Explanation: The ''replySelection'' attribute of the service does not have a valid value.
User action: Correct the value of the ''replySelection'' attribute.

CSQZ0039E: A service with no 'id' attribute has been discovered, users will not be able to call this service.
Explanation: A service without an id cannot be referenced by users.
User action: Contact the administrator of the service and ask them to correct the configuration of the service. Then resubmit the request.

CSQZ0040E: Service ''{0}'' cannot be started or stopped because it is not active.
Explanation: An unexpected internal error occurred when trying to start or stop the service.
User action: Contact the IBM service organization and provide this error message along with the FFDC which will have occurred at the same time.

CSQZ0041E: A method on service ''{0}'' cannot be invoked because the service is inactive.
Explanation: An unexpected internal error occurred when trying to activate the service.
User action: Contact the IBM service organization and provide this error message along with the FFDC which will have occurred at the same time.

CSQZ0042I: ''{0}'' code level is ''{1}''.
Explanation: This message is for informational purposes only.
User action: None; this message is for informational purposes only.