"C" Configuration Settings
CASESENSITIVE
This setting determines whether text comparisons are case-sensitive.

0 | CONNX ignores the case during comparisons unless the query is executed in pass-through mode and the target database has a contrary behavior.
1 | CONNX respects the case during comparisons unless the query is executed in pass-through mode and the target database has a contrary behavior.

Default - CASESENSITIVE = 0
Environments - Client, Windows, UNIX
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CASESENSITIVE
Unix Registry Setting: CONNX.CASESENSITIVE
CDDBASEFOLDER
Optional. Changes the "home" directory for the Online CONNX Data Dictionary Manager. The “home” directory is the root directory for all of the Online CONNX Data Dictionary Manager folders. The value is the absolute path to the location of the new home directory.
Default – location path to the 32 bit CONNX Components installation directory.
The 32 bit value is used for both the 32 and 64 bit versions of the REST Server. The 64 bit value is ignored.
Environments - REST Server, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CDDBASEFOLDER
CDDPASSWORD
This is a Data server setting which, if set, will only allow connections from CDDs when the CDD password matches the specified value. Only the first 10 characters of the password are used for a case insensitive match to allow connections. This setting is a comma separated list of passwords, enabling the support of multiple CDD passwords simultaneously. This also means that you cannot use a comma in any of the CDD passwords. The syntax is as follows:
CDDPASSWORD = <password>[,password][,password ...]
Default - By default, there are no set passwords.
Environments - Client, Windows, Unix, VMS
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CDDPASSWORD
Unix Registry Setting: CONNX.CDDPASSWORD
CERTPATH
Used during the Import of a Redshift database to specify the folder with the SSL Certificate. If this is not set, then the folder used for the certificates is the root installation folder, e.g.
CERTPATH = C:\CONNX32
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CERTPATH
Unix Registry Setting: CONNX.CERTPATH
CHARASVARCHAR
When set to a value of 1, this value allows Adabas Alpha (A) fields to be imported as VARCHAR instead of CHAR. This setting only affects the import process and is only valid for Adabas SYSOBJH Transfer Format (SYSTRANS) imports.
Default - CHARASVARCHAR = 0
Environments - Client, Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = CHARASVARCHAR
Unix Registry Setting: CONNX.CERTPATH
CLIENT_LOCALE
This Unix-only language setting is for Informix access.
Please consult your Informix documentation for information about specific valid values for your operating system.
Environments - Client
Unix Environment Variable: CLIENT_LOCALE
CNXALTUI
This setting is used by the CONNX Installation utility and does not need to be edited. It specifies whether the installer was the CONNX branded installer, or the Adabas SQL Gateway branded installer.
Environments - Client, Windows CONNX
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXALTUI
CNXBARNARD
Enables / Disables the the Barnard TCP/IP stack for the VSAM Server component on CICS. This only applies on CICS systems.

0 | Barnard TCP/IP stack is disabled.
1 | Barnard TCP/IP stack is enabled.

