178 Candle Products Messages Manual (KLVHS–KONCT)
KMC0148E Your request failed. MQSeries cluster queue cannot be a transmission
queue.
Explanation: The request was rejected by MQSeries because it would have
resulted in a cluster queue also being a transmission queue. This is not supported.
User Response: Ensure that the configuration specifies either:
Usage Normal.
The Cluster Name and Cluster Namelist properties with values of blanks.
KMC0149E Your request failed. MQSeries ClusterName and ClusterNamelist
attributes conflict.
Explanation: The request was rejected because it would have resulted in the
Cluster Name property and the Cluster Namelist property both being nonblank.
At least one of these properties must be blank.
User Response: Specify either a blank Cluster Name, or a blank Cluster
Namelist for the object.
KMC0150E Your request failed. MQSeries Channel Status not found.
Explanation: You attempted to view the status of an MQSeries channel.
However, no channel status is available for the specified channel. This may
indicate that the channel has not been used.
User Response: None, unless this is unexpected, in which case consult your
MQSeries systems administrator.
KMC0151E You cannot move cluster managed object @1 into a non-cluster
managed object @2.
Explanation: You are attempting to move cluster-generated object @1 into
non-cluster-generated object @2. This is not supported.
User Response: You can only move a cluster-generated object into another
cluster-generated object.
KMC0152E Your request failed. MQSeries Queue contains one or more messages or
uncommitted put or get requests.
Explanation: You attempted to delete an MQSeries queue that is not empty.
User Response: Ensure that the queue you wish to delete does not contain any
messages. Retry the request.
KMC0153E The Queue Manager is already a member of this cluster.
Explanation: You have attempted to make a Queue Manager participate in a
managed cluster by dragging and dropping the Queue Manager to the cluster.
However, the Queue Manager in question is already participating in the cluster.
User Response: None.