MQRFH2 folder restrictions

Overview of folder restrictions in MQRFH2 headers

• Element names in the <usr> folder must not begin with the prefix JMS ; such property names are reserved for use by JMS and are not valid for user-defined properties.

  Such an element name does not cause parsing of the MQRFH2 to fail, but is not accessible to the IBM MQ message property APIs.

• Element names in the <usr> folder must not be, in any mixture of lower or uppercase, NULL, TRUE, FALSE, NOT, AND, OR, BETWEEN, LIKE, IN, IS and ESCAPE. These names match SQL keywords and make parsing selectors harder, because <usr> is the default folder used when no folder is specified for a particular property in a selector.

  Such an element name does not cause parsing of the MQRFH2 to fail, but is not accessible to the IBM MQ message property APIs.

• The content model of the <usr> folder is as follows:
  • Any valid XML name can be used as an element name, providing that it does not contain a colon.
  • Only simple elements, not nested folders, are allowed.
  • All elements take the default type of string, unless modified by a dt="xxx" attribute.
  • All elements are optional, but should occur no more than once in a folder.

• Element names in any folder considered to contain message properties must not contain a period (.) (Unicode character U+002E), because this is used in property names to indicate the hierarchy.

  Such an element name does not cause parsing of the MQRFH2 to fail, but is not accessible to the IBM MQ message property APIs.

In general, MQRFH2 headers that contain valid XML-style data can be parsed by IBM MQ without failure, although certain elements of the MQRFH2 are not accessible through the IBM MQ message property APIs.