Digital PDFs

AA-J937E-TK

February 1984

23 pages

Original

0.7MB

Document:	BLISS-36 Compiler Installation Notes Nov84
Order Number:	AA-J937E-TK
Revision:	0
Pages:	23
Original Filename:	AA-J937E-TK_BLISS-36_Compiler_Installation_Notes_Nov84.pdf

OCR Text

BLISS-36 C·ompiler
Installation Notes
Order No. AA-J937E-TK

November 1984
This document describes the process by which a BLlSS-36 compiler is installed on a TOPS-10 or TOPS-20 system. It should be read before the
installation is attempted.

OPERATING SYSTEM AND VERSION:

TOPS-10 V7.01A, TOPS-20
V5.1 (KL), TOPS-20 V4.1 (KS)

SOFTWARE VERSION:

BLlSS-36 V4A(225) implementing
BLISS language V4.1

digital equipment corporation · maynard, massachusetts

First Printing, May
Revised, December
Revised, November
Revised, March
Revised, September
Revised, February
Revised, November

1980
1980
1981
1982
1983
1984
1984

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 be used or copied only 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 Equipment Corporation or its
affiliated companies.

Copyright
1980, 1981, 1982, 1983, 1984
by Digltal Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future
documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-lO
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
lAS
MASSBUS
MICRO/PDP-II
Micro/RSX
PDP
PDT

RSTS
RSX
UNIBUS
VAX
VMS

~D~DDmD

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call 800-258-1710

DIRECT MAIL ORDERS (CANADA)

In New Hampshire, Alaska, and HawaII call 603-884-6660

Digital Equipment of Canada Ltd.
940 Belfast Road
Ottawa, Ontario K1G 4C2
Attn: P&SG Business Manager

In Canada call

613-234-7726 (Ottawa-Hull)
800-267-6146 (all other Canadian)

DIRECT MAIL ORDERS (USA & PUERTO RICO)·
Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
P&SG Business Manager
c/o Digital's local subsidiary or
approved distributor

• Any prepaid order from Puerto Rico must be placed
with the local Digital subsidiary (809-754-7575)

