DOCSLIB.ORG

Call Level Interface Guide and Reference Ve R S I O N 7

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Call Level Interface Guide and Reference Ve R S I O N 7 ® ® IBM DB2 Universal Database Call Level Interface Guide and Reference Ve r s i o n 7 SC09-2950-00 ® ® IBM DB2 Universal Database Call Level Interface Guide and Reference Ve r s i o n 7 SC09-2950-00 Before using this information and the product it supports, be sure to read the general information under “Appendix M. Notices” on page 849. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. Order publications through your IBM representative or the IBM branch office serving your locality or by calling 1-800-879-2755 in the United States or 1-800-IBM-4YOU in Canada. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1993, 2000. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About This Book ..........ix Deciding on Which Cursor Type to Use . 67 Who Should Use this book .......ix Specifying the Rowset Returned from the How this Book is Structured.......ix Result Set ............68 Typical Scrollable Cursors Application . 72 Chapter 1. Introduction to CLI......1 Using Bookmarks with Scrollable Cursors 75 DB2 CLI Background Information .....1 Sending/Retrieving Long Data in Pieces . 77 Differences Between DB2 CLI and Embedded Specifying Parameter Values at Execute SQL...............3 Time.............77 Comparing Embedded SQL and DB2 CLI . 3 Fetching Data in Pieces .......78 Advantages of Using DB2 CLI .....4 Piecewise Input and Retrieval Example . 79 Deciding on Embedded SQL or DB2 CLI . 6 Using Arrays to Input Parameter Values . 79 Supported Environments ........7 Column-Wise Array Insert ......80 Other Information Sources .......8 Row-Wise Array Insert .......81 Retrieving Diagnostic Information....83 Chapter 2. Writing a DB2 CLI Application . 9 Parameter Binding Offsets ......84 Initialization and Termination ......10 Array Input Example ........85 Handles ............11 Retrieving a Result Set into an Array....87 Connecting to One or More Data Sources 12 Returning Array Data for Column-Wise Initialization and Connection Example . 13 Bound Data ...........88 Transaction Processing .......15 Returning Array Data for Row-Wise Bound Diagnostics ...........25 Data.............89 Data Types and Data Conversion ....28 Column Binding Offsets .......90 Working with String Arguments ....36 Column-Wise, Row-Wise Binding Example 91 Querying Environment and Data Source Using Descriptors ..........91 Information ...........38 Descriptor Types .........92 Values Stored in a Descriptor .....93 Chapter 3. Using Advanced Features . 39 Allocating and Freeing Descriptors . 95 Environment, Connection, and Statement Getting, Setting, and Copying Descriptor Attributes .............40 Fields .............98 Writing Multi-Threaded Applications . 44 Descriptor Sample ........101 When to Use Multiple Threads.....44 Using Compound SQL ........103 Programming Tips .........45 ATOMIC and NOT ATOMIC Compound Multisite Updates (Two Phase Commit) . 48 SQL.............104 DB2 as Transaction Monitor ......48 Compound SQL Error Handling ....106 Microsoft Transaction Server (MTS) as Compound SQL Example ......107 Transaction Monitor ........54 Using Large Objects .........108 Process-based XA-Compliant Transaction LOB Examples ..........112 Program Monitor (XA TP) ......61 Using LOBs in ODBC Applications . 113 Host and AS/400 Database Servers . 62 Using User Defined Types (UDT) ....114 Querying System Catalog Information . 62 User Defined Type Example .....114 Input Arguments on Catalog Functions . 63 Using Stored Procedures .......116 Catalog Functions Example ......64 Calling Stored Procedures ......117 Scrollable Cursors ..........65 Registering Stored Procedures.....119 Static, Read-Only Cursor .......66 Handling Stored Procedure Arguments Keyset-Driven Cursor ........66 (SQLDA)............119 © Copyright IBM Corp. 1993, 2000 iii Returning Result Sets from Stored SQLBrowseConnect - Get Required Procedures ...........120 Attributes to Connect to Data source . 258 Writing a Stored Procedure in CLI . 122 SQLBuildDataLink - Build DATALINK Stored Procedure Example ......122 Value .............264 Mixing Embedded SQL and DB2 CLI . 127 SQLBulkOperations - Add, Update, Mixed Embedded SQL and DB2 CLI Delete or Fetch a Set of Rows .....268 Example ............128 SQLCancel - Cancel Statement ....282 Asynchronous Execution of CLI .....129 SQLCloseCursor - Close Cursor and Typical Asynchronous Application . 130 Discard Pending Results ......285 Sample Asynchronous Application . 133 SQLColAttribute - Return a Column Using Vendor Escape Clauses ......135 Attribute............288 Escape Clause Syntax .......135 SQLColAttributes - Get Column ODBC Date, Time, Timestamp Data . 136 Attributes ...........301 ODBC Outer Join Syntax ......136 SQLColumnPrivileges - Get Privileges LIKE Predicate Escape Clauses ....136 Associated With The Columns of A Table . 302 Stored Procedure Call Syntax .....137 SQLColumns - Get Column Information ODBC Scalar Functions .......137 for a Table ...........307 SQLConnect - Connect to a Data Source 314 Chapter 4. Configuring CLI/ODBC and SQLCopyDesc - Copy Descriptor Running Sample Applications .....139 Information Between Handles.....318 Setting up the DB2 CLI Runtime SQLDataSources - Get List of Data Environment ...........139 Sources ............322 Running CLI/ODBC Programs .....140 SQLDescribeCol - Return a Set of Platform Specific Details for CLI/ODBC Attributes for a Column ......326 Access ............141 SQLDescribeParam - Return Description Detailed Configuration Information . 147 of a Parameter Marker .......331 Application Development Environments . 152 SQLDisconnect - Disconnect from a Data Compiling a Sample Application....153 Source ............335 Compile and Link Options......153 SQLDriverConnect - (Expanded) Connect DB2 CLI/ODBC Configuration Keyword to a Data Source .........338 Listing .............154 SQLEndTran - End Transactions of a Configuration Keywords ......154 Connection ...........343 SQLError - Retrieve Error Information 347 Chapter 5. DB2 CLI Functions .....205 SQLExecDirect - Execute a Statement DB2 CLI Function Summary ......207 Directly ............352 SQLAllocConnect - Allocate Connection SQLExecute - Execute a Statement . 360 Handle ............214 SQLExtendedBind - Bind an Array of SQLAllocEnv - Allocate Environment Columns ............364 Handle ............215 SQLExtendedFetch - Extended Fetch SQLAllocHandle - Allocate Handle . 216 (Fetch Array of Rows) .......368 SQLAllocStmt - Allocate a Statement SQLExtendedPrepare - Prepare a Handle ............222 Statement and Set Statement Attributes . 376 SQLBindCol - Bind a Column to an SQLFetch - Fetch Next Row .....382 Application Variable or LOB Locator . 223 SQLFetchScroll - Fetch Rowset and SQLBindFileToCol - Bind LOB File Return Data for All Bound Columns . 392 Reference to LOB Column ......233 SQLForeignKeys - Get the List of Foreign SQLBindFileToParam - Bind LOB File Key Columns ..........404 Reference to LOB Parameter .....237 SQLFreeConnect - Free Connection SQLBindParameter - Bind A Parameter Handle ............409 Marker to a Buffer or LOB Locator . 241 SQLFreeEnv - Free Environment Handle 411 iv CLI Guide and Reference SQLFreeHandle - Free Handle Resources 413 SQLPrimaryKeys - Get Primary Key SQLFreeStmt - Free (or Reset) a Statement Columns of A Table ........560 Handle ............417 SQLProcedureColumns - Get SQLGetConnectAttr - Get Current Input/Output Parameter Information for Attribute Setting .........421 A Procedure ..........564 SQLGetConnectOption - Return Current SQLProcedures - Get List of Procedure Setting of A Connect Option .....424 Names............572 SQLGetCursorName - Get Cursor Name 425 SQLPutData - Passing Data Value for A SQLGetData - Get Data From a Column 428 Parameter ...........578 SQLGetDataLinkAttr - Get DataLink SQLRowCount - Get Row Count....583 Attribute Value .........436 SQLSetColAttributes - Set Column SQLGetDescField - Get Single Field Attributes ...........585 Settings of Descriptor Record .....439 SQLSetConnectAttr - Set Connection SQLGetDescRec - Get Multiple Field Attributes ...........586 Settings of Descriptor Record .....445 SQLSetConnection - Set Connection SQLGetDiagField - Get a Field of Handle ............610 Diagnostic Data .........450 SQLSetConnectOption - Set Connection SQLGetDiagRec - Get Multiple Fields Option ............612 Settings of Diagnostic Record .....459 SQLSetCursorName - Set Cursor Name 613 SQLGetEnvAttr - Retrieve Current SQLSetDescField - Set a Single Field of a Environment Attribute Value .....463 Descriptor Record.........616 SQLGetFunctions - Get Functions . 465 SQLSetDescRec - Set Multiple Descriptor SQLGetInfo - Get General Information 468 Fields for a Column or Parameter Data . 643 SQLGetLength - Retrieve Length of A SQLSetEnvAttr - Set Environment String Value...........507 Attribute............648 SQLGetPosition - Return Starting Position SQLSetParam - Bind A Parameter Marker of String ............510 to a Buffer or LOB Locator......656 SQLGetSQLCA - Get SQLCA Data SQLSetPos - Set the Cursor Position in a Structure............514 Rowset............657
Load more

