Customer: Excuse me, do I queue here?
顾客：打扰一下，是在这里排队吗？
等候出租汽车在此排队。
在这里排队等候公共汽车。
等出租车在这里排队。
Note that we declare the queue here, as well.
主要这里我们也同样声明了队列。
If we had booked a table earlier, we wouldn't be standing here in a queue.
如果我们早一点预订，现在就不会站在这儿排队了。
Here, you require access to put messages onto all user-defined queues but without also granting the adjacent queue manager administrative rights.
您要求访问将消息保存到所有用户定义的队列中，但不会为相邻队列管理器赋予管理权限。
The command used here does not specify a queue manager name to load.
这里使用的命令没有指定要装载的队列管理器名称。
The systems described here have included one broker or queue manager instance that is active and one standby.
这里描述的系统包含一个活动代理或队列管理器实例和一个备用实例。
Here, shaping can be used to queue any transactions that exceed that rate.
这里，可以使用定形来对超过此速率的任意事务进行排队。
Here is an example of a RACF PERMIT command to grant the user ID for the channel initiator permission to connect to queue manager CSQ1.
下面是的例子展示了RACFPERMIT命令为用户ID授予连接到队列管理器CSQ1的通道启动程序权限。
This class is not shown here, but maintains the registration information and records usage information for the type and maintains a queue of pooled objects.
这里没有显示该类，但是该类负责维护注册信息并记录类型的使用信息，而且维护所汇聚对象的队列。
You could get quite sophisticated here and queue up the updates so they can be re-tried later when the server or network are back up.
这里可以变得复杂一些并将更新放入队列，这样可以在稍后服务器或网络恢复时重新执行更新。
Here, you are inquiring on the current and maximum queue depth, the maximum message length, and the value of QDEPTHHI.
这里，您查询的是当前和最大队列深度、最大消息长度、以及QDEPTHHI的值。
For example, destination type (queue or topic) can be specified here.
例如，可在这里指定目的类型(队列或主题)。
This is the bare minimum that will restrict administrative access from an adjacent queue manager and is only used here for illustration.
这是限制相邻队列管理器的管理权限的最小基本配置，此处仅用于演示。
Here is an illustration of the multi-instance queue manager and client auto-reconnect.
这是多实例队列管理器和客户端自动重连接的说明。
Here, we will obtain a certificate for the MQ queue manager.
我们可以从该处获取mq队列管理器的证书。
To drive the sample, you can use any application that puts a text message onto the queue, such as the amqsput sample included with WebSphere mq. Here is the MDB code.
要想驱动这个示例，可以使用任何能将一个文本消息放到队列上的应用程序，比如随websphere mq所带的amqsput示例。
Here are a couple of the finer aspects of the concurrent blocking queue design.
并发阻塞队列设计有两个要注意的方面。
Ready queue contains threads that are ready to run, but waiting for necessary resources, such as CPU. Here is the sample output.
就绪队列包含准备运行但在等待必要资源(如cpu等)的线程。
Here is a qm.ini file for a default queue manager on UNIX.
以下是UNIX上缺省队列管理器的qm . ini文件。
The main feature of interest here is the use of a BPEL Fault Handler to catch the Fault thrown when an attempt to forward a message to the target Queue Manager fails.
这里关注的主要特性是在尝试将消息转发给目标QueueManager失败时，使用BPELFaultHandler捕获抛出的故障。
The amqsphac client produced 20 messages, all of which were processed and put in the IBMESB_OUT queue by the copy message flow. Here is the output.
amqsphac客户端生成了20条消息，它们都被复制消息流处理并放置到IBMESB_OUT队列中。
Here the queue manager name should be the one created in WebSphere MQ Server.
这里的queuemanagername应该是在WebSphereMQServer上创建的队列管理器。
In addition to general rules, here are some recommended guidelines for naming queue managers and MQ objects.
除了一般规则以外，下面是一些建议用于对队列管理器和MQ对象命名的指导原则。
Here, in module cleanup, you flush the particular work queue (which blocks until the handler has completed processing of the work), and then destroy the work queue.
在模块清理过程中，会清理一些特别的工作队列(它们将保持阻塞状态直到处理程序完成对任务的处理)，然后销毁工作队列。
The queue manager name entered here is the virtual queue manager name by which WebSphere MQ knows this messaging engine.
此处输入的队列管理器名称是一个虚拟队列管理器名称，WebSphere MQ使用这个名称来引用此消息传递引擎。
The vulnerability here is that a spoke node can address messages not to the input queue at the hub, but rather to the output queue at the hub.
这里的漏洞在于，分支节点可以不将消息发送到中心的输入队列，而是发送到中心的输出队列。
The lesson here is that it is not sufficient to enable SSL on some of the channels on the queue manager.
这里得到的教训是，仅在队列管理器的某些通道上启用SSL还远远不够。
应用推荐