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 High-speed Apply Engine 13.1.

Sections in configuration files

Each section in a configuration file contains a group of parameters that describe a particular type of information that High-speed Apply Engine uses for apply processing. Each parameter in the file must be specified in its designated section. The following figure shows the configuration section format.

Important

You can also include configuration information in an apply request by using overrides. For more information, see Overriding parameters in an apply request.

[SectionName]
parameter01=value01
parameter02=value02

When you include a section name in the configuration file or apply request, you must use square brackets ([ ]) or slashes (/ /) as section-name delimiters. You can use only one type of delimiter within a configuration file. The following figure shows examples of both types of delimiter.

[Agent]

or

/Agent/

If you use a dedicated 3270 terminal to access Db2 on a mainframe target, you should use the slash character for section names. If you use a terminal emulator that supports square brackets, verify that all square brackets in a configuration file resolve to only one of the following hexadecimal code pairs:

  • The [ character resolves to 0xAD, and the ] character resolves to 0xBD.
  • The [ character resolves to 0xBA, and the ] character resolves to 0xBB.

Important

Be particularly cautious if you use cut and paste functions to copy information into a terminal emulator. The characters that you paste into the window might resolve differently than the characters that you type directly into the window. If you mix the different types of square brackets in the same configuration file, High-speed Apply Engine issues an error message for the configuration.

To verify that the brackets are the same throughout a file, display the hexadecimal values for the configuration file and examine the section names for discrepancies.

Related topic

Configuration-file-format


 

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