Digital PDFs

AA-P344B-TM

March 1985

24 pages

Original

0.6MB

Document:	TOPS-20 FORTRAN Installation V10 May85
Order Number:	AA-P344B-TM
Revision:	0
Pages:	24
Original Filename:	AA-P344B-TM_TOPS-20_FORTRAN_Installation_V10_May85.pdf

OCR Text

TOPS-20
FORTRAN Installation Guide
M-P344B-TM

May 1985

This manual dE!scribes how to install the FORTRAN·-20 Version
10 software.
This manual supersedes the TOPS-20 FORTRAN Installation
Guide, order number AA-P344A-TM.
OPERATING SYSTEM:
SOFTWARE:

TOPS-20 V4.1, VS.1

FORTR:AN-20 V10

Software and manuals should be ordered by title and order numbm. In the United States. send orders
to the nearest distribution center. Outsid.~ the United States. orders should be directed to the nearest
DIGITAL Field Sales Office or representative.

Northeast/MId-Atlantic Region

Cen!tral Region

Digital Equipment Corporation
PO Box CS2008
Nashua. New Hampshire 03061

Digital Equipment Corporatior
Digital Equipment Corporation
ACcElssories and Supplies Cellter Accessories and Supplies Center
1050 East Remington Road
632 Caribbean Drive
Schaumburg. Illinois 60195
Sunnyvale. California 94086
Teleph()ne:(408)734-4915
Telephone:(312)64(}-5612

Telephone:(603)88~660

Western Region

digital equipment corporation. rllarlboro massachusetts

First Printing, March 1983
Revised, May 1985
© Digital Equipment Corporation 1983, 1985. All Rights Reserved.

The information in this document is subject to change without notice and should
not be construed as a commitment by Digital Equipment Corporation. Digital
Equipment Corporation assumes no responsibility for any errors that may
appear in this document.
The software described in this document is furnished under a license and may
only be used or copied in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment
that is not supplied by DIGITAL or its affiliated companies.
The following are trademarks of Digital Equipment Corporation:

~DmDD~DTY
DEC
DECmate
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter
DIBOL

MASSBUS
PDP
P/OS
Professional
O-BUS
Rainbow
RSTS

RSX
RT
UNIBUS
VAX
VMS

VT
Work Processor

The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future
documentation.

CONTENTS

CHAPTER 1

SUMMARY

CHAPTER 2

INSTALLING AND TESTING STANDARD FORTRAN

2.1
2.2
2.3
CHAPTER 3
3.1
3.1.1
3.2
3.3
3.4
3.5
CHAPTER 4
4.1
CHAPTER 5

INSTALLING STANDARD FORTRAN
TESTING STANDARD FORTRAN •
CLEAN UP • • • • • • • • • •

• • • 2-1
• • • 2-4
• • • 2-5

BUILDING NONSTANDARD FORTRAN
BUILDING THE FORTRAN COMPILER FROM SOURCES • •
Debugging the FORTRAN Compiler with DDT
BUILDING FO~OTS AND FORLIB FROM SOURCES
PATCHING FO~OTS WITH DDT • • • • • • •
•
BUILDING FO~DDT FROM SOURCES • • • • •
•
APPLYING SOURCE PATCHES TO THE FORTRAN PRODUCT

• •
••
•
• •
• •
• •

3-1
3-2
3-2
3-3
3-3
3-4

BUILDING DBMS VERSION 6.1 WITH FORTRAN-20
DEBUGGING FCRTRAN-DBMS USING DDT • • • • • • • • • 4-2
USING SORT VERSION 5 WITH FORTRAN-20

iii

CHAP~rER

SUMMARY

This document describes the procedures for
software:

installing

the

following

Version 10 of the FORTRAN compiler

Version 10 of FOROTS (the FORTRAN object-time system)

Version 10 of FORLIB (the FORTRAN library)

Version 10 of FORDD'r (the FORTRAN debugger)

FORTRAN, FORLIB, FOROTS, FORODT, and .HLP files should be installed on
SYS: •
The Version 10 release is on a 1600
written in TOPS-20 DUMPER format.

BPI

FORTRAN

distribution

tape