Default - CNXBARNARD = 0
Environments - Server
CICS: CNXBARNARD
CNXBATCHBUFFER
Determines the size of buffer, in bytes, used for sending records from the data server back to the client in batch. The buffer size can have a substantial impact on performance depending on the network latency between the client and the server.
Default - CNXBATCHBUFFER = 65535
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXBATCHBUFFER
Unix Environment Variable: CNXBATCHBUFFER
VMS Logical: CNXBATCHBUFFER
Started Task: CNXBATCHBUFFER
CICS: CNXBATCHBUFFER
CNXCONNECTBACK
Enables / Disables TCP/IP socket sharing in the Listener connection logic.
The client creates a TCP/IP socket and associates it with the installation port (usually 6500). The installation port will need to be open on the CONNX listener machine. After the initial connection to the listener with this socket:
If CNXCONNECTBACK = 0, the listener hands the client-created socket to the CONNX server. This socket is used by the rest of the server-client and client-server communications until the client closes the connection. This is the optimal setting.
If CNXCONNECTBACK = 1, the listener tells the CONNX server the client information and closes the client-created socket. The server creates a new socket and associates it with a port on the client machine. This server-created socket is used by the rest of the server-client and client-server communications until the client closes the connection.
The presence or absence of a firewall between the CONNX client and server will affect the use of CNXCONNECTBACK:
If there is no firewall between the CONNX client and server, you do not need to be concerned with the CNXCONNECTBACK setting.
If there is a firewall between the CONNX client and server, we recommend setting CNXCONNECTBACK to 0 because the only port that needs to be open through the CONNX server machine firewall is the installation port (usually 6500). If CNXCONNECTBACK is 1, a port must be opened in the firewall on each of the client machines connecting to the server because the server is creating a new socket associated with a port on the client.
There is no performance gain with either setting of CNXCONNECTBACK. All communication is done over one socket for each connection; it only changes which part of CONNX creates the socket.
Default - CNXCONNECTBACK = 0
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXCONNECTBACK
Unix Environment Variable: CNXCONNECTBACK
VMS Logical: CNXCONNECTBACK
Started Task: CNXCONNECTBACK
CICS: CNXCONNECTBACK
CNXDECNETTASK
On VMS, this setting determines whether DECNet Task-to-Task is used to start a new server process. By default CONNX will attempt this method, and if it fails, it will use the CREPRC system call instead. With DECNet Task-to-Task, the server process type is "Network", with CREPRC, the server process type is "Interactive", which may have VMS licensing implications. This setting is the opposite of CNXUSEMBX.
Default - CNXDECNETTASK = 1
Environments - Server, VMS
VMS Logical: CNXDECNETTASK
CNXDIR
VMS logical that points to the location of the CONNX server binaries.
Environments - Server, OpenVMS
VMS Logical: CNXDIR
CNXHASH
CAUTION:
Use the standard hashing algorithm on the CONNX client and server in almost all circumstances. Do not adjust or change this setting unless instructed to by a CONNX Technical Support representative.
If your older mainframe system uses too many CPU cycles running DataSync, contact Technical Support and, if appropriate, we will help you change your hashing routine.
To enable the selection of the hash function for incremental updates, enter one of the following values:

0 = fnv hash routine | If CNXHASH is set to 0, or the configuration setting for HASH is 0, CONNX uses the Fowler / Noll / Vo (FNV) Hash algorithm.
1 = oy_djb 64bit hash routine | If CNXHASH is set to 1, or the configuration setting for HASH is 1, CONNX uses the Ozan Yigit (SDBM) Hash combined with the Daniel J. Bernstein Hash algorithm.
2 = bj 64bit hash routine | If CNXHASH is set to 2, or the configuration setting for HASH is 2, CONNX uses the Bob Jenkins Hash algorithm.
3 = oy 32bit hash routine | If CNXHASH is set to 3, or the configuration setting for HASH is 3, CONNX uses the Ozan Yigit (SDBM) Hash algorithm.
4 = djb 32bit hash routine | If CNXHASH is set to 4, or the configuration setting for HASH is 4, CONNX uses the Daniel J. Bernstein Hash algorithm.
5 = returns zero | If CNXHASH is set to 5, or the configuration setting for HASH is 5, CONNX uses the NULL hash algorithm. The NULL hash does nothing and returns zero. It is only for benchmarking purposes and cannot be used for any other purpose.
6 = oy_djb 32bit + djb 32bit hash routine | If CNXHASH is set to 6, or the configuration setting for HASH is 6, CONNX uses an alternate form of the Ozan Yigit (SDBM) Hash combined with the Daniel J. Bernstein Hash algorithm.
7 = u_mac 64bit hash routine | If CNXHASH is set to 7, or the configuration setting for HASH is 7, CONNX uses the UMAC Hash algorithm if the server is NOT a VAX. If the server is a VAX, the program will fire an assert() and stop if data synchronizations are attempted.

If performing data synchronization using CNXHASH and HASH, the hash algorithm used by both client and server must match, or a full synchronization is performed for every sync operation.
Environments - Server, Windows, Unix, VMS, Mainframe
Windows Environment Variable: CNXHASH
Unix Environment Variable: CNXHASH
VMS Logical: CNXHASH
Started Task: CNXHASH
CICS: CNXHASH
VMS Logical: CNXUSEMBX
CNXKBAUTHORIZE
On Unix, if set to 1, this setting enables Kerberos authentication instead of standard unix password file authentication.
Default - CNXKBAUTHORIZE = 0
Environments - Server
Unix Environment Variable: CNXKBAUTHORIZE
CNXLOCALIP
CNXLOCALIP can be used to assign an IP address to the data source server.
Environments - Server
Windows Environment Variable: CNXLOCALIP
Unix Environment Variable: CNXLOCALIP
VMS Logical: CNXLOCALIP
Started Task: CNXLOCALIP
CICS: CNXLOCALIP
CNX_LIBRARY_PATH
On Unix, the specified path, if provided, will be used to set the appropriate library path based on the unix operating system.
Environments - Server
Unix Environment Variable: CNX_LIBRARY_PATH
CNXLISTENER
CNXLISTENER points to the name of the listener program. It is used by CNXSTART on the mainframe.
CAUTION:
This option should not be changed unless instructed by CONNX Technical Support.
Environments - Server
Started Task: CNXLISTENER
CICS: CNXLISTENER
CNXMUALPHA
For Adabas, when this setting is enabled, CONNX will use an MU instead of an LA field during create table for a char or varchar field between 254 and 16381 bytes.
Default - CNXMUALPHA = 0
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXMUALPHA
Unix Environment Variable: CNXMUALPHA
VMS Logical: CNXMUALPHA
Started Task: CNXMUALPHA
CICS: CNXMUALPHA
CNXNOPREAUTHORIZE
Enables / disables the CONNX user ID/password verification logic.
This setting affects RACF.

