HP 3000 Manuals HP 3000 Manuals
900 Series HP 3000 Computer Systems HP ALLBASE/SQL PC API User's Guide HP Part No. B2463-90001 Printed in U.S.A. Edition Second Edition E0293
Company or product names followed by (R) are U.S. registered trademarks of the respective company. Company or product names followed by (TM) are registered trademarks of the respective company. Express Windows(TM), ReportWindows(TM), SQLBase(TM), SQLWindows(TM) and SQLTalk/Windows(TM) are registered trademarks of Gupta Technologies, Incorporated. Forest and Trees(TM) is a registered trademark of Channel Computing, Incorporated. HRMS(TM) and SQR(TM) are registered trademarks of PeopleSoft, Incorporated. MS-DOS(R), Microsoft Windows(TM), and Microsoft(R) are U.S. registered trademarks of Microsoft Corporation. NetWare(R) is a registered trademark of Novell, Incorporated. PowerBuilder(TM) is a registered trademark of Powersoft Corporation. Q+E(TM) is a registered trademark of Pioneer Software. Quarterdeck(TM) is a registered trademark of Quarterdeck Corporation. ________________________________________________________________________ |The information contained in this document is subject to change | |without notice. | | | |HEWLETT-PACKARD MAKES NO 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. Hewlett-Packard | |shall not be liable for errors contained herein or use of this | |material. | | | |Hewlett-Packard assumes no responsibility for the use or reliability | |of its software on equipment that is not furnished by Hewlett-Packard.| | | |This document contains proprietary information which is protected by | |copyright. All rights are reserved. No part of this document may be | |photocopied, reproduced, or translated to another language without the| |prior written consent of Hewlett-Packard Company. | ________________________________________________________________________ Copyright (c) 1991, 1992, 1993 by Hewlett-Packard Company Printed February 1993 Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions. Edition Date Software Version -------------------------------------------------------------------------------------- First Edition December 1991 B2463A A.01.00 Second Edition February 1993 B2463A A.F0.00Preface The HP ALLBASE/SQL PC API User's Guide describes HP ALLBASE/SQL PC API and how to install and maintain it. This guide is written for the system administrator installing HP ALLBASE/SQL PC API and for the person using application software on the PC client. MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX. You can continue to use MPE XL system documentation, although it may not refer to features added to the operating system to support POSIX (for example, hierarchical directories). * Chapter 1, "Getting Started," describes the product and lists the hardware and software requirements for HP ALLBASE/SQL PC API on both the client and server. * Chapter 2, "Installing PC API," provides instructions to install HP ALLBASE/SQL PC API and describes how to prepare the environment on both the client and server. * Chapter 3, "Maintaining PC API," explains how to maintain your client/server environment after you have successfully installed and tested HP ALLBASE/SQL PC API. Configurations and the server-independent views are discussed. * Chapter 4, "Connecting to ALLBASE/SQL," describes the connection process, error handling, and security. * Chapter 5, "Data Type Differences Between ALLBASE/SQL and SQLBase," explains the differences in implementation of data types by ALLBASE/SQL and SQLBase. Any changes you must make to enable SQLBase applications to access ALLBASE/SQL databases are described. * Chapter 6, "SQL Differences Between ALLBASE/SQL and SQLBase," describes the syntax differences between SQLBase and ALLBASE/SQL that can affect applications using HP ALLBASE/SQL PC API. * Chapter 7, "Unsupported ALLBASE/SQL Statements," lists ALLBASE/SQL statements that are not supported by HP ALLBASE/SQL PC API. * Appendix A, "Error Messages From the PC Client," lists error numbers, text, cause, and action for HP errors returned by the PC client. * Appendix B, "PC API Files," lists the files included with the product. * Appendix C, "ALLBASE/SQL Reserved Words," lists the keywords used by ALLBASE/SQL. Additional Resources You may find the following manuals helpful: * From Hewlett-Packard: The ALLBASE/SQL manuals displayed on the documentation map presented earlier. IMAGE/SQL Administration Guide (36385-90001) Using the 900 Series HP 3000: Fundamental Skills (36250-90117 through 36250-90124) HP Network Services 2.1 Installation Guide (D1811-90017) HP ARPA Services 2.1 Installation Guide (D1812-90017) NetIPC 3000/XL Programmer's Reference Manual (5958-8581) NetIPC Programmer's Guide (98194-60527 and 98194-60532) Berkeley IPC Programmer's Guide (98194-60531) Programmer's Reference: ARPA Sockets for MS-DOS/Windows (D1827-90000) NetWare for the HP 3000 Installation (32020-61001) NetWare for the HP 3000 System Administration (32020-61002) NetWare for the HP 3000 User Basics (3202-61003) NetWare for the HP 3000 Utilities (32020-61004) NetWare for the HP 3000 Concepts (32020-61005) NetWare for the HP 3000 System Messages (32020-61006) NetWare for the HP 3000 System Admin. MPE/iX 4.0 Supplement (3202-61015) * From Gupta Technologies, Inc.: SQLBase C/API Reference Manual SQLBase SQLTalk Language Reference Manual SQLWindows Technical Reference Manual SQLWindows Function Call Reference Manual SQLTalk/Windows User's Guide ReportWindows Reference Manual Express Windows User's Guide SQLBase Database Administrator's Guide * From Powersoft Corporation: Using PowerBuilder PowerBuilder Function Reference PowerBuilder ALLBASE/SQL Interface What's New in this Release... The A.F0.00 release of HP ALLBASE/SQL PC API contains the following enhancements: * Improved performance. * Windows-based setup program to automate the installation of PC API. * Programmatic connection to allow a direct connection through application software. This enhancement is used by Powerbuilder. * ERROR.SQL now contains only SQLBase error messages. PC client errors are contained in the new ALLBASE.MSG file. * Multi-connection feature which reduces the number of jobs on the database server. * VIEWS.SQL file to allow you to create SYSSQL catalog views on the database server using ALLBASE/SQL's ISQL. * UNVIEWS.SQL file to allow you to remove SYSSQL catalog views on the database server using ALLBASE/SQL's ISQL. * Connection string option to convert ROMAN8 data to ANSI data. * Ability to close all connections outside the application. Addditionally, the HP ALLBASE/SQL PC API Installation and Administration Guide (part number B2463-90001) and HP ALLBASE/SQL PC API User's Guide (part number B2463-90003) have been combined in this user's guide. Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter any character in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND ComMand italics In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value. In the following example, you must replace FileName with the name of the file: COMMAND FileName punctuation In a syntax statement, punctuation characters (other than brackets, braces, vertical bars, and ellipses) must be entered exactly as shown. In the following example, the parentheses and colon must be entered: (FileName):(FileName) underlining Within an example that contains interactive dialog, user input and user responses to prompts are indicated by underlining. In the following example, yes is the user's response to the prompt: Do you want to continue? >> yes { } In a syntax statement, braces enclose required elements. When several elements are stacked within braces, you must select one. In the following example, you must select either ON or OFF: COMMAND {ON } {OFF} [ ] In a syntax statement, brackets enclose optional elements. In the following example, OPTION can be omitted: COMMAND FileName [OPTION] When several elements are stacked within brackets, you can select one or none of the elements. In the following example, you can select OPTION or Parameter or neither. The elements cannot be repeated. COMMAND FileName [OPTION ] [Parameter] [...] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select Parameter zero or more times. Each instance of Parameter must be preceded by a comma: [,Parameter][...] In the example below, you only use the comma as a delimiter if Parameter is repeated; no comma is used before the first occurrence of Parameter: [Parameter][,...] |...| In a syntax statement, horizontal ellipses enclosed in vertical bars indicate that you can select more than one element within the immediately preceding pair of brackets or braces. However, each particular element can only be selected once. In the following example, you must select A, AB, BA, or B. The elements cannot be repeated. {A} |...| {B} ... In an example, horizontal or vertical ellipses indicate where portions of an example have been omitted. _ In a syntax statement, the space symbol _ shows a required blank. In the following example, Parameter and Parameter must be separated with a blank: (Parameter)_(Parameter) The symbol indicates a key on the keyboard. For example, RETURN represents the carriage return key. CTRLcharacter CTRLcharacter indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously.
![[]](../../pic3k/M012150/FFN23c50.gif)