Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Map audit overview
Audit log contents
Execution summary in the audit log

Projects
A project is a container for HCL Link artifacts.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Maps
  Maps define input and output specifications and mapping rules for data transformation.
  - Using Maps
  - Create maps to specify sources and targets
  - Maps and map source files
    Basic tasks involved in creating and managing maps.
  - Input and output cards
  - Card settings
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map settings
  - Configuring bursts
  - Building maps
  - Running a map
  - Managing invalid data
  - Map audit overview
    - Audit log contents
      - Controlling audit log content
        The map settings that control the map audit. You can also specify audit options from the command line. See Execution Commands documentation for command options. The audit log can be stored in a file or returned in memory if you use the RUN function or an API.
      - Execution summary in the audit log
      - Elapsed execution time in the audit log
      - Source data report by card
      - Target data report by card
      - BurstAudit Data in the audit log
      - Data content information in the audit log
    - Data settings in the audit log
    - Map settings in the audit log
    - Mapping from the audit log
  - Troubleshooting
  - Error and warning messages
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
- Connections and Actions
  This documentation describes connections and actions.
- Files
  Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.

Execution summary in the audit log

The Map Audit Switch = On and the SummaryAudit Execution = On map settings produce an audit log with execution summary information. The ExecutionSummary element of the audit log provides performance data for the map as a whole.

Execution summary information includes:

Map status information
Compiled map name
Map return code
Number of input objects found
Elapsed execution time
Number of output objects built
Burst restart count
Source data report by card
Map return code message
Target data report by card
Work area information by card

The format of the elapsed time is presented differently on Windows platforms than on non-Windows platforms.

Some information is optional, and does not always appear in the ExecutionSummary element of the audit log. For example, information about objects found and built is provided only when using a command engine. WorkArea data is provided only when a work area is used during map processing.