Hp Integrity NonStop H-Series Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Matériel informatique Hp Integrity NonStop H-Series. HP Integrity NonStop H-Series User Manual Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 62
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 0
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.27 and subsequent H-series RVUs
Vue de la page 0
1 2 3 4 5 6 ... 61 62

Résumé du contenu

Page 1 - Published: November 2013

HP NonStop ODBC/MX Client Drivers UserGuide for SQL/MX Release 3.2.1HP Part Number: 734873-002Published: November 2013Edition: J06.16 and subsequent J

Page 2

1 OverviewThe following ODBC/MX client drivers enable ODBC applications running on various platforms,to access a NonStop SQL/MX database:• Linux 32–bi

Page 3 - Contents

Figure 1 ArchitectureODBC/MX Client(Linux or HP-UX System)Nonstop SystemA - TDM_Default_Data SourceB - Data Source BDB - SQL/MX DatabaseApplicationApp

Page 4 - 4 Contents

MXODSN file, and for the OSS driver in the ODBCDSN file. Use the Microsoft ODBC Data SourceAdministrator to configure the parameters for the Windows d

Page 5 - About this document

Data sourcesData sources are logical groupings of connections to the SQL/MX database. There are two typesof data sources.• Client data source, commonl

Page 6

TracingHP-UX, Linux 32 and Linux 64The trace information is captured in a log file. You can enable or disable tracing and specifythe trace file name i

Page 7 - Related Documentation

Table 1 Unsupported ODBC APIsUnsupported APIsCategoryInstaller – Data Sources• SQLManageDataSources• SQLRemoveDefaultDataSource• SQLConfigDataSource•

Page 8 - • Data management guides

The following are the considerations and limitations for the Windows Unicode driver:• You cannot execute DDL statements with character set qualifiers

Page 9 - HP encourages your comments

2 Installing the driversThe hardware and software requirements for the drivers are described in the softdoc or READMEfile delivered with the products,

Page 10 - 1 Overview

1. Download the driver from NonStop system to the HP–UXia64 workstation in binary mode(You can use FTP utility for downloading). The driver is package

Page 11 - Architecture 11

3. Go to download directory, and enter the following command to extract the files:nltar -xvf LODBC64The files are extracted to 64Linux_ODBC_321 direct

Page 12 - Driver managers

© Copyright 2013 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or copyin

Page 13 - Data sources

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 t

Page 14 - Object naming and mapping

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

Page 15 - Unsupported ODBC data types

• /usr/lib/libmxodbc_l_drvr.so.3• /usr/lib/libmxodbc_l_drvr.so.3.2.1• /usr/lib/libhpsecClient.so• /etc/hpodbc/MXODSNThe checksum of the shared librari

Page 16 - 16 Overview

1. Log in to the HP-UXia64 workstation as a root user.2. Go to the HPUXia64_ODBC_64 directory.3. To uninstall the driver, enter the following command:

Page 17 - 2 Installing the drivers

3 Configuring data sourcesThis chapter describes the various procedures to configure the SQL/MX data sources.• “Configuring a client data source”• “Co

Page 18 - 18 Installing the drivers

3. Select the data source name that you want to configure and click Configure.4. Each tab in the configuration view displays different fields in the d

Page 19 - Installation procedures 19

