Defining configurations

Multiple configuration files

A single apply request can refer to several configuration files. This feature gives you the flexibility to create High-speed Apply Engine configurations that meet the needs of your site.

You might use multiple configuration files to:

• Create a separate configuration file for conflict resolution rules
• Specify a standard set of options (for example, temporary file storage options) that can be used by multiple apply requests
• Store database-specific information in one configuration file, and specify different types of apply requests for that database in separate configuration files

To include multiple configuration files in an apply request, specify a data definition (DD) statement for the configuration FileName (CFN) parameter, and use the DD statement to include the files. For more information about specifying a DD statement as part of an apply request, see Creating-and-running-apply-requests.

Creating and managing configuration files

This section provides instructions for creating configuration files for target tables.

They also provide instructions for certain configuration file management tasks, including:

• Mapping source object names to target objects

  If the table or column names in the input file differ from those in the target database, you can configure the apply request to map the source object names to the target objects. For more information, see Mapping source object names to target objects.

• Creating logical partitions for a target table

  You can create logical partitions for a target table to change the workload distribution for an apply request. For more information, see Creating logical partitions for target tables.

For more information about including configuration files in apply requests, see Creating-and-running-apply-requests.

Configuration file management

You can create as many configuration files as you need for the apply requests that you want to run.

Use the following practices to manage configuration files:

• Create a separate library or directory for High-speed Apply Engine configuration files. If you decide to change the location of the configuration files, remember that you must update any apply requests with the new location.
• Use a naming convention for the files to help you identify them. For example, you might identify the files with the target database name, job or task type (migration, SQL processing, or recovery), or input type (SQL or logical log file).
• Organize configuration files in a meaningful way for your site. You might have several data sets or directories in the configuration library, depending on how many configuration files you create.
• Because you can use several configuration files for a single apply request, you should include comments in the configuration file that describe how you use it. For more information about entering comments in a configuration file, see Comments-in-configuration-files.
• High-speed Apply Engine recognizes DD names and data set names for the configuration FileName (CFN) parameter. You can use a DD statement in an apply request to override configuration defaults. For more information see Apply-requests.

Creating or editing a configuration file

The High-speed Apply Engine uses one or more configuration files to determine the parameter values for an apply request.

Use this procedure to create or edit configuration files for your apply requests.

Before you begin

High-speed Apply Engine provides sample configuration files for you to copy and edit. The HLQ.DBSAMP library contains sample configuration files and apply requests. HLQ represents a high-level qualifier that you specified when you installed High-speed Apply Engine.

To help you determine which values to use for the parameters in this procedure, use the parameter descriptions in Command-and-syntax-reference.Configuration-file-format describes the format of the configuration file.

To create a configuration file

1. Create a configuration file with your desired configuration parameters.One method of doing this is to use a sample configuration file located in the HLQ.DBSAMP library as a template. If you use one of these files as a template, copy the file, renaming it according to your site requirements. Edit the file with any standard editor.

2. Edit the configuration parameters as required:

   1. You must include the [Startup] section with the SSID parameter.This step completes the minimum configuration. If you do not need to specify any other parameters, you can skip to Step 3.
   2. (optional) If your input source is a logical log control file, you must include the [Logical Log] section and the SQLType parameter.
   3. (optional) If you include the [ObjectMap] section, you must specify at least one SourceTable parameter and one TargetTable parameter.
   4. (optional) If you include the [ObjectCluster] section, you must define at least one cluster.
   5. (optional) If you include the [ObjectPartition] section, you must define at least one partition.
   6. (optional) Specify other parameters as appropriate for the apply request.Many of the configuration parameters have default values. Ensure that the defaults are acceptable for your environment and for the apply requests that will use the configuration file. For more information about each parameter's default values, see Command-and-syntax-reference.

   Tip

   Indent section names one or two spaces, so that you can easily insert comment characters. Indent parameters under their section headings for readability. If you include grouped parameters, such as those in the [ObjectMap] section, indent all of the parameters in a group to the same level.

3. Save the file.Note the file name and location. You will need this information to specify the configuration file in an apply request.

Where to go from here

You can specify this configuration file in one or more apply requests. For more information about creating apply requests, see Apply-requests.