Handling New Columns

On the DATABridge Client side, you can either ignore the new column or convert the scripts to populate the date field from the new column rather than the old column. You can also do this using a configuration parameter and a DATASETS table option bit.

To ignore the new column

Assuming the new column is named order_date_new, you can configure the DATABridge Client to ignore it by adding the following to the data set mapping customization script. Using our example, the script would be named script.user_layout.order:

update DMS_ITEMS set active=0
where dms_item_name='ORDER-DATE-NEW' and dataset_name='ORDERS'

To populate the date field from the new date column

Assuming the fields are called order_date and order_date_new, the old and the new data set mapping customization scripts would be as follows.

• script.user_layout.orders before the first DMSII reorganization:

  update DMS_ITEMS set di_options=2, dms_subtype=13
  where dms_item_name='ORDER-DATE' and dataset_name='ORDERS'

• script.user_layout.orders after the first DMSII reorganization:

  update DMS_ITEMS set active=0
  where dms_item_name='ORDER-DATE' and dataset_name='ORDERS'

  /***/

  update DMS_ITEMS set di_options=2, dms_subtype=23
  where dms_item_name='ORDER-DATE-NEW', and dataset_name='ORDERS'

You can then rename the resulting column to the same name as the original table. The data table customization script to do this would be as follows.

script.user_define.orders after the first DMSII reorganization:

update DATAITEMS set item_name='order_date'
where item_name= 'order_date_new' and table_name='orders'

The SQL layout is unchanged except that the column order_date may have moved.