HP 3000 Manuals HP 3000 Manuals
HP 3000 MPE/iX Computer Systems IMAGE/SQL Administration Guide HP Part No. 36385-90001 Printed in U.S.A. Edition Fifth E0897
________________________________________________________________________ |ODBCLink/SE(TM) is a registered trademark of M. B. Foster Software | |Labs, Inc. | | | |Microsoft(R) Windows(TM), Visual Basic(TM), and Microsoft Access(TM) | |are U.S. registered trademarks of Microsoft Corporation. | ________________________________________________________________________ Acknowledgements ________________________________________________________________________ |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 or fitness for a particular purpose. Hewlett-Packard | |shall not be liable for errors contained herein or for direct, | |indirect, special, incidental or consequential damages in connection | |with the furnishing 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 reserved. Reproduction, adaptation, or | |translation without prior written permission is prohibited, except as | |allowed under the copyright laws. | ________________________________________________________________________ Copyright (c) 1990, 1992--1994, 1997 by Hewlett-Packard Company ________________________________________________________________________ |Use, duplication, or disclosure by the U.S. Government is subject to | |restrictions as set forth in subparagraph (c) (1) (ii) of the Rights | |in Technical Data and Computer Software clause at DFARS 252.227-7013. | |Rights for non-DOD U.S. Government Departments and Agencies are as set| |forth in FAR 52.227-19 (c) (1,2). | | | |Hewlett-Packard Company | |3000 Hanover Street | |Palo Alto, CA 94304 U.S.A. | ________________________________________________________________________ Restricted Rights Legend Printed August 1997 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 July 1990 36385-A.00.00 Second Edition November 1992 36385-A.00.07 or 36385-B.F0.00 Third Edition June 1993 36385-B.F0.20 Fourth Edition December 1994 36385B B.G0.03 Fifth Edition August 1997 36385B B.G2.03 About this Manual [REV BEG] This manual explains how to use IMAGE/SQL for relational access to your TurboIMAGE/XL database.[REV END] You should be familiar with TurboIMAGE/XL and have a general knowledge of relational databases to use this guide effectively. This manual assumes you are familiar with IMAGE/SQL or have read Getting Started with HP IMAGE/SQL. [REV BEG] The terms Turbo CONNECT and ALLBASE/Turbo CONNECT (ATC) are names used for previous versions of IMAGE/SQL. ATC still appears in some error messages and warnings. The former IMAGE/SQL utility, ATCUTIL, is now called IMAGESQL.[REV END] The following briefly describes each chapter: Chapter 1 Introduction Introduces some basic IMAGE/SQL concepts and shows you how to begin using IMAGE/SQL. Chapter 2 Using the IMAGE/SQL Utility Provides step-by-step directions for several typical administrative tasks. Chapter 3 Understanding IMAGE/SQL Provides a discussions of IMAGE/SQL concepts and functionality. Chapter 4 IMAGE/SQL Utility Commands Contains detailed information about the IMAGE/SQL utility commands. Chapter 5 IMAGE/SQL Locking Describes how IMAGE/SQL assigns locks on IMAGE/SQL tables and how IMAGE/SQL handles deadlocks. Chapter 6 IMAGE/SQL Transactions Describes IMAGE/SQL transactions, repeatable reads, and IMAGE/SQL aborted transactions. Appendix A IMAGE/SQL Error Messages Contains reference information about error messages. Appendix B SALES Database Schema Contains a listing of the SALES database used throughout the manual. Appendix C IMAGE/SQL and Database Utilities Describes the DBUtil, SQLUtil, and SQLGEN utilities. Appendix D SQL Exceptions Lists SQL statements that have restrictions when used on a TurboIMAGE/XL data set. [REV BEG] Appendix E SQL Views for Indices Describes the new views for TurboIMAGE/XL and third-party indices. [REV END][REV BEG] Appendix F DATE/TIME API Describes the new externally callable procedures used to convert data to and from the internal format of ALLBASE/SQL date/time format. These new procedures are called the Date/Time Application Programming Interface or API. [REV END] Glossary Glossary Gives basic definitions of terms. What's New in this Edition This edition of the HP IMAGE/SQL Administration Guide contains the following changes:[REV BEG] * Enhancements added in releases B.G1 through B.G2.03 are documented. * Edits based on suggestions by customers and HP Support Engineers are included throughout the manual. * Changed security for users to allow CLASS as well as PASS. * Information on migrating a DBEnvironment previously in Appendix E is removed. The information on using SQLMigrate and SQLINSTL is in chapter 1 of the ALLBASE/SQL Database Administration Guide and appendix A of the MPE/iX HP 3000 System Software Maintenance Manual. * A new appendix E is added on the new views for TurboIMAGE/XL and third-party indices. * A new appendix F is added on the date/time Application Programming Interface (API). * Other enhancements that are documented in this edition are predicate level locking, packed decimals, B-Tree indices, and the multi-connect feature. [REV END] Migrating a DBEnvironment [REV BEG] If you are migrating from ALLBASE/SQL version F.nn to version G.nn, you must migrate the ALLBASE/SQL DBEnvironment. An ALLBASE/SQL utility called SQLMigrate (SQLMIG.PUB.SYS) lets you migrate between major releases of ALLBASE/SQL. SQLINSTL (SQLINSTL.PUB.SYS) is a job that assists in the migration between minor releases (for example, from G.1 to G.2). For step-by-step instructions to follow in migrating a DBEnvironment using SQLMigrate or SQLINSTL, refer to chapter 1 of the ALLBASE/SQL Database Administration Guide or appendix A of the MPE/iX HP 3000 System Software Maintenance Manual.[REV END] Additional Documentation [REV BEG] Manuals Bundled with IMAGE/SQL Customer Order Number -------------------------------------------------------------------------------------- HP IMAGE/SQL Administration Guide 36385-90001 Getting Started with HP IMAGE/SQL 36385-90008 TurboIMAGE/XL Database Management System Reference Manual 30391-90001 ALLBASE/SQL Reference Manual 36216-90001 ALLBASE/SQL Database Administration Guide 36216-90005 ALLBASE/SQL Message Manual 36216-90009 ALLBASE/SQL Performance and Monitoring Guidelines 36216-90102 ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL 36216-90096 ODBCLINK/SE Reference Manual 36217-90406 Additional ALLBASE Manuals Customer Order Number -------------------------------------------------------------------------------------- ALLBASE/SQL Advanced Application Programming Guide 36216-90100 ALLBASE/SQL C Application Programming Guide 36216-90023 ALLBASE/SQL FORTRAN Application Programming Guide 36216-90030 ALLBASE/SQL Pascal Application Programming Guide 36216-90007 Up and Running with ALLBASE/SQL 36389-90011 [REV END] 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 the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: 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] Conventions (continued) [...] 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. CTRLchar CTRLchar indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously.