Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Considerations for DB2 LUW targets

This section describes requirements and considerations for using the High-speed Apply Engine for DB2 LUW on the UNIX and Windows platforms.

For more information about installing High-speed Apply Engine, see Installing High-speed Apply Engine on UNIX or Windows.

Operational considerations for DB2 LUW targets

When you use High-speed Apply Engine, consider these constraints and recommendations:

  • For optimal performance, High-speed Apply Engine should be installed on the DB2 LUW server that contains the target tables.

  • File names that use mixed case or lowercase are processed exactly as they appear. If your system is case sensitive, specify the file names in the appropriate case. For more information, see Data set and file names in configuration files.

  • Table names that use mixed case or lowercase must be delimited by quotation marks. For more information, see Object names in configuration files.

  • Unless the target DB2 LUW database allows automated login, you must provide a user ID and password as part of the configuration. For more information about specifying these values, see Password and UserID.

  • The user ID that submits the apply request must have appropriate privileges on target tables. For more information, see DB2 LUW authorizations.

Database access for DB2 LUW targets

Using information from the configuration files and the apply request, the High-speed Apply Engine updates the DB2 LUW target tables. The database can continue to run while High-speed Apply Engine performs its updates, so you can update the target tables while they are online.

DB2 LUW authorizations

You must have the following DB2 LUW authorizations to run the High-speed Apply Engine:

  • On the target tables, bind privileges and table privileges (INSERT, UPDATE, and DELETE).

  • On the restart table, bind privileges and table privileges (INSERT, UPDATE, DELETE, and SELECT).

These authorizations can be granted during installation or after, but you must have these authorizations before you can run High-speed Apply Engine. The privileges that High-speed Apply Engine requires depend on the transactions that the apply request performs on the target tables.

DB2 LUW data type support

The High-speed Apply Engine supports the same data types and data type conversions as DB2 LUW.

For more information about compatible data types, consult the appropriate DB2 LUW documentation.

Template file

A template file is a separate file that is generated by Log Master for DB2 that the High-speed Apply Engine can use to efficiently process SQL input as static SQL against DB2 for mainframe targets or DB2 LUW targets.

For DB2 LUW targets, perform the following steps to use the template file:

  • Transfer (download) the SQL file and the corresponding template file to the target DB2 LUW server

  • Edit the SQL file

    The first statement in the SQL file is a comment that indicates the corresponding template file, as in the following example:

    -- @@DSNTMPL <mainframeFileName>

    Replace the existing file name (the name that was used when the template file was first generated by Log Master for DB2) with the fully qualified path name of the template file on the target DB2 LUW server.

  • Run an apply request that uses the SQL file as input

Was this page helpful? Yes No Submitting... Thank you

Comments