这将新队列管理器的构建和部署任务分离，并支持节点的早期测试和验证。
This separates the build and deploy tasks for new queue managers and enables early testing and verification of nodes.
队列管理器和通道启动程序都作为任务运行，并且它们可以在自己的用户ID下运行。
The queue manager and channel initiator both run as started tasks, and each can run under its own user ID.
下面介绍管理这些mi队列管理器的任务。
The tasks to administer these mi queue managers are described below.
结果，要让两个队列管理器同时在线将非常困难或根本不可能，从而影响迁移任务的计划和执行。
As a result, it is difficult or impossible to have both queue managers online at the same time, which affects scheduling and execution of the migration tasks.
您在前面看到，将名称解析向上移动到集群级别减少了队列管理器的任务。
You saw earlier that moving name resolution up to the cluster level diminished the role of the queue manager.
我最近进行的一个咨询工作包括一个任务，需要在两个队列管理器之间建立一些SSL通道。
A recent consulting engagement included a task to set up SSL channels between two queue managers.
完成此任务后，我们将设置在队列管理器控制下开始和结束的发布/订阅代理。
Once that is done, we will set up the publish/subscribe broker to start and end under control of the queue manager.
结果应该显示DB 2地址空间(任务名称以“DF25”开始)、队列管理器和代理(任务名称以“VEG3”开始)。
The result should be a display of the DB2 address Spaces (job names starting with "DF25"), and of the queue manager and broker (job names starting with "VEG3").
结果应该显示DB 2地址空间(任务名称以“DF25”开始)、队列管理器和代理(任务名称以“VEG3”开始)。
The result should be a display of the DB2 address Spaces (job names starting with "DF25"), and of the queue manager and broker (job names starting with "VEG3").
应用推荐