它还在处理期间锁定消息，确保一条消息仅由一个读取器处理，即使多个进程在从单一队列进行读取操作。
It also locks messages during processing, which ensures that a message will only be processed by one reader, even if multiple processes are reading from a single queue.
启动队列管理器和相关进程。
这包括定义一个进程对象和在代理命令队列上启用触发。
This includes definition of a process object and to enable triggering on the agent command queue.
侦听发送到输入队列的消息的某个后端守护程序进程将接收此消息，并将其分派到可以处理此消息的某段代码。
Some back-end daemon process listening for messages posted to the input queue would receive the message and dispatch it to some piece of code capable of handling the message.
在清单5所示的代码片段中，进程创建了一个可包含20个整数的消息队列。
Listing 5 shows a code snippet in which a process has created a message queue of 20 integers.
在本地绑定模式连接中，主体是与连接到队列管理器的进程相关联的帐户。
For a local bindings mode connection, the principal is the account associated with the process that is connecting to the queue manager.
重新启动队列管理器和关联的进程。
表示有多少进程正在为输入而访问该应用程序队列。
Indicates how many processes are accessing the application queue for input.
为了保持队列深度值较低，服务器进程必须以更高的速率运行。
To keep the queue depth low, the server process would have to run at a higher rate.
运行时每次会将消息从队列中取出，将其传递到进程的函数执行。
The runtime pulls messages from the queues, passing them to the process's function one at a time.
每个请求队列将仅具有一个服务应用程序，从而确保序列化效果，但总体工作负载并不限制在一个服务器进程内。
Each request queue would have only one serving application to ensure serialization, but the total workload is not confined to one server process.
在我们给出的简单示例中，由于服务器进程是一个CICS事务，直接在多个CICS区域中运行多个服务器事务副本就可能将队列深度保持在很低的水平。
In our simple example, since the server process is a CICS transaction, simply having multiple copies of the server transaction running in multiple CICS regions would keep the queue depth very low.
TASK_RUNNING：进程当前正在运行，或者正在运行队列中等待调度。
TASK_RUNNING: the process is either running on CPU or waiting in a run queue to get scheduled.
另一个队列是运行队列，其中包含等待运行的进程的有序列表。
The run queue, which holds an ordered list of processes waiting to run, is another queue.
MQI还允许应用程序操作队列上下文、发布或订阅主题、以及查询进程和名称列表。
The MQI can also allow a program to manipulate context for queues, specify alternate userids, publish or subscribe to topics, and inquire on processes and namelists.
进程定义消息到达队列时启动的应用程序。
A process defines the application to start when a message arrives on a queue.
因此，程序要通过MQI进行查询，所需的只是查看进程或名称队列中的信息。
Therefore all a program needs to be able to do through the MQI is to view the information in the process or namelist.
另外，可以使用同一个进程定义和触发器监控器在多个队列上配置ChompQ，每个队列可以拥有不同的设置。
What's more, ChompQ can be configured on multiple queues using the same process definition and trigger monitor, and each queue can have different Settings.
AmazonSQS支持多个进程同时读写一个队列，以及在处理窗口时锁定消息，以避免两个客户端同时处理一条消息。
Amazon SQS supports multiple processes reading and writing to a queue concurrently and locks messages during the processing window to prevent two clients from processing a message concurrently.
场景2与场景1基本相同，但mq进程是通过kill命令终止的，而不是使用endmqm命令关闭队列管理器。
Scenario 2 is the same as Scenario 1, but instead of shutting down the queue manager using the endmqm command, the mq process is killed using the kill command.
您需要创建启动和停止WebSpheremq队列管理器和相关进程的脚本。
You'll create a script to start and stop the WebSphere MQ queue manager and any associated processes.
这意味着Fastpath应用程序和队列管理器之间不存在进程分离。
This means that there is no process separation between the Fastpath application and the queue manager.
本文中列出的一个进程间通信(Inter - Process Communication,IPC)消息队列示例代码将向您展示如何来解决此问题。
An Inter-Process Communication (IPC) message queues sample code listed in this article to show you how to work around it.
注意，上面显示的进程定义假定可执行程序(Windows的perl和unix的Chom pQ . pl)位于队列管理器的PATH中。
Notice that the process definitions shown assume that the executable program (perl for Windows and the ChompQ.pl script for UNIX) is in the queue manager's PATH.
gae队列允许您采取可能长时间运行的进程，将它们变为简洁的任务(servlet)并将这些任务放到队列上以便在后台执行。
GAE queues allow you to take potentially long-running processes, break them up into succinct tasks (servlets), and throw those tasks onto queues to be executed in the background.
WM_HOTKEY消息在用户键入被RegisterHotKey函数注册的热键时发送。该消息将位于消息队列的最前端，并且与注册了这个热键的进程关联。
Posted when the user presses a hot key registered by the RegisterHotKey function. The message is placed at the top of the message queue associated with the thread that registered the hot key.
Fastpath应用程序在与队列管理器相同的进程中运行，因此能够更高效地与队列管理器通信。
Fastpath applications run in the same process as the parts of the queue manager so making communication with the queue manager more efficient.
通过终止队列管理器IBMESBQM2的执行控制器进程amqzxma0来停止IBMESBQM 2队列管理器。
Stop the IBMESBQM2 queue manager by killing the execution controller process amqzxma0 of the queue manager IBMESBQM2.
EnqueueEvent将事件(例如每个发出的事件的消息和进程id)加入一个队列中。
EnqueueEvent stores events (such as message and process id for every fired event) to a queue.
因此，虽然对象名称正在向上迁移到逻辑层，但是队列管理器、通道、进程和其他系统名称正在向下转移，更接近物理基础结构层。
So while the object names are migrating up into the logical layer, the queue manager, channels, processes, and other system names are being driven down closer to the physical infrastructure layer.
应用推荐