HP NonStop ODBC/MX Driver for Windows Abstract This manual describes how to install and configure HP NonStop™ ODBC/MX for Microsoft® Windows. This product enables applications developed for the Microsoft Open Database Connectivity (ODBC) application programming interface to use HP NonStop SQL/MX to access HP NonStop SQL databases on an HP NonStop system. Product Version HP NonStop ODBC/MX 2.0 Supported Release Version Updates (RVUs) This manual supports J06.03 and all subsequent J-series RVUs, H06.
Document History Part Number Product Version Published 527888-001 HP NonStop ODBC/MX 2.0 April 2004 527888-002 HP NonStop ODBC/MX 2.0 June 2005 527888-003 HP NonStop ODBC/MX 2.0 November 2008 527888-004 HP NonStop ODBC/MX 2.
Legal Notices © Copyright 2009 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop ODBC/MX Driver for Windows Glossary Index Figures Tables Legal Notices What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Audience vii Related Documentation vii Notation Conventions xi 1.
2. Installation of the ODBC/MX Client Contents 2. Installation of the ODBC/MX Client Components of the MX connectivity service 2-1 Installing the Client Components 2-1 Installing and Running ODBC/MX version 2.0 Concurrently With MXCS Version 1.
5. ODBC/MX Conformance (continued) Contents 5. ODBC/MX Conformance (continued) SQL/MP Data Types and ODBC/MX Equivalents 5-12 Microsoft Escape Clauses 5-13 Stored Procedures 5-14 Transactions and Cursor Behavior with Multiple Statements 5-14 6. ODBC/MX Messages ODBC/MX Driver Error Codes 6-1 ODBC/MX Client Messages 6-1 Glossary Index Figures Figure 1-1. Connection Data Flow 1-3 Tables Table 1-1. Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. Table 5-6. Table 5-7. Table 5-8. Table 5-9.
Contents HP NonStop ODBC/MX Driver for Windows—527888-004 iv
What’s New in This Manual Manual Information HP NonStop ODBC/MX Driver for Windows Abstract This manual describes how to install and configure HP NonStop™ ODBC/MX for Microsoft® Windows. This product enables applications developed for the Microsoft Open Database Connectivity (ODBC) application programming interface to use HP NonStop SQL/MX to access HP NonStop SQL databases on an HP NonStop system. Product Version HP NonStop ODBC/MX 2.0 Supported Release Version Updates (RVUs) This manual supports J06.
What’s New in This Manual Changes to the 52788-002 Manual Changes to the 52788-002 Manual • • • Using partial Date/Time values, see Partial Date/Time Values on page 5-12. DATETIME mappings from SQL/MP to ODBC/MX. See SQL/MP Data Types and ODBC/MX Equivalents on page 5-12. Using unsigned data types. See Unsigned Data Types on page 5-12.
About This Manual Audience This manual is for: • • ODBC application programmers who write 32-bit applications to access an NonStop SQL database. Other end users or application programmers who use ODBC/MX to access a NonStop SQL database. Related Documentation The SQL/MX library of manuals, which includes: Introductory Guides SQL/MX Comparison Guide for SQL/MP Users Describes SQL differences between SQL/MP and SQL/MX.
Related Documentation About This Manual Specialized Guides SQL/MX Installation and Management Guide Describes how to plan for, install, create, and manage an SQL/MX database. Explains how to use installation and management commands and utilities. SQL/MX Query Guide Describes how to understand query execution plans and write optimal queries for an SQL/MX database. SQL/MX Data Mining Guide Describes the SQL/MX data structures and operations to carry out the knowledge-discovery process.
Related Documentation About This Manual Technical Library (NTL) at http://docs.hp.com. For more information about downloading online help, see the SQL/MX Installation and Management Guide.
Related Documentation About This Manual Programming Manuals Introductory Guides SQL/MX Comparison Guide for SQL/MP Users SQL/MX Programming Manual for C and COBOL SQL/MX Quick Start SQL/MX Programming Manual for Java SQL/MX Guide to Stored Procedures in Java Reference Manuals SQL/MX Reference Manual SQL/MX Messages Manual SQL/MX Glossary SQL/MX Query Guide SQL/MX Queuing and Publish/ Subscribe Services SQL/MX Report Writer Guide DataLoader/MX Reference Manual SQL/MX Online Help Specialized
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
Change Bar Notation About This Manual Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version.
1 ODBC/MX Client Overview Applications developed for the Microsoft® Open Database Connectivity (ODBC) application programming interface (API) can use SQL/MX to access a NonStop SQL database on an HP NonStop server, through HP NonStop SQL/MX connectivity services (MXCS).
ODBC/MX Client Overview Client Data Sources using NSM/web, but you cannot delete it. The TDM_Default_DataSource has these functions: • • ODBC clients can connect to TDM_Default_DataSource and access a NonStop SQL database with no special configuration required.
Connection Mapping ODBC/MX Client Overview An ODBC client application can connect to the default data source without needing to create an MXCS SQL server data source. Figure 1-1. Connection Data Flow ODBC Client Application ODBC API ODBC Driver Manager 1. Request connection to DS1 ODBC/MX Driver MXCS Association Server 2. Connection to DS1 granted 3. Client connects to server 4. Server accepts connection MXCS SQL Server MXCS SQL Server Other Data Source: DS1 Tdm_Default_DataSource VST002.
ODBC/MX Client Overview Connection Pooling the user context to the one defined in the configuration for the data source name on the server. Connection Pooling Connection pooling can improve MXCS performance by allowing an ODBC application to use (or reuse) a connection from a pool of connections without reestablishing the connection. The Microsoft ODBC driver manager maintains the connection pool by continuing to hold a connection for a specified time after the client disconnects.
Enabling Connection Pooling ODBC/MX Client Overview To use connection pooling, an ODBC client application must perform the following sequence: Step Client Action 1. Enable connection pooling Call SQLSetEnvAttr with the environment handle set to NULL and the SQL_ATTR_CONNECTION_POOLING attribute set to SQL_CP_ONE_PER_DRIVER or SQL_CP_ONE_PER_HENV. SQL_CP_OFF (the default) turns connection pooling off. 2.
Object Naming and Mapping ODBC/MX Client Overview Step Client Action 8. Retrieve and process data from the database When using connection pooling, an application must preserve the database context within the session and should not execute SQL/MX statements that change the name of the database or its context. 9. Disconnect and return the connection to the connection pool Call SQLDisconnect. 10. Free the environment and connection handles Call SQLFreeHandle for each handle.
ODBC/MX Client Overview Password Expiration catalog.schema.object-name ANSI names have a maximum of 128 characters for each part of the name (not including the dots). ANSI Names for SQL/MX Objects ANSI names for SQL/MX objects are registered in SQL/MX metadata residing in SQL/MX format tables. ANSI Names for SQL/MP Objects ANSI names (also called alias names) are logical names that map to physical Guardian names of existing SQL/MP objects.
Release Considerations and Restrictions ODBC/MX Client Overview Release Considerations and Restrictions Table 1-1. Release Considerations and Restrictions (page 1 of 3) ODBC driver manager ODBC/MX requires the Microsoft ODBC 3.5.1 (or later) driver manager. If you do not already have the 3.5.1 driver manager, ODBC/MX installs it for you. ODBC/MX client software An ODBC/MX client can be installed in the same workstation as a NonStop ODBC Server client or other ODBC client software.
ODBC/MX Client Overview Release Considerations and Restrictions Table 1-1. Release Considerations and Restrictions (page 2 of 3) SQLCancel Function In an ODBC 2.0 application, ODBC/MX implements the SQLCancel function as an SQLFreeStmt with the SQL_CLOSE option. If the query is running, ODBC/MX tries to stop the server. If the attempt is successful, the client application receives an error and must reconnect. In an ODBC 3.
Traces ODBC/MX Client Overview Table 1-1. Release Considerations and Restrictions (page 3 of 3) SQLStatistics Function This function does not support pattern value arguments for table names, and returns index information for a specified table name in the SQL/MX catalog.
ODBC/MX Client Overview Unsupported ODBC API Functions and Data Types Unsupported ODBC API Functions and Data Types API Functions This release of ODBC/MX does not support the following ODBC 3.51 API functions. For descriptions of the ODBC API functions, see ODBC API Functions on page 5-1. SQLBulkOperations SQLFetchScroll - supported for SQL_FETCH_NEXT attribute only SQLSetScrollOption Data Types This release of MXCS does not support the following ODBC data types.
ODBC/MX Client Overview Restricted ODBC API Functions HP NonStop ODBC/MX Driver for Windows—527888-004 1-12
2 Installation of the ODBC/MX Client Components of the MX connectivity service 2-1 Installing the Client Components 2-1 Uninstalling the Client Interface 2-7 Modifying the Client Installation 2-8 Components of the MX connectivity service To fully install all components of connectivity service, you must install the following: • • MXCS server components on a NonStop system. ODBC/MX client interface on any Windows machine.
Installation Requirements Installation of the ODBC/MX Client • Once an application connects to a driver of a particular version, it must always connect to a driver of that version, even if the application disconnects. To change to a driver of a different version, the application must exit and be restarted.
Step 2: Install the Client Interface Components Installation of the ODBC/MX Client Step 2: Install the Client Interface Components The InstallShield is a wizard that sequentially walks you through the steps to install the client components on your client workstation.
Step 3: Add a Data Source Installation of the ODBC/MX Client Screen Button Description The InstallShield then installs the client interface components. Start Copying Files Back Next Cancel Displays a summary of installed components. Question Yes No If data sources configured for a previous version of ODBC/MX are found, this screen is displayed. Click Yes to reconfigure all data sources for the current version of MXCS. Clicking No leaves data source configuration unchanged.
Step 5: Restart the PC Installation of the ODBC/MX Client Step 5: Restart the PC HP recommends that you restart the PC before you use the ODBC/MX client interface. Note. Before using the client interface, the MXCS service must be started. For information on how to start the service, see the SQL/MX Connectivity Service Manual. Troubleshooting You can repair the ODBC client installation when the Windows Registry or a necessary ODBC file becomes corrupted, or a file is deleted by mistake.
Troubleshooting Installation of the ODBC/MX Client Client Interface Files ODBC/MX core component: ODBC 3.51 Core Component (in system directory) ds16gt.dll ds32gt.dll mdacmigr.dll * migrate.bat* migrate.reg* msdasql.dl msdasqlr.dll msdasqlrm.txt msvcrt.dl mtxdm.dll *Windows 98 only OLE DB 2.0 files (in system directory) asycfilt.dll comcat.dll msdadc.dll msdaenum.dll msdaer.dll msdaosp.dll msdaps.dll msdasc.cnt msdasc.dll Translator (in system directory) 12520437.cpx 12520850.cpx mscpxl32.
Uninstalling the Client Interface Installation of the ODBC/MX Client ODBC documentation (in selected directory) odbcmxds.chm readme.txt Self Registering system files (in system directory) mfc42.dll System files (in system directory) msvcp60.dll Uninstalling the Client Interface You can uninstall the client interface in one of two ways. • • Select Start, Programs, NonStop ODBC-MX 2.0, Remove NonStop ODBC/MX 2.0. Click Yes to uninstall ODBX/MX; click No to cancel the uninstallation. Run the TDMODBC.
Modifying the Client Installation Installation of the ODBC/MX Client Modifying the Client Installation Step 1: Begin Client Installation Again Perform Client Installation Step 1. Step 2: Select Modify Option Screen Button Modify, Repair or Remove the program Modify Remove Click Modify to display the list of components to install or remove. Select Components Next Selects the components to install or remove.
3 Configuring Client Data Sources on Windows Use the Microsoft ODBC Data Source Administrator to add, configure, and remove ODBC/MX data sources. For information about supported versions of Windows, see Client Components on page 1-1. Note.You can install and run ODBC/MX version 2.0 concurrently with MXCS version 1.8. However, to remove or reconfigure ODBC/MX version 1.8 data sources, the corresponding version of MXCS must be installed on your system.
Configuring Client Data Sources on Windows Reconfiguring Client Data Sources For more information about a screen, click Help. 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.
Configuring Client Data Sources on Windows • Removing Client Data Sources The WHERE CURRENT OF clause is used in an UPDATE or DELETE statement. This prevents updating or deleting an incorrect row. Removing 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.
Configuring Client Data Sources on Windows Tracing Client Data Sources 3. Select the Custom Trace DLL (the trace file name) you want to use. Use the Select DLL button to locate the correct file. If you select the ODBC standard trace DLL (odbctrac.dll in the Windows\system32 directory), only the driver manager is traced; additional trace options you select are ignored. If you select the ODBC/MX trace DLL (tdm_odbctrace.
4 Module File Caching (MFC) MFC Overview 4-1 MFC Design 4-1 Configuring MFC 4-1 MFC Usage Scenarios 4-2 MFC Limitations 4-2 Troubleshooting MFC 4-2 MFC Overview Before the H06.18/J06.07 RVU, the ODBC/MX driver did not cache the NonStop SQL/MX prepared statements. As a result, applications recompiled the same SQL/MX statements, causing higher host processor and memory utilization, which lead to poor performance.
Module File Caching (MFC) MFC Usage Scenarios MFC Usage Scenarios The benefits of lower processor and memory utilization mentioned below are applicable on the NonStop Server: • • • ODBC/MX applications using SQLPrepare() have the benefit of lower processor utilization, lower memory consumption, and better response time. ODBC/MX applications using complex queries through prepare calls have higher benefit of lower processor utilization, lower memory consumption, and better response time.
5 ODBC/MX Conformance This section contains tables that describe the ODBC/MX conformance to standard ODBC API functions and SQL conformance levels.
ODBC API Functions ODBC/MX Conformance supported, then the feature was first defined in version 1.0 of the Microsoft ODBC standard and ODBC/MX currently supports the function. For more information about each function, refer to the Microsoft documentation. Table 5-1. Connecting to a Data Source ODBC Version Supported by ODBC/MX SQLAllocHandle 3.0 Yes Obtains an environment, connection, statement, or descriptor handle. SQLConnect 1.
ODBC API Functions ODBC/MX Conformance Table 5-3. Setting and Retrieving Driver Attributes ODBC Version Supported by ODBC/MX SQLSetConnectAttr 3.0 Yes Sets a connection attribute. SQLGetConnectAttr 3.0 Yes Returns the value of a connection attribute. SQLSetEnvAttr 3.0 Yes Sets an environment attribute. SQLGetEnvAttr 3.0 Yes Returns the value of an environment attribute. SQLSetStmtAttr 3.0 Yes Sets a statement attribute.
ODBC API Functions ODBC/MX Conformance Table 5-6. Submitting SQL Requests ODBC Version Supported by ODBC/MX SQLExecute 1.0 Yes Executes a prepared statement. SQLExecDirect 1.0 Yes Executes a statement. SQLNativeSql 1.0 Yes Returns the text of an SQL statement as translated by the driver. SQLDescribeParam 1.0 Yes Returns the description for a specific parameter in a statement. SQLNumParams 1.0 Yes Returns the number of parameters in a statement. SQLParamData 1.
ODBC API Functions ODBC/MX Conformance Table 5-7. Retrieving Results and Information About Results (page 2 of 2) ODBC Version Supported by ODBC/MX SQLExtendedFetch 1.0 Yes Fetches the specified rowset of data from the result set and returns data for all bound columns. No bookmarks are supported. SQLSetPos 1.0 Yes Positions a cursor within a fetched block of data and allows an application to refresh data in the row set or to update or delete data in the result set. SQLBulkOperations 3.
ODBC API Functions ODBC/MX Conformance Table 5-8. Obtaining Information About a Data Source’s System Tables (page 2 of 2) ODBC Version Supported by ODBC/MX SQLProcedureColumns 1.0 Yes Returns the list of input and output parameters, as well as the columns that make up the result set for the specified procedures. SQLProcedures 1.0 Yes Returns the list of procedure names stored in a specific data source. SQLSpecialColumns 1.
SQL Conformance Level ODBC/MX Conformance Table 5-9. Terminating a Statement ODBC Version Supported by ODBC/MX SQLCloseCursor 3.0 Yes Closes a cursor that has been opened on a statement handle. SQLCancel 1.0 Yes Closes a cursor that has been opened on a statement handle. Function Description Note: See the considerations underSQLCancel Function on page 1-9. SQLEndTran 3.0 Yes Commits or rolls back a transaction. Table 5-10.
SQL Scalar Functions ODBC/MX Conformance Table 5-11. Numeric Functions (page 2 of 2) ODBC Function SQL/MX Equivalent Function COS COS COSH COSH COT Not supported in this release. DEGREES DEGREES EXP EXP FLOOR FLOOR LOG LOG LOG10 LOG10 MOD MOD PI PI POWER POWER RADIANS RADIANS RAND RAND ROUND Not supported in this release. SIGN SIGN SIN SIN SINH SINH SQRT SQRT TAN TAN TANH TANH TRUNCATE Not supported in this release. Table 5-12.
SQL Scalar Functions ODBC/MX Conformance Table 5-12. String Functions (page 2 of 2) ODBC Function SQL/MX Equivalent Function REPEAT REPEAT REPLACE REPLACE RIGHT RIGHT RTRIM TRIM...TRAILING SOUNDEX Not supported SPACE SPACE SUBSTRING SUBSTRING UCASE UPPER | UPSHIFT Note. ODBC string functions in queries can return unexpected results for fixed-length (CHAR) column names, because SQL/MX pads a fixed-length string with blanks up to the length of the definition.
ODBC Data Types ODBC/MX Conformance Table 5-14. System Functions ODBC Function SQL/MX Equivalent Function DATABASE Not supported in this release. IFNULL Not supported in this release. USER USER CONVERT Function ODBC/MX uses the SQL/MX CAST function to support the ODBC CONVERT function.
ODBC Data Types ODBC/MX Conformance Table 5-15.
Unsigned Data Types ODBC/MX Conformance Unsigned Data Types Unsigned data types are treated differently, according to the version of ODBC used, and whether the SQL_ATTR_MSACCESS_VERSION flag is set Table 5-16. Behavior of Unsigned Data Types ODBC Version Behavior of Unsigned Data Types 2.0 UNSIGNED SMALLINT promoted to SIGNED INT UNSIGNED INT promoted to BIGINT 3.0, when server side data source is configured with SQL_ATTR_MSACCESS_VERSIO N flag All unsigned types are promoted to the next signed type.
Microsoft Escape Clauses ODBC/MX Conformance Table 5-17.
Stored Procedures ODBC/MX Conformance Table 5-18. Microsoft Escape Clauses (continued) Microsoft Escape Clause SQL/MX Equivalent { escape 'escape-character' } Not supported in the current release. { [?=]call procedure-name... } Not supported in the current release. 1. ODBC syntax does not include nested joins, while SQL/MX does. ODBC/MX extends the Microsoft syntax for an outer join. 2. Functions are controlled by SQLGetInfo. Only SQL/MX native functions are supported.
6 ODBC/MX Messages Topic Page ODBC/MX Driver Error Codes 6-1 ODBC/MX Client Messages 6-1 ODBC/MX Driver Error Codes ODBC/MX Client Messages To display the messages for the SQLSTATE numbers in the following tables, click one of the following starting SQLSTATE numbers: 01000 08001 21001 40001 S0001 S1000 S1010 S1100 SQLSTATE Messages 01000 General Warning. 01000 General Warning. Connected to the default data source. 01002 Disconnect error. Transaction rolled back. 01004 Data truncated.
ODBC/MX Client Messages ODBC/MX Messages SQLSTATE Messages 08002 Connection in use. 08003 Connection not open. 08004 Data source rejected establishment of connection since the MXCS server is connected to a different client now. 08004 Data source rejected establishment of connection for implementation defined reasons. 08005 Communication failure. 08006 Transaction rolled back. 08007 Connection failure during transaction. 08S01 Communication link failure.
ODBC/MX Client Messages ODBC/MX Messages SQLSTATE Message 40001 Attempt to initiate new SQL server operation with data pending. 42000 Syntax error or access rule violation. 70100 Operation aborted (server did not process cancel request). HY721 TranslationDLL Truncation: DataSourceToDriver. HY721 TranslationDLL Truncation: DriverToDataSource. HY722 TranslationDLL Error: DataSourceToDriver. HY723 TranslationDLL Error: DriverToDataSource. IM001 Driver does not support this function.
ODBC/MX Client Messages ODBC/MX Messages SQLSTATE Message S1005 Parameter number out of range. S1006 Invalid conversion specified. S1007 Row count not available from the data source. S1008 Operation cancelled. S1009 Invalid argument value. SQLSTATE Message S1010 Function sequence error S1012 Invalid transaction operator code specified. S1015 No cursor name available. S1090 Invalid string or buffer length. S1091 Descriptor type out of range. S1092 Option type out of range.
Glossary driver manager. The Microsoft ODBC component that manages access to Database Management System (DBMS) drivers for ODBC applications. The driver manager loads and unloads drivers and passes calls for ODBC functions to the correct driver. ODBC/MX requires the Microsoft 3.51 (or later) driver manager. Open Database Connectivity (ODBC). An interface specification for an API that defines a standard set of routines that an ODBC application can use to access data in a data source.
Glossary Open Database Connectivity (ODBC) HP NonStop ODBC/MX Driver for Windows—527888-004 Glossary- 2
Index A ABS function 5-7 ACOS function 5-7 adding data sources to client 2-4, 3-1 alias names, adding 1-7 ANSI name type 1-7 API functions, ODBC supported 5-1/5-7 architecture 1-1 ASCII function 5-8 ASIN function 5-7 association server, functions of 1-2 ATAN function 5-7 ATAN2 function 5-7 autocommit 5-14 B BIGINT data type 5-10 BINARY data type 5-11 BIT data type 5-10 Bring 3-3 C CAST function 5-10 catalog restrictions 1-8 CEILING function 5-7 CHAR data type 5-10 CHAR function 5-8 client adding new data
D Index D Data Source Administrator, Microsoft ODBC 3-1 data sources default TDM_Default_DataSource 1-1 functions for connecting to 5-2 functions for obtaining information 5-2 functions for system tables 5-5 mapping client to server names 1-3 tools for managing 1-1 data sources, client adding 3-1 adding to client interface 2-4 connecting to 1-2 managing 3-1/3-3 overview of 1-2 reconfiguring 3-2 removing 3-3 tracing 3-3, 3-4 Data Types unsigned 5-12 data types unsigned 5-12 data types not supported 1-11 da
H Index H M help repairing client installation 2-5 HOUR function 5-9 managing client data sources 3-1/3-3 mapping, data types 5-12 messages 6-1/6-4 Microsoft escape clauses, support for 5-13 Microsoft ODBC conformance to 5-1 Data Source Administrator 1-2 driver manage functions 5-2 driver manager description 1-1 driver manager restrictions 1-8 functions supported 5-1/5-7 Microsoft ODBC Data Source Administrator 3-1 Microsoft SQL, conformance to 5-7 MINUTE function 5-9 MOD function 5-8 Module File Cachi
O Index O object name types ANSI 1-6, 1-7 ANSI for SQL/MP objects 1-7 ANSI for SQL/MX objects 1-7 Guardian in SQL commands 1-6 ODBC applications, connection pooling 1-5/1-6 ODBC Data Source Administrator, Microsoft 3-1 ODBC data types supported 5-10 ODBC/MX See NonStop ODBC/MX ODBC/MX driver description 1-1 functions for setting and retrieving attributes 5-3 P performance improvements using connection pooling 1-4 PI function 5-8 pooling connections 1-4 POWER function 5-8 PUBLIC_ACCESS_SCHEMA schema 1-8
T Index SQLDisconnect function 5-7 SQLDriverConnect function 5-2 SQLDrivers function 5-2 SQLEndTran function 5-7 SQLExecDirect function 5-4 SQLExecute function 5-4 SQLExtendedFetch function 5-5 SQLFetch function 5-4 SQLFetchScroll function 5-4 SQLForeignKeys function 5-5 SQLFreeHandle function 5-7 SQLFreeStmt function 5-6 SQLGetConnectAttr function 5-3 SQLGetCursorName function 5-3 SQLGetData function 5-4 SQLGetDescField function 5-3 SQLGetDescRec function 5-3 SQLGetDiagField function 5-5 SQLGetDiagRec fu
U Index TRIM...LEADING function 5-8 TRIM...
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.
