> # Defining SequeLink® Service Attributes

> This section describes SequeLink service attributes in alphabetical order.

> ### DataSourceAllowBatchStatements

> Specifies whether the SequeLink data source accepts a batch of SQL statements. A batch is used to submit multiple update commands together as a single unit to the underlying DBMS.

> Valid values are:

> - FALSE=The SequeLink data source does not accept batch SQL statements. Semicolons are considered to be part of a single SQL statement.
> - TRUE=The SequeLink data source accepts batch SQL statements.

> The default is FALSE.

> Type=Dynamic

> NOTE: This service attribute is used by the ODBC Client and the ADO Client.

> ### DataSourceAllowPrefetch

> Specifies whether the JDBC Client launches a request to the server to fetch the next set of rows from the database while the application is processing a previous set of retrieved rows.

> Valid values are:

> - FALSE=Prefetch of result set data is not allowed.
> - TRUE=The JDBC Client launches a request to the server to fetch the next set of rows from the database while the application is processing a previous set of retrieved rows.

> The default is FALSE.

> Type=Dynamic

> NOTE: This service attribute is used by the JDBC Client.

> ### DataSourceApplID

> Specifies a list of application IDs the SequeLink data access service will accept. A valid application ID is an alphanumeric string with a maximum length of 128 characters.

> The default is an empty string.

> Type=Dynamic

> See "Configuring SequeLink® Security" for more information about using application IDs to limit access to SequeLink services.

> ### DataSourceArrayFetchMaxBytes

> Specifies the number of bytes the SequeLink Server uses when doing an arrayfetch from the DBMS. The larger the size of the buffer, the more rows that SequeLink will fetch in one database fetch. This will have a positive effect on performance. However, a larger buffer increases the amount of memory that SequeLink uses.

> A value of 0 disables the array fetch mechanism. Valid values are 0 to 65536.

> The default is 65536.

> Type=Dynamic

> ### DataSourceAutoApplId

> Specifies an application ID that is automatically generated by the ODBC Client to identify the client application to the SequeLink service. A valid automatically generated application ID contains exactly 40 hexadecimal digits. Each provided value can have an optional text description. For example:

>     InventoryControl=aaf7798c8c66e6b3a6b1462eff442b39b7be6946

> The default is an empty string.

> FSee "Configuring SequeLink® Security" for more information about using application IDs to limit access to SequeLink service.

> Type=Dynamic

> ### DataSourceBatchProcessing

> Configures the behavior for batch processing on the SequeLink server. Valid values are:

> - Emulated=Each element of the batch is processed individually. Processing of the batch stops on the first error encountered.
> - Native=The batch interface of the DBMS is used.

> Handling of error conditions is database-specific:

> - DB2 UDB: None of the statements are processed if an error occurs. No update count information is available.
> - Oracle: All elements of the batch are processed. Processing does not stop on errors.
> - JDBC Socket Server: Behavior depends on the back-end JDBC driver.
> - ODBC Socket Server: Behavior depends on the back-end ODBC driver.
> - SQL Server: All elements of the batch are processed. Processing does not stop on errors.
> - Sybase: None of the elements of the batch are processed if an error occurs. No update count information is available.

> The default is Emulated.

> For more information about batch processing, refer to your DBMS documentation.

> Type=Dynamic

> ### DataSourceBlockFetchForUpdate

> When the isolation level is Read Committed and a SELECT FOR UPDATE statement is issued against some data stores, the SequeLink Client does not lock the expected row. Valid values are:

> - 0=The appropriate row will be locked. Specifying 0 will degrade the performance for SELECT FOR UPDATE statements because rows will be fetched one at a time.
> - 1=The appropriate row is not locked.

> The default is 1.

> Type=Dynamic

> For more information, refer to the SequeLink Developer's Reference.

> ### DataSourceCurrentCatalog

> Specifies the default catalog to be used when connected to the SequeLink data access service. The valid value is a defined database catalog name.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceCursorHold

> Specifies the effect of transaction completion on open cursors. Valid values are:

> - 0=cursor no hold. The cursors are destroyed when the transaction is committed.
> - 1=cursor hold. The cursors are not destroyed when the transaction is committed.

> For Informix and for DB2 UDB on z/OS, the default is 1.

> For all other DBMS, the default is 0.

> Type=Dynamic

> ###

> ### DataSourceDB2CatalogOwner

> Specifies the owner of the DB2 catalog. This parameter allows you to limit the meta-information that is returned by using views on the DB2 catalog.

> Specify SYSIBM when making selections on the native DB2 catalog tables. Otherwise, specify a different value for the catalog owner to limit the number of tables retrieved by SequeLink. The valid value is a defined database catalog name.

> The default is SYSIBM.

> Type=Dynamic

> ###

> ### DataSourceDB2CollectionPrefix

> Specifies a user-defined prefix, which can be no longer than 15 characters, for the DB2 collection that identifies where the SequeLink package resides.

> Based on the isolation level (DataSourceTransactionIsolation attribute), a suffix is added to the DB2 collection name, for example, CollectionPrefix_U. Valid values are:

> - U= Read Uncommitted
> - S= Read Committed
> - T= Repeatable Read
> - R= Serializable

> For example, if you use the default prefix SLD600 for an uncommitted connection, the DB2 collection name is SLD600_U.

> The default is SLD600.

> Type=Dynamic

> ### DataSourceDB2ConnectOptions

> Specifies additional connect options to use when the SequeLink server connects to DB2 on Linux, UNIX, or Windows. This string will be appended to the connect string.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceDB2DBFilterList

> Specifies a list of comma-separated values specifying the databases from which tables can be retrieved by a SQLTables (ODBC), getTables (JDBC), or TABLES (ADO) call. You cannot use quotes.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceDB2DBMSName

> Specifies the value that is returned for SQLGetInfo (SQL_DBMS_NAME). Valid values are:

> - 0=DB2/MVS. This value supports the behavior of earlier versions of SequeLink.
> - 1=DB2. This value is compliant with the behavior of the IBM DB2 Connect driver, and supports applications such as the IBM remote administration and development tools.
> - 2=DB2 UDB for OS/390 and z/OS. This value is compliant with the behavior of the DataDirect Connect for DB2 driver.

> The default is 0.

> Type=Dynamic

> ###

> ### DataSourceDB2DecimalPoint

> Specifies whether the decimal point for numbers is a comma (,) or a period(.). This setting allows the data source to overwrite the DB2 installation parameter DECIMAL POINT. If no setting is specified, the DB2 installation parameter is read from the load module of DB2.

> Valid values are:

> - PERIOD=The service uses a period as the decimal point character.
> - COMMA=The service uses a comma as the decimal point character.

> The default is PERIOD.

> Type=Dynamic

> ### DataSourceDB2LogPath

> Defines the log path for all CLI calls executed by the SequeLink service. The valid value is a log path.

> Type=Dynamic

> ###

> ### DataSourceDB2MaxLobSize

> Specifies the size (in bytes) that is reported for BLOB and CLOB data types, for example, in response to a SQLGetTypeInfo call (ODBC) or the equivalent OLE DB and JDBC calls.

> Valid values are from 1 to 2147483647.

> The default is 2147483647.

> Type=Dynamic

> ###

> ### DataSourceDB2ReportLobsFirst

> Specifies the order in which BLOB and CLOB data types are reported, for example, in response to a SQLGetTypeInfo call (ODBC) or the equivalent OLE DB and JDBC calls.

> - FALSE=Report LONG VARCHAR and LONG VARCHAR FOR BIT DATA data types before CLOB and BLOB data types.
> - TRUE=Report CLOB and BLOB data types before LONG VARCHAR and LONG VARCHAR FOR BIT DATA data types.

> The default is FALSE.

> Type=Dynamic

> ###

> ### DataSourceDB2TranslateCount

> On DB2 UDB V7 and earlier, specifies whether the service will substitute COUNT(columnName) with COUNT(*).

> - FALSE=The service will not substitute COUNT(columnName) with COUNT(*).
> - TRUE=The service will substitute COUNT(columnName) with COUNT(*).

> The default is FALSE.

> ### Type=Dynamic

> ### DataSourceDescribeParam

> Defers the fetching of parameter metadata until it is needed by the application.

> - Enabled=The service always requests parameter description information, even when the application does not require it. This value minimizes network traffic and should be used when parameter information is required for most statements.
> - Deferred=The service requests parameter description information from the server when the client application asks for it. Use this value when the application requests description information for a small number of statements.
> - Disabled=Parameter description requests are disabled.

> The default is Enabled for all databases except Sybase, where the Service template contains Disabled.

> Type=Dynamic

> ### DataSourceDescription

> Specifies a general description of the server data source.

> Type=Static

> ### DataSourceDisableWarnings

> Turns on and off the filtering of generated warnings.

> - TRUE=Turns on filtering
> - FALSE=Turns off filtering

> Type=Dynamic

> ### DataSourceEnableAccess

> Determines whether access to a specified data source is enabled.

> - TRUE=Any new connection is accepted.
> - FALSE=Any new connection is rejected. This setting does not terminate existing connections, which will be able to finish their work.

> The default is TRUE.

> Type=Dynamic

> ### DataSourceEnableDescribeParam

> Turns on a workaround for connections to Oracle data stores only. For more information, refer to the SequeLink Developer's Reference.

> - 0=The option is disabled. Support is turned off for SQLDescribeParam.
> - 1=Support is turned on for SQLDescribeParam and will describe all parameters as SQL_CHAR with a precision of 999.

> The default is 0.

> Type=Dynamic

> ### DataSourceFetchNextOnly

> Turns on a workaround for Visual Basic/Remote Data Objects (RDO) that circumvents a problem with FORWARD_ONLY cursors when the driver reports other values than FETCH_NEXT for SQLGetInfo(SQL_FETCH_DIRECTION).

> For example, if the driver only reports FETCH_NEXT, RDO performs SQLExecDirect, SQLBindCol, and SQLExtendedFetch(NEXT). If the driver supports more than FETCH_NEXT, RDO performs SQLExecDirect, SQLExtendedFetch(NEXT), and SQLGetData. This is only valid when the rowsize is 1, but RDO uses a larger rowsize in this situation.

