"T" to "Y" Configuration Settings
TABLECACHE
By default, CONNX keeps logical links open to any table/file that is accessed during the lifetime of a connection. For flat file data sources, such as RMS, VSAM, C-ISAM, DISAM, Micro Focus, Dataflex, and PowerFlex, this setting controls how CONNX opens and closes the underlying data file. This setting has very little impact for relational databases (DB2, Oracle, SQL Server), because relational databases do not need to be "opened".

0 | CONNX opens the file in the appropriate access mode when necessary, and closes the file as soon as it is no longer needed.
1 | The first time a query is executed that accesses a table in a given mode (either read only, or read/write), CONNX opens that file in the specified mode, and keeps the file open for the duration of the connection.
2 | Same as 1 for backward compatibility.

Default - TABLECACHE = 2
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = TABLECACHE
Unix Registry Setting: CONNX.TABLECACHE
TCPIP
This setting is used by the CONNX Installation utility and does not need to be edited. It specifies whether TCP/IP was selected during the last installation.
TCPIPDEBUG
If set to 1, this turns on the TCP/IP Debug Messages.
Default - TCPIPDEBUG = 0
Note:
Unless you are debugging, Software AG recommends that you use the default setting.
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = TCPIPDEBUG
TCPSIZE
This setting determines the size of the CONNX JDBC Server TCP/IP packets. Valid values are 4096 to 32000
Default - TCPSIZE = 8192
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = JDBC; Key Value/Value Name = TCPSIZE
Unix Registry Setting: JDBC.TCPSIZE
TEMPPATH
This setting determines where CONNX stores the temporary directory files created during query processing. Usage:
TEMPPATH = directory
Defaults:
Windows - The directory indicated by the TEMP environment variable.
Unix - The CONNX isntall directory.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX ; Key Value/Value Name = TEMPPATH
Unix Registry Setting: CONNX .TEMPPATH
TEXTDBMS
This setting enables the dynamic compression/uncompression of specialized record layouts with variable length fields. Enabling this setting works in conjunction with the TextDBMS data type for variable length fields. Do not enable this setting unless instructed to do so by CONNX Technical Support.
Default - TEXTDBMS = 0
Environments - Server
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = TEXTDBMS
Unix Environment Variable: TEXTDBMS
VMS Logical: TEXTDBMS
Started Task: TEXTDBMS
CICS: TEXTDBMS
THROTTLECOUNT
The number of records to return before pausing for the THROTTLEDURATION.
Default - THROTTLECOUNT=0
Environments - Server
THROTTLEDURATION
The duration in milliseconds to pause after returning each batch of THROTTLECOUNT number of records.
Default - THROTTLEDURATION=0
Environments - Server
THROTTLESTARTHOUR
The start hour when throttling logic will be enabled to curtail CPU usage on the data server. If THROTTLECOUNT is 0, no throttling will take place.
Default - THROTTLESTARTHOUR=0
Environments - Server
THROTTLESTOPHOUR
The stop hour when throttling logic will be enabled to curtail CPU usage on the data server. If THROTTLECOUNT is 0, no throttling will take place.
Default - THROTTLESTOPHOUR=23
Environments - Server
TIMEOUT
This setting determines the CONNX TCP/IP timeout in milliseconds.
Default - TIMEOUT = 3600000 (1 hour)
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = TIMEOUT
Unix Registry Setting: CONNX.TIMEOUT
TWOPHASECOMMIT
If set to 1, this setting establishes two-phase commit when connecting to multiple Rdb databases located on the same physical VMS server.
Default - TWOPHASECOMMIT = 1
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX\RDB; Key Value/Value Name = TWOPHASECOMMIT
Unix Registry Setting: CONNX.RDB.TWOPHASECOMMIT
UPPERCASEONLY
If set to 1, this setting forces column and table names to appear in uppercase upon import.
Default - UPPERCASEONLY = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = UPPERCASEONLY
Unix Registry Setting: CONNXCDD.OPTIONS.UPPERCASEONLY
USE32KRECORDBUFFER
For Adabas on Open Systems (Linux, Unix and Windows), this setting forces the use of a 32K record buffer rather than the native 64K record buffer. This setting may be useful when connecting to an Adabas database that is running on a non Open Systems platform like zOS via Entire Net-work running on an Open Systems platform. In this situation, CONNX detects that it is running on an Open Systems platform and attempts to use a 64K record buffer which will create an error condition if the database itself does not support 64K record buffers. Setting USE32KRECORDBUFFER to a value of 1 will force CONNX to use a 32K record buffer.
Note:
Setting USE32KRECORDBUFFER to 1 will force the use of a 32K record buffer for all connections regardless of whether or not the connection is made to a non Open Systems platform.
Default - USE32KRECORDBUFFER = 0
Environments - Server, Windows, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = USE32KRECORDBUFFER
Unix Environment Variable: USE32KRECORDBUFFER
USECONNXSCHEMAFORNATIVE
This setting determines which schema CONNX uses when creating tables in relational databases, such as SQL Server, Oracle, DB2, Sybase, and Informix. If the current CONNX schema name does not exist in the database, the specified schema must be valid on the target database. Otherwise, an error can occur on the Create Table command.

