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
Target data report by card
BurstAudit execution 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
        Work area information by card
        Execution summary audit log sample
        BurstAudit execution in the audit log
      - 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.

BurstAudit execution in the audit log

The Map Audit Switch = On and the BurstAudit Execution = On map settings produce an audit log with burst execution information. The burst element provides information on the performance of the burst.

If all input cards have the Fetch_As mode of Integral, there is one burst element in the audit log.
If any input card has the Fetch_As mode of Burst, there is one element for each burst.

The execution log contains the return code of the burst, the amount of time it took to process the burst (in seconds), and a status of each input and output. The input and output status include the card number, the bytes processed, the adapter return code, and the content return code.

For example, if a burst fails because an adapter could not connect, the audit log defines which adapter failed. If an input is invalid, the content return code specifies which input is invalid. If an output rule fails, the content return code tells you which output failed.

A sample of the burst audit execution information in the audit log is:

<Burst count="1">
<ExecutionLog   burstreturn="0" ElapsedSec="0.0118">
<inputstatus    card="1"   bytes="52"   adapterreturn="0"   contentreturn="0"/>
<inputstatus    card="2"   bytes="69"   adapterreturn="0"   contentreturn="0"/>
<outputstatus   card="1"   bytes="119"   adapterreturn="0"   contentreturn="0"/>
</ExecutionLog>
</Burst>