Option Name | Short Name | Argument | Description |
|---|---|---|---|
-Logfile | -l | Filename | Set a log file with this name instead of the default name. This value must include the path of the file. If the path is not included, then Runtime Engine creates the log file in the current directory. If the log file name is not set using this option, then the log file specified in the map or process is used. By default, Runtime Engine logs all messages including informational messages. |
-Automatic_Mapping | -am | Number | Sets the Automatic Mapping Option. 1 - Map by name 2 - Map by relative field position 3 - No automatic mapping 4 - Duplicate source layout |
-New_Transformation | -nt | - | Start a new transformation specification. |
-New_Conversion | -nc | - | Start a new transformation specification. |
-Error_File | -l | Filename | Set logfile for this transformation. |
-Expr_Module_List | -em | String | Add list of expression modules. The string value must contain the path and file name of each expression module delimited by a semicolon (;) or a line feed (\n). For example, if there are two expression modules you want to add to a map or process named c:\test\expr1.ezscript and c:\test\expr2.ezscript, add them using this option on the command line or in a specification file: -Expr_Module_List c:\test\expr1.ezscript;c:\test\expr2.ezscript |
-Layout_Mismatch | -lm | Number | Set option for target layout mismatch. That is specify how Runtime Engine handles any mismatch between the layout of the source data and the source schema: 0 - Treat a mismatch as an error. 1 - Use the layout in the map schema. 2 - Use the layout of the target data and map by position. 3 - Use the layout of the target data and map by name. |
-Max_Errors | -me | Number | Sets the maximum errors for a map or process run. This value is used in the default Error Routine to determine if the number of errors encountered has reached the maximum. If the maximum is reached, the map or process is stopped. |
-Null_Handling | -nh | Number | If the target field is set to not accept Nulls and if the source field has spaces, Nulls, or is an empty string, this option indicates how the Runtime Engine handles this and transforms the data: • 0: Ignore - If a null is encountered, the record is rejected and the transformation proceeds as normal. In this case, the only way to avoid having the record rejected is to write an EZscript in the map or process to transform the data. • 1: Treat as Warning - Runtime Engine transforms the data on a best-fit basis, and a warning message is written to the log file indicating a null was encountered. The transformation continues uninterrupted. • 2: Treat as Error (default) - If a null is encountered, an error message appears. If the maximum error count is set to 1, the transformation is stopped. In this case, the only way to avoid having the record rejected (and possibly stopping the transformation) is to write an EZscript to transform the data. Note: This option is applicable for SQL targets only. |
-Overflow_Handling | -oh | Number | Sets overflow handling. It governs the Runtime Engine's behavior when an overflow is encountered while running a transformation: 0 - Runtime Engine does nothing when an overflow occurs. 1 - Runtime Engine logs a warning message to the log file and continues processing. 2 - Runtime Engine logs an error message to the log file and stops processing. |
-Reject_Type | -rt | String | Set the Reject Type. |
-Reject_Connect_Info | -rc | String | Change the Reject Connection Information. |
-Source_Type | -st | String | Set the Source Type. (New Transformation Only) |
-Source_Connect_Info | -sc | String | Change the Source Connection Information. |
-Source_Mismatch | -sm | Number | Set option for source layout mismatch: 0 - Treat as error 1 - Use map schema 2 - Use connection, match by position 3 - Use connection, match by name |
-Source_Filter_Expr | -sf | String | Add a Source filter Expression. |
-Clear_Source_Filters | -cs | Clear the Source Filter Expressions. | |
-Source_Sample_Logic | -sl | String | Set Sample Logic information for Source. |
-Target_Type | -tt | String | Set the Target Type. (New Transformation Only) |
-Target_Connect_Info | -tc | String | Change the Target Connection Information. |
-Target_Filter_Expr | -tf | String | Add a Target filter Expression. |
-Clear_Target_Filters | -ct | - | Clear the Target Filter Expressions. |
-Target_Sample_Logic | -tl | String | Set Sample Logic information for Target. |
-Truncation_Handling | -th | Number | Sets the Truncation Handling Options. |
-Query_Statement | -qs | Filename | Sets the Query Statement found in the file. |
-Key | -k | String | Specifies a password for accessing a password-protected .djar file. Specify the options, provide the password, and then the name of the .djar file. These .djar files can contain map or process files. For example, to run a process file that is inside a .djar file named abcd.djar, run the following command: djengine -pe -k password abcd.djar |
-Set | -se | name=value | Sets a variable for the map. You can substitute global variables within the Map Editor and provide their values at run time on the command line or in a specification file. Variables are set using the following syntax: -Set NAME=value -se NAME=value where: • NAME - Name of the variable set up in Map Editor. • value - Value that must be assigned for NAME. For example: djengine -se myvar=1000 conv.map.rtc You can also pass database connection string information using the -Set option as follows: djengine -set myvar=\"userid=sa;password=unlock\" conv.map.rtc Escape double quotes with a backslash. |
-Daemonize | -dm | - | Runs the map as a daemon. Note: This option is applicable only for Linux. |