Duplicate Names

DMSII allows duplicate data set names (if the duplicate name is an embedded data set). Relational databases, however, do not allow any duplicate table names. In this case, the DATABridge Client adds a numeric suffix to each name until a unique name is created.

If two data sets have the same name in the DMSII database, the first time the DATABridge Client encounters the duplicate table name, it appends the digit 1. If a table already exists with the duplicate name and the number 1, the DATABridge Client adds the number 2 and so on until a unique table name is created.

For example, if DMSII database A has a data set named PRODUCTS and DMSII database B also has a data set named PRODUCTS, the resulting DATABridge table names would be products and products1.

If you combine this duplicate data set name convention with the convention for naming split tables (when one data set results in more than one table), you can have multiple suffixes for short names.

For example, if you have two data sources with a data set named CUSTOMER, which also generates split tables, the tables are renamed as follows:

• customers and customers1 in the first data source
• customers11 and customers12 in the second data source (as the primary table was renamed customers1)

Duplicate item names may result in the following cases:

• When you use the same name for items in two different GROUPs. DMSII allows this, but the DATABridge Client ignores GROUPs.
• When you truncate two very long DMSII item names that are almost identical

The DATABridge Client handles duplicate item names the same way that it handles duplicate table names.