0 | CONNX validates userid/password.
1 | CONNX does not validate userid/password.

For Mainframe:
If set to 0, then the CONNX load libraries must be APF-authorized.
In addition, for Adabas: When set to 0, the RACF userid is made available in the attached buffer area of the target nucleus. From Adabas 8.3 onwards, this information is then available in UQ displays, CLOG, PLOG, etc.
For UNIX/VMS:
If set to 1, the user name/password combination is not validated on the system.
Default - CNXNOPREAUTHORIZE = 0
Environments - Server, Mainframe, Unix, VMS
Unix Environment Variable: CNXNOPREAUTHORIZE
VMS Logical: CNXNOPREAUTHORIZE
Started Task: CNXNOPREAUTHORIZE
CICS: CNXNOPREAUTHORIZE
CNXNOPOST
Disables the post back message from the server to the listener. Disabling this postback will cause {serverlist} to no longer function.
Default - CNXNOPOST = 0 ( 0 = enabled).
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXNOPOST
Unix Environment Variable: CNXNOPOST
VMS Logical: CNXNOPOST
Started Task: CNXNOPOST
CICS: CNXNOPOST
CNXNOQIO
Disables the use of QIO for TCP/IP communications on OpenVMS for RMS, RDB, and Codasyl DBMS OpenVMS .

0 | CONNX will use QIO if possible.
1 | CONNX will not use QIO.

Default - CNXNOQIO = 0
Environments - Server, VMS
VMS Logical: CNXNOQIO
CNX_NO_TIMER
Disables the heartbeat timer between the client and the server.
CAUTION:
Do not enable this setting unless instructed to do so by CONNX Technical Support.
Default - CNX_NO_TIMER = 0
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNX_NO_TIMER
Unix Environment Variable: CNX_NO_TIMER
VMS Logical: CNX_NO_TIMER
Started Task: CNX_NO_TIMER
CICS: CNX_NO_TIMER
CNXOLDLICENSE
This setting enables the pre CONNX 10.5 licensing methodology for RMS, RDB and Codasyl DBMS OpenVMS users, and does not use the current license server for these data sources.

0 | Use current license server technology.
1 | Use pre CONNX 10.5 licensing method.

Default - CNXOLDLICENSE = 0
Environments - Server, VMS
VMS Logical: CNXOLDLICENSE
CNX_PASS_TICKETS
Enables / disables support for RACF PASSTICKETS.
This setting applies only to Adabas. Not for typical customer usage. Please only set if using RACF passtickets or instructed to by CONNX Technical Support.

0 | Disable RACF passticket support.
1 | Enable RACF passticket support.

