z/OS Connect EE MQ service provider messages

BAQM0001E: The value of the ''{1}'' attribute for service ''{0}'' is either missing, null, blank, or consists entirely of whitespace.

	Explanation	The specified attribute should have a non-blank value.
	Action	Set an appropriate value for the attribute.

BAQM0002E: 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.
	Action	Ensure the request data conforms to the data transformation schema. Contact the administrator of the service if the schema was not provided.

BAQM0003E: Service ''{0}'' is stopped and can not be invoked.

	Explanation	The service is currently stopped and can not be invoked.
	Action	Contact the administrator of the service and ask them to start the service. Then resubmit the request.

BAQM0004E: The request to service ''{0}'' caused an unexpected internal error.

	Explanation	An unexpected internal error occurred.
	Action	Contact the IBM service organization and provide this error message along with any associated information.

BAQM0005E: 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.
	Action	Ensure that only messages of a supported type are put to the reply queue.

BAQM0006E: An unexpected JMSException occurred while processing a request for service ''{0}''. The exception message was ''{1}''.

	Explanation	An unexpected JMSException occurred while processing a request.
	Action	Contact the administrator of the service to resolve the problem.

BAQM0007E: 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.
	Action	Use the information in the exception to resolve the problem.

BAQM0008E: Service ''{0}'' caught an exception while serializing JSON data. The exception message was ''{1}''.

	Explanation	A failure occurred while serializing JSON data.
	Action	Use the information in the exception message to resolve the problem, then resubmit the request.

BAQM0009E: 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.
	Action	Change the value of the 'ibm-mq-md-expiry' HTTP header to be a valid 32 bit integer, then resubmit the request.

BAQM0010E: 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.
	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.

BAQM0011E: 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.
	Action	Use the provided information to resolve the problem, then resubmit the request.

BAQM0012E: 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.
	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.

BAQM0013E: Service ''{0}'' was processing the ''ibm-mq-usr'' HTTP header when a boolean message 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 had a different value.
	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.

BAQM0014E: 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 of an unexpected type was detected.
	Action	Ensure that the message is one of the following types: boolean, i1, i2, i4, i8, r4, r8, string, then resubmit the request.

BAQM0015E: 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.
	Action	Ensure that the value can be converted into a number of the specified type, then resubmit the request.

BAQM0016E: 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.
	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.

BAQM0017E: 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.
	Action	Use the provided information to establish the problem and correct it, then resubmit the request.

BAQM0018E: 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.
	Action	Consider using a different, queue based, service.

BAQM0019E: The request to service ''{0}'' contains an incorrect ''ibm-mq-gmo-waitInterval'' value. The value was ''{1}''.

	Explanation	The request contains an incorrect 'ibm-mq-gmo-waitInterval' value.
	Action	Change the value of the 'ibm-mq-gmo-waitInterval' HTTP header to be a valid 64 bit integer, then resubmit the request.

BAQM0020E: 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.
	Action	Delete the 'ibm-mq-pmo-retain' HTTP header, then resubmit the request.

BAQM0021E: The request to service ''{0}'' contains 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.
	Action	Correct the header so that it is correctly formatted, then resubmit the request.

BAQM0022E: The code page ''{0}'' corresponding to receiveTextCCSID ''{1}'' for service ''{2}'' is not supported.

	Explanation	The code page is not installed on the server.
	Action	Either install the code page or use a CCSID corresponding to a different code page.

BAQM0023E: The request to service ''{0}'' has an unsupported content type of ''{1}''.

	Explanation	The service only supports a content type of application/json and a charset of utf-8.
	Action	Correct either the content type, or charset, of the request and resubmit it.

BAQM0024E: 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 or 'messagingAction' of 'mqget' 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.
	Action	This is likely to be a temporary error, resubmit the request.

BAQM0025E: 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.
	Action	Contact the administrator of the service so that they can resolve the problem.

BAQM0026E: 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.
	Action	Adjust the configuration of the service so that the correct object can be located.

BAQM0027E: 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.
	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.

BAQM0028E: A request to service ''{0}'' resulted in an unexpected internal error.

	Explanation	An unexpected internal error occurred.
	Action	Contact the IBM service organization providing this error message and the FFDC information.

BAQM0029E: 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.
	Action	Set the 'receiveTextCCSID' attribute of the service to a valid, supported CCSID.

BAQM0030E: Service ''{0}'' has the ''replyDestination'' attribute set but the value of the ''waitInterval'' attribute is 0 or is missing.

	Explanation	The 'waitInterval' attribute can not have a value of 0 if the 'replyDestination' attribute is set.
	Action	Change the value of 'waitInterval' to a non-zero integer value.

BAQM0031E: 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.
	Action	Contact the administrator of the service as they might need to adjust the configuration of the data transformation.

BAQM0032E: 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.
	Action	Contact the administrator of the service as they might need to adjust the configuration of the data transformation.

BAQM0033E: The ''password'' attribute of service ''{0}'' can not be decoded.

	Explanation	An error occurred when decoding the 'password' attribute. This might be because it was incorrectly formatted.
	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.

BAQM0034E: The combination of ''userName'' and ''password'' attributes of service ''{0}'' is incorrect.

	Explanation	The 'userName' and 'password' attributes must either both be blank, or they must both be specified.
	Action	Ensure that the 'userName' and 'password' attributes are either both blank, or both specified.

