IMAGE/SQL Administration Guide : COPYRIGHT NOTICE [ IMAGE/SQL Administration Guide ] MPE/iX 5.0 Documentation
IMAGE/SQL Administration Guide
900 Series HP 3000 Computer Systems
IMAGE/SQL Administration Guide
HP Part No. 36385-90001
Printed in U.S.A.
Edition Fourth Edition
E1294
________________________________________________________________________
|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 are reserved. Reproduction, adaptation, or |
|translation without prior written permission is prohibited, except as |
|allowed under the copyright laws. |
________________________________________________________________________
Copyright (c) 1990 - 1994 by Hewlett-Packard Company
Printed 1994
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
About this Manual
This manual explains how to administer and maintain IMAGE/SQL. 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.
For compatibility reasons, this guide uses the acronym ATC (for
ALLBASE/Turbo CONNECT). The terms Turbo CONNECT and ALLBASE/Turbo CONNECT
are synonymous with IMAGE/SQL.
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.
Appendix E Using SQLMigrate
Explains how to migrate from ALLBASE/SQL version F.nn to
version G.nn using SQLMigrate.
Glossary Glossary
Gives basic definitions of terms.
[REV BEG]
Additional Documentation
Here is a list of manuals you may find useful:
Title Customer Order
Number
--------------------------------------------------------------------------------------
Getting Started with HP IMAGE/SQL 36385-90008
ALLBASE/NET User's Guide 36216-90031
ALLBASE/SQL Database Administration Guide 36216-90005
ALLBASE/SQL Message Manual 36216-90009
ALLBASE/SQL Performance and Monitoring Guidelines 36216-90102
ALLBASE/SQL Reference Manual 36216-90001
HP PC API User's Guide for ALLBASE/SQL and IMAGE/SQL 36216-90104
ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL 36216-90096
TurboIMAGE/XL Database Management System Reference Manual 30391-90001
Up and Running with ALLBASE/SQL 36389-90011
ALLBASE/SQL Advanced Application Programming Guide 36216-90100
ALLBASE/SQL FORTRAN Application Programming Guide 36216-90030
ALLBASE/SQL C Application Programming Guide 36216-90023
ALLBASE Pascal Application Programming Guide 36216-90007
What's New in this Edition
This edition of the HP IMAGE/SQL Administration Guide contains the
following changes:
* Enhancements added in release B.G0 are documented.
* Edits based on suggestions by customers and HP Support Engineers
are included throughout the manual.
* A new task to assist in adding log files is added to Chapter 2,
"Task 8: Adding a Log File."
* Information on migrating a DBEnvironment is in Appendix E, "Using
SQLMigrate."
* Limitations (as of version B.G0) on DBEnvironment file size,
number of log pages, and number of fileset pages are documented in
Chapter 2.
[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.
MPE/iX 5.0 Documentation