NOTE
For the initial release of FORTRAN Version 10, the
FORTRAN distribution tape will also contain the LINK
Version 6.0 and DDT Version 43 software.
This
software will eventually be removed from the FORTRAN
distribution tape.
rhus, some FORTRAN distribution
tapes will contain the LINK and DDT software and
others will not.
The installation procedures for this
software
have
been included in this manual in
gray-shading.
If your FORTRAN distribution
tape
contains the LINK and DDT software, you should follow
the instructions,
including those in gray-shading;
otherwise, skip the instructions in gray-shading.
The distribution tape contains the following savesets:
1.

<FORTRAN-DOCUMENTATION>
This saveset includes all FORTRAN documentation files.

<FORTRAN-SYSTEM>
This saveset includes the .EXE, .REL,
should be installed on SYS:.

1-1

and

.HLP

files

that

SUMMARY
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.

<FORTRAN-OTS-DEBUGGER>
This saveset includes the sources for FOROTS and FORDDT, and
all intermediate files generated when building FOROTS and
FORDDT.

<FORTRAN-COMPILER>
This saveset includes the sources for the compiler, and
intermediate files generated when building the compiler.

all

<FORTRAN-TOOLS>
This saveset includes the miscellaneous system utilities
needed to build the compiler and FOROTS.
These files include
the BLISIO compiler, HELPER, and other tools.

<FORTRAN-AUTOPATCH>
This saveset includes a series of files with the extension
.KEY.
These files are supplied for future use when FORTRAN
is Autopatched.

Also included on the distribution tape are four LINK savesets and
DDT saveset:
1.

<DOCUMENTATION>
This saveset
files.

one

includes

the

LINK

documentation

and

beware

<SUBSYS>
This saveset includes the LINK~EXE, .REL, and .HLP files that
shQ~l4 be installed on SYS:.

<tINK.SO~RC~S>

This saveset includes the LINK source files.

<LINK. BUILD>
This saveset includes miscellaneous system
to build LINK.

utili~ies

needed

<DDT>
This saveset includes REt, EXE, and documentation
DDT'Version 43.

1-2

files

for

CHAP~rER

INSTALLING AN)) TESTING 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
FOROIO.EXE
FORLIB.REL
FORDDT.REL
FORDDT.HLP
You also need LINK-20 Version 6.0 on SYS:, and your installation must
be running TOPS-20 Version 5ul (KL Model B) or TOPS-20 Version 4.1 (KS
and KL Model A).

2.1

INSTALLING STANDARD FORTRAN

Perform the following steps to install the FORTRAN system:
(1)

(2)

Give the ENABLE command.

(3)

Mount the FORTRAN distrjbution tape.
(See the TOPS-20 Operator's
Guide for instructions on mounting magnetic tapes.)

(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>
$$WORK 100
$$PERM 100
$$DIRECTORY group
$$<RET>
$BUILD <RUN-directory>
$$WORK 700
$$PERM 700
$$DIRECTORY group
$$<RET>

!GIVE DIRECTORY NAME OF YOUR CHOICE
!FOR DOCUMENTATION DIRECTORY
!ONE OF YOUR USER GROUPS. BUT IF
!NONE, ASK SYSTEM MANAGER FOR A
!GROUP NUMBER
!DIRECTORY NAME FOR FILES REQUIRED
!TO RUN FORTRAN
!SAME GROUP AS ABOVE

2-1

INSTALLING AND TESTING STANDARD FORTRAN
$BUILD <TESTS-directory>
$$WORK 500
$$PERM 500
$$DIRECTORY group
$$<RET>

IDIRECTORY NAME FOR TEST FILES
!SAME GROUP AS ABOVE

$BUILD <FOROTS-directory> !DIRECTORY NAME FOR FOROTS SOURCES
$$WORK 2500
$$PERM 2500
$$DIRECTORY group
!SAME GROUP AS ABOVE
$$<RET>
$BUILD <COMPILER-directory> !DIRECTORY NAME FOR COMPILER
$$WORK 2400
!SOURCES
$$PERM 2400
$$DIRECTORY group
ISAME GROUP AS ABOVE
$$<RET>
$BUILD <TOOLS-directory>
$$WORK 300
$$PERM 300
$$DIRECTORY group
$$<RET>

IDIRECTORY NAME FOR TOOLS REQUIRED
!TO BUILD FORTRAN
ISAME GROUP AS ABOVE

$BUILD <FORTRAN-AUTOPATCH-directory> IDIRECTORY NAME FOR
$$WORK 600
IFORTRAN AUTOPATCH
$$PERM 600
$$DIRECTORY group
ISAME GROUP AS ABOVE
$$<RET>
$BUILD <LINKDOC-directory> !DIRECTORY NAME FOR LINK
$$WORK 300
!DOCUMENTATION
$$PERM 300
$$DIRECTORY group
!SAME GROUP AS ABOVE
$$<RET>
$BUILD <LINKSYS-directory> !DIRECTORY NAME FOR LINK
$$WORK 500
ISUBSYS
$$PERM 500
$$DIRECTORY group
!SAME GROUP AS ABOVE
$$<RET>
$BUILD <LINKSOURCES-directory> !DIRECTORY NAME FOR LINK
$$WORK 800
!SOURCES
$$PERM 800
$$DIRECTORY group
!SAME GROUP AS ABOVE
$$<RET>
$BUILD <LINKBUILD-directory> IDIRECTORY NAME F6~ LINK
$$WORK 200
. . IBUILD TOOLS
$$PERM 200
$$DIRECTORY group
!SAME GROUP AS ABOVE
$$<RET>
$BUILD <DDT-direc~orY>
$$WORK 2000
$$PERM 2000
$$DIRECTORY group
$$<RET)

