"D" to "F" Configuration Settings
DATAFLEXMODE
This setting determines whether CONNX runs in DataFlex or PowerFlex access mode.

0 | PowerFlex access mode.
1 | DataFlex access mode.

Default - DATAFLEXMODE = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = DATAFLEXMODE
Unix Registry Setting: DATAFLEXMODE
DATAFLEXSTRUCTUREUPDATE
If set to 1, CONNX will update the complete DataFlex file structure when performing "Update Statistics".
Default - DATAFLEXSTRUCTUREUPDATE = 0
Environments - Client, Windows, CDD
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = DATAFLEXSTRUCTUREUPDATE
Unix Registry Setting: CONNXCDD.OPTIONS.DATAFLEXSTRUCTUREUPDATE
DATATYPEOPT
The DATATYPEOPT registry setting is only examined after import. Changing the value of the registry variable does not affect runtime operation for a previously imported CDD.
If DATATYPEOPT = 0, CONNX creates data types for Adabas packed and unpacked decimal data. The CONNX data types are stored internally as numeric and mathematical operations are performed using microcode.
If DATATYPEOPT = 1, CONNX creates data types for Adabas packed and unpacked decimal data. The CONNX data types are stored internally as integers and mathematical operations performed against them will be fast.
In general, integer calculations are much faster than numeric calculations, which rely on microcode instead of a single CPU instruction. However, in some instances, such as data replication, the ODBC type will be used and a numeric or decimal type of minimum size is desired on the target server.
In such a case, setting DATATYPEOPT to 0 turns off data type optimization and allows for types that minimize scale and precision on the target database. A possible use case is synchronization of packed or unpacked numeric values from Adabas into Oracle, which supports only the Number data type.
Default - DATATYPEOPT = 0 (data type optimization is applied).
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = DATATYPEOPT
DB_LOCALE
This Unix-only language setting is for Informix access.
Consult the Informix documentation for information regarding specific valid values for your operating system.
Environments - Client
Unix Environment Variable: DB_LOCALE
DEBUG
This setting determines the level of logging and if logging is enabled. The debug messages are written to cnxrun.log

0 | Logging is disabled.
1 | Minimal logging level.
2 | Moderate logging level.
3 | Full tracing.

Default - DEBUG = 0 (Logging is disabled)
Environments - Client, Server, Windows, Unix, Mainframe
Configuration Manager: CONNX Settings; Current Key = CONNX, Key Value/Value Name = DEBUG
Unix Client Registry Setting: CONNX.DEBUG
Unix Server Environment Variable: DEBUG
Started Task: DEBUG
CICS: DEBUG
DEBUGLEVEL
This setting controls the CONNX JDBC server debug output level.

-1 | Only the startup message and error messages are logged. All other debug messages will be suppressed.
0 | No messages are logged. (Debug output disabled.)
1 | Some messages are logged. This provides a moderate amount of debugging/status information without severely affect performance. (Normal debug output level.)
2 | All startup, informational, and error messages are logged. This diagnostic level will impact performance negatively. (Extreme debug output.)

Default - DEBUGLEVEL = -1
Environments - Client, Windows, Unix, Mainframe
Configuration Manager: CONNX Settings; Current Key = JDBC, Key Value/Value Name = DEBUGLEVEL
Unix Client Registry Setting: JDBC.DEBUGLEVEL
DEBUGLOC
This setting allows you to specify a location in which to save the cnxserver.log. Usage:
DEBUGLOC = <filepath>
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = DEBUGLOC
Unix Configuration Setting: DEBUGLOC
DEBUGVERBOSE
This option determines the CONNX JDBC server debug verbosity. This option applies only to the CONNX JDBC server.

0 | Some information is included in the debug messages. This provides a moderate amount of debugging/status information without severely affecting performance.
1 | All information is included in the debug messages. This information level can impact performance negatively.

