Message descriptor (Message header).
消息描述符(消息头)。
Context fields in message descriptor.
消息描述符中的Context字段。
Message descriptor fields as properties.
作为属性的消息描述符字段。
Here Priority is a field in message descriptor.
这里Priority是消息描述符中的一个字段。
There are two versions of the message descriptor.
消息描述符有两个版本。
The embedded message descriptor is always a V1 MQMD structure.
嵌入式消息描述符始终是V1 MQMD结构。
Message descriptor and application data (in versions up through V6).
消息描述符和应用程序数据(V 6及之前的所有版本)。
This enlarged structure is V2, which is the current version of message descriptor.
这种扩展结构即为消息描述符的当前版本V2。
In this situation, WebSphere MQ may add a message descriptor extension (MQMDE) structure.
在这种情况下，WebSphereMQ可能会添加消息描述符扩展(MQMDE)结构。
The attributes of the message descriptor changed starting with V5 — see below for details.
从V5开始消息描述符的属性开始改变—详细信息参见以下内容。
The message context information is stored in the context fields of the message descriptor.
消息上下文信息存储在消息描述符的context字段中。
Message descriptor fields are never represented in an MQRFH2 header as for other properties.
消息描述符字段从来不像其他属性一样以MQRFH2 头的形式表示。
As discussed above, an MQMDE structure is added by the queue manager if the message descriptor is V1.
如上所述，如果消息描述符是V 1,MQMDE结构由队列管理器添加。
A message descriptor is associated with every message that resides on a queue within a queue manager.
消息描述符与队列管理器内驻留在队列上的每个消息相关。
There is a length limit of 100 MB for message properties, excluding the message descriptor or extension for each message.
消息属性的长度限值是 100MB，其中不包括每个消息的消息描述符或扩展。
For this new function, additional fields in message descriptor were needed to keep information for the segmenting and grouping.
对于该新功能，需要在消息描述符中附加字段来保留分段和分组信息。
The message descriptor is defined by an MQMD structure that contains a number of fields that provide information about the message.
消息描述符由一种MQMD结构定义，这种结构包含大量提供消息信息的字段。
If none is found, the queue manager places its own name in the ReplyToQMgr field of the message descriptor, with ReplyToQ unchanged.
如果找不到任何结果，队列管理器会在保持ReplyToQ不变的情况下在消息描述符的replytoqmgr字段中置入自己的名称。
The message format of V7 is shown in Figure 4, as well as the correspondences between the message properties and message descriptor.
V7的消息格式如图4所示，图中还显示了消息属性与消息描述符之间的对应。
Besides the addressing information, an embedded message descriptor (MsgDesc) is stored within the MQXQH structure as part of the message data.
除了寻址信息之外，嵌入式消息描述符(MsgDesc)也作为消息数据的一部分存储在MQXQH结构内。
A new type of context information is added in V7 for message properties: user context. Table 5 lists the context fields in the message descriptor.
v7中为消息属性添加了一种新的上下文信息：用户上下文(user context)。
If you run this code and then browse the queue using WebSphere MQ Explorer, you will see that the message descriptor properties have been set as before.
如果运行此代码，然后使用WebSphereMQExplorer浏览结果，将会看到消息部署描述符属性已像前面一样进行了设置。
A message descriptor (that is, a messages header) is at the start of every WebSphere MQ message, and it includes a set of fields called message context.
消息描述符(即消息头)位于每条WebSphereMQ消息的开始部分，包含一些称为“消息上下文”的字段。
Generally, the application data only contains information that is meaningful to the applications, since the control information in the message descriptor is sufficient.
一般地，应用程序数据仅包含对应用程序有意义的信息，因为消息描述符中的控制信息就已经足够了。
Its anticipated message volume is 1,000,000 messages per day (peak rates are discussed later), with an average message size of 3.5k including the message descriptor (MQMD).
它所预期处理的消息量是每天1,000,000条消息(后文将讨论峰值速率)，消息平均大小为3.5K(含消息描述符——MQMD)。
The reason for this is that the channel agent will preserve the contents of the message descriptor by setting all the fields to match the message from the sending queue manager.
其原因在于通道代理会保留消息描述符的内容，它会设置所有字段以匹配来自发送队列管理器的消息。
When a message flows to a queue manager prior to V7, properties of the message, except those in the message descriptor, are treated as message data and count towards the length of the message.
当消息流向V 7版本之前的队列管理器时，除了那些在消息描述符中的属性之外，消息属性都被看作是消息数据并计入消息长度中。
You can see in Listing 3 that some elements in the deployment descriptor correspond to the JMS concepts of acknowledge mode, subscription durability, and message selector.
在清单3中可以看到，部署描述符中的一些元素对应着JMS概念中的应答模式、订阅、持久性和消息选择器。
Each pattern has a named descriptor that can be assigned to a page, message, or component.
每一个模式都有一个命名的描述符，它可以被分配给页面、消息或者组件。
The BAR file contains the deployment descriptor, compiled message flows, and message set definitions.
BAR文件包含部署描述符、已编译的消息流和消息集定义。
应用推荐