Supported DMSII Structures

This section lists DMSII structures that are supported by the DATABridge Client. (A list of unsupported DMSII structures follows this section.) If you are the relational database administrator and have no experience with DMSII databases, this section will be more useful to you if you are working with the DMSII database administrator.

In addition to standard data sets and variable-format data sets, the DATABridge Client supports the following DMSII structures:

  • Embedded data sets (see exceptions in the following section)
  • Remaps
  • Logical database
  • GROUP
  • FIELD items for GROUPs of BOOLEANS
  • OCCURS
  • GROUP OCCURS
  • Data sets with more items than the max_columns parameter
  • Data sets that generate relational tables whose record sizes exceed the Microsoft SQL Server maximum length (8032 for SQL Server)
  • DMSII links

Not all of these structures, however, are supported by the relational database. The DMSII structures that are not supported by relational databases are mapped into a form that the relational database can use. Each of these structures and the way they are mapped in the relational database is explained in the remainder of this chapter.

Unsupported DMSII Structures

When the DATABridge host replication software does not support a particular DMSII structure, there may or may not be a warning message issued by the DATABridge Client, depending on the DMSII structure. For example, a message is generated when the data set has no keys.

The DATABridge Client does not support the following DMSII structures:

Note: Marking a field REQUIRED in the DMSII DASDL does not prevent the DATABridge Client from assigning the default NULL attribute to the mapped relational database column.

  • Embedded data sets within an ORDERED or COMPACT data set
  • Embedded data sets if the INDEPENDENTTRANS option is reset
  • POPULATION items
  • COUNT data items
  • FILLER data items
  • AGGREGATE data items