A number of folders are defined for use by WebSphere® MQ products.
Each folder is contained in a separate NameValueData field, each of which is preceded by a NameValueLength field.
com.ourcompany.xxx or com.ourcompany.ourData
See Parsers for a description of each domain.
If <Msd> is mrm or idoc, you must use the <Set> element to supply the name of the message model.
If <Msd> is xmlnsc, and validation is enabled in the message flow, you must use the <Set> element to supply the name of the message model.
The format {namespace-uri}name (that is, with no colon) is also valid to maintain compatibility with previous versions of IBM® Integration Bus.
If <Msd> is mrm or idoc, you must use the <Type> element to supply the name of the message definition.
If <Msd> is mrm or idoc, you must use the <Fmt> element to supply the name of the physical format in the message model.
CALL CopyEntireMessage();
DELETE FIELD OutputRoot.MQRFH2.mcd;
PROPAGATE FINALIZE NONE; -- Propagate the message without updating the headers
RETURN FALSE; -- Ensure that the message is not propagated again.
The <psc> folder is used to convey publish/subscribe command messages to the integration node.
Only one psc folder is allowed in the NameValueData field.
See Command messages for full details.
The <pscr> folder is used to contain information from the integration node, in response to publish/subscribe command messages.
Only one pscr folder is present in a response message.
See Broker Response message for full details.
The integration node ignores this folder in messages that it receives from publish/subscribe applications.
See JMS message structure for more information about the content of JMS messages.