!bIRECTORY NAM~ FOR DDT
ISAME GROUP AS ABOVE

2-2

INSTALLING AND TESTING STANDARD FORTRAN
(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 particular RESTORE command with a SKIP I
command. 'Type the following commands:
$DUMP:ER
DUMPER>TAPE MTAn:
DUMPE:R>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>RESTORE PS:<*>*.*.* (TO) <FORTRAN-AUTOPATCH-directory>*.*.*
,~>~f!ST9RE,'P~:t: <1\0)*. * ,:~ ,(TO) <LINKDOC-directory>*. *. *
'>~,liS,~ot{lf'~s; ~*,>,~". ~~~*~',,(T'o"<f.INi<'SYS"dl rectory>*; /; .li
'
irectory>*
~'S1f'pt{E,:}~~':~~>r:}~e,;,*~·~,(rrQl'-";·~~;f~KB;~.l't~~::a:fr~c"t~'r,¥>;*~~:*';~,*~--"
~~S'l',()R~ PS,:<*'>*".*.~' (1'0)' <DDT-dIrectory>*.*.*
DUMPER>EXIT'
,

R~pTPJ'{~"'J?$: f~>*:.~ ';'*',"('t6~"<LiNKS6tJRCES'':''d

.'*~*

(6)

Follow the "SPECIAL INSTRUCTIONS" (if any)
at the end of the
cover
letter.
Also,
read
the
file FORTRA.BWR in the
FORTRAN-DOCUMENTATION saveset for any last minute instructions.

(7)

It is recommended that you save the old version of FORTRAN
case it is needed again. Typ1e the following commands:

$CONNECT SYS: (or wherever you keep the FORTRAN system)
$COPY SYS:FORTRA.EXE (TO) OLD:FORTRA.EXE
$COPY SYS:FOROT7.EXE (TO) OLD:FOROT7.EXE
$COPY SYS:FORLIB.REL (TO) OLD:FORLIB.REL
$COPY SYS:FORDDT.REL (TO) OLD:FORDDT.REL
$COPY SYS:FORTRA.HLP (TO) OLD:FORTRA.HLP
$COPY SYS:FORDDT.HLP (TO) OLD:FORDDT.HLP
$COPY SYS:FORPRM.UNV (TO) OLD:FORPRM.UNV
(8)

If desired, run the standalone FORTRAN test
giving the following commands:

module

provided

$DELETE F20TST.LOG
$SUBMIT <TESTS-directory>F20TST.CTL/TIME:0:5:0
NOTE
For a 2020 processor, use /TIME:0:25:0.
Section 2.2 describes how to test the FORTRAN system with UETP.
The test expects to find all the FORTRAN system components and
the files from the FORTRAN test directory on logical device DSK:.
When the b~st 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::.

2·-3

INSTALLING AND TESTING STANDARD FORTRAN
(9)

Install the FORTRAN software on the system
commands:

area

giving

the

$COPY <RUN-directory>*.HLP HLP:*.*
$DELETE <RUN-directory>*.HLP
$COPY <RUN-directory>*.* SYS:*.*
$COPY <FOROTS-directory>FORPRM.UNV SYS:FORPRM.UNV
LINK Version 6.0 must

~lso

be on SYS:.

(10) See Chapter 4 for DBMS installation instructions.
(11) See Chapter 5 for instructions on using the SORT software.
(12) When the installation is complete, you may want to set up FORTRAN
for Autopatching.
See the TOPS-10/TOPS-20 Autopatch Procedures
Reference Manual, and any FORTRAN specific information provided
with Autopatch documentation files.

2.2

TESTING STANDARD FORTRAN

Perform the following procedures to test the FORTRAN system with UETP:
(1)

Install the FORTRAN UETP test modules by giving the commands:
$COPY <TESTS-directory>*.* PS:<UETP.LIB>*.*

(2)

To run UETP, you must have OPERATOR privileges, IPCF
and you must be in USER group 100.

privileges,

(3)

Once the FORTRAN and LINK Version 6.0 system components have been
installed in SYS:
(see Step 9 in Section 2.1), you may run the
UETP test module provided, by giving the following commands:
$TAKE PS:<UETP.LIB>SET-UP.CMD
$CONNECT PS:<UETP.RUN>
$DELETE FORTRA.LOG,RUN.LOG,EXCEPT.LOG
$RUN UETP
UETP>ENABLE FORTRA/DEPTH:VERIFICATION
[13:48:01 ENABLE COMPLETED]
UETP>BEGIN
[13:48:08 BEGIN COMPLETED]
UETP>
START FORTRA 13:49:25
UETP>STATUS
!PERIODICALLY GIVE STATUS
lCOMMAND FOR STATUS OF JOB
END
FORTRA 13:55:13
[All test complete on processor I 2102]
UETP>EXIT
$DEFINE DSK:
$TAKE PS:<UETP.LIB>CLEAN-UP.CMD
NOTE
For a 2020 processor, add a /TIME:25
ENABLE
command,
such
as,
FORTRA/DEPTH:VERIFICATION/TIME:25.

2-4

the UETP
UETP>ENABLE

INSTALLING Am) TESTING STANDARD FORTRAN
If any errors occur, UETP will report them at your terminal and
in the file EXCEPT. LOG.
For more information on UETP see the
UETP Procedures/Referenee Manual in the TOPS-20 Notebook set.
(4)

Run your own tests if desired.
If you run your own
sure that SYS: is defined to include <RUN-directory>.

2.3

CLEAN UP

Perform the following step
installation:
(1)

1:0

clean-up

your

disk

area

tests,

after

the

Decide if you want to destroy the directories you created in Step
4 in Section 2.1.
FOl: 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-dil:ectory-to-destroy>
$$KILL
[CONFIRM] <RET>
!TO CONFIRM
$$<RET>
!TO EXIT BUILD

2-5

CHAP1~ER

BUILDING 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 COttPILER FROM SOURCES

Required software:
BLISIO
LINK
MACRO

7.5(227)
6.0
~i3 .1

NOTE
All files to build the compiler are
FORTRAN-COMPILER and FORTRAN-TOOLS.

the

savesets

Running the control file B20FTN.C'1~L builds the compile:r from its
sources and produces the binary files.
Edit B20FTN.CTL and B20FTN.CMD
to reflect specifics at your installation.
The file B20FTN.CTL does a Tl~KE of B20FTN.CMD, which defines SYS: and
DSK:.
Note that SYS: includes an area (FORTRAN.SSP) that 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 at DIGITAL
uses
field-image software from SYS:. BLISIO.EXE 7.5(227) is included in
the FORTRAN-TOOLS saveset on the distribution tape.
Building the FORTRAN compile]~ from the sources provided is not
trivial computational task,
It requires a considerable amount
computer resources.
The complete E!xecution of B20FTN.CTL requires
least 1 hour on a 2060 processor.
It takes about five times longer
a 2020 processor.
It is adv:.sed that only installations desiring
modify the compiler consider completely rebuilding it.

