Explanation | Only custom JMS providers can be deleted. |
Action | Select another JMS provider to delete. |
Explanation | A command was not found to handle the deletion of the selected object. |
Action | Select another JMS object to delete. |
Explanation | This message is for informational purposes only. |
Action | Specify a valid object type. |
Explanation | The value supplied contains characters that are not valid for a WMQ name. |
Action | Specify a valid value that contains only legal WMQ name characters |
Explanation | Valid values for the persistence attribute are "APP", "QDEF", "PERS", "NON" and "HIGHT". |
Action | Specify a valid value. |
Explanation | Valid values for the priority attribute are "APP", "QDEF", "0", "1", "2", "3", "4", "5", "6", "7", "8" and "9". |
Action | Specify a valid value. |
Explanation | The attribute identified must have a value of 0 or greater. Negative integer values are not allowed for this attribute. |
Action | Specify a valid value. |
Explanation | Valid values for the readAhead attribute are "YES", "NO", and "QDEF". |
Action | Specify a valid value. |
Explanation | Valid values for the sendAsync attribute are "YES", "NO", and "QDEF". |
Action | Specify a valid value. |
Explanation | Valid values for the encoding attribute are "NNN", "NNR", "NN3", "NRN", "NRR", "NR3", "RNN", "RNR", "RN3", "RRN", "RRR", "RR3" and "NATIVE". |
Action | Specify a valid value. |
Explanation | Valid values for the readAheadClose attribute are "DELIVERALL" and "DELIVERCURRENT". |
Action | Specify a valid value. |
Explanation | Valid values for the integerEncoding attribute are "Normal" and "Reversed". |
Action | Specify a valid value. |
Explanation | Valid values for the decimalEncoding attribute are "Normal" and "Reversed". |
Action | Specify a valid value. |
Explanation | Valid values for the floatingPointEncoding attribute are "IEEENormal", "IEEEReversed" and "S390". |
Action | Specify a valid value. |
Explanation | Valid values for the expiry attribute are "APP", "UNLIM" or any positive long. |
Action | Specify a valid value. |
Explanation | It was not possible to retrieve the WebSphere MQ JMS Provider from the configuration for the scope provided to this command. |
Action | Ensure a valid scope has been provided to the command. |
Explanation | The supplied ccdtUrl value must use valid URL syntax. |
Action | Specify a valid value. |
Explanation | The qmgrPortNumber value must be an Integer between 1 and 65,536. |
Action | Specify a valid value. |
Explanation | The sslResetCount value must be an Integer between 0 and 999,999,999. |
Action | Specify a valid value. |
Explanation | The destinationType value must be either "javax.jms.Queue" or "javax.jms.Topic". |
Action | Specify a valid value. |
Explanation | The compressHeaders value must be either "NONE" or "SYSTEM". |
Action | Specify a valid value. |
Explanation | The compressPayload value must be either "NONE", "RLE", "ZLIBFAST" and "ZLIBHIGH". |
Action | Specify a valid value. |
Explanation | The brokerVersion value must be either "1" or "2". |
Action | Specify a valid value. |
Explanation | The msgSelection value must be either "CLIENT" or "BROKER". |
Action | Specify a valid value. |
Explanation | The subStore value must be either "MIGRATE", "QUEUE" or "BROKER". |
Action | Specify a valid value. |
Explanation | The cleanupLevel value must be either "SAFE", "NONE", "STRONG", "FORCE" or "NONDUR". |
Action | Specify a valid value. |
Explanation | The wildcardFormat value must be either "Char", "Topic", or an empty string. |
Action | Specify a valid value. |
Explanation | The subscriptionDurability value must be either "Durable" and "Nondurable". |
Action | Specify a valid value. |
Explanation | The providerVersion may be either the empty string, or a string in the form "n.n.n.n" or "n.n.n" or "n.n" or "n" - where "n" is an integer greater than or equal to zero. |
Action | Specify a valid value. |
Explanation | An illegal combination of parameters has been supplied along with the qmgrType attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The qmgrType value must be either "QMGR" and "QSG". |
Action | Specify a valid value. |
Explanation | An illegal combination of parameters has been supplied along with the qmgrSvrconnChannel attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The command attributes wmqServerEndpoint and wmqServerSvrconnChannel must be supplied along with wmqServerName. The following attributes must not be supplied along with wmqServerName: qmgrName, qmgrHostname, qmgrPortNumber, qmgrSvrconnChannel, ccdtUrl, ccdtQmgrName. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The command attributes wmqServerName and wmqServerSvrconnChannel must be supplied along with wmqServerEndpoint. The following attributes must not be supplied along with wmqServerEndpoint: qmgrName, qmgrHostname, qmgrPortNumber, qmgrSvrconnChannel, ccdtUrl, ccdtQmgrName. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The command attributes wmqServerName and wmqServerEndpoint must be supplied along with wmqServerSvrconnChannel. The following attributes must not be supplied along with wmqServerSvrconnChannel: qmgrName, qmgrHostname, qmgrPortNumber, qmgrSvrconnChannel, ccdtUrl, ccdtQmgrName. |
Action | Specify a valid combination of parameters to the command. |
Explanation | An illegal combination of parameters has been supplied along with the transportChain attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | An illegal combination of parameters has been supplied along with the ccdtUrl attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The command attribute ccdtUrl must be supplied along with ccdtQmgrName. The following attributes must not be supplied along with ccdtQmgrName: qmgrName, qmgrHostname, qmgrPortNumber, qmgrSvrconnChannel or connectionNameList. |
Action | Specify a valid combination of parameters to the command. |
Explanation | An illegal combination of parameters has been supplied along with the qmgrName attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The wmqTransportType value must be either "BINDINGS","BINDINGS_THEN_CLIENT", or "CLIENT". |
Action | Specify a valid value. |
Explanation | An illegal combination of parameters has been supplied along with the wmqTransportType attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | An illegal combination of parameters has been supplied along with the qmgrHostname attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | An illegal combination of parameters has been supplied along with the qmgrPortNumber attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The command received a target object that was not of the expected object type. |
Action | Specify a valid target object to the command. |
Explanation | It was not possible to retrieve the WebSphere MQ Resource Adapter from the configuration for the scope provided to this command. |
Action | Ensure a valid scope has been provided to the command. |
Explanation | The create command ran but no result object was returned. |
Action | Make sure that the correct configuration information has been passed to the create command being run. |
Explanation | The list command ran but no result object was returned. |
Action | Make sure that the correct configuration information has been passed to the list command being run. |
Explanation | The msgRetention value must be either "YES" or "NO". |
Action | Specify a valid value. |
Explanation | The clonedSubs value must be either "ENABLED" or "DISABLED". |
Action | Specify a valid value. |
Explanation | The wildcardFormat value must be either "allWildcards", "topicWildcards" or "characterWildcards". |
Action | Specify a valid value. |
Explanation | The brokerVersion value must be either "V1" or "V2". |
Action | Specify a valid value. |
Explanation | The type value must be either "CF", "QCF" or "TCF". |
Action | Specify a valid value. |
Explanation | Both of the specified parameters must be supplied in order to be valid. |
Action | Specify a valid combination of values. |
Explanation | One or more parameters were supplied to the command that are not valid for connection factories of type "QCF". |
Action | Ensure that all supplied parameters are valid of connection factories of type "QCF". |
Explanation | One or more parameters were supplied to the command that are not valid for connection factories of type "TCF". |
Action | Ensure that all supplied parameters are valid of connection factories of type "TCF". |
Explanation | The replyWithRFH2 value must be either "ALWAYS" or "AS_REPLY_DEST". |
Action | Specify a valid value. |
Explanation | The sslType value must be either "NONE", "CENTRAL" or "SPECIFIC". |
Action | Specify a valid value. |
Explanation | It is not legal to supply the sslConfiguration parameter if the sslType parameter is not supplied, or if the sslType parameter has a value other than "SPECIFIC". |
Action | Specify a valid combination of SSL parameters. |
Explanation | An illegal combination of parameters has been supplied along with the localAddress attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The brokerVersion value must be either "MA0C" or "MQSI". |
Action | Specify a valid value. |
Explanation | The attribute identified must have a value of 0 or greater. Negative long values are not allowed for this attribute. |
Action | Specify a valid value. |
Explanation | When setting the clonedSubs attribute to a value of "ENABLED", a value must be supplied for the clientId attribute. |
Action | Specify a valid combination of values. |
Explanation | When setting the sslType attribute to a value of "SPECIFIC", a value must be supplied for the sslConfiguration attribute. |
Action | Specify a valid combination of values. |
Explanation | An existing connection factory is required to use as a reference when creating the new activation specification. |
Action | Update the listener port to reference an existing connection factory. |
Explanation | An existing destination is required to use as a reference when creating the new activation specification. |
Action | Update the listener port to reference an existing destination. |
Explanation | The WMQ resource adapter cannot be managed unless at least one parameter is supplied. |
Action | Supply one or more of the nativePath, query, enableInbound or disableWMQ parameters. |
Explanation | Only server scoped WMQ resource adapters can be enabled for inbound JCA messages. |
Action | Supply a server scope WMQ resource adapter as the target object. |
Explanation | Only listener ports are valid target objects for the command. |
Action | Supply a listener port as the target object. |
Explanation | Only WMQ resource adapters are valid target objects for the command. |
Action | Supply a WMQ resource adapter as the target object. |
Explanation | Once a WebSphere MQ server connection type has been specified it cannot be changed. |
Action | Only modify non-CCDT attributes. |
Explanation | Once a WebSphere MQ server connection type has been specified it cannot be changed. |
Action | Only modify CCDT attributes. |
Explanation | There is no WebSphere MQ Resource Adapter configured at cell scope |
Action | Supply an alternative scope. |
Explanation | The cluster scope is only applicable if the application server is a member of a cluster. |
Action | Supply an alternative scope. |
Explanation | It is only possible to supply scope types that can possibly be associated with an application server. |
Action | Supply either "Server", "Node", "Cluster" or "Cell" as the scope. |
Explanation | A resource of a different type already exists that uses the JNDI name supplied. |
Action | Supply a different JNDI name. |
Explanation | A resource at the same scope already exists that uses the JNDI name supplied. |
Action | Supply a different JNDI name. |
Explanation | Valid values for the persistence attribute are "APP", "TDEF", "PERS", "NON" and "HIGHT". |
Action | Specify a valid value. |
Explanation | Valid values for the priority attribute are "APP", "TDEF", "0", "1", "2", "3", "4", "5", "6", "7", "8" and "9". |
Action | Specify a valid value. |
Explanation | Valid values for the readAhead attribute are "YES", "NO", and "TDEF". |
Action | Specify a valid value. |
Explanation | Valid values for the sendAsync attribute are "YES", "NO", and "TDEF". |
Action | Specify a valid value. |
Explanation | Only listener ports configured on Version 7.0 application servers can be migrated to activation specifications. |
Action | Please migrate the application server to Version 7.0 before attempting to migrate its listener ports. |
Explanation | Only certain properties are valid for bindings mode connection factories. Typically anything that refers to WebSphere MQ channel properties, CCDTs or SSL is invalid. |
Action | Do not specify this parameter for bindings mode connection factories. |
Explanation | Only certain properties are valid for bindings mode activation specifications. Typically anything that refers to WebSphere MQ channel properties, CCDTs or SSL is invalid. |
Action | Do not specify this parameter for bindings mode activation specifications. |
Explanation | In a single server environment the only valid scope for disabling WebSphere MQ is the server scope. In a network deployment environment any scope can be used. |
Action | Supply a server scoped WebSphere MQ resource adapter as the target object. |
Explanation | An illegal combination of parameters has been supplied with the connectionNameList attribute. |
Action | Specify a valid combination of parameters to the command. |
Explanation | The connectionNameList attribute must be of the form "host1[(port1)][,host2[(port2)]". |
Action | Specify a valid value. |
Explanation | The connectionNameList attribute has been specified for a WebSphere MQ messaging provider resource which is at either the node or server scope, and the version of WebSphere Application Server at that scope is earlier than WebSphere Application Server Version 8. Support for the connectionNameList attribute was added in WebSphere Application Server Version 8. |
Action | Do not specify a connectionNameList attribute for the specified WebSphere MQ messaging provider resource. |
Explanation | Valid values for the clientReconnectOptions parameter are "ASDEF", "QMGR", "RECONNECT" or "DISABLED". |
Action | Specify a valid value. |
Explanation | Valid values for the messageBody parameter are "UNSPECIFIED", "JMS" or "MQ". |
Action | Specify a valid value. |
Explanation | Valid values for the mqmdMessageContext parameter are "DEFAULT", "SET_IDENTITY_CONTEXT" or "SET_ALL_CONTEXT". |
Action | Specify a valid value. |
Explanation | Valid values for the replyToStyle parameter are "DEFAULT", "MQMD" or "RFH2". |
Action | Specify a valid value. |
Explanation | The cleanupLevel value must be either "SAFE", "NONE", "ASPROP" or "STRONG". |
Action | Specify a valid value. |