DBChange Plus Technical Addendum for MPE/iX Release 4.0 : COPYRIGHT NOTICE [ DBChange Plus Technical Addendum for MPE/iX Release 4.0 ] MPE/iX 5.0 Documentation
DBChange Plus Technical Addendum for MPE/iX Release 4.0
TurboIMAGE/XL Database Management System
DBChange Plus Technical Addendum
for MPE/iX Release 4.0
HP Part No. 36386-90005
Printed in U.S.A.
Edition First Edition
E0692
________________________________________________________________________
|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)1992 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 1992
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 June 1992 36836-A.01.00
Preface
With this release of DBChange Plus, you are introduced to a new document
type called a technical addendum. This document exists to introduce the
new functionality contained in this version of the product. It is meant
to supplement the DBChange Plus User's Guide. The information contained
in this document will be incorporated into the next edition of the
manual.
Introducing MPE/iX
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 Hewlett-Packard 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, and you can continue to use MPE XL system
documentation.
What This Document Contains
This technical addendum describes the new E data type supported by the
TurboIMAGE/XL database management system. This data type is used for
data stored in IEEE format on an MPE/iX system and is fully supported in
the TurboIMAGE, DBChange Plus, and QUERY/3000 products. Read this
document to learn how to include data items of type E in TurboIMAGE/XL
databases and how to convert your data if it already is stored in IEEE
data format.
Each chapter in this document assumes a knowledge of the DBChange Plus
product. New users should read chapters 1, 2, and 4. Experienced users
should read chapter 1 and refer to chapters 3 and 4 for IEEE data type
usage.
The chapters are organized as follows:
Chapter 1 introduces you to the new data type. A diagram of the
formats of IEEE and HP 3000 reals is included for comparison
purposes.
Chapter 2 contains a tutorial of various tasks in which data items
of type E are added to a database and data items of other types
are converted to type E.
Chapter 3 provides the syntax and a brief description of the
revised ADD ITEM, CHANGE ATTRIBUTES, and CHANGE ITEM commands.
For additional information on these commands, refer to the
DBChange Plus guide. Also in this chapter is the BASE command,
which is not impacted by this release but is included to clarify
the function of the NEW option.
Chapter 4 provides the new and revised messages related to the
IEEE data type. This chapter supplements Appendix A of the
DBChange Plus 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 the characters in either uppercase or
lowercase. For example:
COMMAND
can be entered as any of the following:
command Command COMMAND
It cannot, however, be entered as:
comm com_mand comamnd
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
or Shift represents the shift key.
CTRLcharacterCTRLcharacter indicates a control character. For
example, CTRLY means that you press the control
key and the Y key simultaneously.
MPE/iX 5.0 Documentation