Default - DEBUGVERBOSE = 0
Environments - Client, Windows, Unix, Mainframe
Configuration Manager: CONNX Settings; Current Key = JDBC, Key Value/Value Name = DEBUGVERBOSE
Unix Client Registry Setting: JDBC.DEBUGVERBOSE
DEFAULTCOBOLCHAR
To enable the specification of the default signed datatype when importing COBOL FD tables, set the following values:
DEFAULTCOBOLCHAR = <CONNX Data type of choice>
Supply a CONNX data type number in the Value Data text box.
Default - DEFAULTCOBOLCHAR = 1 (Text (Right Space Padded) for ISAM types or Char for relational types)
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = DEFAULTCOBOLCHAR
Unix Environment Variable: CONNXCDD.OPTIONS.DEFAULTCOBOLCHAR
DEFAULTCOBOLDEC
To enable the specification of the default signed datatype when importing COBOL FD tables, set the following values:
DEFAULTCOBOLDEC = <CONNX Data type of choice>
Supply a CONNX data type number in the Value Data text box.
Default - DEFAULTCOBOLDEC = 315 (Signed Overpunch -> Decimal)
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = DEFAULTCOBOLDEC
Unix Environment Variable: CONNXCDD.OPTIONS.DEFAULTCOBOLDEC
DEFAULTCOBOLINT
To enable the specification of the default signed datatype when importing COBOL FD tables, set the following values:
DEFAULTCOBOLINT = <CONNX Data type of choice>
Supply a CONNX data type number in the Value Data text box.
Default - DEFAULTCOBOLINT = 25 (Signed Overpunch -> Integer)
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = DEFAULTCOBOLINT
Unix Environment Variable: CONNXCDD.OPTIONS.DEFAULTCOBOLINT
DEFAULTONDEMAND
This setting determines the default database connection method.

0 or not set | The default application will be set to Connect to All Databases in the CONNX Integrated Logon dialog box.
1 | The default application will be set to Connect on Demand in the CONNX Integrated Logon dialog box.

