"N" to "P" Configuration Settings
NLS_LANG
This Unix-only language setting is for Oracle access.
Please consult your Oracle documentation for information regarding specific valid values for your operating system.
Environments - Client
Unix Environment Variable: NLS_LANG
NOLOGO
If set to 1, this turns of the CONNX.AVI file.
Default - NOLOGO = 0
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = NOLOGO
NOPROCEDURES
If set to 1, this setting disables the import of stored procedures.
Default - NOPROCEDURES = 0 (import stored procedures)
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = NOPROCEDURES
NOVIEWS
If set to 1, this setting disables the import of views.
Default - NOVIEWS = 0 (import views)
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = NOVIEWS
NOWAIT
If set to 1, this setting makes CONNX add the "NO WAIT" clause to the end of the oracle SELECT … FOR UPDATE command.
Default - NOWAIT = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX\ORACLE; Key Value/Value Name = NOWAIT
Unix Registry Setting: CONNX.ORACLE.NOWAIT
NUMBERCONVERT
For either Oracle or PostgreSQL, add the following registry entry to store fractional numbers in a number field:
NUMBERCONVERT = 1
Environments - Client, Windows
For Oracle:
Configuration Manager: CONNX Settings; Current Key = CONNX\ORACLE; Key Value/Value Name = NUMBERCONVERT
Unix Registry Setting: CONNX.ORACLE.NUMBERCONVERT
For PostgreSQL:
Configuration Manager: CONNX Settings; Current Key = CONNX\POSTGRESQL; Key Value/Value Name = NUMBERCONVERT
Unix Registry Setting: CONNX.POSTGRESQL.NUMBERCONVERT
OLEDB
This setting is used by the CONNX Installation utility and does not need to be edited. It specifies whether the OLEDB Desktop Adapter was selected during the last installation.
OLEDBE
This setting is used by the CONNX Installation utility and does not need to be edited. It specifies whether the OLEDB Enterprise Adapter was selected during the last installation.
OLEINIT
This setting controls how CONNX initializes the OLE Subsystem. Based on what it finds in OLEINT, CONNX initializes the OLE Subsystem as either Apartment-Threaded or Multi-Threaded.
Apartment-threading, while allowing for multiple threads of execution, serializes all incoming calls by requiring that calls to methods of objects created by this thread always run on the same thread - the apartment/thread that created them.
Multi-threading (also called free-threading) allows calls to methods of objects created by this thread to be run on any thread. There is no serialization of calls - many calls may occur to the same method or to the same object or simultaneously. Multi-threaded object concurrency offers the highest performance and takes the best advantage of multi-processor hardware for cross-thread, cross-process, and cross-machine calling, since calls to objects are not serialized in any way.
We recommend to set OLEINIT = 0 (Multi-Threaded). This allows the most flexibility and provides the best performance for multi-threaded applications. However, some OLEDB Providers may required their OLE Subsystem to be initialized as Apartment-Threaded. If this is necessary, set OLEINIT = 2.

0 | CONNX initializes the OLE Subsystem as Apartment-Threaded.
2 | CONNX initializes the OLE Subsystem as Multi-Threaded.

