Home
Execution commands
This documentation includes information about the various ways to use execution commands and their options when executing maps. Execution commands are used to specify how to execute a map.
INI commands for debugging maps
This documentation presents the dtx.ini (INI) file commands you can use for the debugging of adapter connections for maps run using non event-driven execution methods.
Logging
The logging feature enables you to specify the type of information you want to capture about adapter connections in log files.

Execution commands
This documentation includes information about the various ways to use execution commands and their options when executing maps. Execution commands are used to specify how to execute a map.
- Command Server overview
  Use execution commands to override the map settings or card settings in a compiled map when a map is run using one of the following methods:
- Using Command Server commands
  When you run a map, you can:
- List of execution commands
  This documentation contains information about the execution commands and associated options, including the syntax of each command and its particular usage.
- Examples
  This documentation presents a variety of examples involving the execution of maps using various execution commands in a RUN() function and from the command line in UNIX™ and Windows™ environments.
- INI commands for debugging maps
  This documentation presents the dtx.ini (INI) file commands you can use for the debugging of adapter connections for maps run using non event-driven execution methods.
  - Logging
    The logging feature enables you to specify the type of information you want to capture about adapter connections in log files.
    - Logging categories
      The logging categories provide a variety of debugging information.
    - Debug
      Use the DebugName and DebugAppend commands configured in the dtx.ini (INI) file to specify how you want to create the output log file.

Logging

The logging feature enables you to specify the type of information you want to capture about adapter connections in log files.

You do this by configuring the following severity classes and debug components. They are listed in the order of impact of these severity classes and debug components referred to as logging categories, from lowest to highest, along with their equivalent entry in the Connections Manager logging entry. The logging categories in the INI file will be configured to 0 to turn that category off or 1 to turn that logging category on.

Logging Category: Logging Category in the Connections Manager
Trace: LogTrace
Debug: LogDebug
Info: LogInfo
Warn: LogWarning
Error: LogError
Fatal: LogFatal