Internal orders should be placed through the Software Distribution Center (SOC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

ZK2728

CONTENTS

Page

CHAPTER 1

INTRODUCTION -- PLEASE READ

CHAPTER 2

INSTALLATION PROCEDURES FOR TOPS-20

2.1
2.2
2.3
2.4
2.5
2.6
2.7
CHAPTER 3
3.1
3.2
3.3
3.4
3.5
3.6
3.7

NORMAL INSTALLATION PROCEDURES • • • •
WHAT TO DO IF SOMETHING GOES WRONG • •
VARIATIONS IN INSTALLATION PROCEDURES
AFTER INSTALLATION • •
• •
. • •
DIRECTORY OF TAPE
INSTALLATION DIRECTORY • •
• •
IMPORTANT FILES
• • • •
• •

••• • •
• • • . •
•
• • • • •
• •
•

•
·
•
•
•
•
•

2-1
2-2
2-3
2-4
2-5
2-6
2-7

INSTALLATION PROCEDURES FOR TOPS-I0
NORMAL INSTALLATION PROCEDURES . • • • . . . .
WHAT TO DO IF SOMETHING GOES WRONG • • . . . .
VARIATIONS IN INSTALLATION PROCEDURES
•
AFTER INSTALLATION • • • • • •
DIRECTORY OF TAPE
• • • • • • • • • • • •
INSTALLATION DIRECTORY • • • • • •
IMPORTANT FILES
• • • •
•

iii

. . 3-1
. . 3-3
• • 3-3
3-4
• • 3-5
• 3-6
• • 3-7

CHAPTER 1
INTRODUCTION -- PLEASE READ

This document is designed to help you install BLISS-36 Version 4.1 on
either a TOPS-IO or TOPS-20 syst~m.
During normal installation, you
will copy the release tape to disk and submit the
installation batch
control file
INS36.CTL,
setting the time limit at 30 minutes.
This
procedure installs BLISS-36 using devices SYS:, BLI:, DOC:, and HLP:.
It is assumed that these devices are available and may be written to,
and that the latest version of LINK (LINK-IO V4A, LINK-20 VS.I
(KL),
LINK-20 V4.1
(KS))
is available on your system area.
Refer to the
installation batch control
file
(INS36.CTL)
and the appropriate
chapter listed
in the table of contents if you have any difficulties
with the
installation or
if you wish to perform a nonstandard
installation.

1-1

CHAPTER 2
INSTALLATION PROCEDURES FOR TOPS-20

2.1

NORMAL INSTALLATION PROCEDURES

This section describes installation procedures that you can use when
performing a normal BLISS-36 installation.
A later section describes
variations you may use.
1.
Log in to an account that allows you write and delete access to
the devices SYS:, BLI:, DOC:, and HLP:.
Connect to a directory that
has at least 2600 free pa~es of working storage.
Installation
is
easier if the directory is empty when you begin.
For this sample
installation, the directory is called <USER-DEFINED-AREA> on device
DSKX.
To connect, type the following at the "@" prompt:
CONNECT DSKX:<USER-DEFINED-AREA>
2.
Transfer the release kit files from the tape to the directory.
The tape has
four
save sets.
The first
save set contains the
documentation files, and the second save set contains the remaInIng
files needed for
the
installation procedure.
The third and fourth
save sets are duplicate save sets provided
in case the files are
garbled. You must make sure that the proper tape parameters are used.
Type the following:
SET TAPE DENSITY 1600
SET TAPE RECORD-LENGTH 512
3.

Mount the tape by typing the following:
MOUNT TAPE BLSTP:

/LABEL:UNLABELED/READ-ONLY

Run DUMPER to transfer the contents of the tape to the disk area:
@DUMPER
DUMPER>TAPE BLSTP:
DUMPER>SUPERSEDE ALWAYS
DUMPER>REWIND
DUMPER>ACCOUNT SYSTEM-DEFAULT
DUMPER>FILES
DUMPER>RESTORE PS:<*>*.*.* DSKX:<USER-DEFINED-AREA>*.*.-l
DUMPER>RESTORE PS:<*>*.*.* DSKX:<USER-DEFINED-AREA>*.*.-l

"DUMPER>" is the DUMPER program's prompt.
You should substitute your
own device and directory in the RESTORE command.
This should cause
the files to be transferred from the tape to the specified area.
Each
file name will be displayed on your terminal as it is transferred.
Do not type anything while the files are being transferred.
following once you receive the DUMPER> prompt:
EXIT

2-1

Type

the

INSTALLATION PROCEDURES FOR TOPS-20
This will return you to the "@" prompt~
It is recommended that you
keep your tape mounted until the BLISS system is completely installed.
If you need the drive, however,
dismount the
tape by typing the
following at the "@" prompt:
DISMOUNT BLSTP:
5.
Now you are ready to install BLISS-36.
A BATCH command file
has
been provided to do the work for you.
If the account you are logged
in to requires that capabilities be enabled before it can write-access
the areas on which the BLISS-36 system will be installed, add an
"ENABLE" command to the BLISS.CMD"file. Run the
installation batch
control
file on a
KL processor by typing the following at the "@"
prompt:
SUBMIT INS36.CTL/TIME:OO:30:00
To run the installation batch control file on a KS processor, type:
SUBMIT INSKS.CTL/TIME:02:30:00
You should receive another prompt almost immediately.
Wait for the batch job to complete.
still running by typing:

You can check to

see

INFORMATION BATCH
On most systems this can be abbreviated to:

I B
When INS36 no longer appears in the batch queue listing, examine
the
resulting log
file.
The file will be called "INS36.LOG." On most
systems the above SUBMIT causes the log file to spool automatically to
the line printer.
Look first at the last few lines of the log file.
If a message such
as
the
following
appears,
something has gone wrong with the
installation procedure:

**********************************************************************

INSTALLATION OF BLISS-36 FAILED
*
*
*
*
**********************************************************************
Read Section 2.2 to find out why the installation failed and how to
correct the problem.
If the installation is successful, you will see
the message:

**********************************************************************

*
*
*

SUCCESSFUL INSTALLATION OF BLISS-36

*
*

**********************************************************************

If the installation is successful, skip to Section 2.4 entitled "After
Installation."

2.2

WHAT TO DO IF SOMETHING GOES WRONG

If you closely follow the procedur~s in this document, you should
encounter any serious installation problems.
2-2

not

INSTALLATION PROCEDURES FOR TOPS-20
If you run out of space during
installation, we suggest that you
delete
and
expunge any previous versions of the files being
transferred.
If files on the tape are garbled, duplicate save sets are provided on
the tape.
To get to them, follow the directions for mounting and
initializing DUMPER.
On the line
following
DUMPER)FILES, however,
type:
SKIP 2
This will move you to the start of the duplicate save sets.
Now use
the RESTORE command to dump either the entire set of files or
individual files that were garbled on the first save set.
If the INS36 batch job failed to complete, search the listing
until
you find
the last statement that was executed.
This last statement
will be followed by an error message, which starts with a
question
mark.
Comments have been
inserted in the file to provide you with
some idea of what went wrong.
If you need further help, contact your
system manager.
There are three types of corrective action you can take if
batch job failed to complete:

