在迁移期间，当队列管理器以新版本启动时，它的本地集群对象将被更改，因为它们现在已拥有新特性。
During migration, when a queue manager is started at the new version, its local cluster objects are changed, since they now have new attributes.
并非所有属性都适合于所有版本的队列管理器。
Not all properties are appropriate for all versions of queue manager.
一旦部署管理器被升级到版本6，单元中的单个节点就可以被升级。
Once the deployment manager has been upgraded to Version 6, the individual nodes in the cell can be upgraded.
如果所有完整存储库在局部存储库之前迁移，那么所有新版本队列管理器都能利用新特性。
If all full repositories are migrated before partial repositories, new features will be exploitable by all queue managers running at the new version.
在启用迁移的节点并将其与以前版本的部署管理器同步后，请启动其他节点。
After the migrated nodes have been enabled and synchronized with the prior release deployment manager, start the nodes.
因此，应该有一个适当类型的客户机版本的插件，从而与数据库管理器配置参数AUTHENTICATION指定的值相对应。
Therefore, you should have a client version of the appropriate plug-in type, according to the value you specified in the database manager configuration parameter AUTHENTICATION.
在迁移集群中的各个队列管理器之间最好间隔几天，以便在所有队列管理器完全在新版本下运行之前测试应用程序。
It is reasonable to leave days between migrating each queue manager in the cluster, in order to test applications before wholly committing all queue managers to run at the new version.
启动以前版本的部署管理器。
该脚本的初始版本包含队列管理器的本地基准，例如设置死信队列、锁定远程管理访问以及优化通道。
The initial version of the script contains the local baseline for a queue manager, such as setting the dead queue, locking down remote administrative access, and tuning channels.
在5.0版本之前，无法设置帧的布局管理器或者直接将组件添加到帧中。
Prior to the 5.0 release, you couldn't set the layout manager of the frame or add components directly to the frame.
这样可以防止禁用旧版本的部署管理器，从而也可以跳过启用旧版部署管理器的步骤。
This will prevent the old release deployment nanager from being disabled, and so the step to enable the old release deployment manager can be skipped.
PACID签名是由资源管理器进行验证的；pac版本是通过一个活动的PAC ID进行标识的。
PAC id signatures are verified by the resource managers; PAC versions are identified by opening up the PAC id.
证书标签需要队列管理器名称的小写版本。
The lower-case version of the queue manager name is required for the certificate label.
具体地说，V 5节点不能与版本6.0.0.0部署管理器联盟(以后的维护版本将纠正这个问题)。
Specifically, V5 nodes cannot be federated into a version 6.0.0.0 deployment manager (this will be changed in a future maintenance release).
在WebSphereMQ信息中心指定了有关哪些属性适用于特定版本的队列管理器的更多信息。
More information about which properties apply with a particular version of queue manager is specified in the WebSphere MQ information Center.
作业管理器旨在对NetworkDeployment和基本版本拓扑形成补充。
The job manager is designed to complement the Network Deployment and base edition topologies.
混合版本管理从将部署管理器概要迁移到Version7开始。
Mixed version management begins with migrating the deployment manager profile to version 7.
LEL并不是专用于某个特定的布局管理器的，但当前的版本使用GroupLayout来创建GUI。
LEL is not specific to a particular LayoutManager, although the current version USES GroupLayout to set up the GUI.
BLV包含AIX内核、rc. boot文件、启动过程所需的命令，以及精简版本的对象数据管理器(odm)。
The BLV contains the AIX kernel, the rc.boot file, commands required during the boot process, and a trimmed-down version of the Object Data Manager (ODM).
重新启动版本 5 的部署管理器。
资源管理器：sybase(版本12.5和15)。
增量升级过程从您的版本5的部署管理器向版本6移植开始。
The incremental upgrade process begins with the migration of your V5 deployment manager to V6.
当部署管理器被移植到版本6时，单元中的节点保持不变，不管它们在部署管理器升级以前支持什么版本。
When the deployment manager is migrated to Version 6, the nodes in the cell remain unchanged at whatever release level they supported prior to the deployment manager upgrade.
增量移植过程从你的版本5 的部署管理器向版本 6 移植开始。
The incremental migration process begins with migration of your Version 5 deployment manager to Version 6.
集群队列管理器的目的是将运行不同版本的队列管理器加入到集群中，这也是分步迁移之所以成为可能的原因。
Cluster queue managers are designed to partake in clusters with queue managers running at different versions, which is why a staged a migration is possible.
这很可能出现在没有LBA支持的BIOS中或者某些旧版本的引导管理器中。
This is most likely to occur in a BIOS that does not have LBA support, or some older boot managers.
低版本队列管理器不能使用新特性，并将出现在新版本队列管理器的存储库中，任何新版本属性均使用默认值。
Queue managers at the back-level version cannot use the new features, and will appear in the repositories of new version queue managers with the default values for any new version attributes.
确保新的版本6的部署管理器正在运行，并能够与正在升级的版本5的节点进行通信。
Ensure that your new V6 deployment manager is running and can communicate with the V5 node you are upgrading.
此结构包含资源管理器的名称、指向资源管理器入口点的非空指针、标志和版本号。
This structure contains the resource manager's name, non-null pointers to the resource manager's entry points, a flag, and version number.
在将部署管理器和版本5的节点之间的配置文件同步化时，将变换设置成版本6的格式以便与版本5兼容。
When synchronizing the configuration file between the deployment manager and a V5 node, transformations are applied to the V6 format to make it V5-compatible.
应用推荐