Creating and running an apply request for Db2 LUW

Because of the command-line interface, generating an apply request for a Db2 LUW target can be as simple as typing a command.

Use the procedure in this section to simplify the apply request process.

Before you begin

Before you perform the tasks in this section, you should be familiar with the default path and configuration file for the High-speed Apply Engine in your environment. For more information, see File names for UNIX and Windows.

When you are configuring High-speed Apply Engine, be sure that the shared library environment variable is set to enable High-speed Apply Engine to run correctly. The name of the environment variable depends on your operating system, as shown in Shared library environment variable values: Db2 LUW. In this table, installationDirectory refers to the directory where High-speed Apply Engine was installed. The platform is the UNIX platform chosen during the installation (aix, sol). The v.r.m is the version, release, and maintenance level of High-speed Apply Engine.

You should also become familiar with the examples/db2udb subdirectory within the installation directory when you are configuring High-speed Apply Engine. The examples/db2udb subdirectory contains a sample apply request. The installation directory is the UNIX or Windows directory that you specified for High-speed Apply Engine during installation.

You can manually set these environment variables and run High-speed Apply Engine by invoking apebmain (for more information, see To run an apply request for DB2 LUW), or you can use the sample scripts in the installation root directory ( installationDirectory/HighSpeedApply/platform/v.r.m).

The sample scripts in the installation root directory are named apeenv and HighSpeedApply:

• The apeenv script originates from the profile and will set the environment variables required to run High-speed Apply Engine. You need to make specific reference to apeenv only once during your login session by typing . apeenv at the command prompt.
• You can use the HighSpeedApply script to run High-speed Apply Engine without having to set the path and shared library path. Using the HighSpeedApply script is the easiest way to run the component. It accepts the same parameters you specify to the High-speed Apply Engine executable command (apebmain), including the overrides to the parameters in the configuration file. BMC Software recommends that you move the HighSpeedApply script to one of the default directories in your path or your group's path.

To run an apply request for Db2 LUW

1. At the command prompt type apebmain.

2. Verify the name and location of the configuration file for the apply request, as follows:

   • If the file uses the default path and file name, skip to Step 4.
   • If the file does not use the default path and file name, go to Step 3.
   • If you are not using a configuration file, enter cfn=none and skip to Step 4.

   (You do not need a configuration file if you want to accept all High-speed Apply Engine default values, or if you enter all nondefault values as overrides on the command line.)

3. Enter the name of the configuration file, using the FileName (CFN) parameter. For an example, see UNIX and Windows command line.

   If the configuration file is in the current directory, type the file name. Otherwise, you must type the complete path and file name for the configuration file.

4. Add any configuration overrides required for the request.

   You can include as many overrides as necessary to complete the apply request. Separate each section name and parameter with a single space.

5. Press Enter to start processing the apply request.