the

INS36

You can replace a file, possibly from the duplicate save sets
as previously described.

You can modify INS36.CTL.
assist you.

You can modify the
release
should not be done since
problems than you solve.

Comments

have

been

provided

files,
though generally this
you are likely to create more

You should delete the previous copy of INS36.LOG before running
the
batch job again.
If you do not, the files will be concatenated by the
batch spooler.
Some installations include a /BATCH-LOG:SUPERSEDE
switch on a
SUBMIT that causes the previous log file, if any, to be
superseded rather than concatenated.
If such a switch is available,
you should use it.

2.3

VARIATIONS IN INSTALLATION PROCEDURES

No one installation procedure can accommodate all
systems.
You can
tailor the procedure to your system by editing INS36.CTL and reading
the comments in that file.
The most common variation in this procedure is installing BLISS-36 on
a nonstandard device. With many systems, you must first install new
software in a temporary area until all concerned are satisfied with
its reliability.
Because we
try very hard to guarantee that every
release is as reliable as any previous release, you are encouraged to
install BLISS~36 directly on SYS:.
However, if you still wish to
install BLISS-36 in a temporary area, read on.
There are three ways you can redirect the
installation procedure to
The
another device.
The simplest way is to use the file BLISS.CMD.
INS36.CTL will look for BLISS.CMD and execute the commands from this

2-3

INSTALLATION

PROCEDUh~S

FOR TOPS-20

file.
You can add to this file some ~lternate definitions f~r devices
SYS:, BLI:, DOC:, and HLP:.
For example, the following will cause any
files written to device SYS:
to go to device NEW:; an attempt to read
a file from SYS:
will find the file on SYS:
if it is not on NEW::
DEFINE SYS:

NEW:,SYS:

Another way to redirect the installation procedure is to change the
definitions appearing in INS36.CTL.
These definitions allow you more
control over what goes where.
Comments appearing with the device
definitions explain what each logical device name means.
The third method to redirect the in~tallation procedure is to find the
place in INS36.CTL where the files in question are transferred and
modify that line appropriately.
This allows you the most control over
the redirection but requires the most work.
A ~ink-time constant has been added to enable the compiler to generate
indirect-through-memory instructions.
This capability is disabled by
default.
To change the default, modify BLISS.LNK where it defines the link-time
constant INDIR.
The link commands have the following meaning:
/DEFINE:INDIR:O - No indirect-through-memory instructions
/DEFINE:INDIR:l - Indirect-through-memory instructions

