MX Release 3.2 (H06.25+, J06.14+)

Configuring Client Data Sources on Windows

HP NonStop ODBC/MX Driver for Windows—691126-003

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 ODBCMX 3.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>";

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.



While creating a new data source from the MS ODBC Administrator, do not add any of the

following special characters to the data source name:

\, /, :, *, ?, “, <, >, |

Note.

The ODBC/MX 3.0 supports the following format of the IPv6 address:

server = <ipaddress>:<port>

However, it does not support the following format of the IPv6 adderss:

2001:db8:85a3::370:7334:<port>