Create Composite Keys

Use the Client Configurator to create composite keys if unique keys haven't been specified in the DMSII data. A composite key is created from a set of column names in a table that's derived from a data set.

If unique keys are not defined and you use Unisys Enterprise Database Server for ClearPath Extended Edition (formerly known as DMSII Extended Edition), the Databridge Client creates unique keys using RSNs, because they provide the best indexes. If RSNs aren't available, valid AA values are used for keys. This means that if a DMSII reorganization occurs, you will need to reclone all of your data sets. In data sets that don't have fixed length records, the AA values continually change and cannot be used as keys.

CAUTION:Before you create keys, make sure that your key (the combination of columns) will be unique and will not encounter duplicates. Otherwise, your data can become corrupted. You can only create composite keys for uncloned data sources.

Create a unique composite key

In the Explorer pane, right-click a data source and click Customize Data Source from the context menu. The Client Configurator opens.
In the DMSII pane, look for the items you want to include in the composite key. Click on one of them.
In the Relational Properties pane, find the Item Key property. In the value column, give it a number. For example, you may assign values of 1, 2, 3, and 4 to four columns to create your composite key. The numbers determine the order of the columns in the index.

NOTE:If you can't edit the Item Key value, a key may already be defined for the table. Keys appear in the Relational pane with this icon.
In the DMSII pane, select the next item you wish to include in the composite key, go to the Relational Properties pane and set the Item Key to the next number in the sequence, and so on until each item is assigned an Item Key number.
When you're done, in the menu bar, click Save.