These tips assume that you have created a mapping node within the message flow, opened the Message Mapping editor, and selected both a source and a target message:
SET OutputRoot.MRM.Fielda...If you change the runtime parser to XMLNSC, for example, the Mapping node generates ESQL with the following format:
SET OutputRoot.XMLNSC.MessageA.FieldA...The parser of the source message is determined by the contents of the MQRFH2 header or by the properties of the input node. The Mapping node generates a target message with a parser that matches the message domain of the message set. The Mapping node supports the following message domains:
To change the database schema name that is generated in ESQL, use the Override Database Schema wizard in the Specify Runtime Schema dialog box. The default name is the schema name of the database definitions that are imported into the Message Broker Toolkit. Use the Specify Runtime Schema dialog box to change the value.
The RouteToLabel node is the next node in sequence after the Mapping node, and causes the flow to jump automatically to the specified label. You can specify a single RouteToLabel value in a splitting map for all maps that output a message assembly. You can also use conditions to set the RouteToLabel value, depending on the values in the source message.
Multipart messages can also contain repeating embedded messages, where each repeated instance of a message is propagated separately. Embedded messages must be from the same message set as the parent message.
SET OutputRoot.MQMD = InputRoot.MQMD; SET OutputRoot.MQMD.ReplyToQ = 'NEW.QUEUE';You must set each field in the structure individually if you intend to modify one or more sibling fields.