The dxeconfig.cfg file is used to globally manage your ODBC Extension or Oracle Extension settings. By default, it contains the following settings:
* Data Express Configuration File LogLevel:1 Always Drop Table:N CSV Data Store:N COBOL Masking:N Validate Target Table:N Validate Source Schema:N Enable Logging:N Hide Progress:N Hide Log Message:N Use Extended C Masking:N Trim Spaces for ODBC Char Columns:N Commit Size(MBs) [user range = from 1 to 4000, default range = 0]:0 * These entries are only applicable to the Oracle Extension. Text Output:N Data Separator:, Fields Enclosed By:" Identify Externally:N Use Append Condition:N |
The following settings can be specified:
Controls the level of detail displayed in the dxe_errorlog.txt file. You can change the LogLevel as needed or when requested to do so by Product Support:
LogLevel | Description |
---|---|
1 | Default log level that provides a summary for each processed data store. |
2 | Verbose output used for diagnostic purposes that contains the SQL statements executed against your source and target data stores. |
3 | Generates ODBC trace output that is written to odbctrace.txt. |
By default (Always Drop Table set to N), if a table already exists within the data store, the Extension Technology first executes a DELETE FROM TableName statement prior to performing INSERT operations. If the setting is changed to Y and a table exists, it is removed by the execution of the DROP TABLE TableName statement, which forces the table to be recreated.
You can also use K and O values, when the target table is not deleted.
If K (keep), the existing records in the target are kept, and a new record with the same key as another record in the target is discarded.
If O (overwrite), the existing records in the target are kept, and a new record with the same key as another record in the target overwrites that record, in effect deleting the original record.
Controls whether the tables referenced by a given method should be stored in text files delimited by commas. To enable, change the CSV Data Store parameter from N to Y.
Controls whether you are using COBOL routines to mask your data. Possible values are:
Y | By default, COBOL Masking is set to Y. |
N | If you want to use C masking routines, change the COBOL Masking parameter to N. |
O | When the value is "O" (from Others), the product can use any language satisfying the following requirements:
|
Controls whether the target tables are validated against the source tables to ensure that the structures are exactly the same. By default, Validate Target Table is set to Y. If you do not want to validate the table structures , change this parameter from Y to N.
Controls the usage of source schema. If Y, the target schema name is the same as the source one. If N, the default target schema name is used. By default, Validate Source Schema is set to Y.
For more information about logging, see Logging Exit Routines in the Data Masking Guide.
Suppresses visual progress during validation.
Controls the display of log messages in the dxe_errorlog.txt file when Enable Logging is used.
Controls the use of extended C masking. If N, standard masking is used. This the default. If set to Y, extended C masking is used. For information on the differences between standard C masking and extended C masking, see Appendix B of the Data Masking Guide.
Optional. If Y, final spaces in ODBC CHAR columns are replaced with low-values (x00). If N or the Trim Spaces for ODBC Char Columns parameter is omitted, final spaces in ODBC CHAR columns are left unchanged.
0 | A commit is performed immediately after processing 95 MB; one commit for each 95 MB processed. Default. |
n | A numerical range from 1 to 4000 indicating the number of processed megabytes (MBs) after which to perform each commit. Any number over 4000 is interpreted as 4000. |
By default, Data Express inserts the processed data into the specified target data store. You can configure Data Express to write the output to a text file instead, which can be subsequently loaded into an Oracle database using the Oracle sqlldr routine. To enable this, change the Text Output parameter from N to Y.
The following settings are only applicable to the Oracle Extension:
Oracle Extension only. By default, the delimiter used to separate Oracle fields is the comma (,). You can override this default by specifying one or more characters.
Oracle Extension only. By default, strings are enclosed by double quotation marks ("). You can override this default by specifying one or more characters.
If the target table does not exist, the Extension Technology executes a CREATE TABLE statement and then INSERT operations in order to create it. However, if the target table already exists, the way the Extension Technology behaves depends on the settings specified in the dxeconfig.cfg file. For example:
Always Drop Table | Validate Target Table | Resulting Behavior |
---|---|---|
Y |
n/a |
A DROP TABLE statement is executed before the CREATE TABLE statement and INSERT operations. |
N | Y |
If the target table's metadata matches the source table's metadata exactly, the method will be executed. If any mismatch in the metadata is found, the method will not be executed. For example, if the source table is defined as: CREATE TABLE SRC.MYTABLE(C1 INT, C2 CHAR(5), C3 DECIMAL(5,2)) and the target table exists, but is defined as: CREATE TABLE TGT.MYTABLE(C3 DECIMAL(5,2), C1 INT, C2 CHAR(5)) the method will not be executed. Note: The
The Always Drop Table parameter set to N and the Validate Target Table parameter set to Y are default settings. |
N | N |
The Extension Technology will not perform any validation. If the target table does not include all columns from the source table (regardless of order), the INSERT operation will fail and the elaboration will terminate abnormally. For example, if the source table is defined as: CREATE TABLE SRC.MYTABLE(C1 INT, C2 CHAR(5), C3 DECIMAL(5,2)) and the target table exists, but is defined as: CREATE TABLE TGT.MYTABLE(C3 DECIMAL(5,2), C1 INT, C2 CHAR(5)) the method should execute and complete normally. If the target table is instead defined with a column C5 instead of C3: CREATE TABLE TGT.MYTABLE(C5 DECIMAL(5,2), C1 INT, C2 CHAR(5)) the INSERT statement will fail, causing the method to terminate abnormally. |
Y | Data Express uses the information in the configured Wallet rather than the method.rc file to connect to the database, eliminating the need to specify user name and password credentials. |
N | Database connection requires that you specify a user name and password. |
Y | During the execution of the
dxestart module, adds the APPEND condition to the INSERT statement and the NOLOGGING condition to the CREATE TABLE statement.
Important: For the full benefit, you must also set
Always Drop Table to
Y.
|
N, or the Using append condition parameter is omitted | Nothing is added during the execution of the dxestart module. |
0 | Commit is performed after processing all inserts. Default. |
n | A numerical range from 1 to 4000 indicating the number of processed megabytes (MBs) after which to perform a commit. This enables incremental commits and should be used when processing a very large number of inserts. |