愚蠢的 WebSphere MQ 问题
我有两个关于 WebSphere MQ 的非常基本的问题 - 考虑到过去几个月我一直在管理它，我倾向于认为这些都是愚蠢的问题
有没有办法“停用”一个 队列 ？ （例如通过 runmqsc 命令或通过 资源管理器界面）-我认为不是。我 我想我能做的就是删除 它。
如果我创建一个会发生什么 远程队列定义是否真实 远程队列没有到位？将要 它会导致队列出现任何问题 经理？ - 我认为不是。我认为所有 我将收到错误消息 日志。
请让我知道您的想法。 谢谢！
I have two very basic questions on WebSphere MQ - given that I had been kind of administrating it for past few months I tend to think that these are silly questions
Is there a way to "deactivate" a
queue ? (for example through a
runmqsc command or through the
explorer interface) - I think not. I
think what I can do is just delete
it.What will happen if I create a
remote queue definition if the real
remote queue is not in place? Will
it cause any issues on the queue
manager? - I think not. I think all
I will have are error messages in
the logs.
Please let me know your thoughts.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的。您可以像这样更改队列属性：
ALTER Q(QUEUE_NAME) PUT(DISABLED) GET(DISABLED)任何连接的应用程序都将在下一次 API 调用时收到返回代码，告诉它们队列不再可用于 PUT/GET。如果这些程序表现良好，它们将报告错误并结束或进入重试循环。
QRemote 定义将解析为传输队列。如果消息可以成功放置在那里，您的应用程序将收到返回代码零。 （任何不成功的 PUT 都将是由于达到 MAXDEPTH 或其他与远程定义不存在这一事实无关的本地问题。）
当通道尝试传递消息时，该问题将可见。如果远程 QMgr 有死信队列，消息将发送到那里。如果没有，它将被退回到本地 XMitQ 并且通道将停止。
Yes. You can change the queue attributes like so:
ALTER Q(QUEUE_NAME) PUT(DISABLED) GET(DISABLED)Any connected applications will receive a return code on the next API call telling them that the queue is no longer available for PUT/GET. If these are well-behaved programs they will then report the error and either end or go into a retry loop.
The QRemote definition will resolve to a transmit queue. If the message can successfully be placed there your application will receive a return code of zero. (Any unsuccessful PUT will be due to hitting MAXDEPTH or other local problem not connected to the fact that the remote definition does not exist.)
The problem will be visible when the channel tries to deliver the message. If the remote QMgr has a Dead Letter Queue, the message will go there. If not, it will be backed out onto the local XMitQ and the channel will stop.