Recommended publications
  • Derivation of the Required Elements for a Definition of the Term Middleware
    Rochester Institute of Technology RIT Scholar Works Theses 2002 Derivation of the required elements for a definition of the term middleware Maya Mathew Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Mathew, Maya, "Derivation of the required elements for a definition of the term middleware" (2002). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Derivation of the Required Elements for a Definition of the Term Middleware By Maya Mathew Thesis submitted in partial fulfillment ofthe requirements for the degree ofMaster ofScience in Information Technology Rochester Institute ofTechnology B. Thomas Golisano College Of Computing and Information Sciences May 2002 - 1 - Rochester Institute of Technology B. Thomas Golisano College Of Computing and Information Sciences Master of Science in Information Technology Thesis Approval Form Student Name: Maya Mathew Thesis Title: Derivation of the Required Elements for a Definition of the Term Middleware Thesis Committee Name Signature Date Prof. William Stratton Chair Prof. Andy Phelps ?-/ z /qL-.-- Committee Member I I :-.P.:...::ro~f.~J~e;.:..:.ff...::L:.:::a.=..:sk~y ~ 17, d-fIoJ--. Committee Member ~ Thesis Reproduction Permission Form Rochester Institute of Technology B. Thomas Golisano College Of Computing and Information Sciences Derivation of the Required Elements For a Definition of the Term Middleware I, Maya Mathew, hereby grant permission to the Wallace Library of the Rochester Institute of Technology to reproduce my thesis in whole or in part.
    [Show full text]
  • DB2 UDB for Z/OS Security Target
    DB2 UDB for z/OS Security Target Version 1.3.13 Status: Final Last Update: 2007-12-06 DB2 UDB for z/OS Security Target IBM atsec is a trademark of atsec GmbH IBM, IBM logo, DB2 UDB for z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: • Advanced Function Presentation • AFP • DFS • DFSORT • • IBM • Infoprint • MVS • PR/SM • Print Services Facility • Processor Resource/Systems Manager • RACF • VTAM • z/Architecture • z/OS • z/VM • zSeries Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States, other countries, or both. Java and all Java-based products are trademarks of Sun Microsystems, Inc., in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. This document is provided AS IS with no express or implied warranties. Use the information in this document at your own risk. This document may be reproduced or distributed in any form without prior permission provided the copyright notice is retained on all copies. Modified versions of this document may be freely distributed provided that they are clearly identified as such, and this copyright is included intact. Copyright (c) 2004, 2005 by atsec GmbH and IBM Corporation or its wholly
    [Show full text]
  • Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) Document Number: C911
    Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) NICAL H S C T A E N T D A R D [This page intentionally left blank] Open Group Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) The Open Group December 1999, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. This documentation and the software to which it relates are derived in part from copyrighted materials supplied by International Business Machines. Neither International Business Machines nor The Open Group makes any warranty of any kind with regard to this material, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Open Group shall not be liable for errors contained herein, or for any direct or indirect, incidental, special, or consequential damages in connection with the furnishing, performance, or use of this material. Open Group Technical Standard DRDA, Version 2, Volume 1: Distributed Relational Database Architecture (DRDA) Document Number: C911 Published in the U.K. by The Open Group, December 1999. Any comments relating to the material contained in this document may be submitted to: The Open Group Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii Open Group Technical Standard (1999) Contents Chapter 1 The DRDA Specification................................................................... 1 1.1 The DRDA Reference................................................................................
    [Show full text]
  • Distributed Communication Methods and Role-Based Access Control For
    Distributed Communication Methods and Role*Based Access Controi for Use in Heaith Care Applications Joseph Poole John Barkley Kevin Brady Anthony Cincotta Wayne Salamon U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 QC 100 .U56 NIST NO. 5820 1996 if 1 •t r i I i j •? f Distributed Communication Methods and Roie-Based Access Controi for Use in Health Care Appiications Joseph Poole John Barkley Kevin Brady Anthony Cincotta Wayne Salamon U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 April 1996 U.S. DEPARTMENT OF COMMERCE Michael Kantor, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director Abstract The use of software in the health care industry is becoming of increasing importance. One of the major roadblocks to efficient health care is the fact that important information is distributed across many sites. These sites can be located across a significant area. The problem is to provide a uniform mechanism to integrate this information. This paper documents the results of an investigation into the suitability of several different distributed access mechanisms. Five methods were examined: the Common Object Request Broker (CORBA), Object Linking and Embedding (OLE), remote procedure call (RPC), remote database access (SQL/RDA) and Protocol Independent Interfaces (PH, we specifically examined sockets). These mechanisms were compared with regard for use in health care applications. In particular, the following capabilities were compared: • Ease of use by the developer • Class of applications for which the technology is particularly effective in developing • Security capabilities • Protocols utilized • Performance of the transport mechanism.
    [Show full text]
  • Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems
    Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems Release 13.10 B035-2417-020A February 2010 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.
    [Show full text]
  • Windows Release 8206
    WebFOCUS and ReportCaster Installation and Configuration for Windows Release 8206 July 29, 2020 Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWay Software, Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUS Magnify are registered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc. Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher's intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any of these names other than to refer to the product described. Copyright © 2019, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual, or parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc. Contents Preface ......................................................................... 9 Conventions ........................................................................10 Related Publications .................................................................11
    [Show full text]
  • Oracle Database Gateway for DRDA User's Guide Is Included As Part of Your Product Shipment
    Oracle® Database Gateway for DRDA User’s Guide 11g Release 1 (11.1) B31046-01 June 2007 Oracle Database Gateway for DRDA User’s Guide, 11g Release 1 (11.1) B31046-01 Copyright © 2004, 2007, Oracle. All rights reserved. Primary Author: Maitreyee Chaliha Contributing Author: Denis Raphaely, Peter A. Castro The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987).
    [Show full text]
  • Database Administration Guide for SAP on IBM Db2 for Linux, UNIX, and Windows Company
    Administration Guide | PUBLIC Document Version: 2.5 – 2021-09-23 Database Administration Guide for SAP on IBM Db2 for Linux, UNIX, and Windows company. All rights reserved. All rights company. affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 Introduction................................................................7 1.1 Document History............................................................ 8 1.2 Naming Conventions..........................................................10 2 Administration Tools and Tasks.................................................12 2.1 Administration Tools..........................................................12 2.2 Administration Tasks..........................................................13 3 Architectural Overview.......................................................16 3.1 SAP Application Server for ABAP.................................................16 3.2 SAP Application Server for Java..................................................17 3.3 Db2 Components............................................................18 3.4 Db2 Client Connectivity........................................................19 4 User Management and Security................................................ 21 4.1 SAP System Users and Groups...................................................21 Access Authorizations for Db2 Directories and Database-Related Files....................25 4.2 Role-Based Security Concept for Database Users..................................... 27 Database Roles for
    [Show full text]
  • Systems Programmer's Guide To
    Front cover Systems Programmer’s Guide to Resource Recovery Services (RRS) Managing, optimizing, and sizing RRS environments Restart and recovery with RRS How exploiters can get the most out of RRS Paola Bari Frank Kyne Alan Murphy ibm.com/redbooks International Technical Support Organization Systems Programmer’s Guide to Resource Recovery Services (RRS) November 2004 SG24-6980-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (November 2004) This edition applies to Version 1, Release 4 of z/OS (product number 5694-A01, 5655-G52). © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . .x Comments welcome. .x Part 1. Resource Recovery Services (RRS) introduction and concepts . 1 Chapter 1. Introduction to Resource Recovery Services (RRS) . 3 1.1 Transactions . 4 1.2 Resource managers and protected resources . 5 1.3 The role of Resource Recovery Services (RRS). 6 1.3.1 Who uses RRS . 7 Chapter 2. Two-phase commit and RRS . 9 2.1 Introduction to two-phase commit . 10 2.2 Two-phase commit as supported by legacy resource managers . 13 2.2.1 CICS . 14 2.2.2 IMS . 15 2.2.3 DB2 . 15 2.3 How RRS works . 16 2.3.1 Registration services. 16 2.3.2 Context services . 17 2.3.3 RRS invocation .
    [Show full text]
  • Welcome to Discussion on Ingres Code Architecture
    Welcome to discussion on Ingres Code Architecture. In this presentation we will discuss the • Various components of Ingres database, • Their interrelationship and • Their code architecture. 1 To an Ingres user, an Ingres database stores and retrieves data based on an SQL query. For example here is a screen shot of Ingres Terminal monitor session connected to database testdb. Here we wish to retrieve the details of all employees in a company. We enter our SQL query <Click To Animate > “Select * from emp” The database server processes the query <Click to Animate> 2 We obtain the results of our query. To understand the code architecture of Ingres. <Click Here> let us examine how Ingres processes this query <Click Here> 3 1. The Query is processed by Global Communications facility which communicates the data and results between the terminal monitor to the DBMS server. <Click Here to Animate> 2. The DBMS server and its associated processes process the query and send the results to the client through GCF. <Click Here to Animate> 3. Broadly categorizing we can summarize the code into • User interface facilities • Connectivity and Communications • DBMS server • And Utility libraries to interact with Operating system. 1. Ingres has several kinds of user interface for example 1. Embedded SQL precompiler for programmatic operations of database. 2. Ingres applications like, SQL Terminal Monitor, Query by forms (QBF), Report by Forms (RBF), VISION etc. 3. We have Ingres Internet Commerce (ICE) for web deployment. These user interfaces and others can be commonly grouped as Front End for Ingres. • Similarly in connectivity tools we have • Java Database connectivity (JDBC) driver • Open Database connectivity driver (ODBC) driver • Dot Net Data provider • Open API a C api to Ingres etc.
    [Show full text]
  • The US Government's Open System Environment Profile OSE/1 Version
    C NIST Special Publication 500-21 Computer Systems APPLICATION PORTABILITY PROFILE Technology (APP) The U.S. Government's U.S. DEPARTMENT OF COMMERCE Technology Administration Open System Environment Profile National Institute of Standards and Technology OSE/1 Version 2.0 Nisr NAT L !NST."OF STAND i TECH R.I.C. llllllllllllllllllll NIST PUBLICATIONS AlllDM QEETfll APPLICA TION PORTABILITYPROFILE j)JT)) The U S. Government's ^ k^Open System Environment IL Profile OSE/1 Version 2.0 -QG 100 .U57 #500-210 1993 7he National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . needed to improve product quality, to modernize manufacturing processes, to ensure product reliability . and to facilitate rapid commercialization ... of products based on new scientific discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's competitiveness; advance science and engineering; and improve public health, safety, and the environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national standards of measurement, and provide the means and methods for comparing standards used in science, engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government. As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and applied research in the physical sciences and engineering and performs related services. The Institute does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.
    [Show full text]
  • TRM) Para Telconet Cloud Center
    UNIVERSIDAD TÉCNICA PARTICULAR DE LOJA La Universidad Católica de Loja ÁREA TÉCNICA TÍTULO DE INGENIERO EN INFORMÁTICA Definición de un modelo técnico de referencia (TRM) para Telconet Cloud Center. TRABAJO DE TITULACIÓN AUTOR: Cabrera Burgos, Xavier Antonio. DIRECTOR: Cabrera Silva, Armando Augusto, MSc. CENTRO UNIVERSITARIO GUAYAQUIL 2018 Esta versión digital, ha sido acreditada bajo la licencia Creative Commons 4.0, CC BY-NY- SA: Reconocimiento-No comercial-Compartir igual; la cual permite copiar, distribuir y comunicar públicamente la obra, mientras se reconozca la autoría original, no se utilice con fines comerciales y se permiten obras derivadas, siempre que mantenga la misma licencia al ser divulgada. http://creativecommons.org/licenses/by-nc-sa/4.0/deed.es 2018 APROBACIÓN DEL DIRECTOR DEL TRABAJO DE TITULACIÓN MSc. Armando Augusto Cabrera Silva. DOCENTE DE LA TITULACIÓN De mi consideración: El presente trabajo titulación: “Definición de un modelo de referencia técnica (TRM) para Telconet Cloud Center”, realizado por Xavier Antonio Cabrera Burgos ha sido orientado y revisado durante su ejecución, por cuanto se aprueba la presentación del mismo. Loja, agosto de 2018 f) ………………………………………….. MSc. Cabrera Silva, Armando Augusto ii DECLARACIÓN DE AUTORÍA Y CESIÓN DE DERECHOS “Yo, Cabrera Burgos Xavier Antonio declaro ser autor del presente trabajo de titulación: “Definición de un modelo técnico de referencia (TRM) para Telconet Cloud Center” de la Titulación en Informática, siendo el MSc. Armando Augusto Cabrera Silva director del presente trabajo; y eximo expresamente a la Universidad Técnica Particular de Loja y a sus representantes legales de posibles reclamos o acciones legales. Además, certifico que las ideas, conceptos, procedimientos y resultados vertidos en el presente trabajo investigativo, son de mi exclusiva responsabilidad.
    [Show full text]