2.4

AFTER INSTALLATION

A few cleanup tasks remain once installation is complete.
Most importantly, place a note in the system login messages to
inform
users that BLISS-36 has been installed.
Because the procedures for
doing this vary widely from system to system, the note is not included
in the
installation batch file.
Th~file "BLISS.NTC," supplied with
the kit, contains a typical message wTIich you can modify.
It is recommended that the installation area, to which you dumped
the
tape, be kept intact.
This will make updates and modifications much
easier.
If, however, disk space is at a premium on your system, you
can delete these files in either of two ways:
1.
If the area was empty when you started, type the following at the
"@" prompt:
DELETE *.*,
@EXPUNGE
2.
If there were files that you wish to keep on the disk, typing the
following will delete most of the files:
SUBMIT DEL36.CTL/TIME:OO:30:00
When this is done, you may type the following to delete
the files:
DELETE DEL36.*,
@EXPUNGE

2-4

the

rest

INSTALLATION PROCEDURES FOR TOPS-20
2.5

DIRECTORY OF TAPE

The following is a list of the files included on the first save set of
the installation tape:

BCREF.HLP
BLISS.BWR
BLISS.DOC
BLISS.HLP
BLISS. INS
CVTIO.DOC
CVTIO.HLP
DEL36.CTL
DMPREL.HLP
INS36.CTL
INSKS.CTL
MONINT.DOC
SIXI2.HLP
SIXI2.MEM
TUTIO.HLP
The following is a list of the files included on the second
of the installation tape:

B36IAB.REL
B36IAT.REL
B36ILB.REL
B36ILT.REL
B362LB.REL
B362PB.REL
BCREF.EXE
BLISS.CMD
BLISS. LNK
BLISS.NTC
BLISS.REL
BLSOTS.MAC
CHKC2L.B36
CHKEXT.B36
CHKMKL. EXE
CHKMT2.EXE
CVTIO.EXE
CVTIO.SNO
DEB36.LNK
DEB36.REL
DMPREL.EXE
ERROR.BNR
EZIOIO.B36
EZIOIO.REL
EZI020.B36
EZI020.REL
FLDDB.R36
LSTCHK.BLI
MONINT.EXE
MONSYM.L36
MONSYM.R36
NORMAL.BNR
PSI20.B36
REGIAB.MAC
REGIAT.MAC
REGILB.MAC
REGILT.MAC
REG2LB.MAC
REG2PB.MAC
SIXI2.B36
TENDEF.L36
TENDEF.R36
2-5

save

set

INSTALLATION PROCEDURES FOR TOPS-20
TUTIO.R36
UUOSYM.L36
UUOSYM.R36
XDUMP.REL
XPORT.L36
XPORT.REQ
XPOTlO.DBG
XPOTlO.REL
XPOT20.DBG
XPOT20.REL

2.6

INSTALLATION DIRECTORY

The following is a list of the files that this installation procedure
actually installs.
The device name given is the default device to
which the file is transferred. The files that go to device NUL:
are
not installed by default.
SYS:B36lAB.REL
SYS:B36lAT.REL
SYS:B36lLB.REL
SYS:B36lLT.REL
SYS:B362LB.REL
SYS:B362PB.REL
SYS:BCREF.EXE
HLP:BCREF.HLP
DOC:BLISS.BWR
DOC:BLISS.DOC
SYS:BLISS.EXE
HLP:BLISS.HLP
NUL:BLISS.REL
BLI:BLSOTS.MAC
DOC:CVTlO.DOC
SYS:CVTlO.EXE
HLP:CVTlO"HLP
BLI:CVTlO.SNO
SYS:DEB36"EXE
NUL:DEB36.REL
SYS:DMPREL.EXE
HLP:DMPREL.HLP
BLI:EZIOlO.B36
BLI:EZIOlO.REL
BLI:EZI020.B36
BLI:EZI020.REL
BLI:FLDDB.R36
DOC:MONINT.DOC
SYS:MONINT.EXE
BLI:MONSYM.L36
BLI:MONSYM.R36
BLI:REGlAB.MAC
BLI:REGlAT.MAC
BLI:REGlLB.MAC
BLI:REGlLT.MAC
BLI:REG2LB.MAC
BLI:REG2PB.MAC
BLI:SIX12.B36
HLP:SIX12.HLP
DOC:SIX12.MEM
BLI:TENDEF.L36
BLI:TENDEF.R36
HLP:TUTIO.HLP
BLI:TUTIO.R36
BLI:UUOSYM.L36
BLI:UUOSYM.R36
2-6

