Neoview ODBC Drivers Manual (R2.5)

1. Checks the location specified by SQL_ATTR_CERTIFICATE_DIR and
SQL_ATTR_CERTIFICATE_FILE (or the corresponding values in the connection string
or—in the case of the certificate directory—in the ODBC driver installation, MXODSN or
odbc.ini file) to determine whether a certificate exists at that location. If the application did
not specify a directory, the driver checks the user's home directory. If the application did
not specify a filename, the driver assumes the name SYSTEM_NAME.cer, where
SYSTEM_NAME consists of the first five characters of the Neoview platform name.
2. If no certificate for the Neoview platform exists at the expected location and if automatic
download is permitted, the driver downloads the certificate from the Neoview platform to
the location specified by SQL_ATTR_CERTIFICATE_ACTIVE. If the application did not
specify that attribute, the driver assumes the name SYSTEM_NAMEActive.cer, where
SYSTEM_NAME consists of the first five characters of the Neoview platform name. If automatic
download is prohibited, an error occurs.
For detailed information about security certificates on your workstation, see the Neoview User
Management and Security Administration Guide.
Release Considerations and Restrictions
Table 1-1 Release Considerations and Restrictions for Windows Driver
HP Neoview ODBC driver requires the Microsoft ODBC
3.51 (or later) driver manager. If you do not already have
the 3.51 driver manager, the HP Neoview ODBC driver
installs it for you.
ODBC driver manager
An HP Neoview ODBC driver can coexist with other
ODBC drivers.
HP Neoview ODBC client software
An ODBC client application can set the schema for an
ODBC client data source by using the HP Neoview ODBC
Driver window in the Microsoft ODBC Administrator. If
an ODBC client does not set the schema for an ODBC
client data source, NDCS defaults to USR. Note:
Schema names follow SQL rules and are case sensitive.
Schema names that are defined by default are not
recognized by NDCS for client data sources because
they are not defined through the Microsoft ODBC
Administrator. You must either define the catalog and
schema names using the Microsoft ODBC
Administrator, or use the fully qualified object name.
Schema
An ODBC application can call SQLSetStmtOption with
the SQL_QUERY_TIMEOUT option to specify the number
of seconds to wait for a query to execute. The
SQL_QUERY_TIMEOUT option protects the NDCS server
and ODBC client from long running queries. If a query
exceeds the specified time before the data source returns
the result set, the HP Neoview ODBC driver returns
HYT00 (Timeout expired) to the ODBC client. When the
query times out, the client gets disconnected from the
server, resulting in a communication link failure. The
client has to reconnect to the server after any query
timeout event.
SQL_QUERY_TIMEOUT Option
For information about SQLCancel function, see
“SQLCancel Function” (page 24).
SQLCancel Function
This function does not support pattern value arguments
for table names, and returns keys information for a
specified table name.
SQLPrimaryKeys Function
Release Considerations and Restrictions 23