IBM Integration Bus, Version 10.0.0.2 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Message Sets: Restrictions for nesting complex types

If you include a group within another group or complex type, the Data Element Separation property for the nested group must be compatible with the Data Element Separation property of the parent group or complex type.

For example, you cannot set the parent property to Fixed Length and the child property to Tagged Delimited, because the length of the Tagged Delimited structure would not be known, and would therefore conflict with the parent definition. If groups are nested to three or more levels, the Data Element Separation property for each nested group must be compatible with all of its parent groups.

The rules for compatibility are listed in the following table.

  Parent
Child Tagged Delimited, Tagged Encoded Length All Elements Delimited, Variable Length Elements Delimited Fixed Length, Fixed Length AL3 Tagged Fixed Length Use Data Pattern
Tagged Delimited, Tagged Encoded Length Allowed Allowed Not allowed Not allowed Allowed
All Elements Delimited, Variable Length Elements Delimited Allowed Allowed Not allowed Not allowed Allowed
Fixed Length, Fixed Length AL3 Allowed Allowed Allowed Allowed Allowed
Tagged Fixed Length Allowed Allowed Not allowed1 Allowed Allowed
Use Data Pattern Allowed Allowed Allowed Allowed Allowed
Note:
  1. Tagged Fixed Length cannot exist at the inner level if any outer level has a Data Element Separation method of Fixed Length or Fixed Length AL3. This is because an item of Tagged Fixed Length can repeat a variable number of times. Fixed Length and Fixed Length AL3 are parsed by moving a set number of bytes: with a variable number of repeats, it is not possible to calculate the number of bytes that need to be parsed.

ad09480_.htm | Last updated 2015-09-24 12:52:15