INSTALLATION PROCEDURES FOR TOPS-20
SYS: XDUMP. EXE
BLI:XDUMP.REL
BLI:XPORT.DBG
BLI:XPORT.L36
BLI:XPORT.REL
BLI:XPORT.REQ
BLI:XPOTIO.DBG
BLI:XPOTIO.REL
BLI:XPOT20.DBG
BLI:XPOT20.REL

2.7

IMPORTANT FILES

The following are important files in the installation kit that you
should be familiar with.
These files may be in one or both of the two
previous directories.
•

B36*.REL -- various versions of the BLISS run-time system

•

BCREF.EXE

the BLISS cross-reference postprocessor

•

BCREF.HLP

a help file for using BCREF.EXE

•

BLISS.BWR

the restriction section from BLISS. DOC

•

BLISS.DOC
a brief description of BLISS-36
and potential users of BLISS

•

BLISS.EXE

the BLISS-36 compiler itself

•

BLISS.HLP

a help file on how to run BLISS

•

BLISS.NTC
a sample login
BLISS-36 has been installed

•

DEL36.CTL -- a file that cleans out the installation area

•

INS36.CTL -- a file that installs the BLISS-36 system from the
installation area

•

INSKS.CTL

version of INS36.CTL for use on a KS processor

•

BLISS. INS

this document

•

XPOTlO.DBG -- special TOPS-IO XPORT debug object file for
with the SIXl2 debugger

•

XPOTlO.REL

•

XPOT20.DBG
special TOPS-20 XPORT debug object file for
with the SIX12 debugger

•

XPOT20.REL -- standard TOPS-20 XPORT object file

message

V4.1

for

users

informing

users

that

use

standard TOPS-IO XPORT object file

2-7

use

CHAPTER 3
INSTALLATION PROCEDURES FOR TOPS-IO

3.1

NORMAL INSTALLATION PROCEDURES

This section describes installation procedures that you can use
in
performing a normal BLISS-36 installation. A later section describes
variations you may use.
1.
Log in to an account that allows you write and delete access to
the devices SYS:, BLI:, DOC:, and HLP:.
Connect to a directory that
has at least 8000 blocks of free storage.
Installation is easier
if
the directory is empty when you begin.
2.
Transfer the release kit files from the tape to the directory.
The tape has
four save sets.
The first
save set contains the
documentation files, and the second save set contains the remaining
files needed
for
the installation procedure.
The third and fourth
save sets are duplicate save sets provided in case the files are
garbled.
3.
Mount the tape. There may be some variation between systems
the following applies to most systems. At the "." prompt, type:
MOUNT MTA:

BTP:

but

/RONLY /REELID:BLISS

Set the tape parameters:
SET BLOCKSIZE BTP:

512

Check the label printed on the tape and depending on which density
specifies, type either:
SET DENSITY BTP:

800

SET DENSITY BTP:

1600

Now run BACKUP:
.R BACKUP
/TAPE BTP:
/REWIND
/INTERCHANGE
/SUPERSEDE ALWAYS
/FILES
/RESTORE DSK:*.*[-]
/RESTORE DSK:*.*[-]

ALL:*.*[*,*]
ALL:*.*[*,*]

3-1

