HP Business BASIC/XL Migration Guide : COPYRIGHT NOTICE [ HP Business BASIC/XL Migration Guide ] MPE/iX 5.0 Documentation
HP Business BASIC/XL Migration Guide
HP Business BASIC/XL Migration Guide
HP 3000 Computers
HP Part No. 32715-90003
Printed in U.S.A.
Printed Oct 1989
Edition First Edition
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 for incidental or
consequential damages in connection with the furnishing, performance, 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 that 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 Æ 1989 by Hewlett-Packard Company
Print History
New editions are complete revisions of the manual. Update packages,
which are issued between editions, contain additional and replacement
pages to be merged into the manual by the customer. The dates on the
title page change only when a new edition or a new update is published.
No information is incorporated into a reprinting unless it appears as a
prior update; the edition does not change when an update is incorporated.
The software code printed alongside the date indicates the version level
of the software product at the time the manual or update was issued.
Many product updates and fixes do not require manual changes and,
conversely, manual corrections may be done without accompanying product
changes. Therefore, do not expect a one to one correspondence between
product updates.
First Edition October 1989 HP32715A.00.00
Addition Documentation
The following manuals provide information that can help you migrate to HP
Business BASIC/XL.
HP Business BASIC/XL Reference Manual 32715-90001
HP Business BASIC/XL Programmer's Guide 32715-90002
Link Editor Reference Manual 32650-90030
HP Pascal Programmer's Guide 31502-90002
Switch Programming Guide 32650-90014
Migration Process Guide 30367-90007
Preface
This guide describes how to migrate programs from the following languages
to HP Business BASIC/XL:
* HP Business BASIC/V
* BASIC/V
* BASIC/260
This guide is intended for experienced BASIC programmers with a good
knowledge of the tools used to maintain BASIC programs. This guide has
three self-contained sections; one section for each migration path.
Part 1 Migrating from HP Business BASIC/V
Chapter 1 Getting Started
Chapter 2 Planning Your Migration from Business BASIC/V
Chapter 3 Evaluating Changes You Need to Make
Chapter 4 Migrating Business BASIC/V Files
Chapter 5 Migrating TurboIMAGE/V Databases
Chapter 6 Enhancing and Optimizing Migrated Business BASIC/V
Applications
Chapter 7 Accessing Compatibility Mode Data Files
Part 2 Migrating from BASIC/V
Chapter 8 Getting Started
Chapter 9 Planning Your Migration from BASIC/V
Chapter 10 Evaluating Changes You Need to Make
Chapter 11 Migrating BASIC/V Files
Chapter 12 Migrating TurboIMAGE/V Databases
Chapter 13 Reviewing What the Migration Aid Changes for You
Chapter 14 Optimizing Migrated BASIC/V Applications
Part 3 Migrating from BASIC/260
Chapter 15 Getting Started
Chapter 16 Planning Your Migration from BASIC/260
Chapter 17 Evaluating Changes You Need to Make
Chapter 18 Moving Files from the HP 260
Chapter 19 Migrating BASIC/260 Files
Chapter 20 Migrating HP 260 Databases
Chapter 21 Migrating FORMS/260 Forms
Chapter 22 Reviewing What the Migration Aid Changes for You
Chapter 23 Enhancing and Optimizing Migrated BASIC/260 Applications
Conventions
Notation Description
nonitalics Nonitalicized words and punctuation characters without
special attributes (such as brackets, braces, and
ellipses) are required and are entered exactly as shown.
In the following example, both the command and the
trailing semicolon are required:
EXIT;
italics Italicized words denote elements that you must replace
with an appropriate value. In the following example,
you must replace filename with the name of the file you
want to close:
CLOSE filename
[ ] An element inside brackets is optional. Several
elements stacked inside brackets means you can select
any one or none of these elements. For example:
[A]
[B]
You can select A or B or neither. When brackets are
nested, parameters in inner brackets can be specified
only if parameters in outer brackets or comma
placeholders are specified. For example:
[parm1[,parm2[,parm3]]]
can be entered as
parm1,parm2,parm3
or
parm1,,parm3
and so forth.
{ } When several elements are stacked within braces in a
syntax statement, you must select one of those elements.
For example:
{A}
{B}
{C}
You must select A or B or C.
... A horizontal ellipsis in a syntax statement indicates
that a previous statement can be repeated. For example:
[,itemname] ...
Within examples, vertical and horizontal ellipses show
where portions of the example have been omitted.
Conventions (continued)
Some syntax diagrams in this manual are in the form of "railroad tracks";
alternative paths are indicated by "switches" in the paths.
The conventions for the railroad syntax diagrams are:
* Items in all uppercase letters represent keywords, predefined
symbolic names, and special symbols. These items must be specified
exactly as given.
* Items in all lowercase letters, with undersocre characters (_) as
required, represent items that the user replaces with appropriate
entities.
* Required items are in ovals or circles.
* Items to be replaced by the user are in boxes.
* A number n beneath a half circle indicates that the path can be
traversed at most n times.
* A number n over a half circle indicates that the path must be
traversed exactly n times.
For example, the syntax diagram for the DO statement looks like this:
NOTE In some diagrams, a number appears in the lower left corner (for
example, LG200025_018 in the diagram above). This number is for HP
control purposes only and should not be interpreted as part of the
diagram or table.
The DO statement syntax on the previous page indicates that a DO
statement must begin with the word DO. The word DO is followed by an
optional label. If label is used, it can be followed by an optional
comma. Next come either the word WHILE, a left parenthesis, a logical
expression, and a right parenthesis, or an index, an equal sign, init, a
comma, and limit. An optional step follows. If step is used, it must be
preceded by a comma.
Following are some DO statements that illustrate the syntax. This
example uses the DO WHILE path:
DO WHILE (i .LE. 10)
This example uses label, the optional comma, index, init, limit, and
step:
DO 10, i = 1, 100, 10
The FORTRAN 77 programs in this manual (programs, program fragments,
statements, and so on) use the following conventions: special symbols,
keywords, and predefined symbolic names are all in uppercase letters and
user-defined symbolic names are in lowercase letters.
For example, in the program fragment
DO WHILE (count .LE. fibs)
WRITE(6,30) count, k
i=j
j=k
k=i + j
count = count + 1
END DO
the following are predefined symbolic names
DO WHILE
.LE.
WRITE
END DO
and the following are user-defined symbolic names:
count
fibs
k
i
j
MPE/iX 5.0 Documentation