In Kanban, if there is an urgent request to implement or a really important user story, the team can just put it on top of the queue.
有了看板，如果来了一个紧急的请求需要实现，或者一个非常重要的用户故事，团队只需把它放在队列的顶端即可。
If the QALIAS names a topic as its target (rather than a queue), then the user opening the QALIAS must have access to not only the alias queue, but also the topic.
如果QALIAS将一个主题(而不是一个队列)命名为其目标，则打开QALIAS的用户不仅需要拥有别名队列的访问权，还需要拥有对主题的访问权。
This user will administer the message queue.
此用户将管理消息队列。
If an attempt is made to start another instance, the user would receive the response that the queue manager instance is not permitted to run as a standby.
如果用户企图启动另一个实例，将收到一个响应，表明该队列管理器实例不允许作为备用实例运行。
As a result, you should not use these techniques to directly project an end user identity to a queue.
因此，不应该使用这些技术来直接将最终用户标识投影到队列。
For example, the user ID for the channel initiator address space needs the authority to connect to the queue manager, but the channels themselves do not.
例如，通道启动程序地址空间的用户ID需要连接到队列管理器的权限，但通道本身不需要。
During queue creation, the user must specify the maximum length of the queue and the maximum size of an individual message.
在创建队列时，用户必须指定队列的最大长度和一个消息的最大大小。
Secondly, it may be necessary to set the MCAUSER property on the channel being used to a user with authorization to access queue manager resources.
其次，可能需要将正在使用的通道上的MCAUSER属性设置为授权访问队列管理器资源的用户。
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的通道启动程序权限。
It is also important that any channel not intended to support administration of the queue manager have a low-privileged user ID in the MCAUSER attribute.
在mcauser属性中，不用于支持管理队列管理器的任何通道都具有低权限用户ID，这一点也很重要。
For example, for a queue, an MQQUEUE profile is used to control MQI access to the queue, but other profiles in the MQADMIN class are used to control context and alternate user security.
例如，对于队列，使用一个MQQUEUE概要文件来控制对该队列的访问，但是mqadmin类中的其他概要文件用于控制上下文和用户安全性。
User context is not set by the queue manager automatically.
用户上下文不由队列管理器自动设定。
Before you start locking down channels, it will be necessary to provision two dedicated user IDs and groups that are accessible to each queue manager.
开始锁定通道前，将有必要提供两个每个队列管理器都可以访问的专用用户ID和组。
When the first user with write access releases the file, the top-most user from the queue is then given the write mode access.
当第一个以写模式访问的用户释放文件后，队列顶部的用户就能以写模式访问。
We designed a separate queue in which to place the write request of each user using the order in which they requested the object and enabling the system to process the request accordingly.
我们设计了一个单独队列，根据请求对象的顺序来放置每个用户的写请求，并允许系统处理对应请求。
Figure 3 shows a user app reading from the MQ queue and writing to a user file or user table.
图3显示一个用户应用程序读取MQ队列，并写入用户文件或用户表。
Connection is based off a vanilla TCP client stream so a user still has access to those features: raw data management, send queue management et cetera.
连接基于普通的TCP客户端流，所以用户仍然能访问原始数据管理、发送队列管理等功能。
ALTER allows the user to MQSET (modify) some attributes of the queue.
允许用户MQSET(修改)队列某些属性。
For simplicity, the queue is configured in a way that this user is the only one allowed to put messages onto it.
出于简洁性考虑，队列被配置为只允许该用户将消息放到队列中。
READ allows the user to browse messages or to MQINQ (inquire) on attributes of the queue.
允许用户浏览消息或MQINQ（查询）队列的属性。
The first requested user is placed in the top of the queue.
第一个请求的用户放在队列头部。
From the write access queue, user B is at the top of the queue since user B requests first to access the file in write mode compared with user C. user B is provided the write access.
在写访问队列中，用户B在队列顶部，这是因为b先于c以写模式请求访问文件。
On the backup node (ha2), create the queue manager as user MQM.
在备份节点(ha2)上，以用户mqm身份创建队列管理器。
It could be an application or user connecting to a WebSphere MQ client channel, or it could be another queue manager.
它可以是连接到WebSphereMQ客户端通道的应用程序或用户，也可以是其他队列管理器。
Removing authorization to the transmit queue forces the user to put messages only onto QRemote definitions, thus limiting messages to specific authorized destinations.
删除对传输队列的授权将强制该用户只能将消息放到QRemote定义中，从而将消息限制到特定的授权目标。
Like most WebSphere products, it listens on a queue, performs administrative and user actions based on commands placed there, and sends replies to the requestor.
与大部分WebSphere产品一样，它在一个队列上监听，基于放置在那里的命令执行管理和用户操作，并将响应发送给请求者。
The health Monitoring widget, shown in Figure 2, is a new widget that aggregates health information for system applications, topology, user applications, messaging, and queue depth.
如图2所示的HealthMonitoring小部件是一个新的小部件，它聚合系统应用程序、拓扑、用户应用程序、消息和队列深度的运行状况信息。
If the user of the Web application is able to send a message to the warehouse queue, then that user could get goods shipped without paying for them, simply by sending a new message.
如果Web应用程序的用户能够向仓库队列发送消息，则该用户可以直接通过发送一条新消息，从而在不用支付的情况下就让仓库配送货物。
Assumption 2: In this tutorial we use two user IDs: MA01USR and MA02USR for queue managers MA01 and MA02 respectively.
假设2：在本教程中，我们对队列管理器MA01和MA02分别使用两个用户ID：MA01USR和MA02USR。
These API methods are reflected in the buzz object's follow and unfollow method, both of which accept a user ID and either add or drop that user from the authenticated user's follow queue.
这些API方法对应着buzz对象的follow和unfollow方法，它们分别接受一个用户ID并向经过身份认证的用户的追随队列添加或删除该用户。
应用推荐