INSTALLATION PROCEDURES FOR TOPS-IO
The "I"
is a
prompt supplied by BACKUP.
The files should be
transferred
from the tape to the specified area.
Each file name will
be displayed on your terminal as it is transferred.
Do not type anything while the files are being transferred.
receive a prompt, type:

Once

you

IREWIND
ICHECK DSK:*.*[-]
ICHECK DSK:*.*[-]
The program will check each file on the disk against the file on the
tape.
As each file
is checked, its name will be displayed on your
terminal. An error message will be displayed if the files are not
identical.
Wait for this process to complete, then type the following at the
prompt:

"I"

EXIT
This should return you to the monitor.
It is recommended that you keep your tape mounted until BLISS-36
is
completely installed.
However,
if you need the drive, dismount the
tape by typing the following at the" " prompt:
DISMOUNT BTP:
5.
Now you are ready to install BLISS-36. A BATCH command file
has
been provided to do the work for you.
On some (nonstandard) systems,
accounting information must be included at the beginning of BATCH
files.
If this is the case on your system, edit that information into
INS36.CTL. To run the
installation batch control
file,
type the
following at the "." prompt:
SUBMIT INS36.CTL/TIME:OO:lO:OO
You will receive another prompt from the monitor almost immediately.
Wait for the batch job to complete. You can check to see
still running by typing the following at the" " prompt:

SUBMIT
When INS36 no longer appears in the batch queue listing, examine the
resulting log
file.
The file will be called "INS36.LOG." On most
systems the previously mentioned SUBMIT command will cause the
log
file to spool automatically to the line printer.
Look first at the last few lines of the log file.
If the following
message appears,
something has gone wrong with the installation
procedure:
**********************************************************************

*
*
*
**********************************************************************

*
*

INSTALLATION OF BLISS-36 FAILED

3-2

INSTALLATION PROCEDURES FOR TOPS-IO
Read Section 3.2 to find out why the installation failed and how to
correct the problem.
If the fnstallation is successful, you will see
the message:

**********************************************************************

*
*
*

SUCCESSFUL INSTALLATION OF BLISS-36

*
*

**********************************************************************

If the installation is successful, skip to Section 3.4 entitled "After
Installation."

3.2

WHAT TO DO IF SOMETHING GOES WRONG

If you closely follow the procedures in this document, you should
encounter any serious installation problems.

not

If you run out of space at any point, we suggest that you
previous versions of the files being transferred.

any

delete

If files on the tape are garbled, duplicate save sets are provided on
the
tape.
To get to them, follow the directions in Section 3.1 for
mounting and initializing BACKUP.
Following the line /FILES, however,
type the following at the "/" prompt:
SKIP 2
This will move you to the start of the duplicate save sets.
Now use
the RESTORE command to dump either the entire set of files or
individual files that were garbled on the first save set.
If the INS36 batch job failed to complete, search the listing
until
you find
the last statement that executed.
This last statement will
be followed by an error message, which starts with a question mark.
Comments have been inserted in the file to provide you with some idea
of what went wrong.
If you need further help,
contact your
system
manager.
There are three types of corrective action you can take if
batch job failed to complete:
.

the

INS36

You can replace a file, possibly from the duplicate save sets
previously described.

You can modify INS36.CTL.
assist you.

You can modify the
release
should not be done
since
problems than you solve.

Comments

have

been

provided

files,
though generally this
you are likely to create more

You should delete the previous copy of INS36.LOG before running
the
batch job again.
If you do not, the files will be concatenated by the
batch spooler.

3.3

VARIATIONS IN INSTALLATION PROCEDURES

No one installation procedure can accommodate all
systems.
You can
tailor the procedure to your system by editing INS36.CTL and reading
the comments in that file.

3-3

