> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/messaging-technology/messaging-bus-comparison-series/comparision-16-queue-owner.md).

# Comparision #16: Queue Owner

Only IBMMQ, Solace PubSub+ and Tibco EMS support this function. 

| Capability          | IBM MQ          | Solace                            | TIBCO EMS                       |
| ------------------- | --------------- | --------------------------------- | ------------------------------- |
| Queue Owner Concept | No              | Yes                               | No                              |
| Send                | `+put`          | Consume/Delete/Modify permissions | `send`                          |
| Receive             | `+get`          | Consume                           | `receive`                       |
| Browse              | `+browse`       | Read-only permission              | Limited/no dedicated permission |
| View Properties     | `+inq`          | Endpoint permissions              | Admin permissions               |
| Modify Queue        | `+chg` / `+set` | Owner or Delete permission        | Admin permissions               |
| Delete Queue        | `+dlt`          | Owner/Delete permission           | Admin permissions               |

Permission

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Product</td><td valign="top">Permission Type</td></tr><tr><td valign="top">IBM MQ</td><td valign="top"><p>·         Browse – Read messages without removing them.</p><p>·         Get – Retrieve (consume) messages from the queue.</p><p>·         Put – Add messages to the queue.</p><p>·         Inquire – View queue attributes (e.g., depth, status).</p><p>·         Set – Modify queue attributes.</p><p>·         Delete – Remove the queue.</p><p>·         Alter – Change queue properties.</p><p>·         Passid / Passall – Pass identity or all context when putting messages.</p><p>·         Change – Change object definitions.</p><p>·         Control – Perform administrative actions (e.g., start/stop).</p></td></tr><tr><td valign="top">Solace PubSub+</td><td valign="top"><p>·         Send – put messages</p><p>·         Receive – get messages</p><p>·         Browse</p><p>·         Modify – change properties</p><p>·         Delete</p><p>·         Admin – full control</p></td></tr><tr><td valign="top">Tibco EMS</td><td valign="top"><p>·         Send – put messages</p><p>·         Receive – get messages</p><p>·         Browse</p><p>·         Modify – change properties</p><p>·         Delete</p><p>·         Admin – full control</p></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/messaging-technology/messaging-bus-comparison-series/comparision-16-queue-owner.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.