Default - CNX_PASS_TICKETS = 0
Environments - Server, Mainframe (Started Task/Batch only. Does not apply to CICS)
Started Task: CNX_PASS_TICKETS
CNXPOSTSERVERNAME
Specify the TCP/IP name of the server for use when performing the postback (see CNXNOPOST). This setting is typically only required when local loopback is not functioning on the server. Usage:
CNXPOSTSERVERNAME = <name or IP Address of the server>
Default - CNXPOSTSERVERNAME = 0
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXPOSTSERVERNAME
Unix Environment Variable: CNXPOSTSERVERNAME
VMS Logical: CNXPOSTSERVERNAME
Started Task: CNXPOSTSERVERNAME
CICS: CNXPOSTSERVERNAME
CNXRUNPORT
Setting CNXRUNPORT will update the server port number. The server port is the TCP/IP port that the CONNX TCP/IP Listener program accepts messages from the CONNX Windows client interfaces (ODBC, OLE DB, and .NET). This setting may affect CONNECTPORT.
Default - The default port is 6500. If you need to change it, enter CNXRUNPORT = <new port number>
Environments - Server
Windows Environment Variable: CNXRUNPORT
Unix Environment Variable: CNXRUNPORT
Started Task: CNXRUNPORT
CICS: CNXRUNPORT
CNXSELECT
Determines whether the TCP/IP call "select" is issued before a recv or send to determine if the socket is in a "ready"state.
This option should not be changed unless instructed by CONNX Technical Support.
Default - CNXSELECT = 1
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXSELECT
Unix Environment Variable: CNXSELECT
VMS Logical: CNXSELECT
Started Task: CNXSELECT
CICS: CNXSELECT
CNXSOCKETTIMEOUT
When CNXCONNECTBACK is enabled, this value is the number of seconds for the server to wait while attempting to connect back to the client.
Default - CNXSOCKETTIMEOUT = 58
Environments - Server
Windows Environment Variable: CNXSOCKETTIMEOUT
Unix Environment Variable: CNXSOCKETTIMEOUT
VMS Logical: CNXSOCKETTIMEOUT
Started Task: CNXSOCKETTIMEOUT
CICS: CNXSOCKETTIMEOUT
CNXTCPIPBUFFER
Determines the requested send and receive buffer size at the TCP/IP protocol level with the setsockopt call.
This option should not be changed unless instructed by CONNX Technical Support.
Default - CNXTCPIPBUFFER = 16384
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CNXTCPIPBUFFER
Unix Environment Variable: CNXTCPIPBUFFER
VMS Logical: CNXTCPIPBUFFER
Started Task: CNXTCPIPBUFFER
CICS: CNXTCPIPBUFFER
CNXUSEMBX
On VMS, this setting determines whether DECNet Task-to-Task is used to start new server process. By default CONNX will attempt DECNet Task-to-Task, and if it fails, it will use the CREPRC system call instead. With DECNet Task-to-Task, the server process type is "Network", with CREPRC, the server process type is "Interactive", which may have VMS licensing implications. This setting is the opposite of CNXDECNETTASK. To disable DECNet Task-to-Task, set CNXUSEMBX = 1.
Default - CNXUSEMBX = 0
Environments - Server, VMS
VMS Logical: CNXUSEMBX
COBOL_COMP_BYTESTEP
Normal processing converts COBOL COMP or BINARY field types to a 1, 2, 4, or 8 byte field depending on the precision.
If you want CONNX to treat the COBOL COMP or BINARY field type as a binary field that contains an exact number of bytes to satisfy the decimal precision requirements, enable COBOL_COMP_BYTESTEP, by setting it to a nonzero value:
COBOL_COMP_BYTESTEP = <nonzero value>
When COBOL_COMP_BYTESTEP is enabled, the decimal precision of the field will only use the exact number of bytes that are necessary.
If COBOL_COMP_BYTESTEP is enabled, the field definition PIC S9(05) COMP would result in a var-binary integer type that has a field byte length of 3 instead of 4.
Environments - Client, Windows
Configuration Manager: CDD Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = COBOL_COMP_BYTESTEP
COLLATINGSEQUENCE
This setting determines which collating sequence CONNX uses for sorting.

0 | CONNX uses the ASCII collating sequence.
1145 | The 1145 value represents the EBCDIC code page that CONNX will use as collating sequence when sorting data.

Default - COLLATINGSEQUENCE = 0.
This feature has the following limitations:
1. The feature works only with non-unicode data.
2. Comparisons are done in codepage 1145 (which should be suitable for any EBCDIC platform)
3. There will be a small performance hit due to the extra translations.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = COLLATINGSEQUENCE
Unix Registry Setting: CONNX.COLLATINGSEQUENCE
COMPRESS
Set this to 1 to speed up data transmission when data is sent over a network. When set, CONNX applies a data compression algorithm that removes repeating characters from the data stream.
Default - COMPRESS = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = COMPRESS
Unix Registry Setting: CONNX.COMPRESS
COMMITCOUNT
This setting makes CONNX automatically issue a commit every specified number of inserts, regardless of transaction mode.
CAUTION:
Setting COMMITCOUNT to a value other that zero can cause transactions to be committed earlier than expected, making subsequent rollbacks be ineffective or incomplete.
Default - COMMITCOUNT = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = COMMITCOUNT
Unix Registry Setting: CONNX.COMMITCOUNT
CONNECTIONPOOLING
When Connection Pooling is enabled, at disconnect time, connections are stored in a dynamically sized "pool". The connection remains in the pool until it is either re-used, or the CONNECTIONPOOLINGTIMEOUT number of milliseconds has elapsed.