INSTALLATION ,PROCEDURES FOR TOPS-IO
The most common variation in this procedure is installing BLISS-36 on
a nonstandard device. With many systems, you must first install new
software in a temporary area until all concerned are satisfied with
its reliability.
Because we
try very hard to guarantee that every
release is as reliable as any previous release, you are encouraged
to
install BLISS-36 directly on SYS:.
However, if you still wish to
install BLISS-36 in a tempora~y area, read on.
There are three ways you can redirect the
installation procedure to
another device.
One way is to change the definitions in INS36.CTL.
Comments appearing with theaevice definitions explain what each
logical device name means.
A second way involves finding the place in INS36.CTL where the file(s)
in question are transferred and modifying that line as desired.
This
procedure allows a finer control but requires considerably more work.
A link-time constant has been added that enables the compiler to
generate
indirect-through-memory instructions.
The default disables
this capability.
To change the default, modify
link-time constant INDIR.
The
meaning:

SEGCMN.LNK where
it defines
the
link commands have the following

/DEFINE:INDIR:O - No indirect-through-memory instructions
/DEFINE:INDIR:I - Indirect-through-memory instructions
A link-time constant has been added to specify the default processor
model of the
target system for which code is to be generated.
The
default is currently set to KLIO/KSIO.
To change the default, modify SEGCMN.LNK where
it defines the
link-time constant CPUTYP.
The link commands have the following
meaning:
/DEFINE:CPUTYP:O - Target sysiem is a KAIO
/DEFINE:CPUTYP:I - Target system is a KIlO
/DEFINE:CPUTYP:2 - Target system is a KLIO or KSIO

3.4

AFTER INSTALLATION

A few cleanup tasks remain once installation is complete.
Most importantly, place a note in the system login messages notifying
users that BLISS-36 has been installed. Because the procedures for
doing this vary widely from system to system, the note is not included
in the
installation batch file.
The file "BLISS.NTC," supplied with
the kit, contains a typical message which you can modify.
It is recommended that the installation area, to which you dumped
the
tape, be kept
intact.
This will make updates and modifications
easier.
If, however, disk space is at a premium on your system, you
can delete these files in either of two ways:
1.

If the area was empty when you started, type the following at the

" " prompt:
DELETE

*.*

2.
If there were files that you wish to keep on the area, typing the
following at the "." prompt will delete most of the files:
SUBMIT DEL36.CTL/TIME:OO:IO:OO
3-4

INSTALLATION PROCEDURES FOR TOPS-IO
When this is done, you may type the following to delete the
rest of the files:

rest

the

.DELETE DEL36.*

3.5

DIRECTORY OF TAPE

The following is a list of the files included on the first save set of
the installation tape:
BCREF.HLP
BLISS.BWR
BLISS.DOC
BLISS.HLP
BLISS. INS
CVTIO.DOC
CVTIO.HLP
DEL36.CTL
DMPREL.HLP
INS36.CTL
MONINT.DOC
SIX12.HLP
SIX12.MEM
TUTIO.HLP
The following is a list of the files included on the second
of the installation tape:
B361AB.REL
B361AT.REL
B36ILB.REL
B361LT.REL
BCREF.EXE
BLISS.NTC
BLISS.REL
BLSOTS.MAC
CVTIO.EXE
CVTl O. SNO
DEB36. LNK
DEB36.REL
DMPREL.EXE
ERROR.BNR
EZIOIO.B36
EZIOIO.REL
LSTCHK.BLI
MONINT. EXE
NORMAL.BNR
REGIAB.MAC
REGIAT.MAC
REGILB.MAC
REGILT.MAC
SEGl.LNK
SEG2. LNK
SEG 3. LNK
SEG4. LNK
SEG5. LNK
SEGCMN.LNK
SIX12.B36
TENDEF.L36
TENDEF.R36
TUTIO.R36
UUOSYM.L36

3-5

save

set

INSTALLATION PROCEDURES FOR TOPS-IO
UUOSYM.R36
XDUMP.REL
XPORT.L36
XPORT.REQ
XPOTIO.DBG
XPOTlO.REL

3.6

INSTALLATION DIRECTORY