0 | Relational database tables are created using the schema specified at import time.
1 | Relational database tables are created using the current CONNX schema.

Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = USECONNXSCHEMAFORNATIVE
Unix Configuration Setting: USECONNXSCHEMAFORNATIVE
USEDOUBLEFORNUMBER
If set to 1, this setting converts all Oracle Number (Numeric) data types to Double (instead of Decimal). This setting only applies to Oracle.
Default - USEDOUBLEFORNUMBER = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = USEDOUBLEFORNUMBER
Unix Registry Setting: CONNX.USEDOUBLEFORNUMBER
USEOLDADABASDECIMALDATATYPE
If set to 1, CONNX maps all Adabas Unpacked Numeric fields to DECIMAL rather than SQL Numeric. This setting only applies to Adabas.
In older versions of CONNX, the Adabas type Unpacked Numeric was mapped to decimal. In current versions, Adabas Unpacked Numeric is mapped to SQL Numeric. In most situations, this change in mapping will not affect the calling application.
Default - USEOLDADABASDECIMALDATATYPE = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = USEOLDADABASDECIMALDATATYPE
Unix Registry Setting: CONNX.USEOLDADABASDECIMALDATATYPE
USEREXITFLAGS
This flag will determine when the Adabas user exit (if defined) is called. Please see USEREXITNAME32 and USEREXITNAME64 for more information.
enum CNXUSEREXITFLAGS
{
CNX_USEREXIT_NONE = 0x00,
CNX_USEREXIT_PRECALL = 0x01,
CNX_USEREXIT_POSTCALL= 0x02
};

0 | Disabled
1 | The exit is called before every adabas call.
2 | The exit is called after every adabas call.
3 | The exit is called before and after every adabas call.

