CONNX Data Integration Suite 14.8.0 | Administration Guide | CONNX Configuration Settings | CONNX Configuration Settings Reference | "A" to "B" Configuration Settings
 
"A" to "B" Configuration Settings
ADA_DEBUG_TRACE_MASK
Specifies which Adabas information is displayed in the debug trace output.
1
Display the hexadecimal dump of the control buffer after each Adabas call.
2
Display the hexadecimal dump of the format buffer for each Adabas call.
4
Display the hexadecimal dump of the record buffer for each Adabas call.
8
Display the hexadecimal dump of the search buffer for each Adabas call.
16
Display the hexadecimal dump of the value buffer for each Adabas call.
32
Display the hexadecimal dump of the ISN buffer for each Adabas call.
64
Display the hexadecimal dump of the control buffer prior to each Adabas call.
128
Display the hexadecimal dump of the control buffer prior to each Adabas call - only if there is an error. The value of DEBUG must be set to 0 when using this setting.
Default - ADA_DEBUG_TRACE_MASK = 127
CAUTION: 
Enabling one or more of these debug bitmap trace settings can produce voluminous output. Only do so if requested by tech support.
Examples
ADA_DEBUG_TRACE_MASK = 1
Display only the hexadecimal dump of the control buffer after each Adabas call.
ADA_DEBUG_TRACE_MASK = 3
Display the hexadecimal dumps of the control and format buffers after each Adabas call.
ADA_DEBUG_TRACE_MASK = 7
Display the hexadecimal dumps of the control, format, and record buffers after each Adabas call.
ADA_DEBUG_TRACE_MASK = 15
Display the hexadecimal dumps of the control, format, record, and search buffers after each Adabas call.
ADA_DEBUG_TRACE_MASK = 31
Display the hexadecimal dumps of the control, format, record, search, and value buffers after each Adabas call.
ADA_DEBUG_TRACE_MASK = 63
Display the hexadecimal dumps of the control, format, and record buffers after each Adabas call.
ADA_DEBUG_TRACE_MASK = 127
Display the hexadecimal dumps the control, format, record, search, value, and ISN buffers before and after each Adabas call.
*Environments - Client, Server, Windows, Mainframe, Unix, Adabas.
*Configuration Manager - CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_DEBUG_TRACE_MASK
*Unix Environment Variable - ADA_DEBUG_TRACE_MASK
*Started Task - ADA_DEBUG_TRACE_MASK
*CICS - ADA_DEBUG_TRACE_MASK
ADA_FIELDNULLASZERO
Enables Alpha fields filled with binary 0's, to be treated as a SQL Null field.
Natural programs sometimes will fill alpha fields with binary 0's if they are unused. If the table is to be replicated with Adabas Event Replicator for LUW, or using SQL ("insert/select"), this will cause binary 0 filled text fields to be converted to a space padded null text fields for the target table. This potentially means that records might not be available when using a superdescriptor, if there was a case where a zero filled field turned into a space padded field. This is due to Adabas not being able to access a record if any of the superdescriptor fields are blank.
Therefore, for Replication customers, we recommend to set this field to 0.
Default - ADA_FIELDNULLASZERO = 1
*Environments - Client, Server, Windows, Mainframe, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_FIELDNULLASZERO
ADA_ISNNAME
Enables the old naming convention of ISN_<DBID>_<FILEID> instead of ISN_<TableName>.
0
Use ISN_<DBID>_<FILEID> (where DBID is the Adabas database number and FILEID is the Adabas file number)
1
Use ISN_<TableName> (where TableName is the Logical Table Name)
Default - ADA_ISNNAME = 1
*Environments - Client, Windows, Adabas, CDD.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_ISNNAME
ADA_LOCKDONTWAIT
Modifies the outcome when a query tries to issue a Hold Lock on a locked record.
0
The query will wait until the record is released.
1
The query will generate a 145 nucleus error.
Default - ADA_LOCKDONTWAIT = 0
*Environments - Client, Server, Windows, Mainframe, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_LOCKDONTWAIT
*Unix Environment Variable: ADA_LOCKDONTWAIT
*Started Task: ADA_LOCKDONTWAIT
*CICS: ADA_LOCKDONTWAIT
ADA_NATURALBYTEASBIT
If you will be importing Natural Logicals, and desire that the logical fields be treated as a Bit field instead of Byte Field, set the following value:
ADA_NATURALBYTEASBIT = 1
If this value is set, CONNX will treat Natural DDM fields that are logical as Bit fields instead of Byte Fields. This is only used by the Import Tool when using Natural Imports, and thus only needs to be set on Windows.
Default - ADA_NATURALBYTEASBIT = 0
*Environments - Windows, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_NATURALBYTEASBIT
ADA_NOQUALIFYBINARY
If you will be manually switching a data type (such as alphanumeric) to binary, set the following value:
ADA_NOQUALIFYBINARY = 1
If this value is set, CONNX will not do extra qualification on Binary Fields. If it is not set (value of 0), CONNX may (depending on data type) fully qualify the format buffer for any given field.
This value is ignored when using Entire Net-work. In this case, binary fields are always fully qualified.
CAUTION: 
We do not recommend manually switching data types.
Default - ADA_NOQUALIFYBINARY = 1
*Environments - Server, Windows, Mainframe, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_NOQUALIFYBINARY
*Unix Environment Variable: ADA_NOQUALIFYBINARY
*Started Task: ADA_NOQUALIFYBINARY
*CICS: ADA_NOQUALIFYBINARY
ADA_RESPECT_ISN_ON_INSERT
For Adabas, if this setting is enabled, if an ISN is supplied during an insert statement, the ISN will be treated as a "user isn" and passed to adabas, otherwise an auto-assigned ISN will be requested from adabas.
Default - ADA_RESPECT_ISN_ON_INSERT = 1
*Environments - Client, Server, Windows, Mainframe, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_RESPECT_ISN_ON_INSERT
*Unix Environment Variable: ADA_RESPECT_ISN_ON_INSERT
*Started Task: ADA_RESPECT_ISN_ON_INSERT
*CICS: ADA_RESPECT_ISN_ON_INSERT
ADA_SECURITY
For Adabas, if this setting is enabled, the user id and password defined in the CDD will be passed to Adabas for authentication. If Adabas is also configured for SSX authentication, the user id and password will be authenticated by the database. If either the user id or password is incorrect, the Adabas nucleus will return nucleus response code 200. If the database is configured for SSX authentication and ADA_SECURITY is not set to one in the CONNX server, the Adabas nucleus will return a response code 200 regardless of the user id and password stored in the CDD.
Note: 
This setting applies to only to Linux, Unix, and Windows.
Default - ADA_SECURITY = 0
*Environments - Server, Windows, Linux, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_SECURITY
*Unix Environment Variable: ADA_SECURITY
ADA_TABLENAME
Specify Root Tables and Flattened Tables extensions.
0
Put a _ROOT extension on the Root table and do not put any extension on the Flat table.
1
Do not put any extensions on any of the Tables. Do not store the Flat table in the CDD.
2
Put a _FLAT extension on the Flat table and do not put any extension on the ROOT Table.
Default - ADA_TABLENAME = 1
*Environments - Client, Windows, Adabas, CDD.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_TABLENAME
ADA_WAITTIME
For Adabas, the number of seconds to wait for a locked record.
Default - ADA_WAITTIME = 0
*Environments - Client, Server, Windows, Mainframe, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_WAITTIME
*Unix Environment Variable: ADA_WAITTIME
*Started Task: ADA_WAITTIME
*CICS: ADA_WAITTIME
ADA_WFIELDASBYTES
If set, this will honor the length of a field that is an ADABAS W Field. If the W field is defined to be 8 Bytes, then CONNX will register it as 8 bytes. The default is to multiply W fields by 2 to allow for more potential storage in the case they represent languages that use 2 or more bytes per character (example Chinese). This is invoked when CREATE TABLE DESCRIPTION or CREATE TABLE is done using NCHAR fields. An example would be:
CREATE TABLE DESCRIPTION L7000 DATABASE NUMBER 2 FILE NUMBER 55
(
ADA_ISN SEQNO(0) NOT NULL,
AA nchar (8) SHORTNAME 'AA'
);
In this example, AA would be represented as 8 Bytes in the CONNX CDD if ADA_WFIELDASBYTES is set to 1, or it will be 16 bytes (Default) if the Setting is not set, or is set to 0.
Default - ADA_WFIELDASBYTES = 0
*Environments - Client, Windows, Unix, Adabas.
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = ADA_WFIELDASBYTES
ALLOWDATATYPECHANGES
Enables the modification of data types in tables for which CONNX does not normally allow modifications.
Default - ALLOWDATATYPECHANGES = 0 (disabled).
To enable, set it to 1.
*Environments - Client, Windows, CDD.
*Configuration Manager: CDD Settings; Current Key = CONNXCDD; Key Value/Value Name = ALLOWDATATYPECHANGES
ALLOWMIXEDCASEPASSWORDS
This controls the use of mixed-case passwords during VMS logon procedures. If you set it to 1, any combination of uppercase and lowercase characters can be used to log on to VMS databases.
Default - AllowMixedCasePasswords = 0
*Environments - Client, Windows, Unix.
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ALLOWMIXEDCASEPASSWORDS
*Unix Registry Setting: CONNX.ALLOWMIXEDCASEPASSWORDS
ALLOWMIXEDPWD
If set to 1, this enables the use of mixed-case passwords on zOS 1.7 and higher. zOS 1.7 and higher allows passwords to be upper case, mixed case, or mixed number. If the system is configured to use mixed case or mixed number passwords, the ALLOWMIXEDPWD confguration parameter must be set in the CONNX CNXPARMS file on the server.
Default - ALLOWMIXEDPWD = 1 (mixed-case passwords on zOS 1.7 or higher are enabled)
*Environments - Server, zOS only
*Configuration: CNXPARMS Settings; ALLOWMIXEDPWD=<0,1>
ALLOWNULLINCHAR
If set to 1, this setting enables a binary zero to be embedded in CHAR fields. Usually, zero is used as a null terminator. Enabling this setting will degrade performance.
Default - ALLOWNULLINCHAR = 0
*Environments - Client, Windows CONNX
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ALLOWNULLINCHAR
ALLOWTRAILINGSPACEINVARCHAR
If set to 1, this setting enables a non ANSI standard behavior to allow VARCHAR fields to contain trailing spaces.
Default - ALLOWTRAILINGSPACEINVARCHAR = 0
*Environments - Client, Windows CONNX
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ALLOWTRAILINGSPACEINVARCHAR
ANSITOOEM
If this setting is not set to 0 or 2, when CONNX writes a string, it translates the string from the OEM-defined character set into either an ANSI or a wide-character string. When reading a string, CONNX translates it from either an ANSI or a wide-character string to OEM-defined character set.
Default - ANSITOOEM = 2
*Environments - Client, Windows CONNX
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ANSITOOEM
ASYNCACCESS
If set to 1, this setting forces CONNX to run queries asynchronously.
You may also remove the ASYNCACCESS value to restore synchronously run queries.
Default - ASYNCACCESS = 0
*Environments - Client, Windows, UNIX
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ASYNCACCESS
*Unix Registry Setting: CONNX.ASYNCACCESS
AUDIT
Enables Auditing for Adabas SQL Gateway.
When auditing is enabled, any query access against one of the configured audit files will result in an audit record being generated and placed into the audit table.
If auditing is enabled, the following configuration settings should also be configured:
* AUDITDBID - the Adabas Database ID that contains the audit file.
* AUDITFILEID - the file number of the audit file.
* AUDITFILECOUNT - the number of files to be audited.
* AUDITFILTER### - where ### is 001 through 999 - the filter specification that will identify which adabas file to be audited, along with the optional key field.
* AUDITFORMAT - the audit file format.
* AUDITPASSWORD - the ADASCR password for writing data to the audit file.
Default - AUDIT = 0
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDIT
*Unix Environment Variable: AUDIT
*VMS Logical: AUDIT
*Started Task: AUDIT
*CICS: AUDIT
AUDITDBID
Specifies the audit file database ID when auditing is enabled for Adabas SQL Gateway.
Default - AUDITDBID = 0
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDITDBID
*Unix Environment Variable: AUDITDBID
*VMS Logical: AUDITDBID
*Started Task: AUDITDBID
*CICS: AUDITDBID
AUDITFILEID
Specifies the audit file ID when auditing is enabled for Adabas SQL Gateway.
Default - AUDITFILEID = 0
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDITFILEID
*Unix Environment Variable: AUDITFILEID
*VMS Logical: AUDITFILEID
*Started Task: AUDITFILEID
*CICS: AUDITFILEID
AUDITFILECOUNT
Specifies the number of adabas audit filters (the number of files to be audited) when auditing is enabled for Adabas SQL Gateway.
Default - AUDITFILECOUNT = 0
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDITFILECOUNT
*Unix Environment Variable: AUDITFILECOUNT
*VMS Logical: AUDITFILECOUNT
*Started Task: AUDITFILECOUNT
*CICS: AUDITFILECOUNT
AUDITFILTER###
Specifies an Adabas file that will trigger auditing when read, and when Auditing is enabled for Adabas SQL Gateway.
### is a number between 000 and 999.
The format of the audit filter is as follows:
<database ID of file you want to audit>, <file id of the file you want to audit>,<key field to be placed in audit table>, <length of key field>, <data type of key field>
The key field must be converted to text 'A' Format. Here are some examples:
AUDITFILTER001
= 1,11,AA,8,A
AUDITFILTER002
= 1,14,AC,10,A
AUDITFILTER003
= 2,31,AG,20,A
Default - AUDITFILTER### = 0
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDITFILTER###
*Unix Environment Variable: AUDITFILTER###
*VMS Logical: AUDITFILTER###
*Started Task: AUDITFILTER###
*CICS: AUDITFILTER###
AUDITFORMAT
Specifies the audit file format when auditing is enabled for Adabas SQL Gateway.
If AUDITFORMAT is zero (the default value) then the audit file must have the following structure:
*AA - 7,P - Natural timestamp - the time of the audit event.
*AB - 8.A - UserID - the user identifier.
*AC - 4,F - The database number for the table that triggered the audit record.
*AD - 4,F - The file number for the table that triggered the audit record.
*AE - 4,F - The ISN of the record that triggered the audit.
*AF - 100,A - The optional key field from the record that triggered the audit.
This audit file can be created using the following SQL statement:
create table AuditFile( AuditTime timestamp NOT NULL,
Userid char(8) NOT NULL,
databasenumber integer NOT NULL,
filenumber integer NOT NULL,
ISN integer NOT NULL,
keyfield varchar(100) NOT NULL)
If the AUDITFORMAT is 1, then the audit file contains a periodic group and must have the following structure:
*1,AA - 7,P - Natural timestamp - the time of the audit event.
*1,AB - 8.A - UserID - the user identifier.
*1,AC - 4,F - The database number for the table that triggered the audit record.
*1,AD - 4,F - The file number for the table that triggered the audit record.
*1,AE, PE - Periodic group use for audit performance.
*2,AF - 4,F - The ISN of the record that triggered the audit.
*2,AG - 100,A - The optional key field from the record that triggered the audit.
This audit file can be created using the following SQL statement:
Create cluster description adalocal.auditfilenewcluster
FILE NUMBER <your adabas file number> (
create table AuditFileNew(
internalisn seqno(0) not null,
AuditTime timestamp shortname 'AA' NOT NULL ,
Userid shortname 'AB' NOT NULL,
databasenumber integer NOT NULL shortname 'AC',
filenumber integer NOT NULL shortname 'AD',
primary key (internalisn)),
create table AuditFileNewValueData(
internalisn seqno(0) not null,
COL_SEQNO_1 SEQNO(1) NOT NULL,
ISN shortname 'AF' NOT NULL,
keyfield varchar(100) NOT NULL shortname 'AG',
foreign key (internalisn) references AuditFileNew,
primary key (internalisn, COL_SEQNO_1))
)
AUDITFORMAT = 0 results in a single adabas record for each audit record, which is a simpler format, easier to read, but results in slower performance.
AUDITFORMAT = 1 will store multiple audit records in the periodic group element of a single adabas record. This results in much better performance, but can make the data a little more difficult to read.
Default - AUDITFORMAT = 0.
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDITFORMAT
*Unix Environment Variable: AUDITFORMAT
*VMS Logical: AUDITFORMAT
*Started Task: AUDITFORMAT
*CICS: AUDITFORMAT
AUDITPASSWORD
Specifies the write access ADASCR password for the audit file when auditing is enabled for Adabas SQL Gateway.
AUDITPASSWORD = ######
Default - AUDITPASSWORD = 0
*Environments - Server
*Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name = AUDITPASSWORD
*Unix Environment Variable: AUDITPASSWORD
*VMS Logical: AUDITPASSWORD
*Started Task: AUDITPASSWORD
*CICS: AUDITPASSWORD
AUTOBULKINSERT
If set to 1, this setting will cause all Insert statements to be cached and sent in batch every 1000 records (by default), controlled by BULKOPERATIONCOUNT.
When a statement handle is freed or dropped, all remaining cached rows will be inserted using the bulk operation interface applicable to the database.
Default - AUTOBULKINSERT = 1
*Environments - Client, Windows CONNX
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = AUTOBULKINSERT
AUTOCONVERTFORLIKE
If set to 1, this setting enables any type of non-character data (such as Numeric, Float, Integer, Timestamp, etc.) to be treated as a string for SQL LIKE queries.
Default = AUTOCONVERTFORLIKE = 0
*Environments - Client, Windows CDD
*Configuration Manager: CDD Settings; Current Key = CONNXCDD; Key Value/Value Name = AUTOCONVERTFORLIKE
BASE1INDEX
If BASE1INDEX = 1, then the cnxarraycolumn or SEQNO fields will begin with 1, instead of 0 and the first occurrence of a MU, PE, or MUPE field will display 1 in the cnxarraycolumn or SEQNO field.
Default - BASE1INDEX = 0
*Environments - Client, Windows, UNIX, Adabas
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = BASE1INDEX
*Unix Registry Setting: CONNX.BASE1INDEX
BULKOPERATIONCOUNT
This setting determines the number of rows to process in batch when performing bulk operations, such as bulk insert.
Default - BULKOPERATIONCOUNT = 1000
*Environments - Client, Windows CONNX
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = BULKOPERATIONCOUNT