Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Log Master for Db2 13.1.

SQLXLAT data set syntax


This topic describes the syntax to use within the SQLXLAT data set.

Use this syntax to change the names of tables and columns as you generate SQL. This capability can be helpful when you use SQL statements to migrate data from one system or platform to another. Specify the existing names of tables or columns and the corresponding new names that you want to use in the generated SQL statements.

SQLXLAT syntax diagram

GUID-D9A62629-B006-4FC7-8538-03B2F7313E68-low.png

Remember the following points:

  • The columns referenced in a COLUMN specification must be part of the table referenced in the preceding TABLE specification.
  • To translate a column without translating a table name, you must specify both tableName and newTableName as the same character string.

    Example
    TABLE user01.firstTable -> user01.firstTable
    COLUMN account -> otherAccount
  • To specify multiple tables in one specification, use an asterisk (*) as a wildcard character in place of any userID, tableName, or newTableName. Log Master translates the names of all tables that match your specified pattern. The asterisk represents a complete user ID or table name (you cannot match on part of a name).

    You cannot specify multiple columns in one specification (Log Master does not support wildcard characters in column names).

For an example of SQL name translation, see Sample SQLXLAT DD statement. For more information about the SQLXLAT DD statement, see SQLXLAT in Specifying-the-DD-statements.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*