Default - USEREXITFLAGS = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX\ADABAS; Key Value/Value Name = USEREXITFLAGS
Unix Environment Variable : USEREXITFLAGS
USEREXITNAME32 and USEREXITNAME64
The 32 and 64 bit CONNX Data Server user exits are currently available only for Adabas and C-ISAM. Usage:
On Windows:
USEREXITNAME[32/64] = e:\mydir\myuserexit.dll
On Unix:
USEREXITNAME[32/64] = /home/mydir/myuserexit.sl
The specified load module must export a public "C" function called "UserExitFunc" with the following signature:
For Adabas:
int UserExitFunc(unsigned int threadid,
const char *userid,
const char * clientid,
void * AdabasControlBlock,
void * szFormatBuffer,
void * szRecordBuffer,
void *szSearchBuffer,
void *szValueBuffer,
void *szISNBuffer,
int nPrePost );
CONNX will call this exit either before, after, or both based on the value of the USEREXITFLAGS setting.
For C-ISAM:
enum CNXUSEREXITFLAGS
{
CNX_USEREXIT_NONE = 0x00,
CNX_USEREXIT_PRECALL = 0x01,
CNX_USEREXIT_POSTCALL= 0x02
};
enum CNXUSEROPERATIONS
{
CNX_USEREXIT_UPDATE = 0x01,
CNX_USEREXIT_DELETE = 0x02,
CNX_USEREXIT_INSERT = 0x04
};
int UserExitFunc(const char *userid,
const char* szFileName,
CNXUSEROPERATIONS nOperation,
CNXUSEREXITFLAGS flags,
const void * uniqueID,
const void * recordnumber,
const void * szRecord,
int nRecordLength);
For C-ISAM
CONNX will call this function in the following circumstances:
1. When a record is inserted, the function is called after the insert has been successful.
2. When a record is updated, the function is called twice, once before the update, once after the update.
3. When a record is deleted, the function is called once after the delete is successful
Sample exit for Adabas:
#include "stdafx.h"
#include <stdio.h>
#include <stdlib.h>
#pragma pack(1)
typedef struct _ADABASCONTROLBLOCK
{
char cb_cmd_res[2]; // Reserved
char cb_cmd_code[2]; // Command Code
char cb_cmd_id[4]; // COMMAND ID
#if defined (CNX_LITTLE_ENDIAN)
char cb_file_nr; // File#
char cb_db_id; // Database Number
#else
char cb_db_id; // Database Number
char cb_file_nr; // File#
#endif
//short cb_file_nr;
short cb_return_code;
int cb_isn;
int cb_isn_l1;
int cb_isn_quantity;
unsigned short cb_fmt_buf_lng;
unsigned short cb_rec_buf_lng;
unsigned short cb_sea_buf_lng;
unsigned short cb_val_buf_lng;
unsigned short cb_isn_buf_lng;
char cb_cop1;
char cb_cop2;
char cb_add1[8];
char cb_add2[4];
char cb_add3[8];
char cb_add4[8];
char cb_add5[8];
int cb_cmd_time;
char cb_user_area[4];
//
} ADABASCONTROLBLOCK;
#pragma pack()
// This is an example of an exported function.
extern "C" __declspec(dllexport) int UserExitFunc(unsigned int threadid, const char *userid, const char * clientid, void * AdabasControlBlock, void * szFormatBuffer, void * szRecordBuffer, void *szSearchBuffer, void *szValueBuffer, void *szISNBuffer, int nPrePost )
{
FILE * fp;
fp = fopen("c:\\adaexit.log", "a+");
if (fp)
{
ADABASCONTROLBLOCK * pBlock = (ADABASCONTROLBLOCK *)AdabasControlBlock;
fprintf(fp, "thread (%d), user(%s), clientid(%s), adabas command(%2.2s)\n", threadid, userid, clientid, pBlock->cb_cmd_code);
fclose(fp);
}
return 0;
}
Sample exit for CISAM:
#include "stdafx.h"
#include "stdio.h"
extern "C" __declspec(dllexport) int UserExitFunc(const char *userid, const char* szFileName, int nOperation, int flags, const void * uniqueID, const void * recordnumber, const void * szRecord, int nRecordLength)
{
FILE * fp;
fp = fopen("c:\\cisamexit.log", "a+");
if (fp)
{
fprintf(fp, "user(%s), filename(%s), operation(%d), flag(%d) record(%-*.*s)\n", userid, szFileName, nOperation, flags, nRecordLength, nRecordLength, szRecord);
fclose(fp);
}
return 0;
}
Default - blank.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX\ADABAS or CONNX\CISAM; Key Value/Value Name = USEREXITNAME[32/64]
Unix Environment Variable : USEREXITNAME[32/64]
USERID
The default userid that will populate the logon dialog when making a connection if no user is specified.
Environments - Client, Windows CONNX
Configuration Manager: CONNX Settings; Current Key = CONNX/Defaults; Key Value/Value Name = USERID
USESXCALL
For Adabas, when set to 0, this setting disables the use of search SX type adabas commands. This setting may be useful in preventing the overflow of adabas WORK area for large databases, but will result in slower performance if set to zero.
Default - USESXCALL = 1
Environments - Client, Server, Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = USESXCALL
Unix Environment Variable: USESXCALL
Started Task:USESXCALL
CICS: USESXCALL
VMSSERVERTYPE
This setting is used by the CONNX Installation utility and does not need to be edited. This specifies the type of VMS server selected during the install (VAX, Alpha, Itanium).
YEARWINDOW
Use this setting to configure the sliding date window for Year 2000 dates and help convert non-Y2K legacy date data. Usage:
YEARWINDOW=nn
Enter the desired year-window, where nn represents the dividing year between centuries.
Interpretation using the default value of 40 years:
Dates nn/nn/59 to nn/nn/99 are seen as 1959 to 1999.
Dates nn/nn/00 to nn/nn/58 are seen as 2000 to 2058.
This setting affects the data types shown in the following table:

CONNX Data Type | SQL Data Type | Length | Description
Text Date 2000 (YYMMDD) | DATE | 6 | Text Date in the specified format. Handles years 1941 to 2040.
Text Date 2000 (MMDDYY) | DATE | 6 | Text Date in the specified format. Handles years 1941 to 2040.
Text Date 2000 (DDMMYY) | DATE | 6 | Text Date in the specified format. Handles years 1941 to 2040.
Long Date 2000 (YYMMDD) | DATE | 6 | Long Date in the specified format. Handles years 1941 to 2040.
Long Date 2000 (MMDDYY) | DATE | 6 | Long Date in the specified format. Handles years 1941 to 2040.
Long Date 2000 (DDMMYY) | DATE | 6 | Long Date in the specified format. Handles years 1941 to 2040.
Packed Date 2000 (YYMMDD) | DATE | 4 | Packed Date in the specified format. Handles years 1941 to 2040.
Packed Date 2000 (MMDDYY) | DATE | 4 | Packed Date in the specified format. Handles years 1941 to 2040.
Packed Date 2000 (DDMMYY) | DATE | 4 | Packed Date in the specified format. Handles years 1941 to 2040.

Default - 40 years
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = YearWindow
Unix Registry Setting: CONNX.YEARWINDOW