3--1

a
of
at
on
to

BUILDING NONSTANDARD FORTRAN
To submit the control file to build a compiler on
use the following command:

2060

processor,

Symbols are loaded into FORTRA.EXE so that DDT can be
FORTRAN compiler without any modifications.

used

with

$SUBMIT B20FTN.CTL/RESTART/TIME:l:0:0
NOTE
On a 2020 processor, use /TIME:5:0:0.

3.1.1

3.2

Debugging the FORTRAN Compiler with DDT
the

BUILDING FOROTS AND FORLIB FROM SOURCES

This section describes the procedures for building FOROI0.EXE and
FORLIB.REL from sources if modifications to the standard FOROTS and
FORLIB are desired.
Required software:
FORTRAN
GALAXY
LINK
MACRO
MAKLIB

10
4.2
6.0
53.1
2.2
NOTE

All the files to build FOROTS and FORLIB from sources
are
in
the
savesets
FORTRAN-OTS-DEBUGGER
and
FORTRAN-TOOLS.
The control file B20FRS.CTL can be used to build FOROTS and FORLIB
from the sources.
The build process uses field-image software from
SYS:.
Edit B20FRS.CTL and B20FRS.CMD to reflect
specifics
at
your
installation.
B20FRS.CTL does a TAKE of B20FRS.CMD, which defines
SYS: and DSK.
To run the control file use the following command:
$SUBMIT B20FRS.CTL/RESTART/TIME:0:30:0
If the FOROTS you are building contains patches or is otherwise
different from the standard FOROTS, you may encounter a problem when
FOROTS is rebuilt using this updated LINK command file.
The likely
problems and their recovery procedures are:
1.

