HP FORTRAN 77/iX Migration Guide : COPYRIGHT NOTICE [ HP FORTRAN 77/iX Migration Guide ] MPE/iX 5.0 Documentation
HP FORTRAN 77/iX Migration Guide
HP FORTRAN 77/iX Migration Guide
________________________________________________________________________
|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 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)1987, 1992 by Hewlett-Packard Company
Printed in U.S.A.
900 Series HP 3000 Computers
HP Part No. 31501-90004
Edition Second Edition
E0692
Printed June 1992
Print History
The following table lists the printings of this document, together with
the respective release dates for each edition. 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 November 1987 31501A.01.04
Second Edition June 1992 31501A.04.31
.
Preface
This manual explains how to run FORTRAN 66/V and HP FORTRAN 77/V programs
on the MPE/iX operating system and how to covert them to HP FORTRAN 77/iX
programs. It is written for experienced FORTRAN programmers.
This manual contains the following chapters:
Chapter 1 Explains terminology used in this manual. Explains
migration to compatibility mode versus migration to
native mode.
Chapter 2 Discusses the scope of Part I and describes the
FORTRAN 66/V to HP FORTRAN 77/V Migration Aid.
Chapter 3 Describes the conversions performed by the
migration aid.
Chapter 4 Describes changes that the migration aid cannot
make.
Chapter 5 Explains how to run the migration aid and includes
a sample migration.
Chapter 6 Describes how to modify the migration aid according
to your needs.
Chapter 7 Describes the scope of Part II
Chapter 8 Compares HP FORTRAN 77/iX to HP FORTRAN 77/V,
outlining the changed, missing, and new features.
Chapter 9 Explains changes to an HP FORTRAN 77/V program that
may be required before it can run properly on the
MPE/iX system.
Chapter 10 Describes data file conversions that allow you to
take full advantage of MPE/iX performance
improvements.
Chapter 11 Summarizes factors affecting migration and offers
tips for avoiding migration problems.
Additional Documentation
This manual does not discuss the MPE/iX operating system in detail. See
the appropriate operating system or language manual for complete
information about those subjects. The following is a partial list of the
operating system and language manuals:
--------------------------------------------------------
| |
| Manual Title Number to Use |
| to |
| Order Manual |
| |
--------------------------------------------------------
| |
| HP FORTRAN 77/iX Reference 31501-90010 |
| |
| HP FORTRAN 77/iX Programmer's Guide 31501-90011 |
| |
| HP Link Editor/iX Reference Manual 32650-90030 |
| |
--------------------------------------------------------
| |
| HP FORTRAN 77 Programmer's Guide 5967-4686 |
| |
| HP FORTRAN 77 Quick Reference Guide 5957-4687 |
| |
| HP FORTRAN 77 Reference Manual 5957-4685 |
| |
| HP FORTRAN 77/V Programmer's Guide 31501-90005 |
| Supplement |
| |
| HP FORTRAN 77/V Reference Manual 30000-90294 |
| Supplement |
| |
--------------------------------------------------------
| |
| FORTRAN/3000 Referecne Manual 30000-90040 |
| |
--------------------------------------------------------
| |
| HP FORTRAN 77 Self Study Guide 22999-90548 |
| |
| Supplement to the HP FORTRAN 77 Self 22999-90549 |
| Study Guide |
| |
--------------------------------------------------------
| |
| MPE/iX Commands Reference Manual 32650-60002 |
| |
| MPE/iX Intrinsics Reference Manual 32650-90028 |
| |
| MPE/iX Utilities Reference Manual 32033-90008 |
| |
--------------------------------------------------------
Conventions
CASE In a syntax statement, commands and keywords are
shown in uppercase and lowercase characters. The
characters must be entered in the order shown;
however, you can enter the characters in either
uppercase or lowercase. For example:
SHOWJOB
can be entered as any of the following:
showjob Showjob SHOWJOB
It cannot, however, be entered as:
shojwob Shojob SHOW_JOB
italics In a syntax statement or an example, a word in
italics represents a parameter or argument that you
must replace with an actual value. In the following
example, you must replace filename with the name of
the file:
RELEASE filename
Italics font is also used to emphasize a word or
words.
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:
SETMSG {ON }
{OFF}
Commands listed in braces are called command lists
throughout this manual.
Conventions (continued)
[ ] In a syntax statement, brackets enclose optional
elements. In the following example, ,TEMP can be
omitted:
PURGE filename[,TEMP]
When several elements are stacked within brackets,
you can select one or none of the elements. In the
following example, you can select devicename or
deviceclass or neither. The elements cannot be
repeated.
SHOWDEV [devicename ]
[deviceclass]
[...] 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 itemname zero or more times.
Each instance of itemname must be preceded by a
comma:
[,itemname] [...]
In the example below, you only use the comma as a
delimiter if itemname is repeated; no comma is used
before the first occurrence of itemname:
[itemname] [,...]
|...| 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 the example have been
omitted.
In a syntax statement, the space symbol shows a
required blank. In the following example, modifier
and variable must be separated with a blank:
SET [(modifier)] (variable);
The symbol indicates a key on the keyboard.
For example, RETURN represents the carriage return
key.
CNTLchar CNTLchar indicates a control character. For example,
CNTLY means you press the control key and the Y key
simultaneously.
Conventions (continued)
Comment Explains an operator entry or debug message.
> The HP Symbolic Debugger prompt.
| Represents "or".
; Separates commands in a command list.
base prefixes The prefixes %, #, and $ specify the numerical base
of the value that follows:
%num specifies an octal number
#num specifies a decimal number
$num specifies a hexadecimal number
If no base is specified, decimal is assumed.
Bits (bit:length) When a parameter contains more than one piece of data
within its bit field, the different data fields are
described in the format Bits (bit:length) bit is the
first bit in the field and length is the number of
consecutive bits in the field. For example, Bits
(13:3) indicates bits 13, 14, and 15:
MPE/iX 5.0 Documentation