Default - OLEINIT = 0
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = OLEINIT
OLDERVERSION
Not for typical customer usage. Please only set if instructed to by CONNX Technical Support.
OPATTRIBUTES
OPATTRIBUTES instructs Adabas SQL Gateway to pass a specific attribute string to Adabas on the OP (open) call. Usage:
OPATTRIBUTES = <OP attribute string>
For example, to set the time zone on the OP call using the TZ attribute to 'America/Vancouver', set the setting value to the following:
OPATTRIBUTES = TZ='America/Vancouver'
This will cause Adabas SQL Gateway to pass the string TZ='America/Vancouver' as an attribute on the OP call.
Note:
For the Mainframe, if the the OP attribute string contains an equal sign (=), the equal sign should be replaced with a comma (,) in the CNXPARMS file. Here is an example: =OPATTRIBUTES=TZ,'America/Vancouver'
Default - not set.
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPATTRIBUTES
Unix Environment Variable: OPATTRIBUTES
Started Task: OPATTRIBUTES
CICS: OPATTRIBUTES
OPDONTCALL
If set to 1, this setting instructs Adabas SQL Gateway to bypass the Open User Session call when a client-server connection is established.
Default - OPDONTCALL = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPDONTCALL
Unix Environment Variable: OPDONTCALL
Started Task: OPDONTCALL
CICS: OPDONTCALL
OPEXF
If set to 1, this setting instructs Adabas SQL Gateway to issue the OP command with the EXF option. The EXF option makes it so files are opened under exclusive control of the user. No other user will be permitted to access the file while this user session is active. Exclusive control will be given only if no other active user has issued an OP command in which the ACC, EXF, EXU or UPD parameter was specified for the file.
Default - OPEXF = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPEXF
Unix Environment Variable: OPEXF
Started Task: OPEXF
CICS: OPEXF
OPEXU
If set to 1, this setting instructs Adabas SQL Gateway to issue the OP command with the EXU option. The EXU option makes it so files are updated under exclusive control of the user. No other user will be permitted to update the file while this user session is active. Exclusive control will be given only if no other active user has issued an OP command in which the ACC, EXF, EXU or UPD parameter was specified for the file.
Default - OPEXF = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPEXU
Unix Environment Variable: OPEXU
Started Task: OPEXU
CICS: OPEXU
OPMAXCMDID
If set to more than 0, this setting defines the maximum number of command IDs per Open User Session that can be active for a user at the same time.
This value cannot be greater than 1/240 * LQ, where LQ is the ADARUN sequential command table length parameter value, which has a default of 10000.
Default - OPMAXCMDID = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPMAXCMDID
Unix Environment Variable: OPMAXCMDID
Started Task: OPMAXCMDID
CICS: OPMAXCMDID
OPMAXHOLD
If set to more than 0, this setting defines the maximum number of records per Open User Session that a user can have in hold status at the same time. The default is the value set by the ADARUN NISNHQ parameter, and the maximum is 1/4 the value set by the ADARUN NH parameter minus 1, or 65535, whichever is smaller.
Default - OPMAXHOLD = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPMAXHOLD
Unix Environment Variable: OPMAXHOLD
Started Task: OPMAXHOLD
CICS: OPMAXHOLD
OPMAXISN
If set to more than 0, this setting defines the maximum number of ISNs per Open User Session that can be stored in the internal ISN element table resulting from the execution of an Sx command. Increasing the default setting decreases access to the Adabas Work dataset. The maximum allowed is 1000.
Default - OPMAXISN = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPMAXISN
Unix Environment Variable: OPMAXISN
Started Task: OPMAXISN
CICS: OPMAXISN
OPNONACTIVITY
For Adabas, this setting determines the non activity timeout for adabas calls.
Default - OPNONACTIVITY = 65535
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPNONACTIVITY
Unix Environment Variable: OPNONACTIVITY
Started Task: OPNONACTIVITY
CICS: OPNONACTIVITY
OPREADONLY
If set to 1, this setting instructs the Adabas SQL Gateway Open User Session logic to request an access-only user session. Read-only users can not issue hold, update, delete, add record, ET (End Trasaction), or BT (Backout Transaction) commands.
Default - OPREADONLY = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPREADONLY
Unix Environment Variable: OPREADONLY
Started Task: OPREADONLY
CICS: OPREADONLY
OPSEARCHTIME
If set to more than 0, this setting defines the maximum amount of time in milliseconds permitted for the execution of an Sx command per Open User Session.
Default - OPSEARCHTIME = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPSEARCHTIME
Unix Environment Variable: OPSEARCHTIME
Started Task: OPSEARCHTIME
CICS: OPSEARCHTIME
OPTIMEOUT
For Adabas, if set to more than 0, this setting provides a user-specific transaction time limit in milliseconds for the Open User Session call. The limit must conform to the maximum specified by the ADARUN parameter MXTT. If this field contains binary zeros, the transaction time limit specified by the ADARUN TT parameter for the Adabas session is in effect.
Default - OPTIMEOUT = 0
Environments - Client, Server,Windows, Mainframe, Unix, Adabas
Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = OPTIMEOUT
Unix Environment Variable: OPTIMEOUT
Started Task: OPTIMEOUT
CICS: OPTIMEOUT
ORACLEBULKMODEDISABLEDFLAG
Set this to 1 to indicate that Oracle does not use Bulk mode.
Default - ORACLEBULKMODEDISABLEDFLAG = 0
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = ORACLEBULKMODEDISABLEDFLAG
Unix Registry Setting: CONNX.ORACLEBULKMODEDISABLEDFLAG
ORACLE_HOME
This Unix-only setting contains the location of both the Oracle client libraries and the tnsnames.ora file.
This is usually set to $CNXDIR/lib32, where CNXDIR is the location of the CONNX Client install for UNIX.
Environments - Client
Unix Environment Variable: ORACLE_HOME
PACKETSIZE
This setting defines the size of the message buffer between the CONNX32.dll file and the database servers. Acceptable values are 4096 to 32000.
Default - PACKETSIZE = 8192
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = PACKETSIZE
Unix Registry Setting: CONNX.PACKETSIZE
PARALLELDATABASECOUNT
CONNX supports the ability to logically combine multiple identically structured Adabas databases and allow them to look and act like a single database. This number represents the number of parallel databases in addition to the main current database.
Default - PARALLELDATABASECOUNT = 0
This is a server setting and only affects Adabas. On Windows, this setting is set in the configuration manager under the CONNX\Adabas key. In Linux/Unix, PARALLELDATABASECOUNT is an environment variable.
PARALLELDBID
PARALLELDBID is used in conjunction with PARALLELDATABASECOUNT. This value assigns a number from 001 to 999 to each parallel Adabas database ID being used.
Usage: PARALLELDBIDnnn=DBID where nnn is a number from 001 to 999.
This is a server setting and only affects Adabas. On Windows, this setting is set in the configuration manager under the CONNX\Adabas key. In Linux/Unix, PARALLELDBID is an environment variable.
Example: If database IDs 134 and 135 are used as parallel databases, two environment variables are defined: PARALLELDBID001=134 PARALLELDBID002=135.
PARALLELQUARTEROFFSET
CONNX supports the ability to logically combine multiple identically structured Adabas databases and allow them to look and act like a single database. In the situation where data is physically stored in files separated by quarters (FY 22 Q1, FY 22 Q2, etc), this number represents the number of file numbers to advance for the next quarter.
Default - PARALLELQUARTEROFFSET = 0
This is a server setting and only affects Adabas. On Windows, this setting is set in the configuration manager under the CONNX\Adabas key. In Linux/Unix, PARALLELQUARTEROFFSET is an environment variable.
PEEKMESSAGE
If set to 1, this setting causes CONNX to issue PeekMessage commands while waiting for TCP/IP commands to asynchronously complete. This setting is required only by some non-Microsoft TCP/IP stacks and is only revelant to them.
Default - PEEKMESSAGE = 0
Environments - Client, Windows
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = PEEKMESSAGE
PERFORMRANGECHECKS
If set to 1, range checks are performed on the data fields that are used during inserts and updates.
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = PERFORMRANGECHECKS
Unix Registry Setting: CONNX.PERFORMRANGECHECKS
PORT
Use this setting to change the default CONNX JDBC server port.
Default - PORT = 7500
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = JDBC; Key Value/Value Name = PORT
Unix Configuration Setting: JDBC.PORT
PRECISIONOVERRIDE
If set to 1, this setting enables you to override the default SQL precision in the CONNX Data Dictionary for packed fields.
Default - PRECISIONOVERRIDE = 0 (override turned off)
Environments - Client, Windows, Unix
Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = PrecisionOverride
Unix Registry Setting: CONNX.PRECISIOVERRIDE