Client vs. Host Filtering

Use the following guidelines to determine when to use the host instead of the DATABridge Client to perform filtering.

Filtering Columns

On the host side, you can filter columns by creating a filtering routine with the DBGenFormat utility. On the DATABridge Client side, you can filter columns the same way you can filter data sets, which is to set the active column to 0 for the corresponding entry in the DMS_ITEMS.

The advantage of performing the filtering on the DATABridge Client side is that you save on host resources. However, there are a few cases where you should consider filtering on the host side, as follows:

• If you plan to filter many columns, consider filtering on the host side to reduce TCP/IP traffic. The best way to determine this is to try the filtering both ways and see which gives you the best throughput.
• If you plan to filter columns with confidential or sensitive information, it is best to perform the filtering on the host.

Filtering Data Sets

You can filter data sets on the host side by using a logical database or by creating a filtering routine with the DBGenFormat program. On the DATABridge Client side, you can filter data sets by setting the active column to 0 for the corresponding entry in the DATASETS client control table.

If you want to filter data sets that contain confidential or sensitive information, consider using a logical database or a filtering routine in the DBGenFormat utility. In this case, the DATABridge Client will have no record that these data sets exist.

Filtering Rows

Row filtering limits data to certain ranges; you can accomplish this via the WHERE clause of filtering routines created with the DBGenFormat program on the host. For more information, see Chapter 4 in the DATABridge Host Administrator’s Guide.