The following is a list of the files that this installation procedure
actually installs.
The device name given is the default device to
which the file is transferred. Those files going to device DSK:
are
not installed by default.
SYS:B36lAB.REL
SYS:B36IAT.REL
SYS:B36ILB.REL
SYS:B36ILT.REL
SYS:BCREF.EXE
HLP:BCREF.HLP
DOC:BLISS.BWR
DOC:BLISS.DOC
HLP:BLISS.HLP
DSK:BLISS.REL
SYS:BLISS.EXE
BLI:BLSOTS.MAC
SYS:BLSSG2.EXE
SYS: BLSSG 3. EXE
SYS:BLSSG4.EXE
SYS: BLSSG 5. EXE
DOC:CVTIO.DOC
SYS:CVTlO.EXE
HLP:CVTIO. HLP
BL I : C VT 1 0 • S N0
SYS:DEB36.EXE
DSK:DEB36.REL
SYS:DMPREL.EXE
HLP:DMPREL.HLP
BLI:EZIOlO.B36
BLI:EZIOlO.REL
DOC:MONlNT.DOC
SYS:MONlNT.EXE
BLl:REGIAB.MAC
BLl:REGlAT.MAC
BLl:REGlLB.MAC
BLl:REGlLT.MAC
BLl: SlX12. B36
HLP:SlX12.HLP
DOC:SlX12.MEM
BLl:TENDEF.L36
BLl:TENDEF.R36
HLP:TUTlO.HLP
BLl:TUTlO.R36
BLl:UUOSYM.L36
BLl:UUOSYM.R36
SYS: XDUMP. EXE
BLI:XDUMP.REL
BLl:XPORT.DBG
BLI:XPORT.L36
BLl:XPORT.REL
BLl:XPORT.REQ
BLl:XPOTlO.DBG
BLl:XPOTlO.REL

3-6

INSTALLATION PROCEDURES FOR TOPS-IO
3.7

IMPORTANT FILES

The following are some important files in the
installation kit that
you should be familiar with.
These files may be found in one or both
of the two previous sections.
•

B36*.REL -- various versions of the BLISS run-time system

•

BCREF.EXE

the BLISS cross-reference postprocessor

•

BCREF.HLP

a help file for using BCREF.EXE

•

BLISS.BWR

the restriction section from BLISS. DOC

•

BLISS.DOC
a brief description of BLISS-36
and potential users of BLISS

•

BLISS.HLP

•

BLISS.NTC
a sample login
BLISS-36 has been installed

message

•

BLISS.EXE -- the
BLISS-36
high-segment overlay I

compiler

•

BLSSG2.EXE

the BLISS-36 compiler high-segment overlay 2

•

BLSSG 3. EXE

the BLISS-36 compiler high-segment overlay 3

•

BLSSG4.EXE

the BLISS-36 compiler high-segment overlay 4

•

BLSSG 5. EXE

the BLISS-36 compiler high-segment overlay 5

•

DEL36.CTL

a file that cleans out the installation area

•

INS36.CTL -- a file that installs the BLISS-36 system from the
installation area

•

BLISS. INS -- this document

•

XPOTIO.DBG -- special TOPS-IO XPORT debug object file for
with the SIXl2 debugger

•

XPOTIO.REL -- standard TOPS-IO XPORT object file

V4.1

for

users

that

low-segment

and

a help file on how to run BLISS

3-7

informing

use

BLISS-36 Compiler
Installation Notes
AA-J937E-TK
READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a written reply and are eligible to receive one under Software
Performance 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 firid errors in this manual? If so, specify the error and the page number.

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

[J Assembly language programmer
lJ Higher-level language programmer
o Occasional programmer (experienced)
User with little programming experience
[J Student programmer
[J Other (please specify)

Name _________________________________________________ Date _________________________________
Organization
Street
City _____________________________________________

State _______ Zip Code _______
or Country

Do Not Tear - Fold Here and Tape
No Postage
Necessary
if Mai led in the
United States

1111I1

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

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

Do Not Tear - Fold Here