Default - DEFAULTONDEMAND = 0 (Connect to All Databases)
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = DefaultOnDemand
Unix Registry Setting: CONNX.DEFAULTONDEMAND
DEFAULTMUPE
Use DEFAULTMUPE to change the default number of MUs and PEs on an Adabas import.
If DEFAULTMUPE is unset, or set to a value less than one or a value greater than 191, the default value will be set to 5. This value determines the default value of the of the Max Repeat field on the ADABAS Count Selection dialog that is displayed during an Adabas file import.
This value is only used at import time and only affects Adabas imports.
Default - DEFAULTMUPE = 5
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = DEFAULTMUPE
DEFAULTPORT
Use DEFAULTPORT to change the default TCP/IP port used by CONNX to connect to CONNX servers.
Default - DEFAULTPORT = 6500
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = DEFAULTPORT
Unix Environment Variable: CONNXCDD.OPTIONS.DEFAULTPORT
DEFAULTVMSCREATEPATH
This setting enables you to set the destination of tables that you create with the Create Table SQL command with the RMS server component. Usage:
DEFAULTVMSCREATEPATH = DKS600:[MYDIR]
Where [MYDIR] is the destination folder you want.
Default - DEFAULTVMSCREATEPATH = DKS600:CNXDIR
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = DEFAULTVMSCREATEPATH
DOWNGRADELOCK
This setting is for Adabas and if set to 1, it causes records that are locked when processing an update or delete statement to be immediately unlocked if the client determines the record does not match the where clause criteria. Normally all locks are released when the transaction has been committed.
Default - DOWNGRADELOCK = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = DOWNGRADELOCK
Unix Environment Variable: DOWNGRADELOCK
Started Task: DOWNGRADELOCK
CICS: DOWNGRADELOCK
EMPTYSTRING
If set to 1, this setting makes CONNX treat zero-length strings as null values. This is required for some applications, like Oracle SQL Plus.
Default - EMPTYSTRING = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = EMPTYSTRING
Unix Configuration Setting: EMPTYSTRING
ENCRYPT
If set to 1, this setting enables an encrypted connection between the CONNX client and the CONNX server.
This setting applies only to databases that use the CONNX Listener/Server component for connections such as RMS, DBMS, RDB, Adabas, VSAM/QSAM, IMS, C-ISAM, D-ISAM, Microfocus COBOL, and Dataflex.
Default - ENCRYPT = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ENCRYPT
Unix Registry Setting: CONNX.ENCRYPT
ENTIRENETWORK
If set to 1, this setting enables CONNX compliancy with Software AG's Entire Network product.
Default - ENTIRENETWORK = 0
Environments - Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ENTIRENETWORK
Unix Environment Variable: ENTIRENETWORK
Started Task: ENTIRENETWORK
CICS: ENTIRENETWORK
ENTIRENETWORKMULTIFETCHFIXED
If set to 1, a specific Entire Network connection is applied to your EntireNetwork and MULTIFETCH becomes available as a setting.
Default - ENTIRENETWORKMULTIFETCHFIXED = 0
Environments - Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ENTIRENETWORKMULTIFETCHFIXED
Unix Environment Variable: ENTIRENETWORKMULTIFETCHFIXED
Started Task: ENTIRENETWORKMULTIFETCHFIXED
CICS: ENTIRENETWORKMULTIFETCHFIXED
ERRORONTRUNCATE
If set to 1, this setting will cause an error when truncation occurs during bulk loading operations, such as DataSync syncs or Replication initial states. Truncation occurs when a string data did not fit into the target.
When this setting is set to 1, the whole operation will stop when an error occurs.
Default - ERRORONTRUNCATE = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ERRORONTRUNCATE
Unix Registry Setting: CONNX.ERRORONTRUNCATE
ESQNULL
If set to 1, this setting makes CONNX treat Null Suppressed fields that contain empty values as a SQL NULL during imports. This setting is import only and applies only to FDT and Natural DDM imports.
Default - ESQNULL = 0
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ESQNULL
EXACTADSEARCH
If set to 1, the REST Server accepts only fully qualified Active Directory users in the format DIRECTORY\ADUSER in the log on screen. This limits the REST Server Active Directory lookup to the specified user.
Default - EXACTADSEARCH = 0
Environments - REST Server
Configuration Manager - CONNX Settings; Current key CONNX\RESTServer
FASTMEMORYSIZE
This setting determines how much physical memory is used to hold temporary results before using a memory mapped file. Usage:
FASTMEMORYSIZE = value
Default - FASTMEMORYSIZE = 16000000 (16 million)
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = FASTMEMORYSIZE
Unix Registry Setting: CONNX.FASTMEMORYSIZE
FASTPATHMATCH
CONNX for VSAM assumes that alternate index (path) cluster names have the same first two letters as the main cluster name - this assumption significantly speeds up index metadata retrieval.
Default - FASTPATHMATCH = 1
Environments - Server, Mainframe
Started Task: FASTPATHMATCH
CICS: FASTPATHMATCH
FILTERDATATYPES
This setting determines whether CONNX filters data types by database type.
Default - FILTERDATATYPES = 1 (Filter by database types)
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = FILTERDATATYPES
Unix Registry Setting: CONNXCDD.OPTIONS.FILTERDATATYPES
FIXMUPENAME
This setting corrects the SYSOBJH import naming behavior of MUs and PEs.

0 | The table name will be {Embedded_MU_Name}.
1 | The table name will be {Root_Table_Name}_{PE_Name}_{Embedded_MU_Name}.
2 | The table name will be {Root_Table_Name}_{Embedded_MU_Name}.

