|
Scroll to the appropriate option name in the
following list and follow the tips for setting its value in the Option Value Entry dialog box. |
|
- ADD_QUALIFIERS
- Select TRUE or FALSE. If TRUE, TDT automatically qualifies SQL table names for all
statements except SQLPrepare and SQLExecuteImmediate. The qualifier used is determined by
the "Qualifier" entry in the Source
Setup dialog box (which ultimately ends up setting the "qual=xxx" option in
sai_sql.cfg). The default is TRUE.
|
|
- APP
- Enter an application name when connecting. Currently, this only applies to Sybase and MS
SQLServer (and is optional in both cases). Any application name may be used such as
"exampleapp".
|
|
- ARRAY_SIZE
- Enter a number to specify how many rows should be fetched at once (in a block). Block
fetching can reduce network overhead. TDT automatically sets this to one (1) for
SQLSelectInto. Also, TDT may or may not be able to honor your ARRAY_SIZE value, depending
on the value of ARRAY_BUFFER_SIZE. Currently, this option is supported only in Oracle. The
default is 100 rows.
|
|
- ARRAY_BUFFER_SIZE
- Enter a number to specify how many bytes are allocated for a single string-type column,
such as CHAR, LONG, or VARCHAR, when performing array (block) fetching. Setting this to a
large value prevents truncation; however, setting this to smaller values minimizes the
amount of data transmitted across the network. TDT automatically sets this value to 255
for SELECTS resulting from SQLManage. Currently, this is supported only in Oracle. The
default is 4096.
|
|
- AUTO_CONNECT
- Select TRUE or FALSE. Setting this to TRUE causes TDT to automatically connect to this
data source when the first (non-connect) SQL statement is executed. Note that this is
different than the DEFAULT source.
- Warning: This option is provided for backwards compatibility only, and
is likely to be unsupported in future releases.
|
|
- BIND_ALL
- Select TRUE or FALSE. Setting this to TRUE causes all parameters to always be bound
(instead of expanded in-line). The default for Oracle and Informix is TRUE; the default
for all other databases is FALSE.
|
|
- BIND_PARAMETER_BUFFER_SIZE
- Enter a number to specify the output parameter buffer size used for STRINGS returned by
stored procedures. The current default is 2049 for most databases. SQLServer and Sybase
have a default of 257.
|
|
- BIND_PARAMETER_FILL_OUTPUT_NULL_VALS
- Select TRUE or FALSE. This causes NULL strings being bound as output parameters to be
converted to an empty ('') string before being bound. The default is FALSE.
|
|
- BIND_PARAMETER_PAD_OUTPUT_STRINGS
- Select TRUE or FALSE. This causes strings being bound as output parameters to be
right-padded with spaces to BIND_PARAMETER_BUFFER_SIZE before being bound. The default is
FALSE.
|
|
- BOOLEAN_FORMAT
- This specifies the format of Boolean values in the DBMS. Currently, all TSD applications
store booleans as integers, so this option is not used.
|
|
- BOOLEAN_STORAGE_TYPE
- Select INTEGER or STRING to specify the DBMS storage class used for booleans. Currently,
all TSD applications store booleans as INTEGER.
|
|
- CASE_CONVERSION
- Select NONE, UPPER, or LOWER to control whether or not TDT performs an automatic case
conversion of SQL statements prior to submitting them. Normally, for case-sensitive DBMSs,
the Tivoli Script programmer must observe the correct case when coding SQL queries.
Because TDT forces a consistent case, the practice of coding to a particular DBMS's case
requirement may be eliminated. The default is NONE.
- Note: For this option to work, all database objects
(tables, columns, indexes, etc.) must be created in a consistent case (i.e. all upper, or
all lower).
|
|
- CASE_SENSITIVE
- Select TRUE or FALSE. This option informs TDT whether or not the DBMS has case-sensitive
object names such as table or column names. The default is FALSE.
- Note: This setting does not refer to the
case-sensitivity of data.
|
|
- CATALOG_CASE_CONVERSION
- Select NONE, UPPER, or /LOWER. This option controls whether or not TDT performs an
automatic case conversion of the data in queries against the system catalog views
(SAI_SYSCOLUMNS and SAI_SYSTABLES). The default for Informix is LOWER; the default for
case-sensitive Sybase and MS SQLServer is NONE; the default for all others is UPPER.
|
|
- CLIENT_VERSION
- Enter the database client version, such as 1.20.
|
|
- COLUMN_CATALOG_METHOD
- Select STANDARD, DBMS_SPECIFIC, or ODBC to specify the method used to query the database
catalog for column definitions for tables.
- STANDARD uses the COLUMN_DEFINITION_TABLE and other COL parameters to query the data.
- DBMS_SPECIFIC uses a database platform specific query optimized for performance. If
there is no DBMS_SPECIFIC query, the STANDARD query is performed.
- ODBC enables the use of the ODBC SQLColumns function to retrieve the column information
for a table.
- The default for MS SQLServer and Sybase is DBMS_SPECIFIC, all others default to
STANDARD.
|
|
- COLUMN_DEFINITION_TABLE
- Type the name of the system catalog view used by TDT for column information. The default
is SAI_SYSCOLUMNS.
|
|
- COL_BUFFER_SIZE
- Type a number to specify the size of the buffer used to retrieve character data. Setting
this to 512, for example, does not imply that you are limited to 512 bytes: TDT
"chunks" the retrieval. The default size is 1998. In general, the larger the
buffer, the better the performance; however, our testing shows that you reach the point of
diminishing returns rather quickly.
|
|
- COL_LENGTH_COLUMN
- Type the name of the column in the column catalog view which contains the column length.
The default is LENGTH.
|
|
- COL_NAME_COLUMN
- Type the name of the column in the column catalog view which contains the column name.
The default is NAME.
|
|
- COL_NULLS_COLUMN
- Type the name of the column in the column catalog view which contains the column null
capability. The default is NULLS.
|
|
- COL_REMARKS_COLUMN
- Type the name of the column in the column catalog view which contains the column
comments. The default is REMARKS.
|
|
- COL_SCALE_COLUMN
- Type the name of the column in the column catalog view which contains the column scale.
The default is SCALE.
|
|
- COL_TBCREATOR_COLUMN
- Type the name of the column in the column catalog view which contains the table creator.
The default is TBCREATOR.
|
|
- COL_TBNAME_COLUMN
- Type the name of the column in the column catalog view which contains the table name.
The default is TBNAME.
|
|
- COL_TYPE_COLUMN
- Type the name of the column in the column catalog view which contains the column type.
The default is TYPE
|
|
- COMMIT_SELECTS
- Select TRUE or FALSE. If TRUE and in manual commit mode, TDT commits read-only units of
work (to release share locks). The default is TRUE.
|
|
- COMM_PACKET_SIZE
- Type a number to specify the communication packet size used between the database client
and server. This is not the underlying transport protocol (e.g. TCP/IP) packet size.
Currently, this only applies to Sybase. The default is 512 bytes.
|
|
- DATE_FORMAT
- Specify the date format expected by the DBMS.
- Examples: MM/DD/YYYY, DD.MM.YYYY, YYYY-MM-DD, DD-MON-YY.
- Note: Refer to the TDT manuals for an in-depth discussion on the
available formats.
|
|
- DATE_PARAMETER_PRECISION
- Type a number to specify how many digits of precision are used when parameter-binding a
date value. See your database documentation for default value for your DBMS.
|
|
- DATE_PARAMETER_SCALE
- Type a number to specify how many digits of scale are used when parameter-binding a date
value. Use this only if REAL_PARAMETER_TYPE is SQL_NUMERIC or SQL_DECIMAL. The default
value is 0 (zero).
|
|
- DATE_PARAMETER_TYPE
- Select SQL_DATE, SQL_CHAR, or SQL_TIMESTAMP to specify the DBMS's parameter-binding
class used for dates. Currently, the default is SQL_DATE for all databases except MS
SQLServer and Sybase. MS SQLServer and Sybase use SQL_TIMESTAMP.
|
|
- DATE_STORAGE_TYPE
- Select DATE, STRING, or INTEGER to specify the storage class the DBMS uses for dates.
Currently, the default for all TSD applications is DATE.
|
|
- DRIVER_XOOR_DESC_CACHE_SIZE
- For Oracle databases only, type a number to define a limit on the amount of description
data that XOOR keeps in its LRU cache. The default is 2000000000 descriptions, which is
effectively no limit. If you do not want to cache descriptions, set this to 0 (zero).
- Warning: Never set this to a non-zero value less than the maximum
expected number of simultaneously executing statements. Therefore a setting of 40 is
always a safe minimum.
|
|
- DRIVER_XOOR_MAX_LONG_COL_SIZE
- For Oracle databases only, type a number to define the maximum size that can be
retrieved for LONG data types when the ARRAY_SIZE is 1. If this value is greater than
32512, then the OCI call "oflng" is used to retrieve all of the data. If it is
less than or equal to 32512, then a buffer of this size is bound with "odefin".
When the ARRAY_SIZE is greater than 1, then "odefin" is always called, and the
buffer size is determined by ARRAY_BUFFER_SIZE. The default is 32512.
|
|
- DRIVER_XOSS_ANSI_TO_OEM
- For Sybase and MS SQLServer databases only, and under Windows only, select TRUE or
FALSE. This parameter is optional. Setting it to TRUE causes ANSI to OEM and OEM to ANSI
codepage translations to take place in the database client. The default is FALSE.
- Note: This does the same thing as the NEEDS_CODEPAGE_TRANSLATION
option, except at a different layer (DB-Lib vs. TDT); therefore, you should not enable
both at once.
|
|
- DRIVER_XOSS_CANCEL_FREQUENCY
- For Sybase and MS SQLServer databases only, select 0 or 1.
- This parameter is optional. It allows you to specify the frequency of result set
canceling. Legal choices are: 0 (as needed) or 1 (always). As an optimization, XOSS makes
every effort not to call dbcancel (or dbcanquery) unnecessarily; therefore the default is
0. However, the nature of DB-Lib programming makes this a little complicated, and if
problems should ever arise due to result set cancellation failures, set this to 1
(always).
|
|
- DRIVER_XOSS_CANCEL_METHOD
- For Sybase and MS SQLServer databases only, select 0, 1 or 2.
- This parameter is optional. It allows you to specify the method used to cancel result
sets. Legal choices are: 0 (dbresults in conjunction with iterating through dbnextrow), 1
(db results in conjunction with one iteration of dbnextrow and (if more rows) dbcancel),
or 2 (dbcancel). The default is 1, which should be the most optimal; however, if problems
should ever arise due to result set cancellation failure, try setting this to 1 or 2.
|
|
- DRIVER_XOSS_CHARSET
- For Sybase databases only, specify your client character set (refer to your database
vendor's documentation for a list of allowable character sets). This parameter is
optional.
|
|
- DRIVER_XOSS_HOST
- For Sybase and MS SQLServer databases only, set your workstation name (which will show
up in sysprocesses table). If your site is using a common configuration file for all
users, a more appropriate way of setting this is via the XOSS_HOST environment variable
(for example, your autoexec.bat could contain: SET XOSS_HOST=Mozart).This parameter is
optional.
|
|
- DRIVER_XOSS_LANG
- For Sybase and MS SQLServer databases only, specify the natural language name for your
locale (refer to your database vendor's documentation for a list of supported
languages).This parameter is optional.
|
|
- DRIVER_XOSS_LOGIN_TIMEOUT
- For Sybase and MS SQLServer databases only, type a number to specify the amount of time
DB-Lib waits before returning with a login error. It is important to understand that
setting this doesn't always guarantee that the time-out always happens; some communication
errors still cause DB-Lib (or Net-Lib) to hang.
|
|
- DRIVER_XOSS_MAX_TEXT_SIZE
- For Sybase and MS SQLServer databases only, type a number to specify the maximum amount
(in characters) of TEXT data that you may send or receive. The default is 4096.
|
|
- DRIVER_XOSS_PACKET_SIZE
- For Sybase and MS SQLServer databases only, type a number to specify the TDS packet size
used by your application. The default is 512 bytes.
- Note: We have found that, depending on your communication protocol,
setting this to larger values can cause communication errors.
|
|
- DRIVER_XOSS_SQL_TIMEOUT
- For Sybase and MS SQLServer databases only, type a number to specify the amount of time
DB-Lib waits for a server response to an SQL command.
- Note: Setting this value doesn't guarantee that the time-out always
occurs. Some communication and/or server errors can still cause DB-Lib (or Net-Lib) to
hang.
|
|
- DRIVER_XOSS_USE_DBROWS
- For Sybase and MS SQLServer databases only, select TRUE or FALSE to specify whether or
not XOSS will use an optimization that calls DBROWS to determine whether or not there are
any more rows pending in this result set. The default is TRUE. It is conceivable that in
some environments you may actually get better results by setting this to FALSE; however,
it should be pointed out that in any case this is probably a very minor optimization.
|
|
- DRIVER_XOINF_SERVICE
- For Informix only, specify the TCP/IP service name that Informix Net (INET) uses when
connecting to the database server. The name should match the one specified in the SERVICES
file used by the TCP/IP networking software on your machine.
Possible SERVICES file locations: c:\windows; c:\win95;
c:\winnt\system\drivers\etc; c:\ftp\etc; c:\ibmtcp\etc. Please refer to your vendor's (not
Tivoli Systems, Inc.) networking software reference manual for locations specific to your
brand of networking software. If this entry is not present (or empty), the default is the
TCP/IP service name specified in INFORMIX.INI.
|
|
- DRIVER_XOINF_PROTOCOL
- For Informix only, specify the networking transport protocol (e.g. TCP/IP) that Informix
Net (INET) uses when connecting to the database server. Please refer to the Informix Net
(INET) manuals for acceptable values for this entry. If this entry is not present (or
empty), the default is the networking transport protocol specified in INFORMIX.INI.
|
|
- DRIVER_XOINF_DBDATE
- For Informix only, specify the date format that Informix Net uses for date conversions.
- Note: This is not formatted the same as the SAI_SQL
layer's DATE_FORMAT option. Refer to your Informix Net manuals for acceptable values.
Normally, you should not change this setting unless you have a good reason to do so. If
this entry is not present (or empty), the default is the date format specified in
INFORMIX.INI which defaults to "mdy4-".
|
|
- DRIVER_XOINF_DBTIME
- For Informix only, specify the date-time format that Informix Net uses for date-time
conversions.
- Note: This is not formatted the same as the SAI_SQL
layer's TIME_FORMAT option. Refer to your Informix Net manuals for acceptable values.
Normally, you shouldn't change this setting unless you have a good reason to do so. If
this entry is not present (or empty), the default is "%Y-%m-%d %H:%M:%S", unless
you use "INI" to signify the use of the INFORMIX.INI value.
|
|
- DRIVER_XOINF_USE_HOLD_CURSORS
- For Informix only, select TRUE or FALSE. This causes XOINF to create cursors with the
WITH HOLD option, so that they won't be closed upon committing. The default is TRUE.
|
|
- DRIVER_XOINF_CHECK_PARAM_COUNT
- For Informix only, select TRUE or FALSE. This causes XOINF to parse the submitted SQL
statements to ensure that the number of parameters bound do not exceed the number of
parameter makers embedded in the SQL statement text. The default is TRUE, but FALSEe is
more optimal. However, if you are executing code that has extra parameters being passed
into SQLExecuteImmediate, you may need to set this to TRUE.
|
|
- DRIVER_XOINF_MAX_TEXT_SIZE
- For Informix only, type a number to specify the maximum limit in bytes of the size of
TEXT data that can be read from a single column at a time. The default is 4096. If this is
not enough, you can raise it up to 32768 (32K).
|
|
- DRIVER_XOINF_MAX_DESC_CACHE_SIZE
- For Informix only, type a number to specify the limit on the amount of description data
that XOINF keeps in its LRU cache. The default is 2000000000 descriptions, which is
effectively no limit. If you do not want to cache descriptions, set this to 0 (zero).
- Warning: Never set this to a non-zero value less than the maximum
expected number of simultaneously executing statements. Therefore, a setting of 40 is
always a safe minimum.
|
|
- FTR_MAX_HITS
- Type a number to specify the maximum number of row IDs (hits) returned from the text
search server. Any hits above this maximum number are not returned, and a warning message
is displayed. This limit should be set to prevent exceeding the query limits of your DBMS.
The default is 250.
|
|
- FTR_TEXT_INDEX_SOURCE
- Type the name of the index data source (in sai_sql.cfg) used by the text search driver.
|
|
- GET_COM_ERRCODE
- Select TRUE or FALSE to specify whether to require common return codes for errors, such
as "Column already exists," "Dropping non-existing objects,"
"Create objects which already exist," and "Adding a record with duplicate
key."
|
|
- HAS_TRANSACTIONS
- Select TRUE or FALSE. If TRUE, then the DBMS supports transactions. This is the default
for all currently supported DBMSs (except for the text search driver).
|
|
- INFORMIX_LOCK_MODE
- For Informix only, select WAIT or NO_WAIT. This specifies the lock mode. The default
mode is WAIT.
|
|
- INTEGER_FORMAT
- Specify the format used (on the database server) for integers, such as "nnnn"
and "n.nnn". Although the hooks are in place to support different integer
formats, this has not been certified to work in all cases.
|
|
- INTEGER_PARAMETER_PRECISION
- Enter a number to specify how many digits of precision are used when parameter binding
an integer value. See the documentation for default values for your DBMS.
|
|
- INTEGER_PARAMETER_TYPE
- Select SQL_INTEGER, SQL_NUMERIC, SQL_DECIMAL, or SQL_SMALLINT to specify the DBMS's
parameter-binding class used for integers. Currently, the default is SQL_INTEGER for all
but Oracle7. Oracle7 uses SQL_NUMERIC.
|
|
- INTEGER_STORAGE_TYPE
- Select INTEGER, REAL, or STRING to specify the the DBMS storage class used for storing
integers. Currently, the default for all TSD applications is INTEGER.
|
|
- MANUAL_COMMITS
- Select TRUE or FALSE. If TRUE, TDT (not the database driver) controls auto-committing.
The default is TRUE for XOOR, FALSE for all others.
|
|
- MAX_LITERAL_LEN
- Type a number to specify the maximum number of characters in a data column that is being
inserted or updated before TDT uses bound parameters instead of in-line expansion. The
default is 2000 for Oracle, 255 for Informix, and -1 (disabled) for all others.
|
|
- MULTIPLE_CONNECT
- Select TRUE or FALSE. If TRUE, this data source supports multiple, simultaneous
connections. The default is TRUE for all except DB2/2 and DB2/6000 version 1.x.
|
|
- MULTIPLE_CONNECT_REQUIRED
- Select TRUE or FALSE. If TRUE, this DBMS requires multiple connections to execute
concurrent SQL statements. In other words, the DBMS can only execute one statement at a
time on a connection. The default for Sybase and MS SQLServer is TRUE, for all others it
is FALSE.
|
|
- NEEDS_CODEPAGE_TRANSLATION
- Select TRUE or FALSE. If TRUE, TDT performs ANSI-to-OEM and OEM-to-ANSI codepage
conversions for data going to or coming from the database server. This is only applicable
under Windows. The default is TRUE for DB2/2 and DB2/6000, and FALSE for all others.
|
|
- PROCESS_RESULTS_ON_FREESTMT
- Select TRUE or FALSE. If TRUE, TDT performs a fetch of all rows from the database before
executing a SQLFreeStmt. This is a work around for some ODBC drivers that do not correctly
clear the results on SQLFreeStmt.
|
|
- REAL_FORMAT
- Type the name of the format used on the database server for reals such as
"n,nnn.n" and "nnnn". Although the hooks are in place to support
different real formats, this has not been certified to work in all cases.
|
|
- REAL_PARAMETER_PRECISION
- Type a number to specify how many digits of precision are used when parameter binding an
real value. See your database documentation for the default value for RDBMS.
|
|
- REAL_PARAMETER_TYPE
- Select SQL_REAL, SQL_FLOAT, SQL_DOUBLE, SQL_NUMERIC, or SQL_DECIMAL to specify the
DBMS's parameter binding class used for reals. Currently, the default is SQL_DOUBLE for
all but Oracle7. Oracle7 uses SQL_FLOAT.
|
|
- REAL_STORAGE_TYPE
- Select REAL, STRING, or INTEGER to specify the DBMS storage class used for storing
reals. Currently, the default for all TSD applications is REAL.
|
|
- REUSE_STATEMENTS
- Select TRUE or FALSE to specify whether or not TDT re-uses statement handles at the
X/Open (or ODBC) level. This defaults to TRUE for Oracle, since there is a known benefit
for doing so: the Oracle server can re-use the cursor data area. It defaults to FALSE for
all other DBMSs.
|
|
- ROW_BUFFER_SIZE
- Type a number to specify the number of rows in the row buffer that is used for fetching
data. Currently, this option is not enabled.
|
|
- SERVER_VERSION
- Enter the database server version, such as 7.0.16.
|
|
- SETDB
- Select TRUE or FALSE. If TRUE, TDT sets the database immediately after connecting, even
if the database is specified in ODBC.INI. Currently, this option is only used (set to
TRUE) to compensate for a known problem in Intersolv's SQLServer ODBC driver.
|
|
- SHOW_WARNINGS
- Select TRUE or FALSE. If TRUE, the user sees warning dialog boxes on warning conditions
(the program still continues).
|
|
- SQL_CONN_POOL_SIZE
- Type a number to specify the cached connection pool size. The default number is 40. You
can turn off this caching by setting it to 0.
|
|
- STRING_FORMAT
- Type the name of the DBMS storage format used for strings. Currently, this option is not
enabled.
|
|
- STRING_PARAMETER_TYPE
- Select SQL_CHAR, SQL_VARCHAR, or SQL_LONGVARCHAR to specify the DBMS's parameter-binding
class used for strings. Currently, the default is SQL_CHAR for all database platforms.
|
|
- STRING_STORAGE_TYPE
- Type the name of the DBMS storage class used for storing strings. Currently, the default
for all TSD applications is STRING.
|
|
- SYSQUAL
- Type the name of the system table qualifier, such as SYSIBM.
|
|
- TABLE_CATALOG_METHOD
- Select STANDARD, DBMS_SPECIFIC, or ODBC to specify the method used to query the database
catalog for tables.
- STANDARD uses the TABLE_DEFINITION_TABLE and other TAB parameters to query the data.
- DBMS_SPECIFIC uses a database platform specific query optimized for performance. If
there is no DBMS SPECIFIC query, the STANDARD query is performed.
- ODBC enables the use of the ODBC SQLTables function to retrieve the column information
for a table.
The default for MS SQLServer and Sybase is DBMS_SPECIFIC, all others default to
STANDARD.
|
|
- TABLE_DEFINITION_TABLE
- Type the name of the system catalog view, for table information, used by TDT. The
default is SAI_SYSTABLES.
|
|
- TAB_COLCOUNT_COLUMN
- Type the name of the column in the table catalog view which contains the column count.
The default is COUNT.
|
|
- TAB_CREATOR_COLUMN
- Type the name of the column in the table catalog view which contains the table creator.
The default is CREATOR.
|
|
- TAB_NAME_COLUMN
- Type the name of the column in the table catalog view which contains the table name. The
default is NAME.
|
|
- TAB_REMARKS_COLUMN
- Type the name of the column in the table catalog view which contains the table's
comments. The default is REMARKS.
|
|
- TAB_TYPE_COLUMN
- Type the name of the column in the table catalog view which contains the table type,
such as view or table. The default is TYPE.
|
|
- TIME_FORMAT
- Type the name of the time format expected by the DBMS, such as"hh:mm:ss" or
"hh.mm.ss". Refer to the TDT manuals for an in-depth discussion of the available
formats.
|
|
- TIME_PARAMETER_PRECISION
- Type a number to specify how many digits of precision are used when parameter binding a
time value. See your database documentation for default values for RDBMS.
|
|
- TIME_PARAMETER_TYPE
- Select SQL_TIME, SQL_CHAR, or SQL_TIMESTAMP to specify the DBMS's parameter binding
class used for times. Currently, the default is SQL_TIME for all but Informix, MS
SQLServer and Sybase. Informix databases use SQL_CHAR, MS SQLServer and Sybase use
SQL_TIMESTAMP.
|
|
- TIME_STORAGE_TYPE
- Select TIME, STRING, or INTEGER to specify the DBMS's storage class used for times.
Currently, the default for all TSD applications is TIME, except for Oracle and Informix
databases, for which the default is STRING.
|
|
- UPDATE_LOCK_LEVEL
- Select COLUMN or ROW to specify the locking level used for passive concurrency updates.
COLUMN allows the locking to be checked for an individual column in the table. ROW allows
the locking to be checked for an entire row in the table. The default is COLUMN.
|
|
- UPDATE_LOCK_COLUMN
- Type the column name to use when applying the exclusive lock via an UPDATE. This is used
to freeze the data during the passive concurrency checks. The default is MODIFY_DATETIME.
If MODIFY_DATETIME is not present in a table, you would normally use SQLSetOption to
change the column name on a case-by-case basis. Setting it in sai_sql.cfg allows you to
specify the default for all tables.
|
|
- UPDATE_LOCK_ERROR_FILTER
- Type a number to specify the error filter level used when TDT is applying the exclusive
lock via an UPDATE. This is used to freeze the data during the passive concurrency checks.
Please refer to the TDT manuals for a complete discussion of error filters. The default is
0 (zero), which suppresses all non-fatal errors.
|
|
- UPDATE_LOCK_STYLE
- Select UPDATE, SELECT_FOR_UPDATE, NONE, or UPDATE_COND to specify the locking style
(technique) used for passive concurrency updates. Please refer to the Tivoli Script
manuals for a complete discussion of the locking styles available. The default for Oracle,
DB2/2 and DB2/6000 is SELECT_FOR_UPDATE; the default for all others is UPDATE.
|
|
- UPDATE_MODE
- Select DBMS_OPTIMISTIC, SELECT, or NONE to specify the method used to perform the
passive concurrency check. Please refer to the Tivoli Script manuals for a complete
discussion of the update modes available. The default for all DBMSs is SELECT.
|
|
- UPPERCASE_FUNCTION
- Type the name of the DBMS-specific function used for upper-casing. The default for DB/2
and db2/6000 is TRANSLATE, the default for Oracle, Sybase and MS SQLServer is UPPER, and
the default for Watcom is UCASE. Informix does not support this function.
|
|
- VALLIDATE_DRIVER
- Select TRUE or FALSE. If TRUE, TDT performs a driver validation check to see if you are
using an unsupported driver. The default is TRUE.
|