Express (Distributed operating systems), v8.0 > Reference > Messages
CWSJA
CWSJA0000E: Bus "{0}" already exists.
Explanation Bus names must be unique within the administrative domain. Action Specify a name for this bus that is not already in use within the administrative domain.
CWSJA0001E: Bus "{0}" not found.
Explanation The specified bus name could not be located within the administrative domain. Action Make sure that the bus name specified is a valid bus name for an existing bus.
CWSJA0002E: Multiple instances of bus "{0}" found.
Explanation Only one instance of a bus should exist with the name specified, yet more than one instance has been located. Action Make sure that bus names are unique within the administrative domain.
CWSJA0003E: Bus member "{0}" already exists.
Explanation An attempt has been made to add a server to a bus of which it is already a member. Action Do not attempt to add a bus member if the server in question is already a member.
CWSJA0004E: Messaging engine "{0}" already exists.
Explanation The messaging engine specified already exists on the server. Action Make sure that the messaging engine details are not identical to that of another messaging engine on the server.
CWSJA0005E: Unable to create bus member "{0}".
Explanation An exception was generated attempting to create a bus member with the configuration data provided. Action Make sure that all configuration data for the bus member is valid.
CWSJA0006E: Destination type "{0}" is not supported by this command.
Explanation An incorrect destination type has been specified. Action Make sure that the destination type specified is valid.
CWSJA0007E: Incorrect parameter combination supplied : node name = "{0}", server name = "{1}", cluster name = "{2}", WebSphere MQ server name = "{3}".
Explanation The parameters supplied do not provide a valid bus member configuration. Action To correctly identify a bus member, specify node name and server name, or cluster name, or WebSphere MQ server name.
CWSJA0008E: Scope specification is not valid.
Explanation The details specified do not represent a valid scope specification. Action Make sure that valid node name, server name and cluster name details are used to represent the scope.
CWSJA0009E: Destination "{0}" already exists.
Explanation The destination specified already exists on the bus. Action Make sure that destinations on the bus have unique names.
CWSJA0010E: "{0}" must be set to create an alias destination.
Explanation An attempt has been made to create an alias destination without sufficient configuration detail. Action Make sure that an alias parameter is specified when creating the alias destination.
CWSJA0011E: "{0}" must be set to create a foreign destination.
Explanation An attempt has been made to create an foreign destination without sufficient configuration detail. Action Make sure that a foreign parameter is specified when creating the foreign destination.
CWSJA0012E: The messaging engine "{0}" does not exist at scope "{1}" for bus "{2}".
Explanation The operation could not be invoked because the given messaging engine does not exist for the given bus at the specified scope. Action Make sure that a correct messaging engine name and scope are specified.
CWSJA0013E: Multiple messaging engines were found.
Explanation Multiple messaging engines have been found matching the configuration data provided. Action Make sure that messaging engines are unique within the administrative domain.
CWSJA0015E: SIB JDBC provider not found.
Explanation An attempt has been made to locate a SIB JDBC provider within the scope provider, but none was found. Action Make sure that there is a SIB JDBC provider available within the administrative domain.
CWSJA0016E: Unable to create data source.
Explanation An exception occurred creating a data source with the configuration data provided. Action Make sure that the configuration data provided to create a data source is valid.
CWSJA0017E: Unable to create resource property set.
Explanation An exception occurred creating a resource property set with the configuration data provided. Action Make sure that the configuration data provided to create a resource property set is valid.
CWSJA0018E: Bus member supplied is not a member of the specified bus.
Explanation The specified bus member is not a member of this bus. Action Make sure that the specified bus member is a member of this bus.
CWSJA0019E: Unable to create messaging engine.
Explanation An exception occurred creating a messaging engine with the configuration data provided. Action Make sure that the configuration data provided to create a messaging engine is valid.
CWSJA0020E: Unable to create data store.
Explanation An exception occurred creating a data store with the configuration data provided. Action Make sure that the configuration data provided to create a data store is valid.
CWSJA0021E: The bus with name "{0}" contains invalid characters
Explanation Bus names cannot contain any of the following characters \/,#$@:;"*? <>|=+&%' or start with _ or . or contain ]]> . Action Make sure that a valid bus name is specified for the bus that is to be created.
CWSJA0022E: Not allowed to delete a bus called "{0}".
Explanation An exception has occurred attempting to delete a bus with the name specified. Action Make sure that a valid bus name is specified for the bus that is to be deleted.
CWSJA0023E: Bus member not found.
Explanation The bus member specified could not be located within the administrative domain. Action Make sure that a valid bus member is being located.
CWSJA0024E: Multiple bus members found.
Explanation Only one instance of a bus member should exist within the scope specified, yet more than one instance has been located. Action Make sure that bus members have unique configuration data within an administrative domain.
CWSJA0025E: Messaging engine already defined for this bus member.
Explanation A messaging engine already exists with the configuration data supplied. Action Make sure that unique configuration data is specified for the messaging engine that is to be created.
CWSJA0026E: Not allowed to delete "{0}" because it is a system destination.
Explanation The destination with the name specified cannot be deleted. Action Make sure that a valid destination name is specified for the destination that is to be deleted.
CWSJA0027E: Destination {0} not found on bus {1}.
Explanation An exception occurred attempting to locate the specified destination. Action Make sure that the destination being located exists within the administrative domain.
CWSJA0028E: Multiple destinations found.
Explanation Only one instance of a destination should exist within the scope specified, yet more than one instance has been located. Action Make sure that destinations have unique configuration data within an administrative domain.
CWSJA0029E: Failed to find bus. More than one bus found with duplicate UUID.
Explanation An exception occurred due to multiple buses having identical UUIDs. Action Make sure that each bus in an administrative domain has a unique UUID.
CWSJA0030E: Failed to find Bus with UUID "{0}".
Explanation The UUID specified does not belong to a bus in the administrative domain. Action Make sure that the UUID specified belongs to a valid bus.
CWSJA0031E: No messaging engine names available for cluster.
Explanation A suitable messaging engine name could not be created. Action Try specifying different configuration data when creating the messaging engine.
CWSJA0032E: Failed to find destination. More than one destination with duplicate UUID.
Explanation More than one destination within the administrative domain has the same UUID. Action Make sure that each destination within the administrative domain has a unique UUID.
CWSJA0033E: Server supplied does not have a SIB service.
Explanation No SIB services were found for this messaging server. Action Make sure that a SIB service exists for this messaging server.
CWSJA0034E: Failed to find destination "{1}" on bus "{0}".
Explanation The named destination could not be located on the named bus within the administrative domain. Action Make sure that the named destination exists on the named bus.
CWSJA0036E: Required value not supplied for parameter "{1}" of command "{0}".
Explanation Either the specified parameter was not supplied, or no value was supplied for it. Action Run the command again, supplying the missing parameter value.
CWSJA0037E: Incorrect value "{2}" for parameter "{1}" of command "{0}".
Explanation The value supplied for the specified parameter of the specified command is not valid. Action Run the command again, supplying a valid value.
CWSJA0038E: Required value not supplied for parameter "{2}" of step "{1}" of command "{0}".
Explanation Either the specified parameter was not supplied for the specified step, or no value was supplied for it. Action Run the command again, supplying the missing parameter value for the specified step.
CWSJA0039E: Failed to determine values for "reliability" and "maxReliability".
Explanation An internal error occurred while trying to determine values for the reliability and maxReliability parameters. Action Report this problem to the system administrator.
CWSJA0040E: The value supplied for "reliability" is greater than the value supplied for "maxReliability".
Explanation The value supplied for the reliability parameter should be less than or equal to the value supplied for the maxReliability parameter. Action Run the command again, supplying a value for the reliability parameter that is less than or equal to the value supplied for the maxReliability parameter.
CWSJA0041E: Value for parameter "{0}" not recognised.
Explanation The value supplied for the specified parameter was not recognized. Action Run the command again, supplying a valid value.
CWSJA0042E: Not allowed to create a SIBDestination called "{0}"
Explanation The destination name supplied to the createSIBDestination command is not valid. Action Run the command again, supplying a valid destination name.
CWSJA0043E: The value of {2} is not valid for parameter {1} when destination type is {0}.
Explanation The value supplied for the specified parameter is not valid. Action Run the command again, supplying a valid value.
CWSJA0044E: Node, server, WebSphere MQ Server and/or cluster supplied when type is "WebServices".
Explanation The node, server and cluster parameters should not be specified when the type is WebServices. Action Run the command again, supplying a valid combination of parameters.
CWSJA0045E: An internal error occurred while validating reliability and maxReliability.
Explanation An internal error occurred while validating the reliability and maxReliability parameters. Action Report this problem to the system administrator.
CWSJA0047E: Can not have a reply destination bus with out a reply destination name.
Explanation A reply destination cannot be specified without a reply destination name. The reply destination object will be removed. Action If a reply destination is required specify at least the reply destination name.
CWSJA0049E: WebSphere MQ server "{0}" is already a member of bus "{1}".
Explanation An attempt has been made to add an MQ server to a bus of which it is already a member. Action Do not try to add an WebSphere MQ server to a bus of which it is already a member.
CWSJA0050E: Unable to create WebSphere MQ Server Bus Member.
Explanation An exception occurred creating a WebSphere MQ server bus member with the configuration data provided. Action Make sure that the configuration data provided to create a WebSphere MQ server bus member is valid.
CWSJA0051E: No bus member target found for WebSphere MQ server "{0}" on bus "{1}".
Explanation When added to a bus, a WebSphere MQ server should have one bus member target. None was found. Action Report this problem to the system administrator.
CWSJA0052E: Too many bus member targets found for WebSphere MQ server "{0}" on bus "{1}". Number of bus member targets found was {2}.
Explanation When added to a bus, a WebSphere MQ server should have one bus member target. More than one was found. Action Report this problem to the system administrator.
CWSJA0053E: The parameter {0} is only valid when specifying a WebSphere MQ Server name.
Explanation The supplied parameter is not valid when adding a server or a cluster to a bus. Action Remove the parameter from the addSIBusMember command then retry the command.
CWSJA0054E: The parameter {0} with value {1} is only valid when specifying a WebSphere MQ Server name.
Explanation The supplied parameter is not valid when creating a destination. The parameter supplied is only valid when specifying a WebSphere MQ server name. Action Remove the parameter from the createSIBDestination command then retry the command.
CWSJA0055E: The parameter {0} with value {1} is not valid when specifying a WebSphere MQ Server name.
Explanation The supplied parameter is not valid when creating a destination. The parameter supplied is only valid when not specifying a WebSphere MQ server name. Action Remove the parameter from the createSIBDestination command then retry the command.
CWSJA0056E: The WebSphere MQ Server name parameter can only be specified with a destination type of QUEUE, the type specified was "{0}"
Explanation When creating a destination the WebSphere MQ server name was specified with a destination type other than QUEUE. Action Change the destination type to be QUEUE then retry the command.
CWSJA0057E: The WebSphere MQ queue name parameter must be specified for a destination on a WebSphere MQ Server
Explanation When creating a destination on a WebSphere MQ server the wmqQueueName parameter must be specified. Action Change the destination type to be QUEUE then retry the command.
CWSJA0058E: Can not specify both a file store AND a data store, or parameters implying such
Explanation The message store type can be either a file store or a data store, but not both. Therefore parameters relating to both types are not allowed in the same command. Action Either remove parameters relating to file store, or to data store.
CWSJA0059E: Can not specify maximum permanent file store size if unlimited permanent store size is set to true
Explanation When the size of the permanent file store has been set to unlimited, a maximum permanent size cannot be set. Action Remove the maximum permanent file store size parameter or change the unlimited permanent file store size to false then retry.
CWSJA0060E: Unable to create file store.
Explanation A file store could not be created with the configuration data provided. Action Make sure that the configuration data provided to create a file store is valid.
CWSJA0062E: An unexpected error has occurred.
Explanation There is an unexpected problem with the system. Action Check the log files for information about the problem.
CWSJA0063E: Can not specify parameter {0} for message store type {1}
Explanation A file store parameter has been specified for a data store, or a data store parameter has been specified for a file store. Action Check that the parameters are correct for this message store type.
CWSJA0064E: When creating a {0} on a cluster unable to use default values. The parameter {1} is required
Explanation Certain default parameters do not apply with clusters, therefore valid values must be specified. Action Check that parameters are correct for this message store type on a cluster.
CWSJA0065E: Can not create a {0} without a value for {1}
Explanation A value for the specified parameter is required to create a message store of this type. Action Check that the parameters are correct for this message store type.
CWSJA0066E: Minimum permanent store size can not be less than log size
Explanation The permanent file store size must be greater than the file store log size. Action Increase the permanent store size or decrease the log size.
CWSJA0067E: Log size must be greater than {0} megabytes
Explanation The log size specified is lower than the minimum log size. Action Increase the size of the log file.
CWSJA0068E: Maximum permanent store size must be greater than {0} megabytes
Explanation The maximum permanent store size specified is lower than the maximum permanent store size minimum value. Action Increase the size of the maximum permanent store size, or make it unlimited.
CWSJA0069E: Maximum permanent store size can not be less than minimum permanent store size
Explanation Maximum store size cannot be less than minimum store size. Action Either lower the minimum store size, or increase the maximum store size, or make the maximum store size unlimited.
CWSJA0070E: busSecurity parameter specified with scriptCompatibility set to 6. Set the scriptCompatibility to 6.1 when using the busSecurity parameter
Explanation The busSecurity parameter is not compatible with WAS v6.0. The busSecurity parameter is only valid for v6.1 and later. Action Either set the scriptCompatibility to 6.1, or use the secure parameter with scriptCompatibility set to 6.
CWSJA0071E: secure parameter specified with scriptCompatibility set to 6.1. Set the scriptCompatibility to 6 when using the secure parameter
Explanation The secure parameter is not compatible with WAS v6.1. The secure parameter is only valid for v6.0. Action Either set the scriptCompatibility to 6, or use the busSecurity parameter with scriptCompatibility set to 6.1.
CWSJA0072E: Bus security has been specified to be enabled, but administrative security is disabled.
Explanation We cannot set the busSecurity parameter to true unless you also enable administrative security. Action Either use the administrative console to enable administrative security, or set the busSecurity parameter to false.
CWSJA0073E: The permitted transport chain name {0} was not found
Explanation The permitted transport chain with the specified name was not found on the bus. Action Use the administrative console to check that the transport chain name exists and that the case of the name is correct, then reissue the command.
CWSJA0074E: Invalid permittedChains setting {0}. Allowable values ALL|SSL_ENABLED|LISTED
Explanation The supplied parameter permittedChains has a value that is not valid, so the command was rejected. Action Set the permittedChains to an allowable value of ALL, SSL_ENABLED or LISTED.
CWSJA0075E: permittedChains parameter specified with the secure parameter for the modifySIBus command
Explanation We cannot specify the permittedChains parameter with the secure parameter. Action Use the busSecurity parameter instead of the secure parameter.
CWSJA0076E: filestore parameter is specified for a messaging engine on a pre version 6.1 node
Explanation We can only use a file store with a messaging engine on a WAS v6.1 or later node. Action Select a data store, or choose a node that is of v6.1 or later.
CWSJA0077E: The transport chain name {0} already exists as a permitted transport for the bus {1}.
Explanation An attempt was made to add a transport chain as a permitted transport to the bus. This was unsuccessful because the transport chain is already a permitted transport for the bus. Action Add a transport chain with a different name.
CWSJA0078E: The transport chain name {0} was not found as a permitted transport for the bus {1}.
Explanation An attempt was made to remove a permitted transport from a bus. However the specified permitted transport chain is not a permitted transport for the specified bus. Action If the permitted transport exists on the bus, check and correct the name then reissue the command.
CWSJA0079E: Incorrect value "{0}" for parameter "scriptCompatibility".
Explanation The value supplied for the parameter scriptCompatibility is not valid. Action Run the command again, supplying a value that is either 6 (for compatability with WAS v6.0) or 6.1 (for compatability with v6.1).
CWSJA0080E: Destination {0} not found on bus {1}.
Explanation The specified destination could not be found on the specified bus. Action Make sure that the destination being located exists within the administrative domain.
CWSJA0081E: Unable to mediate destination {0} as the WebSphere MQ queue name {1} cannot be used as both the mediation and queue points.
Explanation When mediating a destination that has a message point on WebSphere MQ, the pre-mediation point MQ queue name must not be the same as the message point MQ queue name. Action Choose a different WebSphere MQ destination from which the mediation is to get messages.
CWSJA0082E: busSecurity parameter specified with the secure parameter for the modifySIBus command.
Explanation We cannot specify the busSecurity parameter with the secure parameter. Action Remove either the busSecurity or the secure parameter from the modifySIBus command.
CWSJA0083E: The parameter {0} is only valid for a destination type which is either a Queue, Port or WebService
Explanation The parameter supplied can only be used when the destination type is Queue, Port or WebService. Action Run the command again without using the previously stated parameter.
CWSJA0084E: The value {0} for parameter port is not a valid value.
Explanation Allowable values for the port parameter range between 0 and 65535. Action Run the command again specifying a valid port value.
CWSJA0085E: The value {0} for the WebSphere MQ queue manager or queue sharing group is too long.
Explanation The maximum length for a WebSphere MQ queue manager or queue sharing group is 48 characters. Action Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value.
CWSJA0086E: The value {0} for the WebSphere MQ queue manager or queue sharing group contains invalid characters.
Explanation The WebSphere MQ queue manager or queue sharing group allowable characters range a-z, A-Z, 0-9, ., /, % and _. Action Run the command again specifying a valid WebSphere MQ queue manager or queue sharing group value.
CWSJA0087E: The value {0} for the WebSphere MQ channel is too long.
Explanation The maximum length for a WebSphere MQ channel is 20 characters. Action Run the command again specifying a valid WebSphere MQ channel value.
CWSJA0088E: The value {0} for the WebSphere MQ channel contains invalid characters.
Explanation The WebSphere MQ queue channel allowable characters range a-z, A-Z, 0-9, ., /, % and _. Action Run the command again specifying a valid WebSphere MQ channel value.
CWSJA0089E: Scope specification is not valid, unable to locate node {0} and or server {1}.
Explanation The details specified do not represent a valid scope specification. Action Make sure that valid node and server name details are used to represent the scope.
CWSJA0090E: Scope specification is not valid, unable to locate cluster {0}.
Explanation The details specified do not represent a valid scope specification. Action Make sure that valid cluster name details are used to represent the scope.
CWSJA0091E: The parameter "topicAccessCheckRequired" is only valid for a destination type which is TopicSpace.
Explanation The topicAccessCheckRequired parameter can only be used when the destination type is TopicSpace. Action Remove the parameter specified, then reissue the command.
CWSJA0092E: Can not specify maximum temporary file store size if unlimited temporary store size is set to true.
Explanation When the size of the temporary file store has been set to unlimited, a maximum temporary size cannot be set. Action Remove the maximum temporary file store size parameter or change the unlimited temporary file store size to false then retry.
CWSJA0093E: Minimum temporary store size can not be less than log size.
Explanation The temporary file store size must be greater than the temporary store log size. Action Increase the temporary store size or decrease the log size.
CWSJA0094E: Maximum temporary store size must be greater than {0} megabytes.
Explanation The maximum temporary store size specified is lower than the maximum temporary store size minimum value. Action Increase the size of the maximum temporary store size, or make it unlimited.
CWSJA0095E: Maximum temporary store size can not be less than minimum temporary store size.
Explanation An attempt is being made to configure a maximum temporary store size with a value that is less than the minimum temporary store size. Action Either lower the minimum temporary store size, increase the maximum temporary store size, or make the maximum temporary store size unlimited.
CWSJA0096E: The value {0} for the WebSphere MQ reply to queue is too long.
Explanation The maximum length for a WebSphere MQ reply to queue is 48 characters. Action Run the command again specifying an allowable WebSphere MQ reply to queue value.
CWSJA0097E: The value {0} for the WebSphere MQ reply to queue contains invalid characters.
Explanation The WebSphere MQ reply to queue allowable characters range a-z, A-Z, 0-9, ., /, % and _. Action Run the command again specifying an allowable WebSphere MQ reply to queue value.
CWSJA0098E: The parameters "aliasBus" and "foreignBus" were supplied to the deleteSIBDestination command.
Explanation The deleteSIBDestination command takes either the aliasBus or the foreignBus parameter. The command had both parameters supplied. Action If there are multiple destinations with the same name, then the aliasBus or foreignBus parameter can be used to identify either an Alias or a Foreign destination to delete. Only one of the aliasBus or foreignBus parameters can be supplied.
CWSJA0099E: Failed to find destination "{1}" on bus "{0}" with an alias bus "{2}".
Explanation The named alias destination could not be located on the named bus within the administrative domain. Action Make sure that the named alias destination exists on the named bus with the named alias bus.
CWSJA0100E: Failed to find destination "{1}" on bus "{0}" with a foreign bus "{2}".
Explanation The named foreign destination could not be located on the named bus within the administrative domain. Action Make sure that the named foreign destination exists on the named bus with the named foreign bus.
CWSJA0101E: A file store cannot be specified for a server which is not at version 6.1 or later.
Explanation The support for a file store is only available on WAS v6.1 or later. Either the -fileStore option was specified or another option was set that implied that a file store is to be used. Action Run the command again, this time specifying a data store.
CWSJA0102E: The maintainStrictMessageOrder option cannot be used for a destination that has all its message points on servers of a version less than 6.1.
Explanation The option to maintain strict message order is only available on WAS v6.1 or later. Action Run the command again. Only specify strict message ordering if you also specify a server of v6.1 or later.
CWSJA0103E: The specified scope "{0}" is not a member of bus "{1}".
Explanation The operation could not be invoked because the specified server or cluster is not a member of the given bus. Action Make sure that a server or cluster is specified that is a member of the given bus.
CWSJA0104E: No messaging engines found at scope "{0}" for bus "{1}".
Explanation The operation could not be invoked because no messaging engines exist at the specified scope for the given bus. Action Make sure that there is a messaging engine at the specified scope for the given bus.
CWSJA0105E: The messaging engine with UUID "{0}" does not exist at scope "{1}".
Explanation The operation could not be invoked because the messaging engine with the given UUID does not exist at the specified scope. Action Make sure that there is a messaging engine at the specified scope.
CWSJA0106E: Security settings for bus "{0}" are not compatible with server "{1}" because it resides on pre-6.1 node "{2}".
Explanation The server could not be added to the bus because the server resides on a WAS v6.0 node, and bus security settings are not compatible with pre-Version 6.1 nodes. The permitted transport chains setting must not be LISTED or SSL_ENABLED. The Server group must not be in the bus connector role. Action Disable security on the named bus, or modify the bus security settings so that bus security is compatible with pre-Version 6.1 nodes, or upgrade the named server so that it resides on a v6.1 node.
CWSJA0107E: Security settings for bus "{0}" are not compatible with cluster "{1}" because one or more of its member servers reside on a pre-6.1 node.
Explanation The cluster could not be added to the bus because at least one of its member servers resides on a WAS v6.0 node, and bus security settings are not compatible with pre-Version 6.1 nodes. The permitted transport chains setting must not be LISTED or SSL_ENABLED. The group Server must not be in the bus connector role. Action Disable security on the named bus, or modify the bus security settings so that bus security is compatible with pre-Version 6.1 nodes, or upgrade the pre-Version 6.1 servers on the named cluster so that they reside on v6.1 nodes.
CWSJA0108E: The value "{1}" for the permitted transport chains bus security attribute is not valid for bus "{0}" because the bus contains at least one pre-6.1 bus member.
Explanation Enabling bus security, or changing the named bus security attribute to the indicated value when the bus contains one or more WAS v6.0 bus members, is not allowed because the value is not compatible with pre-Version 6.1 bus members. The permitted transport chains setting must not be LISTED or SSL_ENABLED. Action Disable security on the named bus, or modify the named security setting to a value that does not conflict with pre-Version 6.1 bus members, or remove all pre-Version 6.1 bus members from the bus.
CWSJA0109E: Found group "Server" in the bus connector role for bus "{0}". This is not allowed because the bus contains at least one pre-6.1 bus member.
Explanation The named bus contains one or more WAS v6.0 bus members. Having the named group in the bus connector role is not compatible with pre-Version 6.1 bus members. The Server group must not be in the bus connector role. Action Disable security on the named bus, or remove the named group from the bus connector role, or remove all pre-Version 6.1 bus members from the bus.
CWSJA0110E: The assistanceEnabled and policyName parameters are not valid when you add a server or WebSphere MQ Server as a bus member.
Explanation The assistanceEnabled and policyName parameters are valid only when you add a server cluster as a bus member. Action Either do not use the assistanceEnabled and policyName parameters, or add a server cluster as a bus member.
CWSJA0111E: The value of policyName {0} is not valid.
Explanation Valid policy names are HA, SCALABILITY, SCALABILITY_HA, or CUSTOM. Action Either specify a valid policy name, or do not use messaging engine policy assistance (set the assistanceEnabled parameter to false).
CWSJA0112E: The assistanceEnabled or policyName parameter is missing, when both are required.
Explanation To use messagine engine policy assistance, set the assistanceEnabled parameter to true and specify a policyName parameter. Action Either set the assistanceEnabled parameter to true and specify a valid policyName parameter, or do not use messaging engine policy assistance (set the assistanceEnabled parameter to false).
CWSJA0113E: The failover, failback, preferredServersOnly, or preferredServerList parameters are not valid.
Explanation The failover, failback, preferredServersOnly, and preferredServerList parameters are valid only when assistanceEnabled is true and policyName is CUSTOM. Action Either set the assistanceEnabled parameter to true and the policyName parameter to CUSTOM, or or do not use these parameters.
CWSJA0114E: Server {1} on node {0} is not a member of cluster {2}.
Explanation You specified a server in the preferred servers list when that server is not a member of the current cluster. Action Ensure that the servers specified for the preferredServerList parameter are members of the current cluster.
CWSJA0115E: The enableAssistance or policyName parameter is missing.
Explanation To modify messagine engine policy assistance for a cluster, specify either the assistanceEnabled or the policyName parameter. Action Specify the assistanceEnabled parameter, the policyName parameter, or both.
CWSJA0116E: The assistanceEnabled parameter is set to true but the policyName parameter is missing.
Explanation To use messagine engine policy assistance, set the assistanceEnabled parameter to true and specify a valid policyName parameter. Valid policy names are HA, SCALABILITY, SCALABILITY_HA, or CUSTOM. Action Either specify a valid policy name, or do not use messaging engine policy assistance (set the assistanceEnabled parameter to false).
CWSJA0117E: A policyName parameter is specified when the assistanceEnabled parameter is set to false.
Explanation To disable messaging engine policy assistance, set the assistanceEnabled parameter to false and do not specify a policyName parameter. Action Either set the assistanceEnabled parameter to false and do not specify a policyName parameter, or set the assistanceEnabled parameter to true and specify a valid policyName parameter.
CWSJA0118E: If a messaging engine cannot fail over, it must run on one preferred server.
Explanation The failover parameter is set to false but either the preferredServersOnly parameter is set to false or the preferredServerList parameter does not specify one server. Action Either ensure that the preferredServersOnly parameter is set to true and the preferredServerList parameter specifies one server, or set the failover parameter to true.
CWSJA0119E: If a messaging engine can not fail over, it can not fail back.
Explanation The failover parameter is set to false, but the failback parameter is set to true. Action Either set the failback parameter to false, or set the failover parameter to true.
CWSJA0120E: If a messaging engine can fail over to preferred servers only, there must be at least two servers in the preferred servers list.
Explanation The failover parameter is set to true and the preferredServersOnly parameter is set to true, but the the preferredServerList parameter does not specify at least two servers (one to run on, and one to fail over to). Action Either ensure that the preferredServerList parameter specifies at least two servers, or set the preferredServersOnly parameter to false.
CWSJA0121E: We can not change the messaging engine policy when messaging engine policy assistance is disabled.
Explanation You specified a new policyName parameter when the assistanceEnabled parameter is set to false. Action Ensure that the assistanceEnabled parameter is set to true, then specify a valid policyName parameter.
CWSJA0122E: The messaging engine {0} is not valid.
Explanation You attempted to create a core group policy for a messaging engine when the messaging engine is not associated with a server cluster that is a member of a bus. Action Ensure that the name parameter is the name of a messaging engine that is associated with a server cluster that is a member of a bus.
CWSJA0123E: The messaging engine is associated with a server cluster that does not have messaging engine policy assistance enabled and the CUSTOM policy specified.
Explanation To create a core group policy for a messaging engine, the server cluster that the messaging engine is associated with must have messaging engine policy assistance enabled and the CUSTOM policy specified. Action Either specify a messaging engine that is associated with a server cluster that has messaging engine policy assistance enabled and the CUSTOM policy specified, or use modifySIBusMemberPolicy to modify the server cluster so that messaging engine policy assistance is enabled and the CUSTOM policy is specified.
CWSJA0124E: The messaging engine is associated with a server cluster that does not have messaging engine policy assistance enabled, or that has messaging engine policy assistance enabled and the CUSTOM policy specified.
Explanation To correct a core group policy for a messaging engine, the server cluster that the messaging engine is associated with must have messaging engine policy assistance enabled and the HA, SCALABILITY, or SCALABILITY_HA policy specified. Action Either specify a messaging engine that is associated with a server cluster that has messaging engine policy assistance enabled and a valid policy type specified, or use modifySIBusMemberPolicy to modify the server cluster so that assistanceEnabled is true and policyName is set to a valid policy type.
CWSJA0125E: The bus "{0}" could not be found.
Explanation The bus name that was supplied to the command could not be resolved to a Bus object. Action Ensure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration.
CWSJA0126E: The server "{1}" could not be found on node "{0}".
Explanation The node and server names that were supplied to the command could not be used to resolve a Server object. Action Ensure that you used the correct spelling for the node and server names, and that the Server exists in the configuration.
CWSJA0127E: A messaging engine for bus "{0}" could not be found on server "{1}".
Explanation The old bus and server names that were supplied to the command could not be used to resolve a messaging engine object. Action Ensure that you used the correct spelling for the old bus and server names, and that the server is a member of the old bus.
CWSJA0128E: The cluster "{0}" could not be found.
Explanation The cluster name that were supplied to the command could not be used to resolve a Cluster object. Action Ensure that you used the correct spelling for the cluster name, and that the Cluster exists in the configuration.
CWSJA0129E: The server "{1}" on node "{0}" is not a member of the cluster "{2}".
Explanation The node and server supplied to the command do not correspond to a member of the cluster supplied. Action Ensure that you used the correct spelling for the node, server and cluster name, and that the server is a member of the cluster.
CWSJA0130E: The cluster "{0}" is already a member of bus "{1}". Messaging engine migration is not supported in this scenario.
Explanation To migrate a server messaging engine to a cluster, the cluster cannot be a member of the same bus already. Action Ensure that the cluster is not a member of the same bus to which the server belongs.
CWSJA0131E: The server "{1}" on node "{0}" is not a member of the bus "{2}".
Explanation The node and server supplied to the command do not correspond to a member of the bus supplied. Action Ensure that you used the correct spelling for the node, server and bus name, and that the server is a member of the bus.
CWSJA0132E: No messaging engine names available for cluster.
Explanation A suitable messaging engine name could not be created. Action Try specifying different configuration data when creating the messaging engine.
CWSJA0133E: Incorrect parameter combination supplied : node name = "{0}", server name = "{1}", cluster name = "{2}".
Explanation The parameters supplied do not provide a valid bus member configuration. Action To correctly identify a bus member, specify node name and server name, or cluster name.
CWSJA0134E: Server supplied does not have a SIB Service.
Explanation An exception occurred retrieving the SIB Services for the messaging server. Action Ensure that a SIB Service exists for the messaging server.
CWSJA0135E: Scope specification is not valid.
Explanation The details specified do not represent a valid scope specification. Action Make sure that valid node name, server name and cluster name details are used to represent the scope.
CWSJA0136E: bootstrapPolicy setting {0} is not valid. Allowable values MEMBERS_ONLY, SIBSERVICE_ENABLED, MEMBERS_AND_NOMINATED.
Explanation The supplied parameter bootstrapPolicy has a value that is not valid, so the command was rejected. Action Set the bootstrapPolicy to an allowable value of MEMBERS_ONLY, SIBSERVICE_ENABLED, MEMBERS_AND_NOMINATED.
CWSJA0137E: The value "{1}" for the bootstrap member policy bus attribute is not valid for bus "{0}" because the bus contains at least one pre-7.0 bus member.
Explanation The bootstrap member policies of MEMBERS_ONLY and MEMBERS_AND_NOMINATED are not supported by pre-7.0 nodes, as a result they cannot be specified for a bus that contains pre-7.0 bus members. Action Specify a setting that is supported by a bus with pre-7.0 members, or remove all pre7.0 bus members from the bus.
CWSJA0138E: The bootstrap policy for bus "{0}" is not compatible with server "{1}" because it resides on pre-7.0 node "{2}".
Explanation The server could not be added to the bus because the server resides on a pre-7.0 WAS vnode, and the bootstrap policy setting is not compatible with pre-Version 7.0 nodes. The bootstrap policy setting must not be MEMBERS_ONLY, or MEMBERS_AND_NOMINATED. Action Change the bootstrap policy to be SIBSERVICE_ENABLED, or upgrade the named server so that it resides on a v7.0 node.
CWSJA0139E: The bootstrap policy for bus "{0}" is not compatible with cluster "{1}" because it has members that reside on pre-7.0 nodes.
Explanation The cluster could not be added to the bus because the cluster has members that reside on a pre-7.0 WAS vnode, and the bootstrap policy setting is not compatible with pre-Version 7.0 nodes. The bootstrap policy setting must not be MEMBERS_ONLY, or MEMBERS_AND_NOMINATED. Action Change the bootstrap policy to be SIBSERVICE_ENABLED, or upgrade the named cluster so that all servers in the cluster reside on a v7.0 node.
CWSJA0140E: The server {0} on node {1} does not support the useServerIdForMediations option configured for bus {2}.
Explanation The server could not be added to the bus because the bus has been configured to use the server identity for mediations, but the server resides on a pre-7.0 WAS vnode. The useServerIdForMediations is not compatible with pre-Version 7.0 nodes. Action Change the bus to use an authentication alias for mediations instead of the server identity.
CWSJA0141E: The cluster {0} does not support the useServerIdForMediations option configured for bus {1}.
Explanation The cluster could not be added to the bus because the bus has been configured to use the server identity for mediations, but the cluster contains members that reside on pre-7.0 WAS vnode. The useServerIdForMediations is not compatible with pre-Version 7.0 nodes. Action Change the bus to use an authentication alias for mediations instead of the server identity.
CWSJA0142E: The bus {0} could not be modified to use the server identity for mediations as it contains members that reside on pre-Version 7.0 nodes.
Explanation The bus contains servers or clusters that run on pre-Version 7.0 nodes. The userServerIdForMediations option does not support pre-Version 7.0 nodes so the command could not complete. Action Upgrade the pre-Version 7.0 nodes.
CWSJA0143E: The new initial JVM heap size value of {0} MB is not in the acceptible range of {1} MB to {2} MB.
Explanation The supplied initial JVM heap size value is not in the acceptable range. Action Change the supplied initial JVM heap size value to one that is in the acceptable range.
CWSJA0144E: The new maximum JVM heap size value of {0} MB is not in the acceptible range of {1} MB to {2} MB.
Explanation The supplied maximum JVM heap size value is not in the acceptable range. Action Change the supplied maximum JVM heap size value to one that is in the acceptable range.
CWSJA0145E: Duplicate destination "{0}" in nameList.
Explanation The given destination is specified more than once in the nameList. Action Make sure that the destinations specified in the nameList are unique.
CWSJA0146E: The new initial JVM heap size value of {0} is bigger than the new maximum JVM heap size value of {1}.
Explanation The supplied initial JVM heap size value is bigger than the supplied maximum JVM heap size value. Action Change the supplied initial and maximum JVM heap size values so that the initial JVM heap size value is not be bigger than the maximum JVM heap size value.
CWSJA0147E: The parameter "auditAllowed" is only valid for a destination type which is TopicSpace.
Explanation The auditAllowed parameter can only be used when the destination type is TopicSpace. Action Remove the parameter specified, then reissue the command.
CWSJA0148E: The "queuePoints" parameter can only be used when the target destination is an existing queue destination.
Explanation Specifying queue points is only permitted when the alias directly targets a Queue destination. Action Do not supply the "queuePoints" parameter, or supply it and target a Queue destination.
CWSJA0149E: The "queuePoints" parameter can only be used when the target destination is in the same bus as the alias destination definition.
Explanation Specifying queue points is only permitted when the alias directly targets a Queue destination in the same bus as the alias definition (the 'bus' parameter). Action Do not supply the "queuePoints" parameter, or supply it and target a Queue destination in the same bus as the alias definition.
CWSJA0150E: The "queuePoints" parameter can only be used when the target destination is a queue destination with one or more queue points.
Explanation Specifying queue points is only permitted when the alias directly targets a Queue destination localized to a bus member with multiple messaging engines. Action Do not supply the "queuePoints" parameter, or supply it and target a Queue destination localized to a bus member with multiple messaging engines.
CWSJA0151E: The supplied queuePoints are not valid for the specified target destination. Each queue point must be a SIBQueueLocalizationPoint belonging to the target queue.
Explanation Each queue point must be a SIBQueueLocalizationPoint belonging to the target queue. Action Identify any non valid queue point(s) and correct the list.
CWSJA0152E: The "mediationPoints" parameter can only be used when the target destination is an existing queue destination.
Explanation Specifying mediation points is only permitted when the alias directly targets a Queue destination. Action Do not supply the "mediationPoints" parameter, or supply it and target a Queue destination.
CWSJA0153E: The "mediationPoints" parameter can only be used when the target destination is in the same bus as the alias destination definition.
Explanation Specifying mediation points is only permitted when the alias directly targets a Queue destination in the same bus as the alias definition (the 'bus' parameter). Action Do not supply the "mediationPoints" parameter, or supplpy it and target a Queue destination in the same bus as the alias definition.
CWSJA0154E: The "mediationPoints" parameter can only be used when the target destination is a queue destination with one or more mediation points.
Explanation Specifying mediation points is only permitted when the alias directly targets a Queue destination localized to a bus member with multiple messaging engines. Action Do not supply the "mediationPoints" parameter, or supply it and target a Queue destination localized to a bus member with multiple messaging engines.
CWSJA0155E: The supplied mediationPoints are not valid for the specified target destination. Each mediation point must be a SIBMediationPoint belonging to the target queue.
Explanation Each mediation point must be a SIBMediationPoint belonging to the target queue. Action Identify any non valid mediation point(s) and correct the list.
CWSJA0156E: The "queuePoints" and "mediationPoints" parameters can only be specified when the type of the destination is ALIAS.
Explanation It is not valid to supply either queuePoints or mediationPoints when the destination type is not set to ALIAS. Action Only supply "queuePoints" or "mediationPoints" when the destination type is set to ALIAS.
CWSJA0157E: The target destination for an Alias destination must not be localized on an MQ Server.
Explanation It is not valid to supply a target destination for an Alias destination that is localized on an MQ Server. Action Supply a target destination that is not localized on an MQ Server.
CWSJA0158E: The useAllQueuePoints parameter can only be set false where queuePoints contains some values
Explanation It is not valid to clear this option (setting it false) unless queuePoints contains at least one queue point Action Either set useAllQueuePoints true, or set queuePoints to contain at least one queue point
CWSJA0159E: The useAllMediationPoints parameter can only be set false where mediationPoints contains some values
Explanation It is not valid to clear this option (setting it false) unless mediationPoints contains at least one mediation point Action Either set useAllQueuePoints true, or set mediationPoints to contain at least one mediation point
CWSJA0160E: Only one server bus member for each service integration bus can be added as part of the current profile.
Explanation Multiple server bus members for each service integration bus are not allowed for base profiles. Action Review the proposed service integration bus configuration requirements and either adopt a single server bus member for each service integration bus deployment or use multiple server bus members for each service integration bus in a non-base profile.
CWSJA0200E: Failed to get SIB JMS resource adapter at specified scope.
Explanation An unsuccessful attempt was made to locate a JMS JCA resource adapter installed at the specified scope. Action Make sure that a JMS JCA resource adapter exists within the specified scope.
CWSJA0201E: Incorrect value for type parameter: {0}.
Explanation An incorrect type has been found for the connection factory. Action Make sure that the connection factory type is either Queue, Topic or All.
CWSJA0202E: Failed to get J2C command result: {0}.
Explanation The command was run but no result object was returned. Action Make sure that the correct configuration information has been passed to the command being run.
CWSJA0203E: Target object is not a SIB JMS connection factory.
Explanation The target object specified is not of type QueueConnectionFactory, TopicConnectionFactory or ConnectionFactory. Action Make sure that a valid connection factory interface is specified to the target object.
CWSJA0204E: Target object is not a SIB JMS queue.
Explanation The interface of the target object is not of type Queue. Action Make sure that the target object is of type Queue.
CWSJA0205E: Target object is not a SIB JMS topic.
Explanation The interface of the target object is not of type Topic. Action Make sure that the target object is of type Topic.
CWSJA0206E: Not allowed to create a SIB JMS connection factory called "{0}".
Explanation The name provided for the SIB JMS connection factory does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0207E: Not allowed to delete a SIB JMS connection factory called "{0}".
Explanation The name provided for the SIB JMS connection factory does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0208E: Not allowed to create a SIB JMS queue called "{0}".
Explanation The name provided for the SIB JMS queue does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0209E: Not allowed to delete a SIB JMS queue called "{0}".
Explanation The name provided for the SIB JMS queue does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0210E: Not allowed to create a SIB JMS topic called "{0}".
Explanation The name provided for the SIB JMS Topic does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0211E: Not allowed to delete a SIB JMS topic called "{0}".
Explanation The name provided for the SIB JMS topic does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0212E: Not allowed to configure a SIB JMS queue with "{0}" = "{1}".
Explanation The value provided for the specified JMS Queue property is not valid. Action Make sure that the value specified is allowed for the given property.
CWSJA0213E: Not allowed to configure a SIB JMS topic with "{0}" = "{1}".
Explanation The value provided for the specified JMS Topic property is not valid. Action Make sure that the value specified is allowed for the given property.
CWSJA0215E: Failed to create a SIB JMS queue with queue name : "{0}".
Explanation An instance of a JMS Queue with the specified queue name could not be created. Action Make sure that a valid queue name has been specified upon creation of the Queue object.
CWSJA0216E: Failed to create a SIB JMS topic with topic name : "{0}".
Explanation An instance of a JMS topic with the specified topic name could not be created. Action Make sure that a valid topic name has been specified upon creation of the Topic object.
CWSJA0217E: An internal error has occurred. Failed to create a SIB JMS connection factory.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSJA0400E: ActivationSpec with given name({0}) or jndiName({1}) already exists in given scope.
Explanation The named ActivationSpec already exists on the specified resource adapter. Action Make sure that ActivationSpec objects are unique within a given scope.
CWSJA0401E: Unable to create SIB JMS ActivationSpec at scope {0}.
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.
CWSJA0402E: Unable to modify attributes of ActivationSpec {0}.
Explanation It is likely that incorrect or null parameters were passed to the modify command. Action Make sure that all parameters passed to the modify command are valid.
CWSJA0403E: Unable to find SIB JMS resource adapter in scope {0}.
Explanation It is likely that incorrect or null parameters were passed to the command. Action Make sure that all parameters are valid, and that a JMS JCA resource adapter is installed at the specified scope.
CWSJA0404E: Failed to get list of existing SIB JMS ActivationSpecs from resource adapter {0}.
Explanation The list command was unsuccessful either because null parameters were given, or no result was returned. Action Make sure that all parameters passed to the command are valid, and not null.
CWSJA0405E: {0} is not a valid SIB JMS ActivationSpec.
Explanation The target object specified is not of the correct type. Action Make sure that the target object is of type JMS ActivationSpec.
CWSJA0406E: Not allowed to create a SIB JMS ActivationSpec called "{0}".
Explanation The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0407E: Not allowed to delete a SIB JMS ActivationSpec called "{0}".
Explanation The name provided for the SIB JMS ActivationSpec does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0409E: {0} is not a valid value for read ahead.
Explanation A value that is not valid has been entered for the read ahead property. Action Check the documentation for a valid value for this property.
CWSJA0410E: {0} is not a valid value for destination type.
Explanation A value that is not valid has been entered for the destination type property. Action Check the documentation for a valid value for this property.
CWSJA0411E: {0} is not a valid value for target type.
Explanation A value that is not valid has been entered for the target type property. Action Check the documentation for a valid value for this property.
CWSJA0412E: {0} is not a valid value for target significance.
Explanation A value that is not valid has been entered for the target significance property. Action Check the documentation for a valid value for this property.
CWSJA0413E: {0} is not a valid value for the parameter: Consumer does not modify payload after get.
Explanation A value that is not valid has been entered for this property. Valid values are GuaranteedByUser and NotGuaranteedByUser. Action Make sure that a valid value is entered for the property.
CWSJA0414E: {0} is not a valid value for the parameter: Forwarder does not modify payload after set.
Explanation A value that is not valid has been entered for this property. Valid values are true and false. Action Make sure that a valid value is entered for the property.
CWSJA0415E: {0} is not a valid value for retry interval.
Explanation A value that is not valid has been entered for the retry interval property. Action Check the documentation for a valid value for this property.
CWSJA0416E: The autoStopSequentialMessageFailure value, {0}, is not an valid integer value greater than or equal to zero.
Explanation Valid values are zero which indicates that MDB endpoints will not be automatically stopped. Or one or more, which indicates the number of failing sequential messages that will cause the MDB endpoint to be stopped. Action Specify a value of zero or more.
CWSJA0417E: The failingMessageDelay value, {0}, is not an valid long value greater than or equal to zero.
Explanation Valid values are zero or more, which indicate the period of time in milliseconds that passes before a failing message is retried before its maximum failed delivery limit is reached Action Specify a value of zero or more.
CWSJA0418E: The failingMessageDelay value can only be greater than zero if autoStopSequentialMessageFailure is greater than zero.
Explanation The message delay is only used when sequential message failures are being monitored and the MDB endpoint can be automatically stopped. Action Specify a value of zero for the failingMessageDelay or a positive value for autoStopSequentialMessageFailure.
CWSJA0600E: Mediation "{0}" already exists.
Explanation The mediation specified already exists within the administrative domain. Action Make sure that all mediations are uniquely identified within an administrative domain.
CWSJA0601E: Mediation "{0}" cannot be found.
Explanation The mediation specified could not be found within the administrative domain. Action Make sure that the mediation specified to the command exists.
CWSJA0602E: Mediation "{0}" cannot be deleted. It is being used to mediate destination "{1}".
Explanation A mediation cannot be deleted whilst it is being used to mediate a destination. Action Make sure that a mediation is not being used before trying to delete it.
CWSJA0603E: Destination "{0}" cannot be found.
Explanation The destination specified could not be found within the administrative domain. Action Make sure that the specified destination exists.
CWSJA0604E: Destination "{0}" is already mediated.
Explanation The destination specified is already mediated, and a destination cannot be mediated twice. Action Make sure that the specified destination is not already mediated before trying to mediate it.
CWSJA0605E: Supply either "node" and "server" parameters or "cluster" parameter.
Explanation Null parameters have been supplied to the command. Action Make sure that either the node and server parameters, or the cluster parameter, is supplied to the command.
CWSJA0606E: Bus member "{0}" cannot be found.
Explanation The bus member specified could not be located in the administrative domain. Action Make sure that the bus member specified exists before trying to use it.
CWSJA0607E: Destination "{0}" cannot be mediated.
Explanation An inconsistent configuration has been detected. Action Run cross document validation to check the destination configuration.
CWSJA0608E: Destination "{0}" is not mediated.
Explanation We cannot un-mediate a destination which is not already mediated. Action Make sure that the destination is mediated before attempting to un-mediate it.
CWSJA0609E: Not allowed to create a mediation called "{0}".
Explanation The name provided for the mediation does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0610E: Not allowed to delete a mediation called "{0}".
Explanation The name provided for the mediation does not adhere to naming restrictions. Action Make sure that the name does not begin with an underscore, and is not empty or null.
CWSJA0611E: When supplying "wmqServer" parameter it must be supplied with either "node" and "server" parameters or "cluster" parameter.
Explanation Invalid parameters have been supplied to the command. When specifying the wmqServer parameter, specify execution point where the mediation will run. Action Make sure that the wmqServer parameter is supplied with either the node and server parameters, or the cluster parameter.
CWSJA0612E: The parameter {0} is only valid when specifying a WebSphere MQ Server name using the "wmqServer" parameter.
Explanation The supplied parameter is not valid when mediating a destination and a WebSphere MQ server name was not specified. Action Remove the parameter from the mediateSIBDestination command then retry.
CWSJA0613E: When specifying a WebSphere MQ Server name using the "wmqServer" parameter the "wmqQueueName" parameter must be supplied.
Explanation When specifying a WebSphere MQ server name a WebSphere MQ Queue name must be supplied. Action Add the wmqQueueName parameter to the mediateSIBDestination command then retry.
CWSJA0614E: No bus member found for WebSphere MQ server {0} on bus {1}.
Explanation When mediating a destination using a WebSphere MQ server it must have been added to the bus, but no bus member was found. Action Make sure that the WebSphere MQ server has been added to the bus specified then retry the command.
CWSJA0615E: node parameter specifies a pre version 6.1 node, which is not valid for a WebSphere MQ mediation execution point
Explanation The node parameter specifies a WAS v6.0 node. This node cannot host a mediation execution point for a WebSphere MQ mediated destination. Action Select a node that is of v6.1 or later.
CWSJA0616E: When specifying a value of true for parameter "externallyMediated" a "wmqServer" parameter must be supplied.
Explanation External mediation support is only valid for destinations localized to WebSphere MQ. Action Either specify a false value for the externallyMediated parameter or add a wmqServer parameter.
CWSJA0617E: When specifying a value of true for parameter "externallyMediated" and a WebSphere MQ server, the "node", "server" or "cluster" parameters should not be specified.
Explanation Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ. Action Remove the node, server or cluster parameter that was specified.
CWSJA0618E: When specifying a value of true for parameter "externallyMediated" the destination being mediated must be assigned to WebSphere MQ.
Explanation Externally mediating destinations are only supported for destinations that are localized in WebSphere MQ. Action Set the externallyMediated parameter to false, or mediate a destination that is assigned to WebSphere MQ.
CWSJA0800E: No cells found in configuration archive.
Explanation The configuration archive does not contain any cells. Action Make sure that the configuration archive contains a cell.
CWSJA0801E: No cells found in the dmgr configuration.
Explanation The dmgr configuration does not contain any cells. Action Make sure that the dmgr configuration contains a cell.
CWSJA0802W: WARNING: Bus "{0}" already exists in the dmgr configuration. Bus "{0}" will NOT be replaced in the dmgr configuration.
Explanation A bus of the same name already exists in the dmgr configuration. As a result the bus on this node will not be added to the dmgr configuration. However the node will still be federated. Action Make sure that the named bus does not exist in the dmgr configuration before running the addNode command. If there is a conflict in the names, the bus on the node being federated is not included. As a result the bus on the dmgr must be configured to have the required resources needed. Either that, or the bus should be renamed or deleted.
CWSJA0803E: Configuration contains no cells.
Explanation The configuration does not contain any cells. Action Make sure that the configuration contains a cell.
CWSJA1000E: Deployment manager configuration contains no cells.
Explanation No cells were found in the dmgr configuration. Action Make sure that the dmgr configuration contains a cell definition.
CWSJA1001E: No dmgr configuration session supplied.
Explanation Internal error. Method invoked requires a dmgr configuration session parameter. Action Please contact the system administrator to resolve this problem.
CWSJA1002E: No cell specified.
Explanation Internal error. Method invoked requires a cell object. Action Please contact the system administrator to resolve this problem.
CWSJA1003E: No bus specified.
Explanation Internal error. Method invoked requires a bus object. Action Please contact the system administrator to resolve this problem.
CWSJA1004E: No destination specified.
Explanation Internal error. Method invoked requires destination object. Action Please contact the system administrator to resolve this problem.
CWSJA1200E: The {0} command did not return a result.
Explanation Internal error. The specified command did not return a result. Action Please contact the system administrator to resolve this problem.
CWSJA1400E: Application server template ID is null.
Explanation Internal error. The application server template ID is null. Action Please contact the system administrator to resolve this problem.
CWSJA1600E: WebSphere MQ Server "{0}" not found.
Explanation The specified WebSphere MQ server name could not be located within the administrative domain. Action Make sure that the WebSphere MQ server name specified is a valid name for an existing WebSphere MQ server.
CWSJA1601E: More than one WebSphere MQ Server named "{0}" found.
Explanation Only one instance of a WebSphere MQ server should exist with the name specified, yet more than one instance has been found. Action Make sure that WebSphere MQ server names are unique within the administrative domain.
CWSJA1602E: A WebSphere MQ Server named "{0}" already exists.
Explanation A WebSphere MQ server name must be unique. A WebSphere MQ server with the supplied name already exists. Action Make sure that WebSphere MQ server names are unique within the administrative domain.
CWSJA1603E: WebSphere MQ Server Proxy "{0}" not found on Bus {1}.
Explanation The specified WebSphere MQ server proxy name could not be located within the bus administrative domain. Action Make sure that the WebSphere MQ server proxy name specified is a valid name for an existing WebSphere MQ server proxy. Check that the bus name specified is the correct bus for the WebSphere MQ server proxy.
CWSJA1604E: Multiple instances of WebSphere MQ Server Proxy "{0}" found on Bus {1}.
Explanation Only one instance of a WebSphere MQ server proxy should exist with the name specified, yet more than one instance has been located. Action Make sure that WebSphere MQ server proxy names are unique within the administrative domain.
CWSJA1605E: The selected JMS provider is built-in and cannot be deleted.
Explanation Only custom JMS providers can be deleted. Action Select a different JMS provider to delete.
CWSJA1606E: A WebSphere MQ server has not been supplied as the target object
Explanation A WebSphere MQ server must be supplied as the target object Action Set a WebSphere MQ server as the target object.
CWSJA1607E: A name has not been supplied for the WebSphere MQ server SVRCONN channel
Explanation A WebSphere MQ server SVRCONN channel must have a name. Action Set the WebSphere MQ server SVRCONN channel name using the "name" parameter.
CWSJA1608E: The parameters "sslEndpoint", "sslChain", "sslCRL", "sslReset" and "sslPeer" are not valid when the "sslType" parameter is set to "NONE".
Explanation The parameters "sslEndpoint", "sslChain", "sslCRL", "sslReset" and "sslPeer" are not valid when the "sslType" parameter is set to "NONE". Action Specify a different sslType or do not use the illegal parameters.
CWSJA1609E: The parameters "sslEndpoint" and "sslChain" are not valid when the "sslType" parameter is set to "CENTRAL".
Explanation The parameters "sslEndpoint" and "sslChain" are not valid when the "sslType" parameter is set to "CENTRAL". Action Specify a different sslType or do not use the illegal parameters.
CWSJA1610E: The "sslChain" parameter is not valid when the "sslType" parameter is set to "SPECIFIC".
Explanation The "sslChain" parameter is not valid when the "sslType" parameter is set to "SPECIFIC". Action Specify a different sslType or do not use the illegal parameters.
CWSJA1611E: The "sslChain" parameter is not valid when the "sslType" parameter is set to "CHAIN".
Explanation The "sslChain" parameter is not valid when the "sslType" parameter is set to "CHAIN". Action Specify a different sslType or do not use the illegal parameters.
CWSJA1612E: The sslType {0} is not valid (valid values are "NONE", "CENTRAL", "SPECIFIC" and "CHAIN").
Explanation Valid values for the sslType parameter are "NONE", "CENTRAL", "SPECIFIC" and "CHAIN". Action Set the sslType parameter to be either "NONE", "CENTRAL", "SPECIFIC" or "CHAIN"
CWSJA1613E: The "sendExitInit" parameter can only be supplied if the "sendExit" parameter is supplied.
Explanation The "sendExitInit" parameter can only be supplied if the "sendExit" parameter is supplied. Action Supply the "sendExit" parameter or do not suplly the "sendExitInit" parameter.
CWSJA1614E: The "receiveExitInit" parameter can only be supplied if the "receiveExit" parameter is supplied.
Explanation The "receiveExitInit" parameter can only be supplied if the "receiveExit" parameter is supplied. Action Supply the "receiveExit" parameter or do not suplly the "receiveExitInit" parameter.
CWSJA1615E: The "securityExitInit" parameter can only be supplied if the "securityExit" parameter is supplied.
Explanation The "securityExitInit" parameter can only be supplied if the "securityExit" parameter is supplied. Action Supply the "securityExit" parameter or do not suplly the "securityExitInit" parameter.
CWSJA1616E: A host has not been supplied for the WebSphere MQ server endpoint
Explanation A WebSphere MQ server endpoint must have a host. Action Set the WebSphere MQ server endpoint host using the "host" parameter.
CWSJA1617E: A port has not been supplied for the WebSphere MQ server endpoint
Explanation A WebSphere MQ server endpoint must have a port. Action Set the WebSphere MQ server endpoint port using the "port" parameter.
CWSJA1618E: A valid value must be supplied for the endpoint port.
Explanation A valid value must be supplied for the endpoint port. Action Set the WebSphere MQ server endpoint with a valid port number.
CWSJA1619E: A WebSphere MQ server endpoint has not been supplied as the target object
Explanation A WebSphere MQ server endpoint must be supplied as the target object Action Set a WebSphere MQ server endpoint as the target object.
CWSJA1620E: Neither a host or port has not been supplied for the WebSphere MQ server endpoint
Explanation At least one of the endpoint attributes must be modified Action Supply either a host, port or both parameters.
CWSJA1621E: A WebSphere MQ server server connection channel has not been supplied as the target object
Explanation A WebSphere MQ server server connection channel must be supplied as the target object Action Set a WebSphere MQ server server connection channel as the target object.
CWSJA2000E: The Foreign Bus "{0}" could not be found on Bus "{1}"
Explanation A foreign bus name was supplied to the command that could not be resolved on the specified bus. Action Make sure that the foreign bus supplied to the command exists in the configuration.
CWSJA2001E: The parameter nextHopBus must be specified when routingType = Indirect
Explanation When the routingType parameter is set to Indirect, a valid nextHopBus parameter must be supplied. Action Make sure that the nextHopBus parameter and value is supplied to the command.
CWSJA2002E: The type parameter must be specified when routingType parameter = Direct
Explanation When the routingType parameter = Direct, a valid type parameter must be specified. Action Make sure that the type parameter for the command is either SIBus or MQ.
CWSJA2003E: An invalid routingType parameter was supplied to this command, allowable values are "Direct" or "Indirect".
Explanation The routingType of either Direct or Indirect is required for this command. Action Make sure that the routingType parameter for the command is either Direct or Indirect.
CWSJA2004E: A virtual link could not be found on foreign bus "{0}"
Explanation The foreign bus specified to the command does not have a virtual link child object. Action Make sure that the foreign bus specified has a virtual link child object.
CWSJA2005E: The foreign bus "{0}" does not contain a SIBVirtualMQLink child object.
Explanation The foreign bus specified contains a SIBVirtualGatewayLink, not the required SIBVirtualMQLink. Action Make sure that the foreign bus specified has a SIBVirtualMQLink child object.
CWSJA2006E: The default priority specified "{0}" is not a valid value for this attribute.
Explanation The value of the default priority attribute must be between 0 and 9 inclusive. Action Make sure that a valid value is specified for the default priority attribute.
CWSJA2007E: The value supplied for "reliability" is greater than the value supplied for "maxReliability".
Explanation The value supplied for the reliability parameter should be less than or equal to the value supplied for the maxReliability parameter. Action Report this problem to the system administrator.
CWSJA2008E: An invalid type parameter was supplied to this command, allowable values are "MQ" or "SIBus".
Explanation The type of either MQ or SIBus is required for this command. Action Make sure that the type parameter for the command is either MQ or SIBus.
CWSJA2009E: The routingType parameter is required if the type parameter is supplied.
Explanation The type parameter is only permitted if the routingType parameter is also supplied. Action Make sure that the routingType parameter is supplied if the type parameter is supplied.
CWSJA2010E: The name of the foreign bus cannot be the same as the local bus name "{0}" on which it is to be created.
Explanation When creating a foreign bus, its name cannot be the same as the local bus on which it is being created. The name should be the unique name of the foreign bus to which you are connecting. Action Make sure that the name parameter supplied is different to the bus parameter.
CWSJA2011E: The value "{0}" is not a valid value for the attribute "{1}". Valid values for "{1}" are BEST_EFFORT_NONPERSISTENT, EXPRESS_NONPERSISTENT, RELIABLE_NONPERSISTENT, RELIABLE_PERSISTENT or ASSURED_PERSISTENT.
Explanation An incorrect value has been supplied. Valid values are BEST_EFFORT_NONPERSISTENT, EXPRESS_NONPERSISTENT, RELIABLE_NONPERSISTENT, RELIABLE_PERSISTENT or ASSURED_PERSISTENT. These values are case sensitive. Action Make sure the a valid value is supplied to the command.
CWSJA2200E: The bus name "{0}" could not be found.
Explanation The bus name that was supplied to the command could not be resolved to a Bus object. Action Make sure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration.
CWSJA2201E: The messaging engine "{0}" could not be found on the bus supplied.
Explanation A messaging engine name was supplied to the command that could not be resolved on the bus name supplied. Action Make sure that both the messaging engine and bus name supplied to the command exist in the configuration.
CWSJA2202E: The value "{0}" is not valid for the parameter "{1}"
Explanation A value that is not valid was supplied for the parameter specified above. Action See the command help for a list of valid parameter values.
CWSJA2203E: An internal error occured getting the "name" attribute of MQLink "{0}" : "{1}"
Explanation An internal error has occurred. See linked exception for details. Action Make sure that a valid MQLink name was specified to the command.
CWSJA2204E: The foreign bus "{0}" could not be found on the bus "{1}"
Explanation The foreign bus name supplied to the command is not the name of a foreign bus configured on the bus. Action Make sure that both the foreign bus and bus name supplied to the command exist in the configuration.
CWSJA2206E: A Bus Member Target with an Engine UUID of "{0}" could not be found
Explanation The messaging engine UUID specified above could not be found on any of the existing bus member targets. Action Make sure that the correct messaging engine was supplied to the command.
CWSJA2207E: The MQLink "{0}" could not be found on the messaging engine "{1}"
Explanation An MQLink with the name supplied could not be found on the messaging engine supplied. Action Make sure that both the messaging engine and MQLink named on the command exist in the configuration.
CWSJA2208E: The target object is not a valid SIB MQLink object.
Explanation This command requires a valid SIB MQLink object to be passed in as the target object. Action Ensure that the target object of the command is a SIB MQLink object.
CWSJA2400E: An internal error occured getting the "name" attribute of SIBLink "{0}" : "{1}"
Explanation An internal error has occurred. See the linked exception for details. Action Make sure that a valid SIBLink name was specified to the command.
CWSJA2401E: A virtual link could not be found on foreign bus "{0}"
Explanation The foreign bus specified to the command does not have a SIBVirtualGatewayLink child object. Action Make sure that the foreign bus specified has a SIBVirtualGatewayLink child object.
CWSJA2402E: The foreign bus "{0}" does not contain a SIBVirtualGatewayLink child object.
Explanation The foreign bus specified contains a SIBVirtualMQLink, not the required SIBVirtualGatewayLink. Action Make sure that the foreign bus specified has a SIBVirtualGatewayLink child object.
CWSJA2403E: The SIBLink "{0}" could not be found on the messaging engine "{1}"
Explanation A SIBLink name was supplied to the command that could not be resolved on the messaging engine name supplied. Action Make sure that both the messaging engine and SIBLink names supplied to the command exist in the configuration.
CWSJA2404E: There is already a SIBLink or MQLink with the name "{0}"
Explanation SIBLink and MQLink objects share a namespace within a messaging engine, and require unique names. Action To use the supplied name, ensure that neither an MQLink nor SIBLink already exists with that name. Otherwise, specify a different name.
CWSJA2405E: Scope specification is not valid.
Explanation The details specified do not represent a valid scope specification. Action Make sure that valid node name, server name and cluster name details are used to represent the scope.
CWSJA2406E: The messaging engine "{0}" is running in a cluster that contains one or more v6.1 or earlier servers. The preferLocal attribute can only be set to false when a cluster running the messaging engine contains only v7.0 servers.
Explanation The preferLocal attribute can only be set to false when a cluster running the messaging engine contains only v7.0 servers. Action Ensure that the messaging engine hosting the link is running in a cluster containing only v7.0 servers before setting the preferLocal attribute to false.
CWSJA2407E: The messaging engine "{0}" is running in a v6.1 or earlier server. The preferLocal attribute can only be set to true when the server running the messaging engine is v7.0.
Explanation The preferLocal attribute can only be set to true when the server running the messaging engine is v7.0. Action Ensure that the messaging engine hosting the link is running on a v7.0 server before setting the preferLocal attribute to true.
CWSJA2408E: The foreign bus "{0}" is already in use by another SIBLink.
Explanation The foreign bus specified already contains a reference to a SIBLink. Action Ensure that a foreign bus is specified that doesn't reference a pre-existing SIBLink.
CWSJA2409E: The foreign bus "{0}" is already in use by another MQLink.
Explanation The foreign bus specified already contains a reference to a MQLink. Action Ensure that a foreign bus is specified that doesn't reference a pre-existing MQLink.
CWSJA2500E: The configuration service is not available.
Explanation An AdminTask command is trying to work with a process that is not connected to a server that has a running configuration service. Action Reissue the command on a process that is connected to a server that has a running configuration service. For example a dmgr, managed server or unmanaged server.
CWSJA2501E: Target object and target parameters "{0}" can not be both specified.
Explanation An AdminTask command is specifying both a target object and one of the parameters used to specify the target. Action Reissue the command either specifying the target object directly, or specifying the target object using the target parameters.
CWSJA2502E: A target object or target parameters "{0}" must be specified.
Explanation An AdminTask command is invoked without specifying either a target object or the parameters that are used to specify the target. Action Reissue the command either specifying the target object directly, or specifying the target object using the target parameters.
CWSJA2601E: Incorrect parameter combination supplied : node name = "{0}", server name = "{1}", cluster name = "{2}".
Explanation The command should specify a specific server or a cluster. To specify a server a valid node name and server name must be provided.
To specify a cluster just the cluster name should be provided.
Action Rerun the command specifying either a node and server name, or a cluster name.
CWSJA2602E: The cluster {0} does not exist.
Explanation The specified cluster does not exist. Action Rerun the command specifying the name of a cluster that exists.
CWSJA2603E: The server {0} on node {1} does not exist.
Explanation The specified server does not exist. Action Rerun the command specifying the name of a server and node that exists.
CWSJA2604E: The cluster {0} is not a bootstrap member.
Explanation The specified cluster is not a bootstrap member, so cannot be removed from the list of bootstrap members. Action Rerun the command specifying the name of a cluster that is a bootstrap member.
CWSJA2605E: The server {0} on node {1} is not a bootstrap member.
Explanation The specified server is not a bootstrap member, so cannot be removed from the list of bootstrap members. Action Rerun the command specifying the name of a server and node that is a bootstrap member.
CWSJA2606E: The cluster {0} contains servers that do not support bootstrap members. The servers are on the nodes: {1}.
Explanation In order for clusters to be bootstrap members all the servers in the cluster must be on a node whose version is at least 7.0.0.0. Action This can be resolved either by upgrading all the nodes, or by choosing a different cluster.
CWSJA2607E: The cluster {0} is a bus member.
Explanation A cluster cannot be both a bus member and a bootstrap member. Action No action is required.
CWSJA2608E: The cluster {0} is already a bootstrap member.
Explanation This message is for informational purposes only. Action No action is required.
CWSJA2609E: The node {0} does not support bootstrap members.
Explanation In order for a server to be a bootstrap member the node it is defined to needs to have a version that is at least 7.0.0.0. Action This can be resolved either by upgrading the nodes, or by choosing a server on a different node.
CWSJA2610E: The server {0} on the node {1} is a bus member.
Explanation A server cannot be both a bus member and a bootstrap member. Action No action is required.
CWSJA2611E: The server {0} on the node {1} is already a bootstrap member.
Explanation This message is for informational purposes only. Action No action is required.