PSECT overlap - You must move .CODE. down; LINK will
the information you need in the error message.

Not enough room for symbols after .CODE. - You must move down
.CODE. origin.

3-2

provide

BUILDING NONSTANDARD FORTRAN
3.3

PATCHING FOROTS WITH DDT

FOROlO.EXE normally contains symbols, but in order to use them the
following procedure must be followed (underlined text indicates user
input):
@GET FOROlO
ITo find out starting and ending page number
@I MEM
FOROlO.EXE
1-46
R, CW, E
520-574
@DDT
DDT
115/
75/

1
520

(Starting page numbe:r from the I MEM command)

At this point, DDT knows about the FOROTS local symbols, so they can
be used in applying patches. After you have installed a patch, type
Control-Z to DDT, then type:
@SAVE FOROlO (PAGES FROM) 400 (TO)

3.4

~OO

BUILDING FORDDT FROM SOURCES

This section describes the procedures for building FORDDT from sources
if modifications to the standard FORDDT are desired.
Required software:
MACRO 53.1
No'rE

All the files to build FORDDT from sources are in
savesets FORTRAN-OTS-DEBUGGER and FORTRAN-TOOLS.

the

The control file B20FDT.CTL C3n be used to build FORDDT from
The build process uses field-image software from SYS:.
Edit B20FDT.CTL to reflect specifics at your installation.
To run the control file use the following command:
$SUBMIT B20FDT.CTL/RESTART/TIME:O:5:0
No'rE

On a 2020 processor, use /TIME:0:25:0

3-3

sources.

BUILDING NONSTANDARD FORTRAN
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 that 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 that 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, COMMAN.MAC, 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
set of source line changes.
The component revision histories and edit number definitions are found
in REVHST.MAC for
the compiler, FORHST.MAC for the library and OTS,
and FORDDT.MAC for the debugger.
In addition,
the compiler source
files all have a
local 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:

1**; [nnnn] Where field 1, Where field 2, XXX, Date - for BLISIO 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 numbel~
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:
(Decimal)

(Decimal) 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
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.

3-4