0 | Connection pooling is disabled.
1 | Connection pooling is enabled for all applications. This setting is only supported by systems that use TCP/IP.
2 | Connection pooling is enabled only for the following applications: CNXJDBC - Our JDBC Service IISADMIN - Internet Information Server ASPNET_WP - ASP.NET INETINFO - Internet Information Server (used in debugging) DLLHOST - Any COM/DCOM DLL based applications SVCHOST - Any non-COM/DCOM DLL based applications SQLSERVR - SQL Server

Default - CONNECTIONPOOLING = 2
CONNECTIONPOOLINGTIMEOUT
If CONNECTIONPOOLING is enabled, this setting determines the amount of time a connection remains idle in the connection pool.
This setting is in milliseconds and is valid only when CONNECTIONPOOLING is enabled.
Default - CONNECTIONPOOLINGTIMEOUT = 600000 (10 minutes).
Note:
When using Connection Pooling with Adabas, this timeout value must be smaller than any of the Adabas inactivity and ET timeout values, otherwise pooled connections could be timed out by Adabas and become invalid.
CONNECTPORT
Specify a default port number to use when communicating to the CONNX server component.
This setting maybe affected by CNXRUNPORT.
Note:
We recommend that you do not change the default value.
Default - The default port is 6500. If you wish to change it, enter CONNECTPORT = <new port number>.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CONNECTPORT
Unix Registry Setting: CONNX.CONNECTPORT
CONNECTRETURNPORT
When CNXCONNECTBACK is enabled, this setting specifies the port number that will be reserved on the client and that the server component will use to connect back to the client.
This option applies when CONNX makes TCP/IP connections to a CONNX Listener on a remote server (for example when connecting to VSAM files on a IBM Mainframe, or a RMS file on a VMS Server, or C-ISAM files on a UNIX server). CONNX initiates a connection to a listener, sends some connection information, and then disconnects. The listener starts a new server process, and the server connects back to the client PC on a specified port.
This option controls the port that is used during that connect back process. If this option is zero (default), or not present, CONNX chooses the next available port on the client PC. If a port number is specified, then CONNX first attempts to use that port. If the port is unavailable, CONNX increments the port number until it finds an available port.
Default - CONNECTRETURNPORT = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CONNECTRETURNPORT
Unix Registry Setting: CONNECTRETURNPORT
CONNECTTIMEOUT
This setting determines how long in milliseconds the CONNX client waits for a connection from a server.
Default - CONNECTTIMEOUT = 30000 (30 seconds)
Note:
The option applies to TCP/IP connections only. The value gives the number of milliseconds CONNX waits for a connection to complete before timing out.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CONNECTTIMEOUT
Unix Registry Setting: CONNECTTIMEOUT
CONNECTTRIES
This setting determines how many times the CONNX client attempts to connect to a host server before returning a failure on connection request.
Default - CONNECTTRIES = 2
Note:
The option applies to only to TCP/IP connections. One common cause of "Connection refused" is that the listener process has a backlog of connection requests.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CONNECTTRIES
Unix Registry Setting: CONNECTTRIES
CONNXENTERPRISESERVER
This setting is used by the CONNX Installation utility and does not need to be edited. It specifies whether the Enterprise Service was selected during the last installation.
CONNXREG_DISPLAY_OPTS
If set to 1, this settings makes it so the current AdabasSQLRegistry key/value pairs output is displayed on a single line.
On Unix systems, this allows you to use UNIX tools to operate on the data.
Default - CONNXREG_DISPLAY_OPTS = 0 (the key/value pairs output is displayed on multiple lines)
Environments - Client, Windows, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = CONNXREG_DISPLAY_OPTS
Unix Environment Variable: CONNXREG_DISPLAY_OPTS
CONNXSTORESERVER
This setting is used by the CONNX Installation utility and does not need to be edited. It specifies whether CONNXStore was selected during the last installation.
CONTINUEONGPF
If set to the default value of 1, CONNX continues to process queries even when it encounters an error.
Default - CONTINUEONGPF = 1
Environments - Client, Windows CONNX
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = CONTINUEONGPF