> - TRUE=The driver will incorrectly report that only SQL_FETCH_NEXT is supported, which satisfies RDO.
> - FALSE=The workaround is not turned on.

> The default is FALSE.

> Type=Dynamic

> For more information, refer to the SequeLink Developer's Reference.

> ### DataSourceFetchTimeStampAsString

> Specifies whether a workaround for a Microsoft Access problem with timestamps is turned on.

> - TRUE=Yes
> - FALSE=No

> The default is FALSE.

> Type=Dynamic

> ### DataSourceFixCharTrim

> Turns on a workaround for applications that have a problem using SQL_CHAR data padded with spaces. The ODBC driver returns SQL_CHAR data padded with spaces as mandated by the ODBC specification. For more information, refer to the SequeLink Developer's Reference.

> - 0=The workaround is turned off.
> - 1=Returns SQL_CHAR data that is not padded with spaces.

> The default is 0.

> Type=Dynamic

> ### DataSourceGetOutputParams

> Turns on a workaround that allows you to control when output parameters of stored procedures are returned to calling applications. For more information, refer to the SequeLink Developer's Reference.

> The value for this service attribute should be set to the cumulative value of all chosen options added together.

> Valid values are:

> - 0=The workaround is not turned on.
> - 1=Output parameters are returned after an execute.
> - 2=Output parameters are returned after a fetch is complete.
> - 4=Output parameters are returned after moreresults no more rows.
> - 7=Output parameters are returned after all of the above.

> The default is 7.

> Type=Dynamic

> NOTE: Set GetOutputParams=3 when executing stored procedures with output parameters in RDO (Visual Basic 5 and 6).

> ### DataSourceINFClientLocale

> Sets the Informix CLIENT_LOCALE environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFDbAnsiWarn

> Sets the Informix DBANSIWARN environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFDbLang

> Sets the Informix DBLANG environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFDbLocale

> Sets the Informix DBLOCALE environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFDbNls

> Sets the Informix DBNLS environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFDelimldent

> Sets the Informix DELIMIDENT environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFHost

> Sets the Informix INFORMIXHOST environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFInformixDir

> Sets the Informix INFORMIXDIR environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFInformixServer

> Sets the Informix INFORMIXSERVER environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFLang

> Sets the Informix LANG environment variable used by the SequeLink service.

> Type=Dynamic

> ### DataSourceINFService

> Sets the value of the Informix SERVICE network parameter used by the SequeLink service.

> Type=Dynamic

> ### DataSourceKeySetDataType

> Specifies the SQL data type of the auto-unique column (ROWID) in a database table. Valid values are:

> SQL_BINARY SQL_CHAR SQL_DECIMAL SQL_DOUBLE SQL_FLOAT SQL_INTEGER SQL_LONGVARCHAR SQL_NUMERIC | SQL_REAL SQL_SMALLINT SQL_TYPE_DATE SQL_TYPE_TIME SQL_TYPE_TIMESTAMP SQL_VARBINARY SQL_VARCHAR

> Examples include:

> DB2 | SQL_BINARY, SQL_TIMESTAMP
> Microsoft SQL Server | SQL_VARCHAR
> Sybase | SQL_NUMERIC
> ODBC Socket and JDBC Socket | Depends on the backend driver

> Type=Dynamic

> NOTE: This service attribute is not used by the SequeLink Server for Informix and SequeLink Server for Oracle.

> ### DataSourceKeySetName

> Specifies the name of the auto-unique column (Rowid) in a database table, as shown in the following examples:

> DB2 | The name of any column that enforces uniqueness of the column data, such as ROWID.
> Microsoft SQL Server | IDENTITYCOL
> Sybase | SYB_IDENTITY
> ODBC Socket and JDBC Socket | Depends on the backend driver

> The default is an empty string.

> Type=Dynamic

> NOTE: This service attribute is not used by the SequeLink Server for Informix and SequeLink Server for Oracle.

> ### DataSourceKeySetOptions

> Specifies the behavior of SQL Select statements with a auto-unique column (Rowid). Valid values are:

> - No_Rowid_with_asterisk, which specifies that a Select statement of the format `SELECT *, ROWID` is not allowed.
> - Rowid_with_group_by, which specifies that a Select statement with ROWID in the Select clause and in a Group By clause is allowed.
> - Rowid_with_order_by, which specifies that a Select statement with ROWID in the Select clause and in a Order By clause is allowed.
> - Rowid_with_table_alias, which specifies that a Select statement with ROWID in the Select clause and a table alias in the From clause is allowed.

> Type=Dynamic

> NOTE: This service attribute is not used by the SequeLink Server for Informix and SequeLink Server for Oracle.

> ### DataSourceKeySetSize

> Specifies the bind size of the auto-unique column (ROWID) in a database table.

> DB2 | 40
> Microsoft SQL Server | 38
> Sybase | 38
> ODBC Socket and JDBC Socket | Depends on the backend driver.

> The default is 0.

> Type=Dynamic

> ### DataSourceLimitCursorColumnSize

> Limits the columnSize of a result set column to an acceptable value. When a default varchar column is created in FileMaker, the database defines it as 1000000 characters. When the application requests a static cursor on a Unicode datasource, the driver reserves 3000000 (UTF-8) bytes in its internal row buffer for this type of column.

> NOTE: In earlier SequeLink releases, this attribute was called DataSourceLimitColumnBindSize.

> Limiting the column size makes the row buffer size smaller and reduces disk access.

> The default is 0. No value is set.

> Type=Dynamic

> ### DataSourceLimitParamBindSize

> Specifies the bind size to use when exporting a table that contains null data in a memo column from Microsoft Access. Microsoft Access binds the parameter with a columnSize of 4294967295. The SequeLink Client attempts to allocate a buffer of this size, and typically fails due to lack of memory.

> To configure the bind size and get around this application bug, set the parameter bind size for SQL_CHAR, SQL_VARCHAR, SQL_BINARY, SQL_VARBINARY values to a reasonable value.

> The default is 0.

> Type=Dynamic

> ### DataSourceLogoffBehaviour

> Specifies the database action that needs to be taken when an abnormal logoff terminates a transaction. When the attribute is not set, the current transaction will be ended according to the database default logoff behavior.

> Valid values are:

> - COMMIT=The current transaction will be committed.
> - ROLLBACK=The current transaction will be rolled back

> Type=Dynamic

> ### DataSourceLogonMethod

> Specifies the data store logon method to be used to log on to the data store. The values you use depend on the SequeLink security configuration. Valid values are:

> - DBMSLogon(DBUID,DBPWD)
> - DBMSLogon(UID,PWD)
> - OSIntegrated

> Setting DataSourceLogonMethod=OSIntegrated means that database authentication relies on the operating system user credentials supplied in the Kerberos ticket. See "ServiceAuthMethods" for more information.

> See "Configuring Data Store Logon" for more information about configuring data source logons refer to the SequeLink Administrator's Guide.

> Type=Dynamic

> ###

> ### DataSourceMaxCpuAction

> Specifies the action to be taken when DataSourceMaxCpuTime is exceeded. Valid values are:

> - LOG=Message VAIS208I is written to VAILOG.
> - ABORT=The connection will be aborted.

> The default is LOG.

> Type=Dynamic

> ### DataSourceMaxCpuTime

> Specifies (in seconds) the total amount of CPU time that the connection is allowed to consume. If unspecified or set to zero (0), the service is not monitored for exceeding total CPU time. Valid values are:

> - 0=Service is not monitored for exceeding total CPU time.
> - CPU time_in_seconds=The number of seconds the connection is allowed to consume.

> The default is 0.

> Type=Dynamic

> ### DataSourceMSSBindAllLOBs

> Specifies which columns will be buffered. Valid values are:

> - True=The SequeLink Server buffers all columns in the result set.
> - False=The SequeLink Server for Microsoft SQL Server does not buffer large object columns that are at the end of a result set. Instead, it uses SQLGetData to get the CLOB/BLOB data as it is requested by the client, which saves memory on the server.

> The default is False.

> Type=Dynamic

> ### DataSourceMSSConnectOptions

> Specifies additional connection options to use when the SequeLink Server connects to Microsoft SQL Server. This string is appended to the connection string. Keyword-value pairs are separated by a semicolon.

> You can use this option to connect to a non-default Microsoft SQL Server instance located on another machine. For example:

>     DataSourceMSSConnectOptions=Server=Belg-John\MSSS2000;SnapshotSerializable=1;

> connects to the Microsoft SQL Server instance named MSSS2000 on the machine Belg-John and enables Snapshot isolation level.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceMSSCursorType

> Specifies the type of cursor the SequeLink Server will use. Valid values are:

> - Serverside=Allows multiple concurrent statements (and cursors) to be active at the same time for each connection.
> - Serverside-Preserve=Server-side cursors that stay open and positioned when a transaction is committed.
> - Clientside=Allows only one active statement/cursor for each connection.

> The default is Serverside.

> Type=Dynamic

> ### DataSourceMSSCursorWarnings

> Microsoft SQL Server sometimes has problems opening server-side cursors for select or stored procedure result sets. This setting masks the warning issued by Microsoft SQL Server each time it encounters this problem. Valid values are:

> - True=The warning is not masked from the client application.
> - False=The warning is masked from the client application.

> The default is False.

> Type=Dynamic

> ### DataSourceMSSLogPath

> Specifies the log path to be used for all ODBC calls executed by the SequeLink data access service.

> Type=Dynamic

> ### DataSourceMSSMapLongToDecimal

> Specifies whether the JDBC Client uses the NUMERIC data types instead of the BIGINT data type. Because Microsoft SQL Server 7 does not support the SQL data type BIGINT, a call to setLong results in an exception. Valid values are:

> - 0=The JDBC Client uses the BIGINT data type for a call to setLong. An exception results, indicating that an optional feature was not implemented.
> - 1=The JDBC Client uses the NUMERIC data type for a call to setLong.

