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 3.2 Supported Release Version Updates (RVUs) This manual supports J06.15 and all subsequent J-series RVUs and H06.
Document History Part Number Product Version 691126-002 HP NonStop ODBC/MX 3.
Legal Notices Copyright 2013 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 About This Manual vii Audience vii Related Documentation vii Notation Conventions xi HP Encourages Your Comments v xii 1.
2. Installation of the ODBC/MX Client Contents Limitations of ODBC/MX Driver 1-12 2. Installation of the ODBC/MX Client Components of the MX connectivity service 2-1 Installing the Client Components 2-1 Installation Requirements 2-1 Step 1: Download and Run the Installation File Step 2: Install the Client Interface Components Step 3: Add a Data Source 2-3 Step 4: Delete the Installation Folder 2-3 Step 5: Restart the PC 2-3 ODBC/MX Driver Component 2-3 Uninstalling the Client Interface 2-4 2-2 2-2 3.
6. ODBC/MX Messages Contents SQL/MP Data Types and ODBC/MX Equivalents 5-13 Microsoft Escape Clauses 5-13 Stored Procedures 5-14 Transactions and Cursor Behavior with Multiple Statements Timestamp Values with Fraction 5-15 SQL Interval Value Insertion Property 5-21 Datetime Retrieval Property 5-24 5-15 6. ODBC/MX Messages ODBC/MX Driver Error Codes 6-1 ODBC/MX Client Messages 6-1 Glossary Index Figures Figure 1-1. Figure 3-1. Figure 5-1. Figure 5-2.
Contents Table 5-17. Table 5-18. Table 5-19. Table 5-20. Table 5-21. Table 5-22. Table 5-23. Table 5-24. Table 5-25. Table 5-26.
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 3.2 Supported Release Version Updates (RVUs) This manual supports J06.
What’s New in This Manual New and Changed Information Added connection attributes to Configuring Client Data Sources using Connection String on page 3-2. Changes to the 663858-001 manual: Added a section Configuring Client Data Sources using HP SSL on page 3-7. Updated the section MFC Usage Scenarios on page 4-2. Updated SQLGetInfo in Obtaining Information About a Driver and Data Source on page 5-1. Added a Note on page 5-13. Added Windows 7 to the list of operating systems on page 1-1.
About This Manual Audience This manual is for: ODBC application programmers who write 32-bit or 64-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 Upgrade Guide Describes how to plan for install and upgrade an SQL/MX database. SQL/MX Query Guide Describes how to understand query execution plans and write optimal queries for an SQL/MX database. SQL/MX Management Guide Describes how to manage 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 The NSM/web, SQL/MX Database Manager, and Visual Query Planner help systems are accessible from their respective applications. You can download the Reference, Messages, and Glossary online help from the HP Software Depot at http://www.software.hp.com. For more information about downloading the online help, see the SQL/MX Release 3.2 Installation and Upgrade 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 Default Data Source Default Data Source MXCS provides a preconfigured, default server data source on the server called TDM_Default_DataSource. You can stop and start the TDM_Default_DataSource 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 3. The ODBC client application sends a connection request to the MXCS SQL server that was assigned by the association server. If the user information is not valid, the connection is rejected. 4. When the ODBC client application disconnects, the MXCS SQL server notifies the association server that it is available for connections from other ODBC clients and returns to the server data source pool.
ODBC/MX Client Overview Connection Pooling source name does not exist, the association server routes the connection to the default data source. If the default data source is not started, the connection request is rejected. After a data source name is assigned, the association server uses any MXCS SQL server that was previously used by the same userid.
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 other ODBC client software. R 2.3.
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-2. 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 Limitations of ODBC/MX Driver The precision of the NUMERIC data type is extended up to 128 digits for signed and unsigned values. Limitations of ODBC/MX Driver The system running an R 3.x version of Windows ODBC/MX Driver does not connect to a NonStop system running an R 2.x version of ODBC/MX server objects. When you try to connect an R 3.x version of Windows ODBC/MX Driver to an R 2.x version of ODBC/MX server objects, the behavior is unpredictable.
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-4 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.
Step 1: Download and Run the Installation File Installation of the ODBC/MX Client Step 1: Download and Run the Installation File 1. Turn off all other applications running on the client workstation. Note. If Microsoft OutsideView32 is running, it must be stopped before you perform this installation. 2. Create a temporary client installation folder on the client workstation; for example: C:\ODBCTEMP.
Step 3: Add a Data Source Installation of the ODBC/MX Client Screen Button Description 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.
Uninstalling the Client Interface Installation of the ODBC/MX Client File Name Description tdm_oadm0300.dl NonStop ODBC/MX Client Adminstration DLL tdm_odbc0300.dll NonStop ODBC/MX Driver DLL tdm_odbcDrvMsg_intl0300.dll NonStop ODBC/MX Client Msg DLL tdm_OdbcTrace0300.dll NonStop ODBC/MX Client Trace DLL tdm_ores0300.dll NonStop ODBC/MX Driver Resource DLL tdm_tcpipv40300.dll NonStop ODBC/MX TCPIPV4 DLL tdm_tcpipv60300.dll NonStop ODBC/MX TCPIPV6 DLL tdm_translation.dll.
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 Configuring Client Data Sources using Connection String Attribute Description DSN Name of the data source as returned by SQLDataSources API or the data sources dialog box of SQLDriverConnect API. FILEDSN Name of a .dsn file. The driver builds the connection string for the data source with the information stored in this file. DRIVER Description of the driver as returned by the SQLDrivers API. For example, Rdb or SQL Server. SAVEFILE The file name of a .
Configuring Client Data Sources for Update Operations Configuring Client Data Sources on Windows TRANSLATIONDLL Translates the data from one character set to other. Set the TRANSLATIONDLL in either of the following ways: TRANSLATIONDLL= Click Browse to select a DLL. The DLL you specify is used to map the character set for a particular language. TRANSLATIONOPTION Options supported by the translation DLL. SERVERDSN Server Data Source.The default is TDM_Default_DataSource.
Configuring Client Data Sources on Windows Removing Client Data Sources Figure 3-1. ODBC/MX Data Source Configuration 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 ODBCMX 3.2 option, then select the MS ODBC Administrator option. 2.
Configuring Client Data Sources on Windows Tracing Client Data Sources For more information about a screen, click Help. Tracing Client Data Sources Configure tracing on a client data source: 1. Bring up the Microsoft ODBC Data Source Administrator. You can usually find this by selecting the Start menu, Programs option, NonStop ODBCMX 3.2 option, then select the MS ODBC Administrator option. 2. Select a data source name then click Configure. 3. Select the Tracing tab. 4. Select one or both trace options.
Configuring Client Data Sources on Windows Configuring Client Data Sources using HP SSL Stop tracing on a client data source: 1. Bring up the Microsoft ODBC Data Source Administrator. You can usually find this by selecting the Start menu, Programs option, NonStop ODBCMX 3.2 option, then select the MS ODBC Administrator option. 2. Select the Tracing tab. 3. Click Stop Tracing Now. 4. Click Apply then OK. Configuring Client Data Sources using HP SSL IPV6 is not supported for ODBC/MX driver through HP SSL.
Configuring Client Data Sources on Windows Configuring Client Data Sources using HP SSL HP NonStop ODBC/MX Driver for Windows—691126-002 3-8
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() and SQLExecDirect() have the 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 ODBC API Functions ODBC/MX conforms with the ODBC interface core level. The following tables show the ODBC/MX support for each ODBC API function. The column headed ODBC Version lists the version of the Microsoft ODBC standard in which a function was first introduced. For example, if ODBC Version 1.0 is listed as supported, then the feature was first defined in version 1.0 of the Microsoft ODBC standard and ODBC/MX currently supports the function.
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 ATAN2 ATAN2 CEILING CEILING 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 LOCATE LOCATE (ODBC LOCATE start parameter is not supported.) LTRIM TRIM...LEADING REPEAT REPEAT REPLACE REPLACE RIGHT RIGHT RTRIM TRIM...TRAILING SOUNDEX Not supported SPACE SPACE SUBSTRING SUBSTRING UCASE UPPER | UPSHIFT Note.
ODBC Data Types ODBC/MX Conformance Table 5-13. Time and Date Functions (page 2 of 2) ODBC Function SQL/MX Equivalent Function TIMESTAMPADD Not supported TIMESTAMPDIFF Not supported WEEK WEEK 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 Table 5-15. ODBC Data Types (page 3 of 3) ODBC Data Type SQL/MX Data Type SQL/MP Data Type Supported by ODBC/MX INTERVAL HOUR(p) TO SECOND(q) INTERVAL HOUR(p) TO SECOND(q) Yes INTERVAL MINUTE(p) TO SECOND(q) INTERVAL MINUTE(p) TO SECOND(q) Yes * The VARCHAR length can be up to 4059 for key-sequenced files or 4070 for entry-sequenced files. ** Starting with SQL/MX Release 3.0, the precision of the NUMERIC data type is extended to 128 digits.
SQL/MP Data Types and ODBC/MX Equivalents ODBC/MX Conformance SQL/MP Data Types and ODBC/MX Equivalents Table 5-17.
Microsoft Escape Clauses ODBC/MX Conformance Microsoft Escape Clauses ODBC/MX accepts Microsoft escape clauses and translates them into equivalent SQL/MX clauses. Table 5-18.
Transactions and Cursor Behavior with Multiple Statements ODBC/MX Conformance Transactions and Cursor Behavior with Multiple Statements Table 5-19. Transactions and Cursor Behavior Autocommit SQL/MX Behavior Action Required ON When any open statement reaches end of data or end of cursor, SQL/MX closes all other open statements. N.A. OFF N.A. The application must explicitly rollback or commit the transaction. All open statements are closed at that time.
Timestamp Values with Fraction ODBC/MX Conformance Table 5-20. Sample Values Inserted From a C/C++ Program and Their Corresponding Expected Values in Microsecond (page 1 of 2) Value Specified in the Fraction of the Client Program Column Type Expected Value in the Column of the SQL/MX Table 987654 timestamp(6) or time(6) 0.987654 87654 timestamp(6) or time(6) 0.087654 7654 timestamp(6) or time(6) 0.007654 654 timestamp(6) or time(6) 0.000654 54 timestamp(6) or time(6) 0.
Timestamp Values with Fraction ODBC/MX Conformance Table 5-20. Sample Values Inserted From a C/C++ Program and Their Corresponding Expected Values in Microsecond (page 2 of 2) Value Specified in the Fraction of the Client Program Column Type Expected Value in the Column of the SQL/MX Table 87654 timestamp(1) or time(1) 0.0 7654 timestamp(1) or time(1) 0.0 654 timestamp(1) or time(1) 0.0 54 timestamp(1) or time(1) 0.0 4 timestamp(1) or time(1) 0.
Timestamp Values with Fraction ODBC/MX Conformance Table 5-21. Sample Values Inserted From a C/C++ Program and Their Corresponding Expected Values in Nanosecond (page 2 of 2) Value Specified in the Fraction of the Client Program Column Type Expected Value in Column of the SQL/MX Table 54321 timestamp(4) or time(4) 0.0000 4321 timestamp(4) or time(4) 0.0000 987654321 timestamp(3) or time(3) 0.987 87654321 timestamp(3) or time(3) 0.087 7654321 timestamp(3) or time(3) 0.
Timestamp Values with Fraction ODBC/MX Conformance Table 5-22. SYSTEM_DEFAULT Values Retrieved Using a C/C++ Program Value in the Column of the SQL/MX Table Column Type Value in the Fraction of the Client Program 0.000654 timestamp(6) or time(6) 654 0.000054 timestamp(6) or time(6) 54 0.000004 timestamp(6) or time(6) 4 0.98765 timestamp(5) or time(5) 98765 0.08765 timestamp(5) or time(5) 8765 0.00765 timestamp(5) or time(5) 765 0.00065 timestamp(5) or time(5) 65 0.
Timestamp Values with Fraction ODBC/MX Conformance Table 5-23. Sample Values Retrieved Using a C/C++ Program and Their Corresponding Expected Values in Nanosecond Value in the Column of the SQL/MX Table Column Type Value in the Fraction of the Client Program 0.987654 timestamp(6) or time(6) 987654000 0.087654 timestamp(6) or time(6) 87654000 0.007654 timestamp(6) or time(6) 7654000 0.000654 timestamp(6) or time(6) 654000 0.000054 timestamp(6) or time(6) 54000 0.
SQL Interval Insertion Property ODBC/MX Conformance The ODBC programs can insert the time and timestamp values into the time and timestamp columns of an SQL/MX table using the FRACTION_STRUCT structure. The structure fields are: Note.
SQL Interval Insertion Property ODBC/MX Conformance In the Data Access tab, set the SQL Interval Insertion property for INTERVAL data type behavior to be the same as MSDN behavior. You can set the property using the Microsoft ODBC Data Source Administrator by selecting the respective Data Source configuration. Figure 5-1.
SQL Datetime Retrieval Property ODBC/MX Conformance create table interval_frac ( ID2S interval day to second, ID2S0 interval day to second ID2S1 interval day to second ID2S2 interval day to second ID2S3 interval day to second ID2S4 interval day to second ) (0), (1), (2), (3), (4) For the above DDL, when you insert values for all columns as 11 22:33:44.1 and 02 11:21:12.1234 binding to valid datatypes, the values are inserted as follows: Table 5-25.
SQL Datetime Retrieval Property ODBC/MX Conformance SYSTEM_DEFAULT - Year is set to 0001. MSDN_DEFAULT - Year is set to 1900. If not specified, the default is SYSTEM_DEFAULT. This property is applicable only when SQL/MP Datetime datatype is bound to SQL/MX datatypes such as DATE or TIMESTAMP. In the Data Access tab, set the SQL Datetime Retrieval property using the Microsoft ODBC Data Source Administrator by selecting the respective Data Source configuration. Figure 5-2.
SQL Datetime Retrieval Property ODBC/MX Conformance Retrieve the data from the SQL/MP Datetime datatype “month to day” column from ODBC/MX driver by binding to DATE. The retrieved value is 0001-1231. If the value of SQL Datetime Retrieval is set to MSDN_DEFAULT, there is a change in the behavior of the driver when compared to earlier releases of SQL/MX. For example: Create a table in SQL/MP with Datetime column as “month to day”.
ODBC/MX Conformance SQL Datetime Retrieval Property HP NonStop ODBC/MX Driver for Windows—691126-002 5-26
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 6001 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 6001 INVALID DLL HANDLE. 6002 CANNOT LOAD PROCADDRESS. 6003 WRONG WINSOCK VERSION. 6004 WRONG SIGNATURE. 6005 WRONG VERSION. 6006 ERROR FROM SERVER. 6007 INCORRECT LENGTH. 6008 MEMORY ALLOCATE. 6009 WRONG IP ADDRESS. 6010 Connection lost, invalid code path. SQLSTATE Messages 08001 No more MXCS servers available to connect. 08001 MXCS services not yet available. 08001 Datasource not yet available or not found.
ODBC/MX Client Messages ODBC/MX Messages SQLSTATE Message 22001 String data right truncation. 22003 Numeric value out of range. 22005 Error in assignment. 22005 Precision or scale out of range. 22008 Datetime field overflow. 22012 Division by zero. 22015 Interval field overflow. 22018 Invalid character value for cast specification. 23000 Integrity constraint violation. 24000 Invalid cursor state. 25000 Invalid transaction state. 26000 Invalid SQL statement identifier.
ODBC/MX Client Messages ODBC/MX Messages SQLSTATE Message S0012 Invalid index name; index not found. S0021 Invalid column name; column already exists. S0022 Invalid column name; column not found. SQLSTATE Message S1000 General error. S1000 General error: Ongoing transaction has been committed. S1000 General error. Failed since resource governing policy is hit.
ODBC/MX Client Messages ODBC/MX Messages SQLSTATE Message S1095 Function type out of range. S1096 Information type out of range. S1097 Column type out of range. S1098 Scope type out of range. S1099 Nullable type out of range. SQLSTATE Message S1100 Uniqueness option type out of range. S1101 Accuracy option type out of range. S1102 Table type out of range. S1103 Direction option out of range. S1105 Invalid parameter type or parameter type not supported.
ODBC/MX Messages ODBC/MX Client Messages HP NonStop ODBC/MX Driver for Windows—691126-002 6-6
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—691126-002 Glossary-2
Index A ABS function 5-7 ACOS function 5-7 adding data sources to client 2-3, 3-1 alias names, adding 1-7 ANSI name type 1-7 API functions, ODBC supported 5-2/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-8 autocommit 5-15 B BIGINT data type 5-11 BINARY data type 5-11 BIT data type 5-11 Bring 3-6 C CAST function 5-10 catalog restrictions 1-8 CEILING function 5-8 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-2 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-3 connecting to 1-2 managing 3-1/3-6 overview of 1-2 reconfiguring 3-2, 3-4, 5-15 removing 3-5 tracing 3-6, 3-7 Data Types unsigned 5-12 data types unsigned 5-12 data types not suppor
I Index I IFNULL function, ODBC/MX 5-10 INSERT function 5-8 installation restrictions 1-8 installing overview of 2-1 installing the client interface requirements 2-1 step 1, download installation file 2-2 step 2, run InstallShield 2-2 step 3, add a data source 2-3 step 4, delete installation folder 2-3 INTEGER data type 5-10 INTERVAL...
P Index 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 Q QUARTER function 5-9 R RADIANS function 5-8 RAND function 5-8 REAL data type 5-10 release restrictions 1-8 REPEAT function 5-9 REPLACE function 5-9 requests funct
T Index 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 function 5-5 SQLGetEnvAttr function 5-3 SQLGetFunctions function 5-2 SQLGetInfo function 5-2 SQLGetStmtAttr function 5-3 SQLGetTypeInf
U Index U UCASE function 5-9 uninstalling client interface 2-4 update 3-4 UPPER function 5-9 UPSHIFT function 5-9 USER function 5-10 V VARBINARY data type 5-11 VARCHAR data type 5-10 W WEEK function 5-10 HP NonStop ODBC/MX Driver for Windows—691126-002 Index-6
