Trailing-Edge
-
PDP-10 Archives
-
BB-4157E-BM
-
fortran-documentation/fortra.ins
There is 1 other file named fortra.ins in the archive. Click here to see a list.
FORTRAN-20 Version 6 Installation Guide
December 1981
COPYRIGHT (C) 1981 BY
DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS.
THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER
COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY
TRANSFERRED.
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
CORPORATION.
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
FORTRA.INS - FORTRAN-20 Version 6 Page 2
FORTRAN-20 Installation Guide
December 1981
CONTENTS
CHAPTER 1 SUMMARY
CHAPTER 2 INSTALLATION AND TESTING OF STANDARD FORTRAN
2.1 INSTALLATION OF STANDARD FORTRAN . . . . . . . . . 2-1
2.2 TESTING OF STANDARD FORTRAN . . . . . . . . . . . 2-3
CHAPTER 3 INSTALLATION AND BUILDING OF NONSTANDARD FORTRAN
3.1 BUILDING THE FORTRAN COMPILER FROM SOURCES . . . . 3-1
3.1.1 Using The FORTRAN Compiler With DDT . . . . . . 3-2
3.2 BUILDING FOROT6.EXE AND FORLIB.REL FROM SOURCES . 3-2
3.2.1 Using A Non-standard QUASAR Interface . . . . . 3-2
3.3 PATCHING FOROT6.EXE WITH DDT . . . . . . . . . . . 3-3
3.4 BUILDING FORDDT FROM SOURCES . . . . . . . . . . . 3-3
3.5 APPLYING SOURCE PATCHES TO THE FORTRAN PRODUCT . . 3-4
CHAPTER 4 BUILDING DBMS VERSION 6 WITH FORTRAN-20
CHAPTER 5 BUILDING SORT VERSION 4C WITH FORTRAN-20
CHAPTER 1
SUMMARY
This document describes the procedures for installing the following
software:
1. Version 6(1144) of the FORTRAN compiler
2. Version 6(2033) of FOROTS (the FORTRAN object-time system)
3. Version 6(2033) of FORLIB (the FORTRAN library)
4. Version 6(154) of FORDDT (the FORTRAN debugger)
FORTRAN, FORLIB, FOROTS, FORDDT, and .HLP files should be installed on
PS:<SUBSYS>.
The release is in the form of a 1600 BPI FORTRAN distribution tape
written in TOPS-20 DUMPER format containing six savesets.
The distribution tape consists of the following savesets:
1. <FORTRAN-DOCUMENTATION>
This saveset includes all FORTRAN documentation files.
2. <FORTRAN-SYSTEM>
This saveset includes the .EXE, .REL, and .HLP files that
should be installed on PS:<SUBSYS>.
3. <FORTRAN-TEST>
This saveset includes the UETP tests and .VER file. It also
includes a .CTL file that will run the same tests without
using UETP.
4. <FORTRAN-OTS-DEBUGGER>
This saveset includes the sources for FOROTS and FORDDT, and
all intermediate files generated when building FOROTS and
FORDDT.
SUMMARY Page 1-2
5. <FORTRAN-COMPILER>
This saveset includes the sources for the compiler, and all
intermediate files generated when building the compiler.
6. <FORTRAN-TOOLS>
This saveset includes the miscellaneous system utilities
needed to build the compiler and FOROTS. This includes the
BLIS10 compiler, HELPER, and other tools.
CHAPTER 2
INSTALLATION AND TESTING OF STANDARD FORTRAN
The following files comprise the FORTRAN compiler and object-time
system. Merely copying these files from the distribution tape
provides a working FORTRAN system. The files are:
FORTRA.HLP
FORTRA.EXE
FOROT6.EXE
FORLIB.REL
FORDDT.REL
FORDDT.HLP
2.1 INSTALLATION OF STANDARD FORTRAN
Perform the following steps to install the FORTRAN system:
(1) LOGIN as the operator or as a user with WHEEL privileges.
(2) Give the ENABLE command.
(3) Mount the FORTRAN distribution tape.
(4) Use the BUILD command to create directories for the contents of
the FORTRAN distribution tape. You may use directory names of
your choice. Type the following commands:
$BUILD <DOC-directory> !GIVE DIRECTORY NAME OF YOUR CHOICE
WORK 100
PERM 100
DIRECTORY group !1 OF YOUR USER GROUPS. BUT IF NONE,
!<RET> !ASK SYSTEM MANAGER FOR A GROUP
NUMBER
$BUILD <RUN-directory>
WORK 400
PERM 400
DIRECTORY group !SAME GROUP AS ABOVE
!<RET>
INSTALLATION AND TESTING OF STANDARD FORTRAN Page 2-2
$BUILD <TESTS-directory>
WORK 100
PERM 100
DIRECTORY group !SAME GROUP AS ABOVE
!<RET>
$BUILD <FOROTS-directory>
WORK 800
PERM 800
DIRECTORY group !SAME GROUP AS ABOVE
!<RET>
$BUILD <COMPILER-directory>
WORK 1800
PERM 1800
DIRECTORY group !SAME GROUP AS ABOVE
!<RET>
$BUILD <TOOLS-directory>
WORK 300
PERM 300
DIRECTORY group !SAME GROUP AS ABOVE
!<RET>
(5) Use the DUMPER program to restore the files from the distribution
tape to disk. If you wish not to restore a particular saveset,
just replace the the particular RESTORE command with a SKIP 1
command. Type the following commands:
$DUMPER
DUMPER>TAPE MTAn:
DUMPER>REWIND
DUMPER>FILE !OPTIONAL
DUMPER>DENSITY 1600
DUMPER>ACCOUNT SYS
DUMPER>RESTORE PS:<*>*.*.* (TO) <DOC-directory>*.*.*
DUMPER>RESTORE PS:<*>*.*.* (TO) <RUN-directory>*.*.*
DUMPER>RESTORE PS:<*>*.*.* (TO) <TESTS-directory>*.*.*
DUMPER>RESTORE PS:<*>*.*.* (TO) <FOROTS-directory>*.*.*
DUMPER>RESTORE PS:<*>*.*.* (TO) <COMPILER-directory>*.*.*
DUMPER>RESTORE PS:<*>*.*.* (TO) <TOOLS-directory>*.*.*
DUMPER>EXIT
(6) Follow the "SPECIAL INSTRUCTIONS" (if any) at the end of the
cover letter. Also, read the FORTRAN Beware file for any last
minute instructions.
(7) It is recommended that you save the old versions of FORTRAN in
case they are needed again. Type the following commands:
$CONNECT SYS: (or wherever you keep the FORTRAN system)
$COPY SYS:FORTRA.EXE (TO) OLD:FORTRA.EXE
$COPY SYS:FOROTS.EXE (TO) OLD:FOROTS.EXE
$COPY SYS:FORLIB.REL (TO) OLD:FORLIB.REL
$COPY SYS:FORDDT.REL (TO) OLD:FORDDT.REL
INSTALLATION AND TESTING OF STANDARD FORTRAN Page 2-3
$COPY SYS:FORTRA.HLP (TO) OLD:FORTRA.HLP
$COPY SYS:FORDDT.HLP (TO) OLD:FORDDT.HLP
(8) Install the FORTRAN system software by giving the commands:
$COPY <RUN-directory>*.HLP HLP:*.*
$DELETE <RUN-directory>*.HLP
$COPY <RUN-directory>*.* SYS:*.*
(9) Decide if you want to destroy the directories you created in step
(4). For each directory you wish to destroy, give the following
commands. (Note: a directory cannot be deleted unless all of
its subdirectories have been deleted.)
$BUILD <name-of-directory-to-destroy>
KILL
!<RET> TO CONFIRM
!<RET> TO EXIT BUILD
2.2 TESTING OF STANDARD FORTRAN
Perform the following procedures to test the FORTRAN system:
(1) Install the FORTRAN UETP test module by giving the command:
$COPY <TESTS-directory>*.FOR PS:<UETP.LIB>*.*
$COPY <TESTS-directory>*.VER PS:<UETP.LIB>*.*
(2) If desired, run the standalone FORTRAN test module provided by
giving the following command:
$SUBMIT F20TST.CTL
The test expects to find all the FORTRAN system components and
the distributed FORTRAN test programs on logical device DSK:.
When the test batch job is completed, the F20TST.LOG file must be
examined to make sure that none of the tests branched to the
error label UERR::.
(3) Once the FORTRAN system components have been installed in SYS:
(see Step 8 above), you may run the UETP test module provided, by
giving the following commands:
$DEFINE DSK: DSK:,PS:<UETP.LIB>
$DELETE FORTRA.LOG,RUN.LOG,EXCEPT.LOG
$RUN UETP
UETP>ENABLE FORTRA/DEPTH:VERIFICATION
UETP>BEGIN
UETP>EXIT
If any errors occur, UETP will report them at your terminal and
in the file EXCEPT.LOG. For more information on UETP, including
INSTALLATION AND TESTING OF STANDARD FORTRAN Page 2-4
the run-time privileges, see the UETP Procedures/Reference
Manual.
Run your own tests if desired. If you run your own tests, be
sure that SYS: is defined to include <RUN-directory>.
CHAPTER 3
INSTALLATION AND BUILDING OF NONSTANDARD FORTRAN
This chapter describes building the FORTRAN compiler from sources if
modifications to the standard compiler are desired. It also describes
building FOROTS, FORLIB, and FORDDT from sources.
3.1 BUILDING THE FORTRAN COMPILER FROM SOURCES
Required software:
BLIS10 7E(227)
LINK 4A
MACRO 53A
SCAN 7B
HELPER 5(41)
Running the control file B20FTN.CTL will build the compiler from its
sources and produce the binary files. This control file has
successfully built and loaded the compiler at the Digital Equipment
Corporation - Marlboro computer facilities. This, however, in no way
guarantees its operation or support.
Note that B20FTN.CTL does a TAKE of B20FTN.CMD which defines SYS: to
include an area <FORTRAN.SSP>. This area is assumed to contain the
files that are in the FORTRAN-TOOLS saveset on the distribution tape.
The control file used to build the compiler in-house uses field-image
software from PS:<SUBSYS>. BLIS10.EXE 7E(227) is included on the
distribution tape.
Building the FORTRAN compiler from the sources provided is not a
trivial computational task. It requires a considerable amount of
computer resources. The complete execution of B20FTN.CTL requires at
least 2 and 1/2 hours on a 2040 processor. It is advised that only
installations desiring to modify the compiler consider completely
rebuilding it.
INSTALLATION AND BUILDING OF NONSTANDARD FORTRAN Page 3-2
NOTE
When loading the programs LEFT72, LEFTFM
and BUILD, undefined globals will be
encountered. These should be ignored,
as indicated by comments in the .CTL
file.
To submit a control file to run on a 2040, use the following command:
$SUBMIT filename/RESTART/TIME:3:0:0/UNIQUE:0
3.1.1 Using The FORTRAN Compiler With DDT
Symbols are loaded into FORTRA.EXE so that DDT may be used with the
FORTRAN compiler without any modifications.
3.2 BUILDING FOROT6.EXE AND FORLIB.REL FROM SOURCES
This section describes the procedures for building FOROT6.EXE and
FORLIB.REL from sources if modifications to the standard FOROTS and
FORLIB are desired.
The control file B20FRS.CTL can be used to build FOROTS and FORLIB
from the sources. The build process uses field-image software from
PS:<SUBSYS>.
This control file has successfully built and loaded the FOROTS and
FORLIB at the Digital Equipment Corporation - Marlboro computer
facilities. This, however, in no way guarantees its operation or
support.
To run the control file use the following command:
$SUBMIT B20FRS.CTL/RESTART/TIME:0:30:00/UNIQUE:0
3.2.1 Using A Non-standard QUASAR Interface
If your site has modified the QUASAR system file QSRMAC.MAC, to
include new fields in the "CREATE" message for example, you must
rebuild FOROTS from sources. If you have added non-standard fields
that should not be left blank, you must modify FOROPN.MAC near the
label "CLSQ", otherwise FORTRAN programs will not be able to use the
DISPOSE='<queue>' options of the CLOSE statement.
INSTALLATION AND BUILDING OF NONSTANDARD FORTRAN Page 3-3
3.3 PATCHING FOROT6.EXE WITH DDT
FOROT6.EXE normally contains symbols, but in order to use them the
following procedure must be followed:
@GET FOROT6
@I MEM !To find out starting and ending page number
527-574 FOROT6.EXE 1-46 R, CW, E
@DDT
DDT
MOVE 1,527006$X !Start of first page + 6
<>
MOVEM 1,@DDT+1$X
<>
.
.
.
At this point, DDT will know about the FOROTS local symbols, so they
may be used in applying patches. After you have installed a patch,
type Control-C to DDT, then type:
@SAVE FOROT6 (PAGES FROM) 527 (TO) 574 (*)
(*) The appropriate page numbers from the first "I MEM" command should
be used.
3.4 BUILDING FORDDT FROM SOURCES
This section describes the procedures for building FORDDT from sources
if modifications to the standard FORDDT are desired.
The control file B20FDT.CTL can be used to build FORDDT from sources.
The build process uses field-image software from PS:<SUBSYS>.
This control file has successfully built and loaded the FORDDT at the
Digital Equipment Corporation - Marlboro computer facilities. This,
however, in no way guarantees its operation or support.
To run the control file use the following command:
$SUBMIT B20FDT.CTL/RESTART/TIME:0:30:00/UNIQUE:0
INSTALLATION AND BUILDING OF NONSTANDARD FORTRAN Page 3-4
3.5 APPLYING SOURCE PATCHES TO THE FORTRAN PRODUCT
Source patches (edits) are published in the DECSYSTEM-20 Software
Dispatch as a problem description, accompanied by one or more FILCOM
files which detail some number of source module changes. The
specified problem is eliminated by insertion of the source changes,
and rebuilding the affected FORTRAN product component using the
procedures described above. There are a number of FORTRAN product
files which are absent from the FORTRAN-20 version of the product.
These files are OWNDM.MAC, DOPT.MAC, DGCMN.MAC, DNPT.MAC, ERROVA.BLI,
ERROVB.BLI, ERROVC.BLI, ERROVD.BLI, ERROVG.BLI, and ERROVR.BLI for the
compiler, and FORRTF.MAC for the library (FORLIB.REL). Source changes
to these modules can be safely ignored when installing patches to the
FORTRAN-20 version of the product.
In general, each edit to the product consists of a new entry in the
revision history comments, a change to the edit number of the product
component, and some number of changes to the code. Code changes are
pinpointed by a line of commentary (banner line) that accompanies each
non contiguous set of source line changes.
The component revision histories and edit number definitions are found
in REVHST.MAC for the compiler, FOROTS.MAC for the library and OTS,
and FORDDT.MAC for the debugger. In addition, the compiler source
modules all have a local edit number and revision history, found at
the beginning of each source module. All new revision history
comments will always precede the line "***** End Revision History
*****".
Banner lines, which are provided only as a tool for patch insertion,
are NOT to be added to the sources. They are comment lines, taking
the forms:
!**;[nnnn] Where field 1, Where field 2, XXX, Date - for BLIS10 sources
or
;**;[nnnn] @ TAG + (or -) mL, Action, XXX, Date - for MACRO sources
Where field 1: Routine, module, or macro name.
Where field 2: @ line mmmm: where mmmm is the line number
taken from a compiler listing
of the module. The word "line"
may not always appear.
@ text: where text is used to describe
positioning when line numbers
are not available (such as
REQUIRE files).
TAG: Closest unique MACRO tag to the source change.
May be qualified with feature test indicators.
mL: The change goes at m Lines down (+) or up (-)
from the specified TAG. Using an editor to
position to the line defining the TAG, and
INSTALLATION AND BUILDING OF NONSTANDARD FORTRAN Page 3-5
then advancing m lines will assure correct
positioning for the actual source change.
Action: The usual 3 are: inserted x lines, deleted
x lines, or replaced x lines.
The BLIS10 line numbers referenced are those produced by compiling the
distributed version of the module, using the distributed REQUIRE files
(if any are required). Distributed means exactly as they appear on
the FORTRAN distribution tape, with no edits installed.
In situations where lines of code are deleted, a single line of
commentary will be left behind containing the edit number that removed
the code. This line MUST remain in the sources (just as banner lines
must NOT appear). Failure to adhere to these rules may cause
difficulties with later edits that give line counts from MACRO module
TAGs used in previous edits.
Each changed line of source code (where feasible), will be flagged
with an edit indicator [nnnn] in commentary associated with the source
line. For MACRO changes, this text will usually appear as the first
item in the comment field, such as:
MOVEI T1,3 ;[1234] Get error count
For BLIS10 changes, this text will generally appear down the left
margin of the source module, such as:
%[1234]% T1 _ 3; !Get error count
but may also appear as the first item in the comment field.
CHAPTER 4
BUILDING DBMS VERSION 6 WITH FORTRAN-20
The control file DBMS6.CTL provided on the FORTRAN tape will build
DBMS V6 into FORTRAN-20. It will create a new FORLIB.REL which will
contain DBMS V6, and also create the file DBMSF.EXE to be put on SYS:.
Before running it, you must copy the DBMS .REL files from the DBMS V6
tape into some directory, for example <DBMS-BUILD>.
You must also create a file SETUP.CMD which should reside in the area
in which you will submit DBMS6.CTL. This file should contain a
definition for DSK:, for example:
DEFINE DSK: DSK:,<DBMS-BUILD>
The DSK: definition must include the directory (or directories) that
contain the DBMS .REL files, the file DBCS2F.CMD from the FORTRAN
tape, and FORLIB.REL.
If you desire more information, the installation of DBMS is documented
thoroughly in the control file DBMS6.CTL.
CHAPTER 5
BUILDING SORT VERSION 4C WITH FORTRAN-20
To install SORT Version 4C with FORTRAN-20, just restore the file
SORT.EXE from the SORT distribution tape and place on SYS:. The
necessary interface routine is built into FORLIB.REL.
[End of FORTRA.INS]