> The default value is 0.

> Type=Dynamic

> ### DataSourceMSSODBCConnStr

> This service attribute is obsolete. Instead, use "DataSourceMSSConnectOptions" to specify additional connection options to use when the SequeLink Server connects to Microsoft SQL Server.

> ### DataSourceMSSODBCLogPath

> This service attribute is obsolete. Use one of the following service attributes:

> - "DataSourceDB2LogPath": Specifies the log path for all CLI calls executed for the data access service for SequeLink Server for DB2.
> - "DataSourceMSSLogPath": Specifies the log path to be used for all ODBC calls executed by the SequeLink data access service.
> - "DataSourceSOCODBCLogPath": Specifies the log path to be used for all ODBC calls executed by the SequeLink data access service for SequeLink Server for ODBC Socket.
> - "DataSourceSYBLogPath": Specifies the log path for all CLI calls executed for the data access service for SequeLink Server for Sybase.

> ### DataSourceName

> Specifies the name of the server data source. The data source name is defined during configuration and cannot be changed afterward.

> The default data source has a fixed name, such as "Default".

> Type=Dynamic

> ### DataSourceORAMapTSWTZ

> Determines whether columns with a TIMESTAMP WITH TIME ZONE data type are mapped to a timestamp data type when they are retrieved from an Oracle 9i or higher database. Valid values are:

> - TRUE=Columns with a TIMESTAMP WITH TIME ZONE data type are mapped to a timestamp data type when they are retrieved.
> - FALSE=An error is generated when TIMESTAMP WITH TIME ZONE columns are retrieved.

> The default is FALSE.

> Type=Dynamic

> ### DataSourceORANumber0IsNumeric

> Specifies how the JDBC Client treats FLOAT columns and columns that are the result of a function (for example, COUNT(*), SUM(...)). Because Oracle describes both types of columns as NUMBER(0,0), the SequeLink Server cannot differentiate between them. SequeLink therefore handles these columns as SQL data type FLOAT. Valid values are:

> - 1=SequeLink treats FLOAT columns and all columns that are the result of a function as SQL data type NUMERIC.
> - 0=SequeLink treats FLOAT columns and all columns that are the result of a function as SQL data type FLOAT.

> The default is 0.

> Type=Dynamic

> ### DataSourceORAPublicSchemaSupp

> Determines whether the Oracle schema named PUBLIC is supported in catalog statements (for example, SQLTables). Valid values are:

> - TRUE=Turns on support.
> - FALSE=Turns off support.

> Type=Dynamic

> ### DataSourceORARecyclebinSupp

> Determines whether database objects in the Oracle recycle bin are shown in the SequeLink catalog statements. Valid values are:

> - TRUE=Database objects in the recycle bin are shown in the SequeLink catalog statements.
> - FALSE=Database objects in the recycle bin are not shown in the SequeLink catalog statements.

> The default is FALSE.

> Type=Dynamic

> ### DataSourceORAReportDBLinkAsCatalog

> Specifies whether DBLinks are reported as catalogs. Valid values are:

> - TRUE=DBLinks are reported as catalogs.
> - FALSE=Catalogs are not supported. Use this value for applications such as Microsoft Access that require consistent catalog reporting behavior.

> The default is FALSE.

> Type=Dynamic

> ### DataSourceORAServiceName

> Specifies the Oracle service name to which the application wants to connect. The valid value is a defined Oracle service name.

> Type=Dynamic

> ### DataSourceORASynDBLinkObjSupp

> Turns on and off support for synonyms of remote Oracle objects in Catalog statements. Valid values are:

> - TRUE=Turns on support.
> - FALSE=Turns off support.

> The default is FALSE.

> Type=Dynamic

> ### DataSourceProviderTypesFile

> Specifies the name of the file that contains the information returned from the OLE DB ProviderTypes call by an ADO provider data source. The file must be located in the SequeLink installation directory.

> Each driver is assigned a specific section name, which is configured in the SequeLink server data source using DataSourceProviderTypesSection.

> The default file is swsoc.ini.

> Type=Dynamic

> ### DataSourceProviderTypesSection

> Specifies the section within the providertypes file that will be used to retrieve OLE DB ProviderTypes information.

> The default is Default.

> Type=Dynamic

> ### DataSourceReadOnly

> Controls read-only access to the SequeLink data access service. Valid values are:

> - No=All statements are allowed.
> - Select=Only Select statements are allowed.
> - Select and batches=Select statements and stored procedures are allowed.
> - DBMS=The read-only capabilities of the database are used.

> NOTE: DBMS is not supported on DB2 for z/OS.

> The default is No.

> Type=Dynamic

> ### DataSourceReportLobsAsLongvar

> Enables the JDBC Client to map BLOB and CLOB data types to LONGVARCHAR or LONGVARBINARY.

> - TRUE=BLOB and CLOB are mapped to LONGVARCHAR or LONGVARBINARY.
> - FALSE=LOBs and getObject on an LOB column use the default behavior for the JDBC Client.

> The default is FALSE.

> Type=Dynamic

> ### DataSourceSchemaFilterList

> A schema name filter for SQLTables and SQLProcedures (ODBC), getTables and getProcedures (JDBC), and TABLES and PROCEDURES (OLE DB/ADO). This attribute is not valid when ServiceCodePage=Database. Valid values are any defined schemas including:

> - list_of_schema_names=A comma-separated list of schemas. Only tables owned by the listed schemas are included in the result set. You can use the % or _ character as a search pattern. You cannot use quotes.
> - CURRENT SCHEMA=Only tables owned by the current user are returned.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceSessionToken

> Specifies a setting that allows easy correlation of the SequeLink session as displayed in SequeLink monitoring/tracing tools, and the RDBMS session as it can be visualized using the RDBMS-specific monitoring/tracing tools.

> Associated with each connection, the SequeLink 6.0 server creates a session token, which is exported to:

> - The SequeLink monitor tree, if a monitor profile with session monitoring enabled is active.
> - The SequeLink event trace, if an event trace profile that has been configured to trace any session-related events is active.
> - An RDBMS-specific session/connection setting, which allows easy correlation of the SequeLink session as displayed in the SequeLink monitor, and the RDBMS session as viewed using RDBMS-specific monitoring and tracing tools.

> If the length of the session token exceeds the allowed length of the DBMS field, the session token is truncated and a warning is issued as shown in the following table:

> DB2 UDB on Linux, UNIX, and Windows | TP Monitor client accounting string
> DB2 on z/OS | Accounting-token (in DB2 statistics and accounting trace records)
> Oracle9 or higher | view v$session:column CLIENT_IDENTIFIER
> SQL Server | Sysprocesses.program_name
> Sybase | table sysprocesses: column clientname

> Valid values are a combination of static text and the following placeholders that will be replaced at runtime by the corresponding values. For example:

> `Session from ${ClientInfo} connected to ${DataSourceName}`

> Placeholder Value | Runtime Value
> --- | ---
> ${ClientApi} | One of JDBC, ODBC, ADMIN, or OLEDB
> ${ClientInfo} | Client IP address or host name
> ${ClientApplName} | Application name provided by the client application through the ApplicationName connect attribute/keyword
> ${DataSourceName} | Name of data source for the current session
> ${ServiceName} | Name of the SequeLink service for the current session
> ${SessionId} | SequeLink session ID
> ${ClientApplId} | Application ID being used for the current session
> ${ClientAutoApplIdDesc} | The text part of the automatic application ID is used for the current session

> Type=Dynamic

> ### DataSourceSLKStcCrsrLngCLBuff

> Turns on a workaround that allows you to specify the amount of data (in KB) that is buffered for SQL_LONGVARCHAR and SQL_LONGVARBINARY columns with a static cursor. For more information about this client attribute, refer to the SequeLink Developer's Reference.

> The default is 4.

> Type=Dynamic

> ### DataSourceSOCEmptyRowSyntax

> Specifies the syntax to use when inserting an empty row into a database table. Valid values are:

> - None: Empty rows cannot be inserted.
> - SQL92: Empty rows can be inserted using SQL92 syntax, for example:

> `INSERT INTO TABLE default_values`

> - EmptyValueList: An empty row with an empty values list can be inserted, for example:

> `INSERT INTO table` values`()`

> - DefaultValueList: An empty row with an empty values list that contains the default keyword for each column in the target database table can be inserted, for example, for a table with two columns:

> `INSERT INTO table` values`(`default`,` default`)`

> - NullValueList, which specifies that an empty row with an empty values list that contains the NULL keyword for each column in the target database table can be inserted, for example, for a table with two columns:

> `INSERT INTO table values (NULL, NULL)`

> Type=Dynamic

> ### DataSourceSOCJDBCConnectOptions

> Specifies additional connection options to use when the SequeLink Service for JDBC Socket connects to the ODBC-to-JDBC bridge. This string will be appended to the connection string.

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> The default value is an empty string.

> Type=Dynamic

> ### DataSourceSOCJDBCConnectionURL

> Specifies the URL string to pass to the JDBC driver to connect to the database. For example, if you are using the Websphere Information Integrator Classic Federation for z/OS (also known as CrossAccess or DB2 II Classic Federation) driver, the value could be:

>     jdbc:dd-crossaccess30:datasource:tcp/host/port:CODEPAGE=USS

> The default value is an empty string.

> Type=Dynamic

> To set up a DataDirect Spy log with the SequeLink Server for JDBC Socket, add the key-value pair spy_log=Spy log specification to the DataSourceSOCJDBCConnectionURL to include the DataDirect Spy driver as follows:

>     DataSourceSOCJDBCConnectionURL=DataSourceSOCJDBCConURL;spy_log=(file)filename

> For example:

>     DataSourceConnectionURL=
>     jdbc:dd-crossaccess30:EXIMS:tcp/10.30.14.109/9001:CODEPAGE=USS};
>     spy_log=(file)/tmp/spy.log

> Other DataDirect Spy options can be specified by adding key-value pairs in which the original Spy-option name is prefixed with spy_. For example:

