TRANSQ（传输队列）
A transmission queue with the same name as the target queue manager.
与目标队列管理器名称相同的传输队列。
Only one gateway queue manager can be attached to a transmission queue.
只有一个网关队列管理器可以附带在一个传输队列中。
A similar approach is to use one transmission queue per device queue manager.
一种类似的方法是每个设备队列管理器使用一个传输队列。
On the MQSC command line, enter the following command to define the transmission queue
在MQSC命令行输入以下命令，以定义传输队列
The structure of a distribution-list message on a transmission queue is shown in Figure 8.
传输队列上分布列表消息的结构如图8所示。
Connection name and transmission queue are not needed for receiving; defaults are used.
对于接收，不需要连接名称和传输队列；缺省情况下使用连接名称和传输队列。
The message data of a distribution-list message on a transmission queue has the following sequence.
传输队列上分布列表消息的消息数据排列顺序如下。
As there is only one default transmission queue per MQ server, only one gateway queue manager can work with it.
因为每个MQ服务器只有一个缺省传输队列，所以只有一个网关队列管理器可以使用它。
Create a transmission queue that provides the QM_reinitz queue manager with a link to the SIBus as a queue manager.
创建传输队列，以提供带有指向SIBus的链接的qm_reinitz队列管理器作为队列管理器。
WebSphere MQ transmission queues are queues that temporarily store messages that are destined for a remote queue manager.
WebSphereMQ传输队列是临时存储将发送到远程队列管理器的消息的队列。
MQDH describes the additional data in a message when that message is a distribution-list message stored on a transmission queue.
当消息是存储在传输队列中的分布列表消息时，MQDH会描述该消息中的附加数据。
In this case, WebSphere MQ adds a distribution header structure (MQDH) to the message, and puts it on the relevant transmission queue.
在这种情况下，WebSphereMQ添加分布式头结构(MQDH)到消息中，并将其放在相关的传输队列中。
Using a default transmission queue at first glance appears to improve matters, because it removes the need for remote queue definitions.
使用缺省传输队列一开始看起来使状况有所改善，因为它使得不需要远程队列定义。
Unlike communications from one MQ server to another, MQ channels are not defined for transmission queues from an MQ server to a gateway queue manager.
与从一个MQ服务器到另一个的通信不同，从MQ服务器到网关队列管理器的传输队列没有定义MQ通道。
But there are some drawbacks — any message that does not have a corresponding remote queue or transmission queue ends up on the default transmission queue.
但是也有一些缺陷——任何没有相应的远程队列或传输队列的消息最终都被送到该缺省传输队列。
When a message is put on a remote queue, WebSphere MQ adds a transmission header structure (MQXQH) to the message before placing it on the transmission queue.
当消息位于远程队列时，WebSphereMQ 在将消息置于传输队列之前向其添加传输头结构（MQXQH）。
If a transmission queue listener is required, it must be associated with the client connection channel, queue manager proxy, and bridge objects previously created.
如果需要传输队列监听器，就必须与先前创建的客户端连接通道、队列管理器代理和网桥对象相关联。
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.
如果没有目标设备队列管理器的消息最终都送到缺省传输队列，则网关队列管理器将试图传递该消息并失败。
They can communicate directly with one another across a single network, without the need for extra channel definitions, remote-queue definitions, or transmission queues.
它们直接通过单个网络彼此进行通信，而无需额外的通道定义、远程队列定义或传输通道。
First, the number of resource definitions on the gateway queue manager increases dramatically, such that for every transmission queue, a listener must be defined on the gateway.
首先，网关队列管理器上的资源定义数量增长迅速，例如对于每个传输队列，都必须在网关上定义一个侦听器。
Instead, the gateway queue manager is configured with a listener, which pulls messages from the transmission queue and maintains the assured delivery process to the MQe target destination.
相反，网关队列管理器配置了一个侦听器，它从传输队列提取消息并维护到mqe目的地的确定传递过程。
At least one transmission queue must be defined for each remote queue manager to which the local queue manager is to send messages directly. To configure the WebSphere MQ transmission queue.
至少必须为直接从本地队列管理器接受消息的每个远程队列管理器定义一个传输队列。
If asynchronous transmission is required, the application server must, of course, be configured with the appropriate JMS Queue and Queue Connection Factory.
如果需要异步传输，当然应用服务器必须配置适当的jms队列和队列连接工厂。
When applications have intermittent message transmission needs, use the MQPUT1 call to put only one message on the queue.
当应用程序具有间隙性的消息传输需要时，可以使用MQPUT 1调用以仅在队列上放置一个消息。
Messages arriving from the adjacent system contain the physical name (after name resolution) of the destination queue manager and the queue in the transmission header.
来自相邻系统的消息包含目标队列管理器和传输头中队列的物理名称(对名称解析后得到的名称)。
A JMS transmission profile is configured with the following JMS queue and queue connection factory JNDI name as well as an emitter factory profile at the scope defined.
在定义的范围中使用下面的jms队列、队列连接工厂JNDI名称及发射器工厂概要来配置JMS传输概要。
The transmission header contains the name of the destination queue (RemoteQName) and queue manager (RemoteQMgrName), that is, the addressing information.
传输头包括目标队列名称（RemoteQName）和队列管理器名称（RemoteQMgrName），即寻址信息。
Using a dynamic bandwidth selection, according to real queue size and predicted queue size, the bandwidth wastage offered in the fixed transmission opportunity can be reduced.
根据实队列的大小和预测队列大小，使用动态的带宽选择，可以降低固定传输机会引入的带宽浪费。
It also USES circulatory memory buffering queue to control the receiving and transmission of data.
并采用了循环内存缓冲队列进行了数据的收发控制。
应用推荐