If you are using the Version 5.1 Message Brokers Toolkit, replace all references in this topic to "Version 5.0" with "Version 5.1".
To migrate message sets from Version 2.1 to Version 6.0, use the mqsimigratemsgsets command to convert your Version 2.1 message set export files (.mrp) into Version 6.0 message set projects. Before you run the command, refer to the Migrating Message Sets from Version 2.1 topic, which provides detailed notes on its operation.
To migrate message sets from Version 5.0 to Version 6.0, no migration commands are necessary. The content of a Version 5.0 message set project can be read by the Version 6.0 Message Brokers Toolkit and is converted automatically to Version 6.0 format when it is modified and saved for the first time.
Continue to use TDS Message Key if the message set will ever be deployed to a Version 5.0 or Version 2.1 broker, because these brokers do not support the Message Identity technique of embedded message identification.
<!ELEMENT e0 (e1|e2)+ >will appear in the output as:
<!ELEMENT e0 (e1|e2)+>The new behavior is consistent with the way that the XML physical format processes white space in all other XML constructs.
A specific example of this is where your message contains an embedded message and you are using either the Message Key or Message Identity technique to identify the embedded message. If the element that is providing the message key or message identity value fails to be matched with the model, the parser will not know whether to interpret its value as a message key or message identity.
Prior to Version 6.0, the parser attempted to make sense of all out-of-order Tagged Delimited groups, with a consequent reduction in performance. In Version 6.0, if this is a problem, consider modeling the unordered content of the group as an embedded child group with Composition set to UnorderedSet.
A complex element or group can be identified from the bit stream if it provides a group indicator, a tag, or a data pattern, or if its child members provide a group indicator, tag or data pattern.
Despite its name, there are circumstances where members of a Tagged Delimited group do not need to provide a tag; specifically, if the member is an embedded message or is a complex element or group.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah20250_ |