CONNX Data Integration Suite 14.8.0 | Administration Guide | CONNX Configuration Settings | CONNX Configuration Settings Reference | "Q" to "S" Configuration Settings
 
"Q" to "S" Configuration Settings
QUADWORDDOUBLE
If set to 1, this setting makes it so QuadWord data types are imported as Double data types for Oracle Rdb.
Default - QUADWORDDOUBLE = 0 (the QuadWordDouble data type is disabled)
*Environments - Client, Windows, Unix, CDD
*Configuration Manager: CDD Settings; Current Key = CONNXCDD; Key Value/Value Name = QUADWORDDOUBLE
*Unix Registry Setting: CONNXCDD.QUADWORDDOUBLE
READTIMEOUT
This setting determines the value for the DB2 TCP/IP timeout in milliseconds .
Default - READTIMEOUT = 60000 (60 seconds)
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = READTIMEOUT
*Unix Registry Setting: CONNX.READTIMEOUT
REISSUEOP
The Adabas "OP" command will be re-issued in the event that during query operations it receives an Adabas response response 9 with a subcode of 2 or 3 (on mainframe) or subcode of (OR, or TN) on open systems. When this setting is set to 1, when a timeout is received, ACE will issue a new OP command and then retry the last operation.
Default - REISSUEOP = 0
*Environments - Client, Server,Windows, Mainframe, Unix, Adabas
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = REISSUEOP
*Unix Environment Variable: REISSUEOP
*Started Task: REISSUEOP
*CICS: REISSUEOP
REMOVELEADINGZEROS
This setting removes the leading zeroes from field names when importing files into a CDD using file descriptions that have "OCCURS" clauses, like COBOL copybooks, VMS DDL files, and etc.
0
The field name will be {FieldName_00001}.
1
The field name will be {FieldName_1}.
Default - REMOVELEADINGZEROS = 0
*Environments - Client, Windows
*Configuration Manager: CDD Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = REMOVELEADINGZEROS
REPLACEPREFIX
Use this setting to replace prefixes that are attached to COBOL FD imported fields. Usage:
REPLACEPREFIX = "prefix string"
Use REPLACEPREFIX in conjunction with IMPORTPREFIX to exchange the IMPORTPREFIX string with the REPLACEPREFIX string. If IMPORTPREFIX does not exist (or is ""), REPLACEPREFIX replaces the field name. For example:
If the field is "BBB_Customer" and:
1. IMPORTPREFIX does not exist
2. REPLACEPREFIX is "AAA_"
the field in the CDD would be "AAA_Customer".
*Environments - Client, Windows, Unix
*Configuration Manager: CDD Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = REPLACEPREFIX
*Unix Registry Setting: CONNXCDD.OPTIONS.REPLACEPREFIX
RESTDOMAIN
Optional. Sets the default Windows domain for the Online CONNX Suite. If you do not specify a value for this property, you must set the domain of your Windows user when you log on to the Online CONNX Suite, using the format domain\username.
By default the value is empty.
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 = RESTDOMAIN
RMSPADDEDNONULLS
This setting controls whether CONNX treats a field filled with binary zeros as NULL or as an empty string when converted to SQL. The default behavior is to read a field with all binary zeros as SQL NULL. Set this setting to 1 to read the field as an empty string.
Default - RMSPADDEDNONULLS = 0 (binary zeros are treated as a SQL NULL)
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX\RMS; Key Value/Value Name = RMSPADDEDNONULLS
*Unix Registry Setting: CONNX.RMS.RMSPADDEDNONULLS
SBCCSID
Use this setting to set a single-byte codepage. Usage:
SBCCSID = <code page>
Defaults:
Windows = Native Locale
Mainframe = 37 (EBCDIC)
Unix = 1252
*Environments - Client, Server, Windows, Unix, Mainframe
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = SBCCSID
*Unix Environment Variable: SBCCSID
*Started Task: SBCCSID
*CICS: SBCCSID
SCTLOGICAL
This settings defines the RMS file name path when importing files via the SCT COBOL FD files option. Usage:
SCTLOGICAL = logical
Example:
SCTLOGICAL = SI$CONNX
There is only one entry for this setting.
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNXCDD\OPTIONS; Key Value/Value Name = SCTLOGICAL
*Unix Registry Setting: CONNXCDD.OPTIONS.SCTLOGICAL
SETENABLED
This setting specifies whether or not a file will be set to enabled if it is in a disabled state under CICS. This setting applies only to CICS.
0
Files that are in a disabled state will not be enabled and an error will be returned.
1
Files will be enabled when accessed even if they were previously set to disabled.
Default - SETENABLED = 1
*Environments - Server
*CICS: SETENABLED
SETOPEN
This setting specifies whether or not a file will be set to open if it is in a closed state under CICS. This setting applies only to CICS.
0
Files that are in a closed state will not be opened and an error will be returned.
1
Files will be opened when accessed even if they were previously set to closed.
Default - SETOPEN = 1
*Environments - Server
*CICS: SETOPEN
SHARECONNECTIONCOUNT
This setting controls the number of logical connections mapped to a physical connection. Usage:
SHARECONNECTIONCOUNT = value
This setting is ignored if SHARECONNECTIONS = 0
Default - SHARECONNECTIONCOUNT = 5
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = SHARECONNECTIONCOUNT
*Unix Registry Setting: CONNX.SHARECONNECTIONCOUNT
SHARECONNECTIONS
This setting enables or disables connection sharing. This setting is affected by SHARECONNECTIONCOUNT.
0
Connection sharing is disabled. Each connection from a single computer gets a dedicated socket to a server. This consumes more server resources.
1
Connection sharing is enabled for all applications.
2
Connectiuon sharing is enabled, but 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
If more than one connection is made on the same computer, using the same user ID and password, CONNX makes a single physical connection to the server instead of creating multiple connections.
Default - SHARECONNECTIONS = 2
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = SHARECONNECTIONS
*Unix Registry Setting: CONNX.SHARECONNECTIONS
SISWORDCOUNT
The maximum expression length to send to the SIS expression optimizer.
Default - SISWORDCOUNT = 1000.
Under the main CONNX key.
This setting is for the client only.
SOCKETPAUSE
This setting determines the length of time in milliseconds that CONNX waits for the TCP/IP stack to initialize. This setting only applies to non-Microsoft TCP/IP stacks on the client computer.
Default - SOCKETPAUSE = 0
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = SOCKETPAUSE
*Unix Registry Setting: CONNX.SOCKETPAUSE
STRICTCONVERSIONRULES
Whenever possible, CONNX does an implicit data conversion when it encounters data that is not represented as the type required. For example, if a character field is being returned as a number, the value 'ABC123' will be automatically converted to 123. The value 'ABC' as a number however, has no meaning and a 0 will be returned.
In some situations, the preferred behavior would be to return an error rather than a 0. When set to 1, STRICTCONVERSIONRULES makes it so an error is returned when a conversion is not valid.
Default - STRICTCONVERSIONRULES = 0
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = STRICTCONVERSIONRULES
*Unix Registry Setting: CONNX.STRICTCONVERSIONRULES
STRICTNUMERICDATA
If set to a value of 1, the Text -> Integer and Signed Overpunch datatypes will return NULL if the data is not strictly numeric.
Default - STRICTNUMERICDATA = 0
Examples
If STRICTNUMERICDATA = 1, the value 1a34 returns NULL.
If STRICTNUMERICDATA = 0, the value 1a34 returns 0.
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = STRICTNUMERICDATA
*Unix Registry Setting: CONNX.STRICTNUMERICDATA
SUBQUERYROWESTIMATE
Use this setting to give CONNX a hint on how to report the query plan when {statistics} is used.
Some queries that have a sub query may use a less optimized query plan if the sub query returns more than one row. In this case, CONNX will automatically switch to the correct query plan at runtime, but the query plan reported by the {statistics} function may not be the same as the plan which was ultimately used. If you find that the query plan reported by {statistics} is different than what is being used at runtime due to multiple rows being returned in a sub query, set SUBQUERYROWESTIMATE to a value greater than 1.
The query plan will only change at run time if returning multiple rows in a sub query will return duplicate rows. For example, if an Adabas sub query uses a PE index and the sub query only returns 1 row, the PE index can be used. If the sub query returns multiple rows however, duplicates would be returned, so CONNX must switch to a different query plan at runtime. Since the {statistics} function does not know the number of rows that will be returned, it is possible that it will return a query plan that is different than the one that will ultimately be used.
Default - SUBQUERYROWESTIMATE = 0
*Environments - Client, Windows, Unix
*Configuration Manager: CONNX Settings; Current Key = CONNX; Key Value/Value Name = SUBQUERYROWESTIMATE
*Unix Registry Setting: CONNX.SUBQUERYROWESTIMATE
SUPERDESCRIPTORASFIELD
For non-MU fields, this setting enables the import feature to include a superdescriptor, so that it appears as a field in the CONNX Data Dictionary. The superdescriptor field is read-only.
Default - SUPERDESCRIPTORASFIELD = 1
*Environments - Server,Windows, Mainframe, Unix, Adabas
*Configuration Manager: CONNX Settings; Current Key = CONNX\Adabas; Key Value/Value Name = SUPERDESCRIPTORASFIELD
*Unix Environment Variable: SUPERDESCRIPTORASFIELD
*Started Task: SUPERDESCRIPTORASFIELD
*CICS: SUPERDESCRIPTORASFIELD