This setting determines whether CONNX runs in DataFlex or PowerFlex access mode.

Default - DATAFLEXMODE = 0

If set to 1, CONNX will update the complete DataFlex file structure when performing "Update Statistics".

Default - DATAFLEXSTRUCTUREUPDATE = 0

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).

This Unix-only language setting is for Informix access.

Consult the Informix documentation for information regarding specific valid values for your operating system.

This setting determines the level of logging and if logging is enabled. The debug messages are written to cnxrun.log

Default - DEBUG = 0 (Logging is disabled)

This setting controls the CONNX JDBC server debug output level.

Default - DEBUGLEVEL = -1

This setting allows you to specify a location in which to save the cnxserver.log. Usage:

This option determines the CONNX JDBC server debug verbosity. This option applies only to the CONNX JDBC server.

Default - DEBUGVERBOSE = 0

To enable the specification of the default signed datatype when importing COBOL FD tables, set the following values:

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)

To enable the specification of the default signed datatype when importing COBOL FD tables, set the following values:

Supply a CONNX data type number in the Value Data text box.

Default - DEFAULTCOBOLDEC = 315 (Signed Overpunch -> Decimal)

To enable the specification of the default signed datatype when importing COBOL FD tables, set the following values:

Supply a CONNX data type number in the Value Data text box.

Default - DEFAULTCOBOLINT = 25 (Signed Overpunch -> Integer)

This setting determines the default database connection method.

Default - DEFAULTONDEMAND = 0 (Connect to All Databases)

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

Use DEFAULTPORT to change the default TCP/IP port used by CONNX to connect to CONNX servers.

Default - DEFAULTPORT = 6500

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:

Where [MYDIR] is the destination folder you want.

Default - DEFAULTVMSCREATEPATH = DKS600:CNXDIR

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

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

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

If set to 1, this setting enables CONNX compliancy with Software AG's Entire Network product.

Default - ENTIRENETWORK = 0

If set to 1, a specific Entire Network connection is applied to your EntireNetwork and MULTIFETCH becomes available as a setting.

Default - ENTIRENETWORKMULTIFETCHFIXED = 0

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

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

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

This setting determines how much physical memory is used to hold temporary results before using a memory mapped file. Usage:

Default - FASTMEMORYSIZE = 16000000 (16 million)

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

This setting determines whether CONNX filters data types by database type.

Default - FILTERDATATYPES = 1 (Filter by database types)

This setting corrects the SYSOBJH import naming behavior of MUs and PEs.

Default - FIXMUPENAME = 0 (do not use corrected behavior for backward compatibility)

Examples:

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)

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

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)

This setting determines whether the version banner is displayed for the CONNX listener.

Default - FORCEVERSION = 1 (enabled)

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:

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+)

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)