>     DataSourceConnectionURL=
>     jdbc:dd-crossaccess30:EXIMS:tcp/10.30.14.109/9001:CODEPAGE=USS;
>     spy_log= (file)/tmp/spy.log;spy_timestamp_yes

> ### DataSourceSOCJDBCDbProperties
> Name

> Specifies the name of a JDBC driver/database-specific properties file that contains the configuration values. Valid values are the file name of a properties file minus the .properties extension.

> This properties file is used to set specific database properties that cannot be retrieved by the JDBC driver. In other words, it corrects differences between the ODBC and JDBC APIs. A number of examples are provided, for example, crossaccess30, db2v7mvs, db2v8udb, derby, oracle9i, sqlsrv2000, sybase125.

> If you need a properties file for your specific JDBC driver, contact SequeLink technical support.

> The default value is an empty string.

> Type=Dynamic

> ### DataSourceSOCJDBCDriverClassName

> Specifies the name of the JDBC driver being used to connect to the database. For example, if you are using the SequeLink JDBC driver, the value would be:

> `com.ddtek.jdbc.crossaccess30.CrossAccessDriver`

> The default value is an empty string.

> Type=Dynamic

> ### DataSourceSOCJDBCLogPath

> Specifies the log path to be used for tracing the calls executed by the SequeLink data access service. The valid value is a defined path for a log file.

> Type=Dynamic

> ### DataSourceSOCJDBCReadLongDataLength

> Specifies whether the SequeLink Server for JDBC Socket can cache long data in order to read the length and provide this information to the application. Valid values are:

> - TRUE=The SequeLink Server for JDBC Socket can cache long data. This setting can affect performance.
> - FALSE=The SequeLink Server for JDBC Socket cannot cache long data.

> Type=Dynamic

> ### DataSourceSOCODBCConnStr

> Specifies the connection string used by a SequeLink client application for a connection to an ODBC system data source. When the application provides the optional DBMS user name, password and database values, the values will be appended to the values of the UID, PWD, and DB keywords provided by the client when connecting to the ODBC Socket. The data source specified in the value for this attribute must be a system ODBC data source on Windows.

> Example 1

> Suppose you want to connect to a Microsoft Access database. You use DataSourceSOCODBCConnStr to connect to the Microsoft Access driver. You specify the backend ODBC data source name for DataSourceSOCODBCConnStr, for example, DSN=MS_Access_2003.

> You can also specify other connection options to overwrite the backend ODBC data source settings that were specified in the ODBC Administrator. For example, the data source MS_Access_2003 is set up to access the database D:\DATA\MSACCESS\db1.mdb.

> Example 2

> Suppose you want to access two Access databases (db1.mdb and db2.mdb) with one SequeLink Service Socket for ODBC.

> First, you create an ODBC data source for your application that uses the SequeLink ODBC driver, specifying only the host and port of the SequeLink Server Socket for ODBC in the ODBC administrator. In this case, you connect to the default SequeLink Server data source, which is configured to access db1.mdb.

> To access db2.mdb, you create a new SequeLink server data source, for example, SLAccess_db2mdb, using the SequeLink Command Line Administrator or the SequeLink MMC snap-in.

> After creating this new SequeLink server data source, the service attribute DataSourceSOCODBCConnStr contains DSN=MS_Access2003.

> Change this value to DSN=MS_Access2003;DBQ=D:\DATA\MSACCESS\db2.mdb.

> On the client side, specify the SequeLink server data source SLAccess_db2mdb in your connection string or define it in your ODBC data source.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceSOCODBCLogPath

> Specifies the log path to be used for all ODBC calls executed by the SequeLink data access service for SequeLink Server for ODBC Socket. The valid value is a defined path for a log file.

> Type=Dynamic

> NOTE: This service attribute replaces DataSourceMSSODBCLogPath, which was used in earlier versions of SequeLink.

> ### DataSourceSybConnectOptions

> Specifies additional connection options to use when the SequeLink server connects to the Sybase DBMS. This string will be appended to the connect string.

> Valid connection options include:

> CharSet | Use the CharSet connection option only on Windows when ServiceCodePage=OS. Use CS=cp`ACP`, where `ACP` is determined through the registry (see earlier for an explanation on how to find this out). On a typical English Windows installation, use CS=cp1252.
> IANAAppCodePage | Use the IANAAppCodePage connection option only on Linux/UNIX when ServiceCodePage=OS. Use IANAAppCodePage=`value`, where `value` refers to an entry in Table D-11, namely IANAAppCode value. In order to find the correct value to use, you must map the value that is specified in the LC_ALL environment variable to one of the entries in Table D-11 using the first column of the table.

> Table D-11. Values for DataSourceSybConnectOptions
> OS Code Page | Description1 | IANAAppCodePage Value
> --- | --- | ---
> ascii_8 | US_ASCII | 3
> big5 | Big5 | 2026
> cp437 | IBM437 | 2008
> cp850 | IBM850 | 2009
> cp852 | IBM852 | 2013
> cp855 | IBM855 | 2046
> cp857 | IBM857 | 2047
> cp860 | IBM860 | 2048
> cp864 | IBM864 | 2051
> cp866 | IBM866 | 2052
> cp869 | IBM869 | 2054
> cp1250 | WINDOWS_1250 | 2250
> cp1251 | WINDOWS_1251 | 2251
> cp1252 | WINDOWS_1252 | 2252
> cp1253 | WINDOWS_1253 | 2253
> cp1254 | WINDOWS_1254 | 2254
> cp1255 | WINDOWS_1255 | 2255
> cp1256 | WINDOWS_1256 | 2256
> cp1257 | WINDOWS_1257 | 2257
> cp1258 | WINDOWS_1258 | 2258
> iso_1 | ISO_8859_1 | 4
> iso88592 | ISO_8859_2 | 5
> iso88595 | ISO_8859_5 | 8
> iso88596 | ISO_8859_6 | 9
> iso88597 | ISO_8859_7 | 10
> iso88598 | ISO_8859_8 | 11
> iso88599 | ISO_8859_9 | 12
> iso885915 | ISO_8859_15 | 111
> koi8 | KOI8_R | 2084
> roman8 | roman8 | 2004
> sjis | sjis | 17
> tis620 | tis620 | 2259

> 1Depending on the version of Linux/UNIX that you are using, the actual description of the code page will be different.

> The default is an empty string.

> Type=Dynamic

> ### DataSourceSYBLogPath

> Specifies the log path for all CLI calls executed for the data access service for SequeLink Server for Sybase.

> Type=Dynamic

> NOTE: This service attribute replaces DataSourceMSSODBCLogPath, which was used in earlier versions of SequeLink.

> ### DataSourceSybNetworkAddress

> Specifies the Sybase network address. This string will be appended to the connect string.

> The default is installation-dependent.

> Type=Dynamic

> ### DataSourceTableTypeFilterList

> Specifies a table-type filter for SQLTables (ODBC), getTables (JDBC), and TABLES and PROCEDURES (OLE DB/ADO). This attribute is not applicable when ServiceCodePage=database.

> The valid value is a comma-separated list of table types. Valid table types on this platform are:

> - ALIAS
> - GLOBAL
> - SYNONYM
> - SYSTEM TABLE
> - TABLE
> - VIEW

> The default is an empty string.

> Type=Dynamic

> ### DataSourceThreadMaxRpc

> Specifies the number of connection requests that will be accepted before the thread allocated to the connection is released to the thread pool. Valid values are from 0 to 1 000.

> If 0 is specified, the thread is only released when the connection terminates.

> The default is 10.

> Type=Dynamic

> ### DataSourceThreadRpcTimeOut

> Specifies the idle time (in milliseconds) for threads allocated to connections. Once this value is reached, the thread allocated to the connection is released to the thread pool. Valid values are from 0 to 1 000 000.

> Specify 0 to disable the timeout mechanism.

> The default is 2 000.

> Type=Dynamic

> ### DataSourceTransactionIsolation

> Specifies the transaction isolation level used for the connection. Valid values are:

> Committed | Dirty reads are not possible. Phantoms and reads that cannot be repeated are possible.
> Uncommitted | Phantoms, dirty reads, and reads that cannot be repeated are possible.
> RepeatableRead | Dirty reads and reads that cannot be repeated are not possible. Phantoms are possible.
> Serializable | Transactions can be serialized. Phantoms, dirty reads, and reads that cannot be repeated are not possible.
> Not supported | SequeLink cannot set the transaction isolation level. The DBMS default transaction isolation level will be used.

> Refer to your database documentation for a definition of each isolation level.

> For DB2 UDB on z/OS: The default is Committed. The Not Supported value is not allowed.

> All other DBMS: The default is Not Supported.

> Type=Dynamic

> ### DataSourceWorkArounds

> Turns on workarounds that allow you to take full advantage of the ODBC driver with ODBC applications requiring nonstandard or extended behavior.

> When this attribute is set in the configuration file, it is valid for all clients that connect to SequeLink. When you add this attribute in the connection string, it is set for that client connection only.

> Refer to the SequeLink Developer's Reference for more information about connecting using a connection string.

> IMPORTANT: Each of these options has potential side effects related to its use. An option should only be used to address the specific problem for which it was designed.

> - 1= If an ODBC driver reports to Microsoft Access 2.0 that its SQL_CURSOR_COMMIT_BEHAVIOR or SQL_CURSOR_ROLLBACK_BEHAVIOR is 0, Microsoft Access opens tables as read-only. If this option is on, the ODBC driver returns 1, allowing Microsoft Access to open tables as read-write.
> - 2=Some applications cannot handle database qualifiers. If this option is on, the driver reports that qualifiers are not supported.
> - 4=Visual Basic 4.0 sometimes requires two connections to a DBMS. For DBMSs that support only a single connection, the second attempt fails. If this option is on, the driver detects when this condition occurs and has the two ODBC connections share a single physical connection to the DBMS.
> - 8=If an ODBC driver cannot detect the number of rows affected by an Insert, Update, or Delete statement, it may return -1 in SQLRowCount. Some products cannot handle this. Turning this option on causes the driver to return 1 instead.
> - 16=If an ODBC driver in SQLStatistics reports to Microsoft Access 1.1 that an INDEX_QUALIFIER contains a period, Microsoft Access returns a tablename is not a valid name error. If this option is on, the driver returns no INDEX_QUALIFIER, allowing Microsoft Access to open the table.
> - 32=This option allows users of flat-file drivers to abort a long-running query by pressing the ESC key.
> - 64=This option results in a column name of Cposition where position is the ordinal position in the result set. For example:

