Neoview ODBC Drivers Manual (R2.2 SP1)
Table Of Contents
- HP Neoview ODBC Drivers Manual
- Table of Contents
- About This Document
- 1 HP Neoview ODBC Driver Overview for Windows
- 2 HP Neoview ODBC Drivers Overview for Linux, HP-UX, IBM AIX®, and Sun Solaris
- 3 Installing the HP Neoview ODBC Drivers
- Installing ODBC Client Software
- Avoiding Driver-Platform Version Incompatibility
- Installing the HP Neoview ODBC Driver for Windows
- Reinstalling the HP Neoview ODBC Driver for Windows
- Uninstalling the HP Neoview ODBC Driver for Windows
- Setting Up the Client Environment
- Troubleshooting
- Getting the Version of the Driver
- ODBC API Reference
- Installing or Reinstalling HP Neoview ODBC Drivers for Linux, HP-UX, IBM AIX®, and Sun Solaris
- Setting Up the Client Environment
- Running the Sample Program
- Troubleshooting
- Debugging
- Getting the Version of the Driver
- ODBC API Reference
- 4 Configuring Client Data Sources
- 5 HP Neoview ODBC Drivers Conformance
- 6 HP Neoview ODBC Drivers Messages
- Index

Traces
You can trace activity for the ODBC client. The following data is collected:
• Entry and exit calls to the HP Neoview ODBC drivers
• Contents of the buffers, except password buffers
• Activity between the HP Neoview ODBC drivers and the transport layer
Using the Driver With a Third Party Driver Manager
• If you are using an external driver manager, you must point to libhpodbc_drvr and not to
libhpodbc.
• The driver (libhpodbc_drvr.so) has been verified with iODBC and unixODBC driver
managers.
• These driver managers, as well as documentation, can be found at these Web sites:
http://www.iodbc.org/
http://www.unixodbc.org/
• The three environment variables that control tracing are:
— HPODBC_TRACE_LEVEL — sets trace level (ERROR, WARNING, CONFIG, INFO,
or DEBUG)
— HPODBC_TRACEFILE_NAME — specifies the name of the log file
— HPODBC_TRACEFILE_SIZE — specifies the maximum files size of the log files
• For information on the necessary data source configuration options, you will need to add
to the respective configuration files (for example, to odbc.ini).
• You must configure the following data source attributes. For an example of configuration
values, refer to the MXODSN file template provided with the installation. This is an example:
DESCRIPTION = Default Data Source
Catalog = CAT
Schema = SCH
DataLang = 0
FetchBufferSize = SYSTEM_DEFAULT
Server = TCP:arc0101.caclab.cac.cpqcorp.net:5000
SQL_ATTR_CONNECTION_TIMEOUT = SYSTEM_DEFAULT
SQL_LOGIN_TIMEOUT = SYSTEM_DEFAULT
SQL_QUERY_TIMEOUT = NO_TIMEOUT
For questions related to your third party driver manager, refer to your driver manager's
documentation.
INFOSTATS Command
INFOSTATS is a pass-through command that collect statistics for a prepared statement. Statistics
are returned to the ODBC application as a result set as soon as the PREPARE is finished. The
result set has these columns:
• Query ID (SQL_CHAR)
• CPUTime (SQL_DOUBLE): An estimate of the number of seconds of processor time it might
take to execute the instructions for this query. A value of 1.0 is 1 second.
• IOTime (SQL_DOUBLE): An estimate of the number of seconds of I/O time (seeks plus data
transfer) to perform the I/O for this query.
• MsgTime (SQL_DOUBLE): An estimate of the number of seconds it takes for the messaging
for this query. The estimate includes the time for the number of local and remote messages
and the amount of data sent.
26 HP Neoview ODBC Drivers Overview for Linux, HP-UX, IBM AIX®, and Sun Solaris