BUILDING NONSTANDARD FORTRAN
The BLISIO line numbers refelenced are those produced by compiling the
distributed version of the module, using the distributed REQUIRE files
(if any are required).
Distlibuted 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 behir,d containing the edit number that removed
the code.
This line MUST reu~ain in the sources (just as banner lines
must NOT appear).
Failure to adhere to these rules can 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
the edit number (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

Tl,3

; [1234] Get error count

For BLISIO changes, this text will generally
margin of the source module, such as:
%1234%

appear

down

!Get error count

but may also appear as the first item in the comment field.

3-5

the

left

CHAPTER 4
BUILDING DBMS VERSION 6.1 WITH FORTRAN-20

To install the DBMS Version 6.1 software with FORTRAN-20
following steps:

perform

the

(1)

Make sure you have the files from the FORTRAN-OTS-DEBUGGER
saveset
on
the
FORTRAN
distribution
tape
in
your
<FOROTS-directory> (see Section 2.1).

(2)

Make sure you have the following files from the DBMS-SOURCES
saveset
on
the
DBMS
Velrsion
6.1 distribution tape in
<FOROTS-directory>:
DBS20.REL
DBSANY.REL
DBSFG.REL
SCHI02.REL
Restore the DBMS-SOURCES

savesE~t

using the following commands:

$DUMPEH
DUMPER>TAPE MTAn:
DUMPER>REWIND
DUMPER>DENSITY 1600
DUMPER>SKIP 2
DUMPER>RESTORE PS:<SOURCES>*.*
DUMPER>REWIND
DUMPER>EXIT
(3)

(TO) <FOROTS-directory>*.*

Connect to <FOROTS-directory>
$CONNECT <FOROTS-directroy>

(4)

The file FDBM6.CTL assumes that you have the following
SYS:
The files from the
distribution tape
LINK-20 V6.0
MAKLIB

(5)

Submit the control file

~ORTRAN-SYSTEM

~DBM6.CTL

$DELETE FDBM6.LOG
$SUBMIT FDBM6.CTL

4-1

files

saveset on the FORTRAN

with the following commands:

BUILDING DBMS VERSION 6.1 WITH FORTRAN-20
NOTE
For a 2020 processor, use /TIME:0:2S:0
The following is typed on the operator console if
successful:
"PLEASE

(6)

build

typed

the

DBMS-20 CREATION SUCCESSFUL!!!"

If the build is not successful, the following
operator console:
"PLEASE

the

DBMS-20 CREATION NOT SUCCESSFUL???"

If the build is not successful, examine FDBM6.LOG for
of error.

the

cause

This control file builds DBMSF.REL
files on the system area.

Put

these

and

DBMSF.EXE.

SCOPY (FOROTS-directory)DBMSF.* (TO) SYS:DBMSF.*

4.1

DEBUGGING FORTRAN-DBMS USING DDT

If you wish to debug a FORTRAN program that uses DBMS, and you want to
use DBMS labels, you must change the contents of .JBHSO to 700. This
points DDT to the symbol table for DBMS. At this point, however, DDT
no longer knows where the symbol table for FOROTS is. To regain
access to FOROTS symbols, you should change the contents of .JBHSO
back to its original value.

4-2

CHAPTER 5
USING SORT VERSION 5 WITH FORTRAN-20

To use SORT Version 5 with FORTRAN-20, the file SORT.EXE from the SORT
distribution tape must be on SYS:. The necessary interface routine is
built into FORLIB.REL.

5-1

TOPS-20
FORTRAN Installation Guide
AA-P344B-TM
READE R'S COMMENTS

NOTE:

This form is for document comments only. DIGITAL will use comments submitted on
this form at the company's discrotion. If you require a written reply and are eligible to
receive one under Software Pel10rmance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well-organized? Please make suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of reader that you most nearly represent.

D Assembly language programmer
D Higher-level language programmer
D Occasional programmer (experienced)
D User with little programming exp 3rience
'
D Student programmer
D Other (please specify) _______.___________________
Name _________________________________ Date _______________________
Organization

Telephone _ _ _ _ _ _ _ _ __

Street ___________________________________________________________________
City _________________.______________________ State __________ Zip Code _ __
or Country

-m_._~_BDOmNotBTear t-

id
FOa He,re and

Ta~ --- --- --- --- -- - -- - ---

-ffl-ll1------ --~~~:~:;~~---

I
I
I
I
I
I

if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SOFTWARE PUBLICATIONS

- - - --

200 FOREST STREET

MR01-2/L 12

MARLBOROUGH, MA

01752

Do Not Tear - Fold Here and Tape

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - --

I
I
I

I
I
1

1
1

1.5

1....:1

"2
o

-<
u