Was this helpful?
Global Options
Global options are global because they do not apply to a single transformation or process.
You must specify global options before the map or process options.
Full Name
Short Name
Argument
Description
-Help
-h
-
Displays information about the syntax and options available for the Runtime Engine. Also, displays version, copyright, and registration information about the engine and exits.
Note:  Do not use this option with any other option.
-Repeat_Count
-r
Number
Sets the number of times the map or process will be run. If set to zero, then the file is run continuously.
-Verbose
-v
-
Displays informational messages during execution.
-Version
-V
-
Displays the version number and some other information of the installed Runtime Engine, then exits.
Note:  Do not use this option with any other option.
-RuntimeConfig
-RC
Filename
Specify the runtime configuration file that must be used.
-Source_List
-ss
-
Displays the available source connections that can be used as the source file types.
-Target_List
-ts
-
Displays the available target connections that can be used as the target file types.
-Initialization_Info
-i
file Name
Sets the location of the initialization file. It is recommended to use the cosmos.ini file available in the default location.
You can also create an initialization file based on the default cosmos.ini file. Make sure that there are no errors in the format and content of the initialization file. For information about the cosmos.ini file settings, see Cosmos.ini Settings.
-Clear_Logfile
-cl
-
Clears the log file before each run. If there are multiple engine steps (processes or maps), then this command clears the log file in each step. If a repeat count is specified, only the log file from the last repetition exists.
-Debug
-d
-
Displays additional information about the steps that are run.
-Trace
-t
-
Trace the map execution.
-Define_Macro
-D
String
Sets a macro value that can be used in the map or process. Instead of specifying directory paths in a map, Macros are set using the following syntax:
-Define_Macro NAME=filepath
where:
NAME: Name of the macro set up in Map Editor
filepath: Value for the macro.
Note:  You can use macros in Connection Strings for ChangeSource, ChangeTarget, SDK interfaces, and the engine Command Line Interface (CLI) for portability.
For information about setting up macros in Map Editor, see Managing Macro Sets and Macros.
-Http_Monitor
-mh
Number
Sets a simple progress monitor on the port specified using HTTP. To monitor the progress, open a web browser and enter the HTTP URL using the name of the local host and the port number provided for the Runtime Engine. For example, if the host name is engine.abcd.com and the port number is 100, the URL is:
http://engine.abcd.com:100
Note:  The URL is only valid while the engine is running.
-Macro_File
-mf
File name
Specifies the location of an XML or JSON file that has been created to store the macros used by the engine.
-Profile
-P
None
Turns on profiling but does not create the Execution Profiles folder within the related project folder. If this folder does not exist, the map runs but the profile.out file is not generated or written. Hence, use -PF with -P and specify the location where the profile.out file must be generated or written. The profile.out file is written to disk in the specified location.
For example:
djengine -P -PF C:\myworkspace\myproject\profile.out -RC C:\myworkspace\myproject\MyMap.map.rtc
-Profile_To_File
-PF
String
Turns on profiling. The specified argument is the path name for the profiling output file.
-Profile_Filter
-PM
Number
Mask of events that will be profiled.
Last modified date: 08/02/2023