MQ 系列中的命令级别是什么?

发布于 2024-11-29 22:42:50 字数 49 浏览 2 评论 0原文

在Websphere MQ系列中,队列管理器的命令级别是701。它实际上指定了什么?

In Websphere MQ series , command level for a queue manager is 701. What does it actually specify ?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

棒棒糖 2024-12-06 22:42:50

WebSphere 产品使用“[版本].[发行版].[修改].[修订包]”命名约定。例如,7.0.1.6 是指定为修订包级别的当前版本。

  • 修复包仅限于错误修复和非常有限的非破坏性功能增强。
  • 修改可以包括功能增强,但不包括 API 更改。例如,7.0.1 中引入了多实例队列管理器。
  • 版本可能会引入重要的新功能和有限的 API 更改,但与同一版本高度向前和向后兼容。
  • 版本封装了一组核心功能。此级别的更改可能会为了重要的新功能而牺牲一些向后兼容性。例如,在 V7 版本中,WMQ Pub/Sub 从 Message Broker 移至基础 MQ。

由于管理功能在修订包中不会更改,但可能会在修改级别更改,因此与管理工具的兼容性基于队列管理器的命令级别。

有一个旧的但仍然有用的技术说明,其中当 WMQ 采用编号约定时对此进行了描述。

WebSphere products use a "[version].[release].[modification].[Fix Pack]" naming convention. For example 7.0.1.6 is the current release specified down to the Fix Pack level.

  • Fix packs are limited to bug fixes and very limited non-disruptive functionality enhancements.
  • Modifications can include functionality enhancements but no API changes. For example the Multi-Instance Queue Manager was introduced in 7.0.1.
  • Releases may introduce significant new function and limited API changes but are highly forward and backward compatible withing the same version.
  • Versions encapsulate a core set of functionality. Changes at this level may sacrifice some backward compatibility in trade for significant new functionality. For example, WMQ Pub/Sub was moved from Message Broker to base MQ in the V7 release.

Since administrative functionality does not change in Fix Packs but may change at the Modification level, compatibility with administrative tools is based on the queue manager's Command Level.

There is an old but still useful TechNote which described this when the numbering conventions were adopted for WMQ.

友欢 2024-12-06 22:42:50

它显示 WMQ 的主要版本号 - 例如 530,600,700,701。尽管“仅”增加了 .0.1,但由于一些内部更改(例如多实例 QM),WMQ 7.0.1 获得了新的主要版本号,尽管 WMQ 6.0.1.x 和 6.0.2.x 都是CM水平600

It displays the major version number of WMQ - e.g. 530,600,700,701. Despite being 'only' a .0.1 increment, WMQ 7.0.1 gets a new major version number due to a number of internal changes (e.g. multi-instance QMs), although WMQ 6.0.1.x and 6.0.2.x were both CMDLEVEL 600

各自安好 2024-12-06 22:42:50

命令级别虽然和VRMF类似,但并不完全是一回事。命令级别用于允许配置应用程序了解命令服务器将理解哪些命令(以及这些命令中的属性)。

任何配置应用程序应该做的第一件事是发现队列管理器的 PLATFORM 和 CMDLEVEL。然后,该应用程序可以确定哪些命令/属性可以发送到该队列管理器。

服务流中的 CMDLEVEL 可能会增加。那么 VRMF 不一定与 CMDLEVEL 匹配。如果在服务流中添加一些新的外部属性,就会发生这种情况,因此没有该补丁的队列管理器将无法理解它们,但具有该补丁的队列管理器可以。应用程序如何确定要发送的内容?嗯,CMDLEVEL 将决定这一点,因此必须通过补丁来提高。

Command level, although similar to the V.R.M.F, it not exactly the same thing. The Command level is used to allow configuration applications to know what commands (and attributes within those commands) will be understood by the command server.

The first thing any configuration application should do is discover the PLATFORM and CMDLEVEL of the queue manager. Then that application can determine which commands/attributes it would be acceptable to send to that queue manager.

It is possible that CMDLEVEL could be increased in the service stream. Then the V.R.M.F. would not necessarily match the CMDLEVEL. This would happen if some new external attributes were added in the service stream, so queue managers without that patch would not understand them, but queue managers with the patch would. How does an application determine what to send? Well, the CMDLEVEL would determine that and so would have to be upped by the patch.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文