Option | Description |
|---|---|
Clear messages after run | Specifies the default setting for clearing message object content after executing a map or process when the Run button is clicked. • When selected (true): Message object content is cleared after execution, including messages in sub-processes. • When not selected (false): Message object content is retained. If you run the map or process a second time, the message objects will contain the same values they had after the previous execution. To override this preference for a single run, use the Run button’s dropdown menu. The menu offers two options, Clear Messages After Run and Do Not Clear Messages After Run. Selecting one of these options will apply the opposite behavior of the current preference for that specific execution. |
Clear log file before run | Specifies the default setting for retaining the log file data before executing a map, process, or data profile. • When selected (true): Log file content is cleared before execution. • When not selected (false): Log file content is retained, and new content is appended. This setting applies to all newly created maps, processes, and data profiles. Existing ones will maintain their current settings. The default value is true. If specified in the Configuration tab, this option overrides the preference setting. Note: This value persists when running a package via the engine command line. However, the -cl command line option can be used to overwrite the setting stored in the artifact. |
Create unique log file name | Allows you to create log files with same name as the artifact name with the file extension as .log. This is applicable only for new artifacts. Note: If this option is selected, the file name specified in the Log File Location is ignored. |
Write log to project folder | Creates log file in the project folder. This is applicable only for new artifacts. If multiple artifacts have the same name, then the logs are included to the previous log file (that has the same name), if available unless the artifacts are in different projects. Note: If this option is selected, the path specified in the Log File Location is ignored. |
Log File Location | This setting allows you to: • Set your log file name and location. You can click Browse and select an existing log file or enter a new log file name and path. The default log file name is DataConnect.log. • If Create Unique Log File Name or Write Log to Project Folder is selected, the specified file name and path in Log File Location will be ignored. • Specify the log file’s execution location and the starting location for browse dialogs when creating new data profiles, maps, and processes (if Write Log to Project Folder is deselected). This option sets your log file location for every new data profile, map and process to a single log file. This is generally not recommended. This option was retained for backward compatibility with DataConnect v9 artifacts. The default log file name and location is <userdirectory>/Actian/DataConnect/Logs/DataConnect.log. For details on browse button behavior and rules, see Browsing Files and Directories. Note: No log file will be created if the path specified in Log File Location is incorrect or left blank. |
Error Types To Log | Allows you to select the types of error messages that must be included in the log file: • Errors: Logs errors that may cause a map or process execution to stop. • Warnings: Logs messages about data truncation in a field, field name changes, loss of precision, or other issues. • Informative Messages: Logs messages such as "Execution initialization", "Execution successful", number of records converted, deleted, updated, or inserted, time to convert, and whether the transformation was stopped. • Debug Messages: All messages generated as a result of a TraceOn action and some other messages are logged at this level. In this case, the record number, first five fields of each record, and all the events are recorded. The messages are logged up to the selected log type including the previous log types in the order of precedence. For example, if Warnings is selected, then the log file includes both Errors and Warnings messages. Similarly, if Debug Messages is selected, then the log file includes Errors, Warnings, Informative Messages, and Debug Messages. Note: In case of v9 compatible artifacts, only the selected type of error message is included in the log file. |
Force Unload Maps and Processes (v10 Process Execution Only) | Allows you to specify whether to unload maps and sub-processes within a process during execution. When enabled, all maps and sub-processes that are executed within loops are unloaded so that macros and other settings can be reevaluated. Note: A loop occurs when a set of steps execute more than once inside a process. This option is typically used when a process contains maps or sub-processes that require different macros values in order to execute properly. For example, maps and/or sub-processes that use macros for artifact locations where the macro values are reset during a looping operation. Setting this option to True forces the engine to unload the maps and sub-processes, and then reload them so that macro values within these maps and subprocesses are reevaluated. Setting this option to False sets the engine to retain and use the same macro values for all the maps and sub-processes it encounters in the process. When specified from the Preferences menu, this option is applied to all new v10 processes and stored in the process .rtc file. Note: To specify this option for a single v10 process, go to the Configuration tab, Execution Options. Tip... Unloading sub-processes might significantly increase processing time. Options are: • Use UnloadMapsAndProcesses setting from Cosmos.ini: (default) Executes new v10 processes according to the setting specified in the cosmos.ini file. Enabling this option requires you to add the following to the cosmos.ini file in the UserInfo section: unloadmapsandprocesses=x where x=1 unloads maps and sub-processes x=0 does not unload maps and sub-processes. For information, see Cosmos.ini Settings. • Do NOT force unload maps and processes (faster processing): Does not unload maps and sub-processes. Use this option when maps and sub-processes do not use macros for their locations, or the process does not loop. • Force unload maps and processes (slower processing): Unloads maps and sub-processes. This option might prolong processing time. |