Configuring the drivers for IPv6HP-UX, Linux 32 and Linux 64You can directly enter the IPv6 address instead of IPv4 address in the MXODSN or odbc.ini(

Page 20 - Click Next

1. Log on as super.super.2. Enter the following command to change to the NonStop SSL directory:$SYSTEM STARTUP 1> volume $system.znsssl3. Enter the

Page 21 - Verifying the installation

1. Download the $SYSTEM.ZNSSSL.PROXYEXE file in binary format and rename it toPROXY.EXE.2. Run PROXY.EXE to start the RemoteProxy installation program

Page 22 - Uninstalling the driver

DataSource configuration in Windows driverDataSource configuration in Windows driver 29

Page 23 - ./runme.sh

ContentsAbout this document...5Intended audience...

Page 24 - 3 Configuring data sources

MXODSN and ODBCDSN file formatsThe following table describes the various sections in the MXODSN and ODBCDSN files.Table File sectionsDescriptionFile S

Page 25

Table 4 MXODSN and ODBCDSN attributes (continued)DescriptionAttributesFile Section1, tracing is on. By default, tracing isoff.TraceFlags indicates the

Page 26 - 26 Configuring data sources

Table 4 MXODSN and ODBCDSN attributes (continued)DescriptionAttributesFile Sectionseconds. SQLIntervalBehaviourhas two values, SYSTEM_DEFAULT andMSDN_

Page 27

[ODBC]TraceFlags = 6TraceStart = 0TraceFile = trlog[ODBC Data Sources]TDM_Default_DataSource = NonStop ODBC/MX 3.xDS1 = NonStop ODBC/MX 3.xDS2 = NonSt

Page 28 - 28 Configuring data sources

WindowsTo add a new data source or configure an existing data source, see “Configuring a client datasource”.Perform the following steps to delete a cl

Page 29

Using connection string without DSNYou can set AUTOCOMMIT as part of the Connection string.“AutoCommit=ON/OFF/SERVER_DEFAULT”.Example 2 Depicting AUTO

Page 30 - Table File sections

If you select the ODBC standard trace DLL (odbctrac.dll from the Windows Systemfolder), only the driver manager is traced; additional trace options th

Page 31

4 Compatibility and considerationsThe drivers are compatible with the following:• ODBC 3.5• SQL-92 features supported by SQL/MXFor more information ab

Page 32

Table 5 Considerations (continued)ConsiderationItemThis API does not support pattern value arguments for table names, andreturns an optimal set of col

Page 33 - Managing data sources

Table 6 ODBC Data Types (continued)Supported by the driver?SQL/MP data TypeSQL/MX data TypeODBC data typeNoNot supportedNot supportedTINYINT UNSIGNEDY

Page 34 - Managing transactions

Partial DATE or TIME values...40Microsoft escape cla

Page 35 - Tracing 35

Table 7 Behavior of unsigned data typesBehaviorODBC versionUNSIGNED SMALLINT is promoted to SIGNED INT andUNSIGNED INT is promoted to BIGINT.2.0All un

Page 36 - 36 Configuring data sources

Table 8 SQL/MP to ODBC/MX Date/Time Mappings (continued)ODBC/MX data typeSQL/MP data typeSQL_TIMESTAMPDATETIME MINUTE TO FRACTIONSQL_TIMEDATETIME SECO

Page 37 - Considerations

Table 10 Transaction and cursor behaviorApplication actionSQL/MX behaviorAUTOCOMMITNot applicableWhen any open statement reachesend of data or end of

Page 38 - ODBC data types

Table 11 Sample values inserted from an application and expected values in microsecond (continued)Expected value in the column ofSQL/MX tableColumn ty

Page 39 - Unsigned data types

Table 12 Sample values inserted from an application and expected values in nanoseconds (continued)Expected value in the column ofSQL/MX tableColumn ty

Page 40 - Partial DATE or TIME values

Table 13 Values retrieved by the application for SYSTEM_DEFAULT setting (continued)Fraction value retrieved by theapplicationColumn typeValue in the c

Page 41 - Stored Procedures

Table 14 Sample values retrieved by the application (continued)Fraction value retrieved by theapplicationColumn typeValue in the column of the SQL/MXT

Page 42

If not specified, the default is SYSTEM_DEFAULT.Set the SQL Interval Behaviour property using the MXODSN property.• The following example describes wh

Page 43

SQL Datetime Retrieval propertyThe SQL Datetime Retrieval specifies how the SQL/MP Datetime data type is retrieved fromthe drivers. The SQL Datetime R

Page 44

5 Error messagesTable 17 lists the driver error codes and error messages.Table 17 Error codes and error messagesError messagesError codesGeneral Warni

Page 45

About this documentThis manual describes how to install, configure and use the ODBC/MX client drivers. These driversallow HP-UX, Linux32, Linux64, OSS

Page 46

Table 17 Error codes and error messages (continued)Error messagesError codesCardinality violation; insert value list does not match columnlist.21001Ca

Page 47

Table 17 Error codes and error messages (continued)Error messagesError codesThe stored procedure required to complete this operationcould not be found

Page 48

Table 17 Error codes and error messages (continued)Error messagesError codesFetch type out of range.S1106Row value out of range.S1107Concurrency optio

Page 49 - 5 Error messages

A Sample ODBC applicationCompiling and linking the sample applicationHP-UXUse the g++ compiler to compile the application with the header files that a

Page 50

-c ThreadODBCTestAppl.c -o ThreadODBCTestAppl.oThe following is a sample compilation command for a 64–bit application:OSS> c89 -g -Winspect -Wexten

Page 51

//// Copyright 2007//// HP CONFIDENTIAL: NEED TO KNOW ONLY//// Copyright Hewlett-Packard Development Company, L.P.// Protected as an unpublished work.

Page 52

memset (szBuf,'\0',600); if (hStmt) st = SQLGetDiagRec(SQL_HANDLE_STMT,hStmt,1,Err->szSqlState, Err->pfNativeError, Err-&

Page 53 - A Sample ODBC application

scanf("%s", Password); strcpy(CreateTable,"create table GGTest(c1 int)"); sprintf(InsertTable, "%s %d %s", "

Page 54 - Testing the sample

} else printf("Connection 2 Successful\n"); st = SQLConnect(hdbc2,(SQLCHAR*)serverName,SQL_NTS,(SQLCHAR*)UserID, SQL_NTS,

Page 55 - Testing the sample 55

else printf("Row(s) affected %d\n", RowCount); st = SQLExecDirect(hstmt,(SQLCHAR *) SelectTable,strlen(SelectTable)); if (st

Page 56 - 56 Sample ODBC application

Italic LettersItalic letters, regardless of font, indicate variable items that you supply. Items not enclosed inbrackets are required. For example:fil

Page 57 - Testing the sample 57

printf("Insert Successful : %d\n", val); strcpy(SelectTable,"select * from GGTest" ); st = SQLExecDirect(hstmt1,(SQLCHAR

Page 58 - 58 Sample ODBC application

GlossaryDriver ManagerThe ODBC component that manages access to Database Management System (DBMS)drivers for ODBC applications. The driver manager loa

Page 59 - Testing the sample 59

IndexAAutoCommit, 42BBIGINT data type, 39BINARY data type, 39BIT data type, 38CCatalog and schemaconsideration, 37CHAR data type, 38Client data source

Page 60 - 60 Sample ODBC application

{, sql-expression}...An ellipsis immediately following a single syntax item indicates that you can repeat that syntaxitem any number of times. For exa

Page 61 - Glossary

• Installation guidesDescribes how to plan for install and upgrade an SQL/MX database.SQL/MX Installation andUpgrade GuideDescribes how to manage an S

Page 62 - 62 Index

• Application development guidesDescribes how to embed SQL/MX statements in ANSI C and COBOL programs.SQL/MX Programming Manualfor C and COBOLDescribe

Commentaires sur ces manuels

Pas de commentaire