HP NonStop ODBC/MX Client Drivers User Guide for SQL/MX Release 3.2.1 HP Part Number: 734873-002 Published: November 2013 Edition: J06.16 and subsequent J-series RVUs; H06.
© 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.
Contents About this document......................................................................................5 Intended audience....................................................................................................................5 Document organization.............................................................................................................5 New and changed information in this edition...............................................................................
Partial DATE or TIME values.....................................................................................................40 Microsoft escape clauses.........................................................................................................41 Stored Procedures...................................................................................................................41 Transaction and cursor behavior...................................................................................
About this document This manual describes how to install, configure and use the ODBC/MX client drivers. These drivers allow HP-UX, Linux32, Linux64, OSS and Windows applications developed for Open Database Connectivity (ODBC) to access data from an SQL/MX database on a NonStop system.
Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name Computer Type Computer type letters within text indicate case-sensitive keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.sh Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.
{, sql-expression}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: expression-n… Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: DAY (datetime-expression) @script-file Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown.
• Installation guides SQL/MX Installation and Upgrade Guide Describes how to plan for install and upgrade an SQL/MX database. SQL/MX Management Manual Describes how to manage an SQL/MX database. NSM/web Installation Guide • • • • 8 Describes how to install NSM/web and troubleshoot NSM/web installations. Reference manuals SQL/MX Reference Manual Describes the syntax of SQL/MX statements, MXCI commands, functions, and other SQL/MX language elements.
• Application development guides SQL/MX Programming Manual Describes how to embed SQL/MX statements in ANSI C and COBOL programs. for C and COBOL • SQL/MX Query Guide Describes how to understand query execution plans and write optimal queries for an SQL/MX database. SQL/MX Queuing and Publish/Subscribe Services Describes how NonStop SQL/MX integrates transactional queuing and publish/subscribe services into its database infrastructure.
1 Overview The following ODBC/MX client drivers enable ODBC applications running on various platforms, to access a NonStop SQL/MX database: • Linux 32–bit and 64–bit drivers • HP-UX 64–bit driver • Windows 32–bit and 64–bit drivers for ANSI and Unicode applications • OSS 32–bit and 64–bit libraries The HP-UX, Linux, OSS, Windows ANSI and Unicode ODBC/MX client drivers are collectively referred as drivers. In this manual the HP-UX, Linux, and OSS drivers are collectively referred as Unix drivers.
Figure 1 Architecture Application unixODBC DM HP SQL/MX DM HP Linux/HP UX ODBC/MX Driver Application ODBC/MX Client (Linux or HP-UX System) OSS ODBC/MX Client Driver ODBC/MX Server (MXCS) Configuration Server Association Server ODBC Server Data sources A and B Application DB Microsoft ODBC DM Nonstop System HP ANSI/Unicode ODBC/MX Driver ODBC/MX Client (Windows System) A - TDM_Default_Data Source B - Data Source B DB - SQL/MX Database The application calls the SQLConnect() ODBC API to open a con
MXODSN file, and for the OSS driver in the ODBCDSN file. Use the Microsoft ODBC Data Source Administrator to configure the parameters for the Windows driver. Client components The common client components are the ODBC applications, which are user-written or third-party products that use the ODBC APIs, and the driver for the application platform.
Data sources Data sources are logical groupings of connections to the SQL/MX database. There are two types of data sources. • Client data source, commonly known as Data Source Name (DSN). The DSN is configured on the client workstation. • Server data source, which you must define and start on the NonStop system. The driver uses the client data source configuration to route the ODBC API requests to MXCS.
Tracing HP-UX, Linux 32 and Linux 64 The trace information is captured in a log file. You can enable or disable tracing and specify the trace file name in MXODSN file. When using the unixODBC driver manager, you can enable the driver tracing by setting the following environment variables: • HPODBC_TRACE_LEVEL. For trace values, see “MXODSN and ODBCDSN file formats” (page 30). • HPODBC_TRACEFILE_NAME to set the trace file name.
Table 1 Unsupported ODBC APIs Category Unsupported APIs Installer – Data Sources • SQLManageDataSources • SQLRemoveDefaultDataSource • SQLConfigDataSource • SQLCreateDataSource • SQLValidDSN • SQLRemoveDSNFromIni • SQLWriteDSNToIni Installer – Drivers • SQLConfigDriver • SQLRemoveDriver • SQLInstallDriver • SQLInstallDriverEx • SQLValidDSN • SQLGetInstalledDrivers Installer – Driver Manager • SQLRemoveDriverManager • SQLInstallDriverManager Installer – Installer Errors • SQLInstallerError • SQLPost
The following are the considerations and limitations for the Windows Unicode driver: • You cannot execute DDL statements with character set qualifiers _UCS2 or N. • Prefix _UCS2 or N to the string literal for the following columns to execute DML statements: ◦ CHAR CHARACTER SET UCS2 column ◦ NCHAR column — the default NATIONAL character set is UCS2 ◦ VARCHAR CHARACTER SET UCS2 column ◦ NCHAR VARYING column — the default NATIONAL character set is UCS2 For example, insert into CAT.SCH.
2 Installing the drivers The hardware and software requirements for the drivers are described in the softdoc or README file delivered with the products, either through the product CD or through the Scout website for NonStop servers in the HP NonStop eServices portal (https://onepoint.nonstop.compaq.com/).
1. 2. 3. Download the driver from NonStop system to the HP–UXia64 workstation in binary mode (You can use FTP utility for downloading). The driver is packaged as a tar file in the Software Update Tape (SUT) and is available on the NonStop system when DSM/SCM is used to install the SUT. The file name is ODBC64HI, and is located in the volume $SYSTEM.ZMXODBC. Log on to the HP–UXia64 workstation as a root user.
3. Go to download directory, and enter the following command to extract the files: tar -xvf LODBC64 nl The files are extracted to 64Linux_ODBC_321 directory. The install scripts and the README file are also extracted with the driver. 4. 5. 6. Go to the 64Linux_ODBC_321 directory. To start the installation, enter the following command: ./runme.sh Enter 1 and press Enter. If you have already installed the driver, a warning message appears.
10. You can retain the default or provide a different Program Folder on the following screen: Click Next. 11. You can see the installation progress in the Setup Status progress bar.
12. Click Finish. NOTE: • HP recommends that you restart the PC before you use the ODBC/MX client interface. • When the installation is complete, delete the temporary installation folder. Verifying the installation HP-UX After a successful installation, the following files are installed: • /usr/lib/hpux64/libmxodbc_ia64.sl • /usr/lib/hpux64/libmxodbc_ia64_drvr.sl • /usr/lib/hpux64/libhpsecClient64.
• /usr/lib/libmxodbc_l_drvr.so.3 • /usr/lib/libmxodbc_l_drvr.so.3.2.1 • /usr/lib/libhpsecClient.so • /etc/hpodbc/MXODSN The checksum of the shared libraries must match the checksum in the md5sum file. Linux 64 After a successful installation, the following files are installed: • /usr/lib64/libmxodbc64.so • /usr/lib64/libmxodbc64.so.3 • /usr/lib64/libmxodbc64.so.3.2.1 • /usr/lib64/libmxodbc64_l_drvr.so • /usr/lib64/libmxodbc64_l_drvr.so.3 • /usr/lib64/libmxodbc64_l_drvr.so.3.2.
1. 2. 3. Log in to the HP-UXia64 workstation as a root user. Go to the HPUXia64_ODBC_64 directory. To uninstall the driver, enter the following command: ./runme.sh 4. 5. 6. Enter 2 and press Enter. Enter yes if you want to continue with uninstall operation. Enter yes if you want to remove the configuration files. Upon successful uninstallation, the following message is displayed: UnInstalled ! Linux 32 Perform the following steps to uninstall the driver: 1.
3 Configuring data sources This chapter describes the various procedures to configure the SQL/MX data sources.
3. 4. Select the data source name that you want to configure and click Configure. Each tab in the configuration view displays different fields in the data source configuration. Make the required changes. For more information about the Microsoft ODBC Data Source Administrator screens and tabs, click Help.
Configuring the drivers for IPv6 HP-UX, Linux 32 and Linux 64 You can directly enter the IPv6 address instead of IPv4 address in the MXODSN or odbc.ini (when using the unixODBC driver manager) configuration files. The driver recognizes the IPv6 address format and connects to the server. The following is a sample from the configuration file: Server = TCP: 2620:0:a17:e03e:a00:8eff:fe08:cd65:3033 OSS Perform the following steps for the driver to use IPv6: 1.
1. 2. Log on as super.super. Enter the following command to change to the NonStop SSL directory: $SYSTEM STARTUP 1> volume $system.znsssl 3. Enter the following command at the TACL prompt to start the setup: $SYSTEM ZNSSSL 10> run $SYSTEM.ZNSSSL.SETUP 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Enter [7] to select ODBC/MX server in run mode. Enter the home terminal. The default value is $YMIOP.#CLCI. Enter the CPU on which you want to run SSL. The default value is CPU 3. Enter the SSL process name.
1. 2. 3. 4. 5. 6. Download the $SYSTEM.ZNSSSL.PROXYEXE file in binary format and rename it to PROXY.EXE. Run PROXY.EXE to start the RemoteProxy installation program, and follow the installation instructions in the wizards. Double-click the NonStop SSL RemoteProxy icon in your system tray. The RemoteProxy configuration window is displayed. Select Session –> New. The HP NonStop SSL RemoteProxy dialog is displayed. 1. Select ODBCMX Client in the Protocol menu. 2.
DataSource configuration in Windows driver DataSource configuration in Windows driver 29
MXODSN and ODBCDSN file formats The following table describes the various sections in the MXODSN and ODBCDSN files. Table File sections File Section Description [ODBC] This section lists the tracing options. [ODBC Data Sources] This section lists the data sources. Data source specification Each DSN listed in the [ODBC Data Sources] section must have this section that describes the DSN. [DataSourceName] Associates a driver with the DSN. Table 4 describes the MXODSN and ODBCDSN attributes.
Table 4 MXODSN and ODBCDSN attributes (continued) File Section Attributes Description 1, tracing is on. By default, tracing is off. TraceFlags TraceFlags indicates the trace level. It can have the following values: • ERROR to trace failed SQL calls and communication problems. • WARNING to trace the warnings. • CONFIG to trace configuration calls. • INFO to trace details about calls made. • DEBUG to trace the internal details about calls made for debugging an issue.
Table 4 MXODSN and ODBCDSN attributes (continued) File Section Attributes Description seconds. SQLIntervalBehaviour has two values, SYSTEM_DEFAULT and MSDN_DEFAULT. If not specified, the default is SYSTEM_DEFAULT. For more information, see “SQL Interval Behaviour property” (page 46). [DataSourceName] SQLDatetimeRetrieval SQLDatetimeRetrieval specifies how the SQL/MP Datetime data type is retrieved from the driver. SQLDatetimeRetrieval has two values, SYSTEM_DEFAULT and MSDN_DEFAULT.
[ODBC] TraceFlags = 6 TraceStart = 0 TraceFile = trlog [ODBC Data Sources] TDM_Default_DataSource = NonStop ODBC/MX 3.x DS1 = NonStop ODBC/MX 3.x DS2 = NonStop ODBC/MX 3.x DataSourceName = Driver [TDM_Default_DataSource] Description = Default Data Source Catalog = CAT Schema = SCH DataLang = 0 FetchBufferSize = SYSTEM_DEFAULT Server = TCP:xxx.xxx.xxx.
Windows To add a new data source or configure an existing data source, see “Configuring a client data source”. Perform the following steps to delete a client data source: 1. Select Start -> Control Panel -> Administrative Tools -> Data Sources (ODBC). 2. Click either the System DSN or the User DSN tab to get the list of data sources. 3. Select the data source name that you want to delete and click Remove. 4. Click Yes in the confirmation dialog box to remove the data source.
Using connection string without DSN You can set AUTOCOMMIT as part of the Connection string. “AutoCommit=ON/OFF/SERVER_DEFAULT”. Example 2 Depicting AUTOCOMMIT set to ON Driver={NonStop(TM)ODBCMX 3.2}; ServerDSN = TDM_Default_DataSource; SERVER =TCP:; UID=; PWD=; AutoCommit=ON; ..,..,.,,.
If you select the ODBC standard trace DLL (odbctrac.dll from the Windows System folder), only the driver manager is traced; additional trace options that you select are ignored. If you select the ODBC/MX trace DLL (tdm_odbctrace0300.dll or tdm_odbctracew0300.dll from the Windows System folder), all trace options that you select for the client data source are considered. 4. 5. 6. Use the Browse button to locate the correct log file. Click Start Tracing Now. Click Apply and then click OK.
4 Compatibility and considerations The drivers are compatible with the following: • ODBC 3.5 • SQL-92 features supported by SQL/MX For more information about SQL/MX supported scalar and string functions, see the SQL/MX Reference Manual for Release 3.x.
Table 5 Considerations (continued) Item Consideration SQLSpecialColumns API This API does not support pattern value arguments for table names, and returns an optimal set of columns that the SQLSpecialColumns API uniquely identifies a row in the table information for a specified table name in the SQL/MX catalog. SQLStatistics API This API does not support pattern value arguments for table names, and returns index information for a specified table name in the SQL/MX catalog.
Table 6 ODBC Data Types (continued) ODBC data type SQL/MX data Type SQL/MP data Type Supported by the driver? TINYINT UNSIGNED Not supported Not supported No BIGINT LARGEINT LARGEINT Yes BINARY(n) Not supported Not supported No VARBINARY(n) Not supported Not supported No LONG VARBINARY Not supported Not supported No DATE DATE DATE Yes TIME(p) TIME TIME Yes TIMESTAMP TIMESTAMP TIMESTAMP Yes INTERVAL MONTH(p) INTERVAL MONTH(p) Yes INTERVAL YEAR(p) INTERVAL YEAR(p) Yes
Table 7 Behavior of unsigned data types ODBC version Behavior 2.0 UNSIGNED SMALLINT is promoted to SIGNED INT and UNSIGNED INT is promoted to BIGINT. 3.x, when server data source is configured with SQL_ATTR_MSACCESS_VERSION flag All unsigned data types are promoted to the next signed type. Partial DATE or TIME values To use partial DATE or TIME values as parameters, provide these values through the ODBC/MX data type returned. To fetch partial DATE or TIME values, see the mappings in Table 8 (page 40).
Table 8 SQL/MP to ODBC/MX Date/Time Mappings (continued) SQL/MP data type ODBC/MX data type DATETIME MINUTE TO FRACTION SQL_TIMESTAMP DATETIME SECOND SQL_TIME DATETIME SECOND TO FRACTION SQL_TIMESTAMP DATETIME VALUE RETRIEVAL SQL DATETIME RETRIEVAL Microsoft escape clauses ODBC/MX accepts Microsoft escape clauses and translates them into equivalent SQL/MX clauses. Table 9 lists the SQL/MX equivalents.
Table 10 Transaction and cursor behavior AUTOCOMMIT SQL/MX behavior Application action ON When any open statement reaches Not applicable end of data or end of cursor, SQL/MX closes all other open statements. OFF Not applicable The application must explicitly rollback or commit the transaction. All open statements are closed at that time.
Table 11 Sample values inserted from an application and expected values in microsecond (continued) Fraction value in the application Column type Expected value in the column of SQL/MX table 54 timestamp(3) or time(3) 0.000 4 timestamp(3) or time(3) 0.000 987654 timestamp(2) or time(2) 0.98 87654 timestamp(2) or time(2) 0.08 7654 timestamp(2) or time(2) 0.00 654 timestamp(2) or time(2) 0.00 54 timestamp(2) or time(2) 0.00 4 timestamp(2) or time(2) 0.
Table 12 Sample values inserted from an application and expected values in nanoseconds (continued) Fraction value in the application Column type Expected value in the column of SQL/MX table 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.007 654321 timestamp(3) or time(3) 0.000 54321 timestamp(3) or time(3) 0.000 4321 timestamp(3) or time(3) 0.
Table 13 Values retrieved by the application for SYSTEM_DEFAULT setting (continued) Value in the column of the SQL/MX Table Column type Fraction value retrieved by the application 0.9876 timestamp(4) or time(4) 9876 0.0876 timestamp(4) or time(4) 876 0.0076 timestamp(4) or time(4) 76 0.0007 timestamp(4) or time(4) 7 0.0000 timestamp(4) or time(4) 0 0.987 timestamp(3) or time(3) 987 0.087 timestamp(3) or time(3) 87 0.008 timestamp(3) or time(3) 8 0.
Table 14 Sample values retrieved by the application (continued) Value in the column of the SQL/MX Table Column type Fraction value retrieved by the application 0.987 timestamp(3) or time(3) 987000000 0.087 timestamp(3) or time(3) 87000000 0.008 timestamp(3) or time(3) 8000000 0.000 timestamp(3) or time(3) 0 0.98 timestamp(2) or time(2) 980000000 0.09 timestamp(2) or time(2) 90000000 0.00 timestamp(2) or time(2) 0 0.9 timestamp(1) or time(1) 900000000 0.
If not specified, the default is SYSTEM_DEFAULT. Set the SQL Interval Behaviour property using the MXODSN property. • The following example describes when the value of SQL Interval Behaviour is set to SYSTEM_DEFAULT, the behavior of the drivers is same as in earlier releases of SQL/MX.
SQL Datetime Retrieval property The SQL Datetime Retrieval specifies how the SQL/MP Datetime data type is retrieved from the drivers. The SQL Datetime Retrieval has two values: • 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. Set the SQL Datetime Retrieval property using the MXODSN property.
5 Error messages Table 17 lists the driver error codes and error messages. Table 17 Error codes and error messages Error codes Error messages 01000 General Warning. 01000 General Warning. Connected to the default data source. 01002 Disconnect error. Transaction rolled back. 01004 Data truncated. 01006 Privilege not revoked. 01033 TRANSPORT LAYER ERROR. 01S02 Option value changed. 07001 Wrong number of parameters. 07003 Dynamic SQL error. Cursor specification cannot be executed.
Table 17 Error codes and error messages (continued) 50 Error codes Error messages 21001 Cardinality violation; insert value list does not match column list. 21002 Cardinality violation; insertion value list does not match column list. 21S01 Cardinality violation; parameter list does not match column list. 21S02 String data right truncation. 22001 Numeric value out of range. 22003 Error in assignment. 22005 Precision or scale out of range. 22008 Datetime field overflow.
Table 17 Error codes and error messages (continued) Error codes Error messages S1000 The stored procedure required to complete this operation could not be found on the server (they were supplied with the ODBC/MX setup disk for the SQL Server driver). Contact your service provider. S1000 Unknown token received from SQL Server S1000 Unable to load communication module. Driver has not been correctly installed. S1000 Communication module is not valid. Driver has not been correctly installed.
Table 17 Error codes and error messages (continued) 52 Error codes Error messages S1106 Fetch type out of range. S1107 Row value out of range. S1108 Concurrency option out of range. S1109 Invalid cursor position; no keyset defined. S1C00 Driver not capable. S1LD0 No long data values pending. S1T00 Timeout expired. 6001 INVALID DLL HANDLE. 6002 CANNOT LOAD PROCADDRESS. 6003 WRONG WINSOCK VERSION. 6004 WRONG SIGNATURE. 6005 WRONG VERSION. 6006 ERROR FROM SERVER.
A Sample ODBC application Compiling and linking the sample application HP-UX Use the g++ compiler to compile the application with the header files that are shipped along with the driver: odbc]$ g++ -m64 -o < output object name > -I < location of the header files > \ < input file for compilation > -l mxodbc_ia64 Linux 32 Use the g++ compiler to compile the application with the header files that are shipped along with the driver: odbc]$ g++ -m32 -o < output object name > -I < location of the header files > \
-c ThreadODBCTestAppl.c -o ThreadODBCTestAppl.o The following is a sample compilation command for a 64–bit application: OSS> c89 -g -Winspect -Wextensions -Ww -Woptimize=0 \ —W lp64 —Wsystype=oss -Wrefalign=8 -Wfieldalign=auto \ -Wallow_cplusplus_comments -Wcplusplus -Wversion3 \ -Wtarget=tns/e -DYOSEMITE -Wcall_shared —D_PUT_MODEL_\ -D__GNUC__ -DOSS_DRIVER -D_DEBUG -DNSK_PLATFORM \ -DTCL_MEM_DEBUG -D__TANDEM -Dset_fieldalign \ -D_TNS_R_TARGET -WIEEE_float -I/usr/include/odbc \ -c ThreadODBCTestAppl.
// // Copyright 2007 // // HP CONFIDENTIAL: NEED TO KNOW ONLY // // Copyright Hewlett-Packard Development Company, L.P. // Protected as an unpublished work. // // The computer program listings, specifications and // documentation herein are the property of Hewlett-Packard // Development Company, L.P.
memset (szBuf,'\0',600); if (hStmt) st = SQLGetDiagRec(SQL_HANDLE_STMT,hStmt,1,Err->szSqlState, Err->pfNativeError, Err->szErrorMsg,150,Err->pcbErrorMsg); else if (hDbc) st = SQLGetDiagRec(SQL_HANDLE_DBC,hDbc,1,Err->szSqlState, Err->pfNativeError, Err->szErrorMsg,150,Err->pcbErrorMsg); else if (hEnv) st = SQLGetDiagRec(SQL_HANDLE_ENV,hEnv,1,Err->szSqlState, Err->pfNativeError, Err->szErrorMsg,150,Err->pcbErrorMsg); if ((st == SQL_SUCCESS) || (st == SQL_SUCCESS_WITH_INFO)) { sprintf(szBuf," %s - [%s]\n", (ch
scanf("%s", Password); strcpy(CreateTable,"create table GGTest(c1 int)"); sprintf(InsertTable, "%s %d %s", "insert into GGTest(c1) values (", value1, ");"); strcpy(SelectTable,"select * from GGTest" ); printf("\n\tUsing Data Source : %s \n\n", serverName); if (!strncmp(serverName, "TDM_Default_DataSource", strlen(serverName))) defaultDS = true; st = SQLAllocEnv(&henv); if (henv == NULL) { printf("Error in allocating Env Handle!\n"); odbc_Error(SQL_NULL_HENV,SQL_NULL_HDBC,SQL_NULL_HSTMT); } st = SQLSetEnvAtt
} else printf("Connection 2 Successful\n"); st = SQLConnect(hdbc2,(SQLCHAR*)serverName,SQL_NTS,(SQLCHAR*)UserID, SQL_NTS,(SQLCHAR*)Password,SQL_NTS); if (st != SQL_SUCCESS) { printf("Error in Connection 3\n"); odbc_Error(henv,hdbc,SQL_NULL_HSTMT); } else printf("Connection 3 Successful\n"); st = SQLGetInfo(hdbc,SQL_DBMS_NAME, infoValueBuf, sizeof(infoValueBuf), &StringLengthPtr); infoValuePtr = infoValueBuf; if (st != SQL_SUCCESS) { printf("Error in SQLGetInfo\n"); odbc_Error(henv,hdbc,hstmt); } else printf
else printf("Row(s) affected %d\n", RowCount); st = SQLExecDirect(hstmt,(SQLCHAR *) SelectTable,strlen(SelectTable)); if (st != SQL_SUCCESS) { printf("Error in Select Table: GGTest\n"); odbc_Error(henv,hdbc,hstmt); } st = SQLBindCol(hstmt, 1, SQL_C_SLONG, &value, 0, &ValInd); if (st != SQL_SUCCESS) { printf("Error in SQLBindCol\n"); odbc_Error(henv,hdbc,hstmt); } while(TRUE) { if ((st = SQLFetch(hstmt)) == SQL_NO_DATA_FOUND) break; if ( (st != SQL_SUCCESS) && (st != SQL_SUCCESS_WITH_INFO) ) { printf("Error
printf("Insert Successful : %d\n", val); strcpy(SelectTable,"select * from GGTest" ); st = SQLExecDirect(hstmt1,(SQLCHAR *) SelectTable,strlen(SelectTable)); if (st != SQL_SUCCESS) { printf("Error in select table : GGTest\n"); odbc_Error(henv,hdbc1,hstmt1); } st = SQLBindCol(hstmt1, 1, SQL_C_SLONG, &value, 0, &ValInd); if(st != SQL_SUCCESS) { printf("Error in SQLBindCol\n"); odbc_Error(henv,hdbc1,hstmt1); } while(TRUE) { if ((st = SQLFetch(hstmt1)) == SQL_NO_DATA_FOUND) break; if ( (st != SQL_SUCCESS) && (s
Glossary Driver Manager The ODBC component that manages access to Database Management System (DBMS) drivers for ODBC applications. The driver manager loads and unloads drivers and passes the calls for ODBC functions to the correct driver. The HP-UX and Linux drivers support both the Nonstop driver manager and the unixODBC driver manager.
Index A R AutoCommit, 42 REAL data type, 38 B S BIGINT data type, 39 BINARY data type, 39 BIT data type, 38 Server data source configuring, 13 Server-side components, 12 SMALLINT data type, 38 SQL Datetime Retrieval, 48 SQL Interval Behaviour, 46 SQL_QUERY_TIMEOUT SQLSetStmtOption, 37 SQLBindParameter consideration, 38 SQLCancel consideration, 37 SQLPrimaryKeys consideration, 37 SQLPutData consideration, 38 SQLSpecialColumns consideration, 38 SQLStatistics consideration, 38 SQLTables SQL_ALL_CATALOGS