Default - FIXMUPENAME = 0 (do not use corrected behavior for backward compatibility)
Examples:
.. "BONUS" (Set to 0 - default)
.. "EMPLOYEES_INCOME_BONUS" (Set to 1)
.. "EMPLOYEES_BONUS" (Set to 2)
Environments - Client, Windows, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = FIXMUPEName
FORCEADANUKEY
This setting enables/disables the use of super descriptors that contain NU or NC constituent fields where no criteria is specified. This setting applies only to NU / NC compound keys (super descriptors). For more information on how to use this setting, see Sub / Super Descriptor Handling in Concepts > Performance Tips and Application Notes.
Default - FORCEADANUKEY = 0 (do not return records with unset key fields)
Environments - Client, Windows, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = FORCEADANUKEY
Unix Registry Setting: CONNX.ADABAS.FORCEADANUKEY
FORCECLIENTSORT
If set to 1, this option forces all data to be resorted using the client codepage. Without this setting, the results of certain queries will be sorted in the codepage of the dataserver when the index used matches order by clause of the SQL statement. Enabling this option will result in slower performance, but data will be consistently ordered using the client codepage.
Default - FORCECLIENTSORT = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = FORCECLIENTSORT
Unix Registry Setting: CONNX.FORCECLIENTSORT
FORCETRANSACTIONS
If set to 1, this setting forces the support of distributed transactions when connecting to two or more data sources and one of them does not support transactions.
Default - FORCETRANSACTIONS = 0 (disabled)
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = FORCETRANSACTIONS
Unix Registry Setting: CONNX.FORCETRANSACTIONS
FORCEVERSION
This setting determines whether the version banner is displayed for the CONNX listener.
Default - FORCEVERSION = 1 (enabled)
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = FORCEVERSION
Unix Environment Variable: FORCEVERSION
VMS Logical: FORCEVERSION
Started Task: FORCEVERSION
CICS: FORCEVERSION
FREEFORMCOBOLFD
This setting allows you to tell CONNX whether your COBOL statements are in fixed or free format.
COBOL source code can be in one of three formats:
1. COBOL (fixed, columns 7-72). This format skips columns 1-6 and 73+ of each line, (the sequence or line number area and the Program Identification Number Area). Only the code in columns 7-72 is used.
2. COBOL (variable, columns 7-). This format skips columns 1-6, that is, the sequence or line number area. All other columns are assumed to contain code. Line length is not limited.
3. COBOL (free format) assumes that all columns are equal and visualizes all the code as if line numbers and the Program Identification Number Area didn't exist. Line length is not limited.
When CONNX encounters COBOL statements, it assumes that you are using the fixed columns 7-72 format (the first format described above) and will ignore anything it finds in columns 1-6 and 73+.
If you are using the free format COBOL format, set FREEFORMCOBOLFD = 1.
Default - FREEFORMCOBOLFD = 0 (fixed, columns 7-72. Skip columns 1-6 and 73+)
Note:
FUJITSUCOBOLFD checks this setting to determine if there are comments in positions 1-6.
Environments - Client, Windows
Configuration Manager: CDD Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = FREEFORMCOBOLFD
FUJITSUCOBOLFD
Use FUJITSUCOBOLFD to ensure that mid-line comment information is not treated as part of a COBOL statement or definition.
Normally, COBOL does not allow inline comments. Comments appear on their own lines, with an * in position (Column) 7. The Fujitsu COBOL compiler allows inline comments. If the Fujitsu COBOL compiler encounters a *> on a line, it treats the rest of the line as a comment. Set FUJITSUCOBOLFD = 1 if you are using the Fujitsu COBOL compiler and the *> comment operand.
Default - FUJITSUCOBOLFD = 0 (only standard COBOL comment formatting applies)
Note:
If there are comments in the left hand margin (first six positions), set FUJITSUCOBOLFD = 0. Otherwise CONNX will treat the COBOL statements as fixed column, 7-72 format.
Environments - Client, Windows
Configuration Manager: CDD Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = FUJITSUCOBOLFD