BAQM0035E: Service ''{0}'' is not configured correctly.

	Explanation	The service is not configured correctly.
	Action	Contact the administrator of the service and ask them to correct the configuration of the service by searching for the BAQM0046E error message. Then resubmit the request.

BAQM0036E: 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.
	Action	Correct the value of the attribute.

BAQM0037E: 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.
	Action	Correct the value of the 'mqmdFormat' attribute.

BAQM0038E: 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.
	Action	Correct the value of the 'replySelection' attribute.

BAQM0039E: A service with no id attribute has been discovered, users will not be able to call this service.

	Explanation	A service without an id can not be referenced by users.
	Action	Contact the administrator of the service and ask them to correct the configuration of the service. Then resubmit the request.

BAQM0040E: Service ''{0}'' can not be started or stopped because it is not active.

	Explanation	An unexpected internal error occurred when trying to start or stop the service.
	Action	Contact the IBM service organization providing this error message and the FFDC information.

BAQM0041E: A method on service ''{0}'' can not be invoked because the service is inactive.

	Explanation	An unexpected internal error occurred when trying to activate the service.
	Action	Contact the IBM service organization providing this error message and the FFDC information.

BAQM0042E: Service ''{0}'' has been configured to expect a caller principal but none was provided.

	Explanation	The service has been configured with the 'useCallerPrincipal' attribute set to 'true', but no caller principal was provided. This is because the z/OS Connect EE service, or API, was configured with the 'requireAuth' attribute set to 'false', and the user did not authenticate to z/OS Connect EE. This combination of attributes is incorrect.
	Action	Either set the MQ Service Provider 'useCallerPrincipal' attribute set to 'false', and adjust your MQ security configuration; or set the z/OS Connect EE 'requireAuth' attribute to 'true' and ensure that the caller authenticates with z/OS Connect EE.

BAQM0043E: Service ''{0}'' has been configured to expect a caller principal but none was provided.

	Explanation	The service has been configured to expect callers to authenticate with z/OS Connect EE, but no authentication information was provided.
	Action	Provide authentication information such as a user name and password when calling the service.

BAQM0044E: Service ''{0}'' received a message from IBM MQ which did not contain valid JSON. The exception message was ''{1}''.

	Explanation	A message was received from IBM MQ that contained text data, but the data was not recognized as valid JSON. The data might not be JSON, or it might be in the wrong CCSID.
	Action	Contact the administrator of the service and ask them to validate that the message contains JSON data, and that the JMS destination(s) associated with the service are configured to use the correct CCSID. Once the administrator of the service has corrected the issue, resubmit the request.

BAQM0045E: Service ''{0}'' is not configured correctly.

	Explanation	The service is not configured correctly.
	Action	To find more information about the configuration errors look for earlier error messages starting with BAQM in the log file, and use the information provided in those error messages to resolve them.

BAQM0046E: Attribute ''{1}'' of service ''{0}'' is unknown.

	Explanation	The attribute is not supported.
	Action	Remove the attribute from the properties file or server.xml file.

BAQM0047E: The service archive file for service ''{0}'' is incompatible with the MQ Service Provider.

	Explanation	The service archive file is incompatible with the MQ Service Provider.
	Action	Consider upgrading the MQ Service Provider or using an earlier version of the MQ build toolkit plugin.

BAQM0048E: The service archive file for service ''{0}'' was created by an unknown tool which is not supported.

	Explanation	The service archive file was created by an unknown tool which is not supported.
	Action	Re-generate the service archive file with a supported MQ build toolkit plugin.

BAQM0049E: Attribute ''{1}'' is not allowed when ''messagingAction'' is ''{2}'' for service ''{0}''.

	Explanation	The attribute is not allowed with the value of 'messagingAction'.
	Action	Correct the input parameter.

BAQM0050E: Service ''{0}'' is configured to use a topic. The value of ''{1}'' for ''messagingAction'' is not supported in this configuration.

	Explanation	Services that use a topic only support a 'messagingAction' of 'mqput'.
	Action	Consider using a different, queue based, service.

BAQM0051E: Applying a configuration update to service ''{0}'' would have resulted in the service not being configured correctly, so the update has not been applied.

	Explanation	The configuration update has not been applied as doing so would have resulted in the service not being configured correctly.
	Action	To find more information look for earlier error messages starting with BAQM in the log file, and use the information provided in those error messages to resolve the problem.

BAQM0052E: The value ''{2}'' is not a supported ''{1}'' for service ''{0}''.

	Explanation	The value must be between 1 and 65535 and a supported 'ccsid'.
	Action	Set an appropriate value for the 'ccsid' or 'receiveTextCCSID' attribute.

BAQM0053I: {0}, code level is {1}.

	Explanation	This message is for informational purposes only.
	Action	None, this message is for informational purposes only.

BAQM0054E: Either the ''replyDestination'' or the ''messagingAction'' attributes must be provided for service ''{0}'', but not both.

	Explanation	The 'replyDestination' and 'messagingAction' attributes are mutually exclusive.
	Action	Specify one of either the 'replyDestination' or 'messagingAction' attributes.

BAQM0055E: An unexpected error occurred while creating a data transformation for service ''{0}'': {1}.

	Explanation	An unexpected internal error occurred.
	Action	Contact the IBM service organization and provide this error message along with any associated information.

BAQM0056E: An unexpected JMSException occurred while processing a request for service ''{0}''. The exception message was ''{1}''.

	Explanation	An unexpected JMSException occurred while processing a request.
	Action	Use the information from the exception and the associated FFDC to resolve the problem.