> SELECT col1, col2+col3 FROM table1

> produces the column names col1 and C2. SQLColAttributes/
> SQL_COLUMN_NAME returns an empty string for result columns that are expressions. Use this option for applications that cannot handle empty strings in column names.

> - 256=Forces SQLGetInfo/SQL_ACTIVE_CONNECTIONS to be returned as 1.
> - 512=To prevent ROWID results, this option forces the SQLSpecialColumns function to return a unique index as returned from SQLStatistics.
> - 2048=This option results in SQLDriverConnect returning "Database='' instead of "DB='' in the returned connection string.
> - 65536=This option strips trailing zeros from decimal results, which prevents Microsoft Access from generating an error when decimal columns containing trailing zeros are included in the unique index.
> - 131072=This option turns all occurrences of the double quote character ("") into the accent grave character (`). Some applications always quote identifiers with double quotes. Double quoting causes problems for data sources that do not return SQLGetInfo/SQL_IDENTIFIER_QUOTE_CHAR = ".
> - 524288=This option overrides the precision and scale settings for SQL_DECIMAL parameters to precision 40 and scale 20.
> - 8388608=This option causes SQLGetInfo/SQL_DATABASE_NAME to be returned as an empty string when SQLGetInfo/SQL_MAX_QUALIFIER_NAME_LEN is 0. This option should be used with Inprise/Borland tools, such as Delphi.
> - 536870912=This option allows SQLBindParameter to be called after SQLExecute to change the precision of previously bound parameters.
> - 1073741824=Microsoft Access assumes that ORDER BY columns do not have to be in the SELECT list. This option provides a workaround for data stores that always use ORDER BY columns.

> The default is 0.

> Type=Dynamic

> ### DataSourceWorkarounds2

> Turns on workarounds that allow you to take full advantage of the ODBC driver with ODBC applications requiring nonstandard or extended behavior.

> When this attribute is set in the configuration file, it is valid for all clients that connect to SequeLink. When you add this attribute in the connection string, it is set for that client connection only.

> Refer to the SequeLink Developer's Reference for more information about connecting using a connection string.

> IMPORTANT: Each of these options has potential side effects related to its use. An option should only be used to address the specific problem for which it was designed.

> - 2=Some applications incorrectly specify the ColumnSize/DecimalDigits when binding timestamp parameters. This option causes the driver to ignore the ColumnSize/DecimalDigits specified by the application and use the database defaults instead.
> - 4=Microsoft Access uses the most recent native type mapping, as returned by SQLGetTypeInfo, for a specific SQL type. This option reverses the order in which types are returned, so that Microsoft Access will use the most appropriate native type. This option is recommended if you are using Microsoft Access against an Oracle data store.
> - 32=Microsoft Access does require that the characters "DSN=" are returned by SQLDriverConnect in the connection string output parameter.

> Type=Dynamic

> ### DataSourceWorkaroundsXliteration

> Turns on multiple transliteration workarounds that resolve transliteration issues between Shift-JIS/Windows-31j and EUC-JP by mapping "look-alike" characters:

> - 0=Transliteration workarounds are not enabled.
> - 1=This option identifies a database that stores character data from the Shift-JIS/Windows-31j character set.
> - 2=This option identifies a database which stores character data from the EUC-JP character set.

> The default is 0.

> Type=Dynamic

> ###

> ### MVSDataSourceDB2Plan

> Specifies the DB2 plan name used by the data source. This attribute is required only when MVSGlobalDB2Attachment=CAF (see "MVSGlobalDB2Attachment").

> The default is SLD600PL.

> Type=Dynamic

> ###

> ### MVSDataSourceMaxStmtLength

> Specifies the maximum length of a SQL statement that the SequeLink Server for DB2 on z/OS can handle.

> This setting is only effective for DB2 v8 or higher (new function mode). For DB2 v7 or DB2 v8 (compatibility mode), this setting has no effect; the maximum statement is limited to 32700 bytes.

> The default is 128 KB.

> Type=Dynamic

> ###

> ###

> ### MVSDataSourceUIDMap

> Specifies the name of a user ID (UID) map. UID maps can be referenced at both the service and data source level. The valid value is a defined UIDMap name.

> A UID map specified with MVSDataSourceUIDMap takes precedence over the UID map specified in the SequeLink service (see the attribute "MVSServiceUIDMap"). If neither MVSDataSourceUIDMap or MVSServiceUIDMap is specified, no UID map is used.

> The default is an empty string. The default for the data source level UIDMap is the UID map specified for the SequeLink service.

> Type=Dynamic

> ###

> ### MVSDB2ExitLibrary

> Specifies the name of the fully qualified DB2 exit-library (without quotes) for this DB2 interface used to generate JCL. Valid values are z/OS data set names.

> NOTE: This library must be APF-authorized.

> Type=Static

> ###

> ### MVSDB2LoadLibrary

> Specifies the name of the fully qualified DB2 load-library (without quotes) for this DB2 interface used to generate JCL. Valid values are z/OS data set names.

> NOTE: This library must be APF-authorized.

> Type=Static

> ###

> ### MVSDB2RootDescription

> Specifies a general description of the DB2 interface. The valid value is a defined DB2 interface.

> Type=Static

> ###

> ### MVSDB2SubsystemName

> Specifies the subsystem ID of the DB2 address space. The valid value is a defined interface ID.

> The default is MVSDB2InterfaceID.

> Type=Static

> ###

> ### MVSDB2Version

> Specifies the DB2 version of the DB2 interface. Valid values are:

> - V710
> - V810
> - V910

> Type=Static

> ###

> ### MVSGlobalClustername

> Specifies the clustername to which the SequeLink Server must register for DNS/WLM-supported Sysplex connection distribution.

> Type=Static

> ###

> ### MVSGlobalCommandChar

> This attribute is obsolete.

> ###

> ### MVSGlobalCompTrace

> Turns on and off tracing for server core components. Valid values are ALL or one of the following component_IDs:

> C - Core components
> D - DB2 component
> L - Generic Log component
> S - Server controller component
> T - Threadpool component

> If unspecified, no tracing will be performed.

> The default is no component trace.

> Type=Static

> ###

> ### MVSGlobalDB2Attachment

> Specifies the type of DB2 attachment to be used for the DB2 service.

> MVSGlobalDB2Attachment=RRSAF can only be used when RRS is active. Valid values are:

> - CAF
> - RRSAF

> The default is RRSAF.

> NOTE: When ServiceConnectionModel=Threadpool is selected, RRSAF must be selected.

> Type=Static

> ###

> ### MVSGlobalDescCode

> Specifies the WTO descriptor code for all messages directed to a console by the message logging task. The valid value is a defined WTO descriptor code.

> The default is 06.

> Type=Static

> ###

> ### MVSGlobalID

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> Specifies an identifier to make this "section" unique. This attribute must be set to GLOBAL and must not be changed.

> The default is GLOBAL.

> Type=Static

> ###

> ### MVSGlobalRouteCode

> Specifies the WTO route code for all messages directed to a console by the message logging task. The valid value is a defined WTO route code.

> The default is 11.

> Type=Static

> ###

> ### MVSGlobalSMFRecordType

> Specifies the System Management Facility (SMF) record type to be used for SMF records produced by the server. Valid values are from 128 to 255.

> If 0, SMF recording is turned off.

> If unspecified, no SMF records are produced.

> If you set this value to a positive number, you must inform the system of these records by changing the z/OS SMF parameters in the SMFPRMxx member of the SYS1.PARMLIB data set. You can activate the collection of these records using the SET command.

> The recommended value is 197.

> Type=Static

> ###

> ### MVSGlobalSosLimit

> Specifies the global short-on-storage (SOS) limit, which is the total amount of private storage (in KB) that must be available in the address space to accept further connections. If this amount of storage is unavailable, the incoming connections will be rejected. To turn this feature off, specify 0 or delete this attribute. Valid values are from 0 to 2048.

> The default is 1024.

> Type=Static

> ###

> ### MVSGlobalSubSysID

> Specifies an ID that the SequeLink Server will use as a suffix to construct a unique ResourceManager name to register to RRS. This is a required parameter when MVSGlobalDB2Attachment=RRSAF.

> The default is SQLK.

> Type=Static

> ###

> ### MVSGlobalWLMEnclaves

> Specifies whether the server address space will use WLM enclaves. Valid values are:

> - NONE=The server address space will not use WLM enclaves.
> - CONNECTION=One new WLM enclave is created for the duration of the connection.
> - RPC=A new WLM enclave is created for every SequeLink RPC (each network access to the SequeLink Server).

> The default is NONE.

> Type=Static

> ###

> ### MVSServiceAdminAuthorizationClass

> Specifies a general resource class name to be used by the server.

> The default is FACILITY.

> Type=Dynamic

> ###

> ### MVSServiceAdminAuthorizationEnable

> Enables authorization for the SequeLink Agent service. Valid values are:

> - TRUE=MVSServiceAdminAuthorizationClass and/or MVSServiceAdminAuthorizationResource take effect for authorization of your resources with the security manager on z/OS.
> - FALSE=Authorization is disabled.

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> The default is FALSE.

> Type=Dynamic

> ###

> ### MVSServiceAdminSecurity

> This attribute is obsolete. Instead, use MVSServiceAdminAuthorization.

> ###

> ### MVSServiceAdminSecurityClass

> This attribute is obsolete. Instead, use MVSServiceAdminAuthorizationClass.

> ###

> ### MVSServiceAdminSecurityResource

> This attribute is obsolete. Instead, use MVSServiceAdminAuthorizationResource.

> ###

> ### MVSServiceAuthorizationClass

> Specifies a general resource class name used by the SequeLink Server when authorization is enabled. The valid value is a string.

> The default is FACILITY.

> Type=Dynamic

> ###

> ### MVSServiceAuthorizationEnable

> Enables authorization for the data access service. Valid values are:

> - TRUE=MVSServiceAuthorizationClass and/or MVSServiceAuthorizationResource take effect for authorization of your resources with the security manager on z/OS.
> - FALSE=Authorization is disabled.

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> Type=Dynamic

> ###

> ### MVSServiceAuthorizationResource

> If MVSServiceAuthorization is enabled, the resource name is used to validate a connection request against the z/OS security system. If the attribute's value is blank or an empty string, the server uses the service name as the resource name to be checked.

> NOTE: The value specified for the data source takes precedence over the value specified for the SequeLink service.

> The default is the service name.

> Type=Dynamic

> ###

> ### MVSServiceDataSourceAuthorization

> Specifies that RACF resource security is used for this server data source. When the resource-based authorization has been set up, you can specify resource-based authorization for your server-side data source by setting this attribute to TRUE. See "MVSServiceAuthorizationResource" for information about defining the name of the SequeLink server data source.

> The default is FALSE.

> Type=Dynamic

> ###

> ### MVSServiceDataSourceSecurity

> This attribute is obsolete. Instead, use MVSServiceDataSourceSecurity.

> ###

> ### MVSServiceDB2InterfaceID

> Specifies the ID of a DB2 interface. A DB2 interface is a set of parameters that describe a DB2 subsystem which can be accessed by the SequeLink Server for z/OS.

> Type=Static

> ###

> ### MVSServiceLoadModule

> Specifies the name of the load module for the service. Valid values are uppercase.

> The default is VAISTHRD (for SequeLink Server for DB2 services).

> Type=Static

> ###

> ### MVSServiceSecurity

> This attribute is obsolete. Instead, use MVSServiceAuthorizationEnable.

> ###

> ### MVSServiceSecurityClass

> This attribute is obsolete. Instead, use MVSServiceAuthorizationClass.

> ###

> ### MVSServiceSecurityResource

> This attribute is obsolete. Instead, use MVSServiceAuthorizationResource.

> ###

> ### MVSServiceUIDMap

> Specifies the name of a user ID (UID) map. The valid value is a defined UIDMap name. A UID map specified in the server data source takes precedence over the UID specified in the SequeLink service (see "MVSDataSourceUIDMap").

> If this attribute is not specified, it is possible to have some data sources that use UID maps while other data sources do not.

> The default is an empty string.

> Type=Dynamic

> ###

> ### MVSUID

> Specifies an entry in the user ID (UID) map. The format of this entry is: user=mapped_user or *=mapped_user, where:

> - user is a valid user or user group for the z/OS security system
> - * is a wildcard for any user
> - mapped_user is a valid DB2 authorization ID

> *=mapped_user is required when anonymous authentication is configured for the z/OS server (ServiceAuthMethods=Anonymous).

> Type=Dynamic

> ###

> ### MVSUIDDefaultAccess

> Specifies the default action for a user ID (UID) map. A UID map set in the server data source takes precedence over a UID map set in the SequeLink service. If the server data source does not specify a UID map, the UID map defined in the SequeLink service is used.

> Valid values are:

> - PERMIT=If user ID mapping is set for the SequeLink service or data source and the user ID cannot be found in the UID map, the connection is accepted.
> - DENY=If user ID mapping is set for the SequeLink service or server data source and the user ID cannot be found in the UID map, the connection is refused.

> Type=Dynamic

> ###

> ### MVSUIDMapDescription

> Specifies a general description of the user ID (UID) mapping table. The valid value is a defined user ID map name.

> ### Type=Dynamic

> ### ServiceAdminAuthMethods

> Specifies one or multiple authentication mechanisms that the SequeLink Manager can use to authenticate itself to the server. Valid values are:

> - anonymous
> - OSLogon(UID,PWD)
> - kerberos
> - integrated_nt

> See "Configuring SequeLink® Security" for more information about SequeLink security features.

> Type=Dynamic

> ### ServiceAdministrator

> Sets authorization for users who are allowed to manage SequeLink services using the SequeLink Manager.

> NOTES:

> - On Windows, users who are allowed to manage SequeLink services using the SequeLink Manager must have administrator rights.
> - On Linux, UNIX, and Windows, specify everyone when ServiceAuthMethod=anonymous.

> Valid values for the ServiceAdministrator attribute are:

> - user_name=The user ID of a user who is allowed to use the SequeLink Manager. To configure authorization for multiple users, you must set this attribute multiple times, one instance of the attribute for each user. For example:

> ServiceAdministrator=RSMITH

> ServiceAdministrator=DJONES

> ServiceAdministrator=TCONRAD

> NOTE: On Windows servers, you must prefix the user ID with the Windows server name or the Windows domain name, for example, SALES\DJONES. When connecting, the user must also prefix the user ID with the Windows server name, if connecting to a local server, or the Windows domain name.

> NOTE: Alternatively, you can set the ServiceAdministratorGroup attribute to configure authorization for groups of users defined on Linux, UNIX, or Windows. See "ServiceAdministratorGroup" for more information about configuring authorization for user groups on Linux, UNIX, and Windows.

> - authenticated=Any user who can provide a valid host user ID and password or who uses Integrated authentication will receive the same authorization.
> - everyone=All connections will receive the same authorization level, regardless of how they are authenticated.

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> Type=Dynamic

> ### ServiceAdministratorGroup

> Sets authorization for defined Linux, UNIX, and Windows user groups who are allowed to manage SequeLink services using the SequeLink Manager. Valid values are user groups defined on Linux, UNIX, and Windows.

> To configure authorization for multiple user groups, you must set the ServiceAdministrator attribute multiple times, one time for each user group. For example:

>     ServiceAdministratorGroup=SLUSERG1
>     ServiceAdministratorGroup=SLUSERG2
>     ServiceAdministratorGroup=SLUSERG3

> NOTE: On Windows servers, you must prefix the user group ID with the Windows server name or the Windows domain name where the group is defined, for example, SALES\SLUSERG1.

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> Type=Dynamic

> ### ServiceAdminKerberosPrincipalName

> Specifies the case-sensitive service principal name to be used for Kerberos authentication for the SequeLink Agent service. Use this attribute to specify another service principal name other than the default service principal name. The name must match the service principal name in the KDC.

> For example:

>     SLDB2UDB60/server1.eu.datadirect.com@XYZ.COM
>     DB2SRV/IRONFLEX.DATADIRECT.COM@IRONFLEX.TEST

> Default=host`/`fully_qualified_domain_name`@`REALM

> Type=Dynamic

> For information about specifying a service principal name to be used for Kerberos authentication to a SequeLink data access service, see "ServiceKerberosPrincipalName".

> ### ServiceAuthMethods

> Specifies one or multiple authentication mechanisms the service accepts. The client must select the supported mechanism to authenticate itself to the server.

> Valid values are:

> Windows | anonymous OSLogon(UID,PWD) OSLogon(HUID,HPWD) OSLogon(UID,PWD,NPWD) OSLogon(HUID,HPWD,NPWD) kerberos integrated_nt
> Linux/UNIX | anonymous OSLogon(UID,PWD) OSLogon(HUID,HPWD) kerberos
> z/OS | Anonymous Kerberos OSLogon(UID,PWD) OSLogon(HUID,HPWD) OSLogon(UID,PWD,NPWD) OSLogon(HUID,HPWD,NPWD)

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> NOTE: UID mapping is required when ServiceAuthMethods=Anonymous.

> Type=Dynamic

> ### ServiceAuthorizedAdminClient

> Specifies one or multiple client TCP/IP network identifiers that are allowed to access the service using an administrator client. Use configuration values to limit the clients that are allowed administrative connections to the agent service.

> This attribute supports both address and name formats as shown in the following examples:

> Client TCP/IP host name | `burner.ddtek.com`
> Client TCP/IP domain names through the use of a wild card | `192.16.2.*` or *.`ddtek.com`
> Client TCP/IP address | `127.0.0.1??`
> Client TCP/IP address range | 192.16.*.*

> NOTE: When using host names, ServiceResolveHostNames must be set to True, and only primary domain names can be used.

> To configure multiple TCP/IP location filters, you must set the ServiceAuthorizedAdminClient attribute multiple times, one instance for each location filter. For example:

>     ServiceAuthorizedAdminClient=192.16.*.*
>     ServiceAuthorizedAdminClient=192.17.*.*
>     ServiceAuthorizedAdminClient=192.18.*.*

> See "TCP/IP Location Filters" for more information.

> Type=Dynamic

> ### ServiceAuthorizedClient

> Specifies one or multiple client TCP/IP network identifiers that are allowed to access the service using a client application. Use configuration values to limit the number of clients that are allowed data access connections to data access services.

> The attribute supports both address and name formats as shown in the following examples:

> Client TCP/IP host name | `burner.ddtek.com`
> Client TCP/IP domain names through the use of a wild card | 192.16.2.* or *.ddtek.com
> Client TCP/IP address | `127.0.0.1`
> Client TCP/IP address range | 192.16.*.*

> NOTE: When using host names, ServiceResolveHostNames must be set to True, and only primary domain names can be used.

> To configure multiple TCP/IP location filters, you must set the ServiceAuthorizedClient attribute multiple times, one instance for each location filter. For example:

>     ServiceAuthorizedClient=192.16.*.*
>     ServiceAuthorizedClient=192.17.*.*
>     ServiceAuthorizedClient=192.18.*.*

> See "TCP/IP Location Filters" for more information.

> Type=Dynamic

> ### ServiceCancelEnabled

> Specifies whether cancelling connection requests using SQLCancel is supported. Valid values are:

> - TRUE=yes
> - FALSE=no

> The default is TRUE.

> Type=Static

> ### ServiceCatchExceptions

> Specifies how the SequeLink service will handle exceptions. Valid values are:

> - TRUE=The service will attempt to recover from unexpected exceptions.
> - FALSE=The exception is passed to the operating system resulting in an error or core dump.

> The default is TRUE.

> Type=Static

> ###

> ### ServiceCodePage

> Controls transliteration for the SequeLink service. Valid values are:

> - Default=SequeLink supports standard ASCII/EBCDIC transliteration for ODBC and OLE DB/ADO Clients, and transliteration to UTF-16 for JDBC and .NET Clients.
> - OS=The client transliterates character data from the code page the SequeLink service is using to the code page of the client application/system.
> - Database=Internationalization support features are enabled. The SequeLink Client uses the optimal encoding to exchange character information between client and server. This value minimizes the amount of transliteration required. Graphic data types are always supported.

> NOTE: The Database value is supported only for the ODBC, JDBC, and .NET Clients. This value cannot be used with SequeLink Server for Informix.

> The default is Default.

> Type=Dynamic.

> ###

> ### ServiceCodePageMap

> Controls transliteration for the SequeLink service when the code page retrieved from the operating system or database is not recognized. When ServiceCodePage is set to OS or Database, operating system- or database-specific code pages can be mapped to the IANA character set name, overwriting or extending the service built-in mappings. For more information about the IANA character set, refer to the IANA Web site.

> The format of the value depends on the type of mapping that is being extended. In general, the value is a semi-colon separated list of values, where the first or second value specified is the code page value retrieved from either the operating system or the database. The ianaName is the official IANA identifier for the code page.

> Valid values are:

> - OS=The code page value returned from the operating system. The syntax is

> OS code page identifier;ianaName;

> - Oracle9=The code page value returned from an Oracle 9.x or higher database. The syntax is:

> charSetId;oracleName;ianaName;[maxByteSz;fixedWidth;]

> Type=Dynamic

> ### ServiceConnectInfo

> Specifies the TCP/IP port on which the service is listening for connection requests. The port is specified using the syntax:

> tcp://host.port

> where host is the name of the host on which the SequeLink service runs and port is an available TCP port.

> Type=Static

> ### ServiceConnectionModel

> Specifies the connection model to be used for connections to the SequeLink service. If you change to another connection model, you must delete and recreate any monitoring or event trace profiles. Valid values are:

> - ThreadPool=A pool of threads is created with ServiceMinThreads prestarted threads and maximum ServiceMaxThreads threads. This thread pool is used to service client connection requests.
> - Process/Connection=SequeLink creates a separate OS process to service client connection requests. (Not valid for z/OS.)
> - Thread/Connection=SequeLink creates a separate thread for each client connection requests.

> The default is ThreadPool.

> Type=Static

> ###

> ### ServiceDB2MaxThreads

> Limits the number of DB2 threads used by the SequeLink DB2 service. This value must be higher than the value of the ServiceMaxThreads parameter and lower than the value of the MAX_BATCH_CONNECT parameter in the Thread Management panel (DSNTIPE) of the DB2 installation.

> A value of 0 means that the number of threads will not be limited by the SequeLink DB2 service.

> The default is 0.

> Type=Dynamic

> ###

> ### ServiceDB2MaxTransactions

> Specifies the number of DB2 transactions that a DB2 thread is allowed to service before it is closed. This ensures that when the DB2 thread terminates, the locks set on temporary tables are released.

> A value of 0 means that the DB2 thread is not terminated.

> The default is 0.

> Type=Dynamic

> ###

> ### ServiceDB2MinThreads

> Specifies the number of reusable DB2 threads that will not be released by the release timer routine or by the RRS RELEASE operator command.

> A value of 0 means that all reusable DB2 threads that exceed an age of 300 seconds will be released.

> The default is 0.

> Type=Dynamic

> ###

> ### ServiceDBConnectionPooling

> Enables the connection pooling feature in the Driver Manager that is used for SequeLink Server for ODBC Socket and SequeLink Server for JDBC Socket on Windows. Valid values are:

> - Disabled=The Driver Manager's connection pooling feature is disabled.
> - Enabled=Connection pooling is enabled. Using connection pooling can result in significant performance improvements.

> The default is Disabled.

> Type=Static

> ### ServiceDeadClntDetInt

> Specifies the interval (in seconds) between requests that are sent from the SequeLink Server to the SequeLink Client to verify the availability of the SequeLink Client. Valid values are 0 and any integer from 61 to 1000000.

> A value of 0 disables the dead client detection feature.

> The default is 600.

> Type=Static

> ### ServiceDebugLogLevel

> Specifies the level of detail for messages logged in the debug log file. One or multiple message levels can be enabled/disabled. Valid values are:

> - Fatal
> - Error
> - Warnings
> - Information
> - Debug
> - SSP Packet log
> - SSP Requests

> The default is Fatal.

> NOTE: The value of this attribute is a bitmask with each bit having the following decimal values when turned on:

> Fatal: Bit 0=1
> Error: Bit 1=2
> Warnings: Bit 2=4
> Information: Bit 3=8
> Debug: Bit 4=16
> SSP Packet Log: Bit 5=32
> SSP Requests: Bit 6=64

> If you set this attribute using a SequeLink Manager command that prompts for a decimal value, such as the ServiceAttributeReplace command, the value you set must equal the total decimal value of the bits you want to turn on. For example, if you want to turn all bits on, meaning all options would be logged, you would set the attribute to 127 (1+2+4+8+16+32+64=127). To turn off all bits, set the attribute to 0.

> Type=Dynamic

> ### ServiceDebugLogPath

> Specifies the directory where debug log files are written. If the log path is fully specified, the log is written to the specified directory. If only a filename is specified, the log file is written in the install_dir\logging directory.

> Contains the directory in which debug log files will be written.

> Specifies a UNIX System Services HFS directory to which Log files will be written.

> The default is none.

> Type=Static

> ### ServiceDescription

> Specifies a general description of the SequeLink service.

> Type=Static

> ### ServiceDetailedOSLogonErrors

> Specifies what type of error will be returned when the OSLogon based authentication fails. Valid values are:

> - TRUE=A detailed error will be returned.
> - FALSE=A generic error will be returned.

> The default is TRUE.

> Type=Dynamic

> ### ServiceEncryptionAlgorithm

> Specifies the data scrambling algorithm used when sending requests or replies across the network between client and server. Valid values are:

> - None
> - DES
> - 3DES
> - Byteswap

> The default is None, which means cleartext.

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> Type=Static

> ### ServiceEnvironmentVariable

> Specifies a list of variables that will be set before the SequeLink service is started. The syntax for valid values is varname=value. For example, ORACLE_SID=ORA10g.

> To define more than one variable, you must add more than one instance of the attribute to your service.

> Examples:

> - To specify the Shared library path for the ODBC-to-JDBC bridge and the JVM LIBPATH , where LIBPATH is:
> - LIBPATH on AIX and z/OS USS
> - LD_LIBRARY_PATH on Solaris and Linux
> - SHLIB_PATH on HP-UX
> - PATH on Windows

> For example, on Windows:

>     ServiceEnvironmentVariable=PATH=D:\Programs\java\j2sdk1.4.2_05\jre\bin\
>     server;D:\Programs\java\j2sdk1.4.2_05\jre\bin

> - To specify options used by the backend JDBC Driver:

>     ServiceEnvironmentVariable=SL_JAVA_OPTIONS=-Xms32m -Xms64m -Xcomp -verbose

> - To specify the directory for the license ini file on Linux or UNIX:

>     ServiceEnvironmentVariable=ISLVINI=/usr/sl60/server/ipe

> - To configure the SequeLink Oracle service to use the Oracle Net Service on Windows:

> ServiceEnvironmentVariable=LOCAL=NetServiceName

> where `NetServiceName` is the Oracle Net service name. See "Configuring a SequeLink® Service for Oracle" for detailed instructions on configuring this SequeLink service.

> Type=Static

> ### ServiceEventTraceLocation

> Specifies the directory where the event trace file is located. The valid value is an existing directory.

> The default is an empty string.

> Type=Static

> ### ServiceEventTraceSize

> Specifies the size (in bytes) of the event trace file. Valid values are from 10 000 to 2 000 000 000. On z/OS, the specified value is rounded to a 4 KB page value.

> The default is 1 000 000.

> Type=Static

> ### ServiceEvQGetNrEventsMax

> Specifies the number of events to get from the event queue in one read operation.

> The default is 10.

> Type=Static

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> ### ServiceEvQPingTimeout

> Specifies the timeout (in milliseconds) the SequeLink Agent will wait for a SequeLink data access service response while determining whether the service is started.

> The default is 1000.

> Type=Static

> ### ServiceEvQShmMonitorSize

> Specifies the size of the shared memory segment (in bytes) to be used for the shared monitor counters. The shared monitor counters are monitor values that are accessible using the Windows performance monitor integration.

> The default is 4096.

> Type=Static

> ### ServiceEvQShmQMaxResend

> Specifies the number of attempts while sending events on the event queue before generating a fatal error.

> The default is 5.

> Type=Static

> ### ServiceEvQShmQSize

> Specifies the size of the shared memory segment for the event queue. The event queue is used as a communication path between SequeLink services.

> The default is 65536.

> Type=Static

> ### ServiceEvQShmQWaitResend

> Specifies the time (in milliseconds) to wait between successive attempts to send events on the event queue.

> The default is 50.

> Type=Static

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> ### ServiceExecPath

> Specifies the path of a SequeLink Server executable and is used differently depending on platform. The valid value is a defined location of a SequeLink server executable.

> - On Windows: The value of the ServiceExecPath is used when registering the service.
> - On Linux and UNIX: The value of ServiceExecPath is used by the SequeLink Agent when starting the service.

> Do not alter this attribute.

> Type=Static

> ### ServiceExecPath2

> Specifies the path of a SequeLink server executable to start by SequeLink service starter. The valid value is a defined location of a SequeLink server executable.

> Type=Static

> ### ServiceHost

> Specifies the name of the host on which the SequeLink service is installed.

> Type=Dynamic for newly-created services

> Type=Read-only for existing services

> ### ServiceIdleTimeInt

> Specifies time (in seconds) a connection can be idle before it is terminated by the SequeLink Server. Because ServiceIdleTimeInt is static, you must restart the SequeLink service to make the change effective.

> Valid values are 0 and any integer from 60 to 1000000.

> - If ServiceIdleTimeInt is greater than ServiceDeadClntDetInt, the value will be rounded down to the nearest multiple of ServiceDeadClntDetInt.
> - If ServiceIdleTimeInt is less than ServiceDeadClntDetInt, the value of ServiceIdleTimeInt will be used.

> The default is 0. Idle time checks are disabled.

> Type=Static

> ### ServiceIIOPObjectKey

> Specifies IIOP object key in IIOP header.

> The default is IIOP:slx::.

> Type=Static

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> ### ServiceIIOPOperationTarget

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> Specifies IIOP operation target in IIOP header.

> The default is SSP.

> Type=Static

> ### ServiceINFMaxNrActStat

> Specifies the maximum number of active statements that are allowed for each connection to an Informix database.

> The default is 250.

> Type=Dynamic

> ### ServiceInternalTimeout

> Specifies the number (in milliseconds) that thread pool synchronization actions block before generating an internal error. Valid values are positive numbers.

> The default is 60000.

> Type=Static

> ### ServiceKerberosPrincipalName

> Specifies the case-sensitive service principal name to be used for Kerberos authentication to the SequeLink data access service. Use this attribute to specify another service principal name other than the default service principal name. The name must match the service principal name in the KDC.

> For example:

>     SLDB2UDB60/server1.eu.datadirect.com@XYZ.COM
>     DB2SRV/IRONFLEX.DATADIRECT.COM@IRONFLEX.TEST

> Default=host`/`fully_qualified_domain_name`@`REALM

> Type=Dynamic

> On Linux/UNIX, the service principal name must exist in the keytab file.

> For information about specifying a service principal name to be used for Kerberos authentication to a SequeLink Agent service, see "ServiceAdminKerberosPrincipalName".

> ### ServiceLanguage

> The specified language for SequeLink messages. The only valid value and the default is 1= English.

> Type=Static

> ### ServiceMaxSessions

> Specifies the maximum number of sessions a multithreaded SequeLink Server will accept.

> On z/OS, verify that this parameter does not exceed the value of MAXFILEPROC in BPXPRMxx. The MAXFILEPROC parameter can be changed dynamically.

> - On z/OS, the default value is 2000.
> - On Linux, UNIX, and Windows, the default value is 0. A value of 0 means unlimited number of sessions is accepted.

> On Linux, UNIX, and Windows, the default value is 0. A value of 0 means unlimited number of sessions is accepted.

> Type=Dynamic

> ### ServiceMaxThreads

> The maximum number of threads that can be started in the thread pool. This attribute is ignored when ServiceConnectionModel is set to Thread/Connection or Process/Connection.

> Valid values are:

> - For DB2 UDB on z/OS, valid values are from 6 to 256.
> - For DB2 UDB on AIX, valid values are from 6 to 512.
> - For all others, valid values are from 6 to 64000.

> The default is 64.

> Type=Static

> ### ServiceMessageFile

> The location of the service message file:

> On Windows: The valid value is the path to a resource-only DLL.

> On Linux/UNIX: The valid value is the path to a .cat file.

> Type=Static

> ### ServiceMinThreads

> The number of pre-started threads that will be started in the thread pool. The value should be equal to or less than the value of ServiceMaxThreads. This attribute is ignored when ServiceConnectionModel is set to Thread/Connection or Process/Connection.

> Valid values are:

> - For DB2 UDB on z/OS, valid values are from 6 to 256.
> - For DB2 UDB on AIX, valid values are from 6 to 512.
> - For all others DBMSs, valid values are from 6 to 64000.

> The default is 8.

> Type=Static

> ### ServiceMSSMergeXaBranches

> When accessing Microsoft SQL Server, enables the application to merge all XA branches as one transaction branch, emulating tightly coupled branch transactions. When disabled, multiple connections within the same distributed transaction ignore each other's locks.

> Valid values are:

> - TRUE=SequeLink merges all XA branches as one transaction branch.
> - FALSE=All XA branches are kept separately.

> The default is FALSE.

> Type=Static

> ### ServiceName

> Specifies the name of the service to be specified during service creation. After a service is created, the name of a service cannot be changed.

> Type=Dynamic for new services

> Type=Read-only for existing services

> ### ServiceORASerializeLogon

> Specifies whether all Oracle API calls that are executed to establish a connection with the Oracle database are serialized.

> Valid values are:

> - TRUE=The Oracle API calls are serialized.
> - FALSE=The Oracle API calls are not serialized.

> The default is TRUE.

> Type=Static

> ### ServiceRegisterTCPPort

> Specifies whether the TCP/IP port will be registered automatically in the operating systems services file (/etc/services on Linux/UNIX or %SystemRoot%\system32\drivers\etc\services on the Microsoft Windows platforms on which SequeLink Server runs, for example).

> - TRUE=The TCP/IP port used by the SequeLink service will be registered automatically in the operating system services file.
> - FALSE=The TCP/IP port used by the SequeLink service will not be registered automatically in the operating system services file.

> The default is FALSE.

> Type=Static

> ### ServiceResolveHostNames

> Specifies how host names are resolved. Valid values are:

> - TRUE=Information about connected clients is displayed using symbolic system names.
> - FALSE=Information about connected clients is displayed in an IP format.

> The default is FALSE.

> Type=Dynamic

> ###

> ### ServiceSSLCipherSuites

> Specifies the SSL cipher suites that SequeLink supports for data transfers between the SequeLink Client and SequeLink Server. Valid values are:

> - SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
> - SSL_DH_anon_WITH_RC4_128_MD5
> - SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
> - SSL_DH_anon_WITH_DES_CBC_SHA
> - SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
> - TLS_DH_anon_WITH_AES_128_CBC_SHA
> - TLS_DH_anon_WITH_AES_256_CBC_SHA

> The default is TLS_DH_anon_WITH_AES_128_CBC_SHA.

> Type=Static

> ###

> ### ServiceSSLEnabled

> Specifies whether SSL is enabled for the SequeLink service. Valid values are:

> - TRUE=The SequeLink service is enabled for SSL.
> - FALSE=The SequeLink service is not enabled for SSL.

> The default is FALSE.

> Type=Static

> ###

> ### ServiceSSLSessionCacheSize

> Specifies the maximum number of SSL (or TLS) session identifiers that are cached on the SequeLink Server before the sessions are flushed from the cache. Caching SSL session identifiers so that clients can reuse them in a subsequent connection improves performance because the CPU-intensive computations required to create an SSL session are eliminated.

> Valid values are from 0 to 100000.

> The default is 10000.

> Type=Static

> ###

> ### ServiceSSLSessionCacheTimeout

> Specifies the maximum time (in seconds) to keep a SSL (or TLS session in the SequeLink Server session cache.

> Valid values are from 0 to 100000.

> The default is 300.

> Type=Static

> ###

> ### ServiceSSLVersions

> Specifies the version of the SSL standard that is used for encryption. Valid values are:

> - SSL 3.0
> - TLS 1.0

> The default is TLS 1.0.

> Type=Static

> ### ServiceTCP1stRecvTimeLimit

> Maximum amount of time (in seconds) the server will wait to receive the first network packet.

> The default is 30.

> Type=Static

> NOTE: Set this attribute only when instructed to do so by DataDirect Technologies technical support.

> ### ServiceThreadLockThreshold

> Specifies a percentage of the value of ServiceMaxThreads. When the number of active threads is less than this percentage, a connection that has executed more RPCs than DataSourceThreadMaxRpc on the current thread is allowed to lock this thread for another DataSourceThreadRpcTimeOut period.

> This attribute is required when
> ServiceConnectionModel=Threadpool (see "ServiceConnectionModel" for more information).

> Valid values are from 0 to 50.

> On Linux, UNIX, and Windows, the default is 0 (the thread switching mechanism is disabled, improving performance in times of low system activity).

> On z/OS, the default is 10.

> Type=Dynamic

> ### ServiceUnixSyslogFacility

> Facility with which all SequeLink syslog messages are logged. Valid values are:

> - USER
> - LOCAL0-LOCAL7

> The default is USER.

> Type=Dynamic

> ### ServiceUser

> Sets authorization for users who are allowed to access the service for data access.

> On Linux, UNIX, and Windows: Specify everyone when ServiceAuthMethods=anonymous. To configure authorization for multiple users, you must set the ServiceUser attribute for each user. Valid values are:

> - user_id=The user ID of a user who is allowed to use the SequeLink service. To configure authorization for more than one user, you must configure this attribute multiple times, one instance for each user.

> NOTES:

> - On Windows servers, you must prefix the user ID with the Windows server name or the Windows domain name, for example, SALES\DJONES.
> - Alternatively, you can set the ServiceUserGroup attribute to configure authorization for groups of users defined on Linux, UNIX, or Windows. See "ServiceUserGroup" for more information about configuring authorization for user groups on Linux, UNIX, and Windows.
> - authenticated=Any user who can provide a valid host user ID and password or who uses Integrated NT authentication will receive the same authorization.
> - everyone=All connections will receive the same authorization level, regardless of how they are authenticated.

> RSee "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> Type=Dynamic

> ### ServiceUserGroup

> Sets authorization for defined Linux, UNIX, and Windows user groups who are allowed to access the service for data access. Valid values are user groups defined on Linux, UNIX, and Windows.

> To configure authorization for multiple user groups, you must set the ServiceAdministrator attribute multiple times, one time for each user group. For example:

>     ServiceUserGroup=SLUSERG1
>     ServiceUserGroup=SLUSERG2
>     ServiceUserGroup=SLUSERG3

> NOTE: On Windows servers, you must prefix the user group ID with the Windows server name or the Windows domain name where the user group is defined, for example, SALES\SLUSERG1.

> See "Configuring SequeLink® Security" for more information about configuring SequeLink security.

> Type=Dynamic