MX 2.x)

Configuring Client Data Sources on Windows

HP NonStop ODBC/MX Driver for Windows—527888-004

3-2

Reconfiguring Client Data Sources

For more information about a screen, click Help.

Reconfiguring Client Data Sources

1. Bring up the Microsoft ODBC Data Source Administrator. You can usually find this

by selecting the Start menu, Programs option, NonStop ODBC-MX 2.0 option, then

select the MS ODBC Administrator option.

2. To display the list of data source names, click either the System DSN tab or the

User DSN tab (the tab on which a data source is listed depends upon how the data

source was originally assigned).

Select the data source name you want to reconfigure then click Configure.

3. Each tab in the configuration view displays different fields in the data source

configuration. Make the desired changes.

For more information about a tab, click Help.

Configuring Client Data Sources using

Connection String

The following connection string is used to configure the Client Data Source:

"DSN=< DataSource name>;catalog=<catalog name>;schema=<schema

name>; Uid=<userid>;Pwd=< password>; FETCHBUFFERSIZE=<value in

bytes>;SQLFRACTIONVALUE=<value>;SQL_ATTR_CONNECTION_TIMEOUT=<val

ue in sec>;SQL_LOGIN_TIMEOUT=< value in sec>;SQL_QUERY_TIMEOUT=<

value in sec>";

Configuring Client Data Sources for Update

Operations

To perform “update . . . on the current of” operations:

Set the fetch buffer size to zero using the ODBC Cient Administrator. This forces

fetching one row at a time instead of a buffered fetch.

An error is returned if:

•

The SQL_ATTR_CONCURRENCY attribute is set to

SQL_CONCUR_READ_ONLY

Note. The catalog and schema names that are defined for server data sources using

NSM/web are not recognized by ODBC/MX for client data sources unless they are defined

through the Microsoft ODBC Data Source Administrator. You must either define the catalog

and schema names using the Microsoft ODBC Data Source Administrator, or use the fully

qualified object name. Catalog and schema names are case sensitive, and they must already

have been created using MXCI.