A similar approach is to use one transmission queue per device queue manager.
一种类似的方法是每个设备队列管理器使用一个传输队列。
Normal practice requires one remote queue definition for every device queue manager.
正常的做法要求每个设备队列管理器都有一个远程队列定义。
Each device runs an MQe queue manager (hereafter referred to as a device queue manager).
每个设备运行一个mqe队列管理器(以下称为设备队列管理器)。
Take a scenario where each device queue manager has two queues and there are 10,000 devices.
给定这样的场景：每个设备队列管理器都有两个队列，而设备数量为10,000。
Applications using the MQ server can send messages that are destined for device queue managers.
使用MQ服务器的应用程序可以发送去往设备队列管理器的消息。
There are a number of ways to configure MQ in order to send messages to a device queue manager.
为了将消息发送到设备队列管理器，有许多配置MQ的方式。
The remote queue definition is defined with the target device queue manager name and queue name.
该远程队列定义是用目标设备队列管理器名称和队列名称定义的。
When a device comes online, the device queue manager pulls messages from the store-and-forward facility.
当设备联机时，设备队列管理器会将消息从存储转发设备提取出来。
A gateway queue manager facilitates the exchange of messages between device queue managers and MQ servers.
网关队列管理器方便了设备队列管理器和MQ服务器之间的消息交换。
You can take advantage of the MQ search order and define just the device queue manager name as the remote queue definition.
您可以利用MQ搜索顺序并只按照远程队列定义来定义设备队列管理器名称。
As with messages going from device queue managers to MQ, the gateway does the reverse transformation from MQ to MQe message format.
对于从设备队列管理器到MQ的消息，网关执行从MQ到MQe消息格式的逆向转换。
One however probably can combine this data with device queue sizes and average request execution time to get some decent values.
然而一方面，我们可能可以把这个数据与设备排队尺寸以及平均请求执行时间结合起来以得到一些合适的数值。
Notice that multiple jobs are in the RUNNING status and as each job completes, a QUEUED job is moved to the job spool device queue and executed.
注意，有多个作业处于RUNNING状态；每当一个作业完成时，一个QUEUED作业就转移到作业假脱机设备队列中并执行。
If a message not destined for a device queue manager ends up on the default transmission queue, the gateway queue manager will attempt to deliver the message and fail.
如果没有目标设备队列管理器的消息最终都送到缺省传输队列，则网关队列管理器将试图传递该消息并失败。
For messages going from MQ servers to device queue managers, the gateway provides a store-and-forward facility holding messages for devices that are not currently online.
对于从MQ服务器到设备队列管理器的消息，网关提供存储转发设备来为当前未联机的设备保存消息。
For messages going from device queue managers to MQ servers, the gateway provides a passthrough facility, transforming messages from the compact MQe format to the MQ format.
对于从设备队列管理器到MQ服务器的消息，网关提供了一个穿透设备，它将消息从compact mqe格式转换成mq格式。
This procedure allows any queue on the device to be addressed through the one definition, reducing the number of remote queue definitions to the number of device queue managers.
这个过程可以使设备上的任何队列都通过一个定义来寻址，从而将远程队列定义的数量降到与设备队列管理器的数量相同。
Attempt to list the queue device again.
再次尝试列出这个队列设备。
The device agent on the client reads the job queue and starts processing all waiting jobs.
客户端的设备代理读取作业队列，并且启动处理所有等候执行的作业。
Otherwise, the jobs would be sent to the first available job queue device.
在其他情况下，作业被发送到第一个可用的作业队列设备。
Spooling sequential job processes on a system with multiple job queues requires that all jobs be directed to a single job queue device.
在有多个作业队列的系统上，对连续作业处理进行假脱机要求把所有作业转发到同一个作业队列设备。
Using this approach, a remote queue definition is required for every queue on every device, and therefore the number of remote queue definitions grows rapidly.
使用此方法，每个设备上的每个队列都需要一个远程队列定义，因此远程队列定义的数量急剧增长。
Maybe it's just me, but I get paranoid that maybe I changed both devices in the queue or accidentally changed the wrong device.
可能是我有一些多疑，总觉得会同时修改队列中的所有设备，或者不小心修改为一个错误的值。
If you wish to remove the second job spooler queue device so that only one job at a time is executed, run the following commands.
如果希望删除第二个作业假脱机程序队列设备，从而每次只执行一个作业，那么运行以下命令。
List the default queue device to verify it still exists.
列出默认的队列设备，确认它仍然存在。
Without specifying bshdev2, each job would be executed on the first available queue device, which would result in multiple jobs running simultaneously (non-sequentially).
如果不指定bshdev2，每个作业会在第一个可用的队列设备上执行，这会导致同时(不连续)运行多个作业。
Restricting the execution of the queued jobs only to the bshdev2 job queue device results in those jobs being executed sequentially.
把排队的作业的执行限制在作业队列设备bshdev2上，就可以确保连续执行这些作业。
The BSH job queue now allows a spooled job to be processed on each available device; if two devices are available, then two jobs can be processed simultaneously, one on each device.
bsh作业队列现在可以在每个可用的设备上处理一个假脱机的作业：如果有两个可用设备，就可以同时处理两个作业，每个设备一个作业。
After adding another queue device, an lpstat -w shows multiple queue devices associated with the BSH job queue.
在添加另一个队列设备之后，使用lpstat- w命令显示与bsh作业队列相关联的多个队列设备。
This queue is managed bv Linux's "netdevice" layer that sits in-between IP and device drivers.
该队列由Linux的“netdevice”层来管理，它位于IP和设备驱动之间。
应用推荐