Trailing-Edge
-
PDP-10 Archives
-
AP-4172F-BM
-
3a-documentation/build.mem
There are 36 other files named build.mem in the archive. Click here to see a list.
+---------------+
! D I G I T A L ! I N T E R O F F I C E M E M O R A N D U M
+---------------+
TO: TOPS20 List A
DATE: August 30, 1978
FROM: TOPS20 S. E. Dept.
DEPT: DEC20 S. E. Dept.
LOC: MR1-2
FILE: [DOC-SPECS]
BUILD.SPC
SUBJ: TOPS20 Monitor Building Procedures and Information
COPYRIGHT (C) 1976,1977,1978 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.
BUILD.MEM Page 2
1.0 INTRODUCTION
This document provides complete information on configuring and
building the TOPS20 monitor. Multiple configurations are provided so
as to minimize the amount of resident storage used while supporting
all of the available peripheral devices. The "build" procedure
produces a core-image file of the monitor from the various relocatable
files and the one parameter-dependent source file.
Generally, an installation will be able to run one of the standard
monitor configurations supplied. Section 2 of this document tells how
to select the appropriate monitor configuration and how to run the
build procedure.
Some installations may wish to use a set of configuration parameters
different from those of the standard set. Section 3 describes the
function of each parameter and its effect on the resultant
configuration.
Section 4 describes how to add installation-specific terminal
definitions.
2.0 BASIC MONITOR SELECTION AND BUILDING PROCEDURES
NOTE: This section is intended for anyone who needs to build a
monitor, and it requires a minimum level of familiarity with the
structure or operation of the system. The knowledge which is required
is:
1. How to login and use basic EXEC commands.
2. How to use the magtape file restore program (DUMPER).
3. How to bring up the system with an existing monitor.
2.1 How to Select a Monitor Configuration
There are seven standard monitor configurations. The first four are
intended for general timesharing and batch operation and differ only
in overall size. The fifth is intended for batch-only operation. The
sixth and seventh are 2020 monitors. An eighth configuration is an
ARPA-only monitor. The configuration names and general descriptions
are:
"Small" A typical small configuration for general
timesharing.
"Medium" A typical medium-size configuration for general
timesharing.
"Batch" A configuration for batch-only operation on a
medium to large non-ARPA hardware configuration.
BUILD.MEM Page 3
"Big" The largest standard monitor supported by Digital.
"2020-small" A typical small configuration for general 2020
timesharing.
"2020-medium" A typical medium-sized configuration for general
2020 timesharing.
"Large" The largest monitor supported by Digital (ARPA
only).
1. If you intend to do batch-only operation and your machine has
at least 128K core, select the "Batch" monitor. If you have
less than 128K core, the "Batch" monitor does not provide any
advantage over the appropriate general purpose monitor. The
"Batch" monitor supports 14 jobs, 12 pseuod-terminals
(PTY's), 8 terminal lines, 256K core memory, 8 magtape units,
and 2 line printers.
2. If you are not using the "Batch" monitor, select one of the
general purpose monitors based on your hardware
configuration. You will want the smallest monitor which
supports all of the hardware you have and which handles the
number of users you wish to allow. All monitors support up
to 8 disk drives.
a. The "Small" Monitor will support the following:
40 Users (interactive and batch)
64 Terminal Lines, 40 active
256K Core memory
8 Magtape units (max)
2 Line Printers (max)
2350 Pages of swapping space
20 Network Virtual Terminals (ARPA only)
b. The "Medium" Monitor will support the following:
60 Users (interactive and batch)
64 Terminal Lines, 60 active
256K Core memory
8 Magtape units (max)
2 Line Printers (max)
3070 Pages of swapping space
30 Network Virtual Terminals (ARPA only)
c. The "Big" Monitor will support the following:
100 Users (interactive and batch)
128 Terminal lines, 100 active
512K Core memory
8 Magtape units (max)
2 Line Printers (max)
5000 Pages of swapping space
40 Network Virtual Terminals (ARPA only)
BUILD.MEM Page 4
d. The "2020-medium" Monitor will support the following:
60 Users (interactive and batch)
32 Terminal Lines, 32 active
256K memory
8 Magtape units (max)
2 Line Printers (max)
3000 Pages of swapping space
e. The "2020-medium" Monitor will support the following:
60 Users (interactive and batch)
32 Terminal Lines, 32 active
512K memory
8 Magtape units (max)
5000 Pages of swapping space
f. The "Large" Monitor will support the following:
100 Users (interactive and batch)
128 Terminal lines, 100 active
1024K Core memory
8 Magtape units (max)
2 Line Printers (max)
5000 Pages of swapping space
40 Network Virtual Terminals
This monitor is only supported on ARPA installations with
the AN20 ARPANET Interface.
It does not matter if the monitor you select supports more of some
devices than you have. The resident core requirements of each are
quite small, and monitors configured between the ones above would not
show significant performance improvement.
2.2 How to Build a Standard Monitor Configuration
At this point, you will have selected one of the standard monitor
configurations described above (or have constructed your own parameter
file as described in Section 3). The following step-by-step procedure
produces a monitor configured according to the parameters in the
corresponding parameter file.
1. Login and connect to a directory containing a complete set of
monitor files. If the monitor files have not been loaded
onto the disk, load them from your distribution tape using
DUMPER (document TOPS20.DOC).
BUILD.MEM Page 5
2. If you are building a standard monitor, copy the appropriate
parameter file to "PARAM0.MAC". If you are building an ARPA
monitor, copy the appropriate parameter file to "PARAN.MAC".
The parameter files for the various monitors are:
Standard Monitor ARPA Monitor
-------- ------- ---- -------
"Small" = PARSML.MAC "Small" = ANPSML.MAC
"Medium" = PARMED.MAC "Medium" = ANPMED.MAC
"Batch" = PARBCH.MAC N/A
"Big" = PARBIG.MAC "Big" = ANPBIG.MAC
N/A N/A
N/A N/A
N/A "Large" = ANPLGE.MAC
For example, if you are building a standard small monitor,
@COPY PARSML.MAC (TO) PARAM0.MAC.1 !new file!
If you are building a medium ARPA monitor,
@COPY ANPMED.MAC (TO) PARAN.MAC.1 !new file!
3. If you are building a standard (OR 2020) monitor, copy the
appropriate name file to "NAMAM0.MAC". If you are building
an ARPA monitor, copy the appropriate name file to
"NAMAN.MAC". The name files for the various monitors are:
2020 MONITOR
---- -------
N/A
N/A
N/A
N/A
N/A
"2020-SMALL" = P20SML.MAC
"2020-MEDIUM" = P20MED.MAC
N/A
Standard Monitor ARPA Monitor
-------- ------- ---- -------
"Small" = NAMSML.MAC "Small" = ANNSML.MAC
"Medium" = NAMMED.MAC "Medium" = ANNMED.MAC
"Batch" = NAMBCH.MAC N/A
"Big" = NAMBIG.MAC "Big" = ANNBIG.MAC
N/A N/A
N/A N/A
N/A "Large" = ANNLGE.MAC
For example, if you are building a standard small monitor,
BUILD.MEM Page 6
@COPY NAMSML.MAC (TO) NAMAM0.MAC.1 !new file!
If you are building a medium ARPA monitor,
@COPY ANNMED.MAC (TO) NAMAN.MAC.0 !new file!
4. Submit the appropriate batch file for the type of monitor you
are build: TOPS20.CTL for a stndard monitor, T20-AN.CTL for
an ARPA monitor, T2020.CTL for 2020.
For example, to build a standard small monitor,
@SUBMIT TOPS20/TAG:SINGLE/TIME:2:0:0
To build a medium ARPA monitor,
@SUBMIT T20-AN/TAG:SINGLE/TIME:2:0:0
This will leave the monitor in your directory. The file name
of the monitor file is MONITR.EXE.
If it is desirable to build all of the standard monitors,
then submit the control file with a TAG:ALL switch, e.g.,
@SUBMIT TOPS20/TAG:ALL/TIME:2:0:0
5. If this monitor is to be loaded from magtape, copy the file
to magtape.
COPY MONITR.EXE (TO) MTA0:
The tape density must be 1600 BPI for MTBOOT to work.
The build procedure is now complete and the new monitor is ready to be
brought up using the normal bootstrap procedures.
3.0 THE MONITOR CONFIGURATION PARAMETERS
NOTE: This section is intended for anyone needing to build a monitor
configuration different from the standard configurations. It requires
some familiarity with the operation of the system and utility
programs, and some knowledge of the structure of the monitor.
Specifically:
1. Everything required in Section 2.
2. How to use the text editor.
3. How to read assembly language.
4. The meaning of common monitor terms, e.g., "jobs", "forks",
"PTY", etc.
BUILD.MEM Page 7
The monitor configuration is determined by a single parameter file
PARAM0.MAC (or PARAN.MAC if building an ARPANET monitor). This file
is the only configuration-dependent file required for a monitor build.
To configure a monitor, you will use the text editor to produce this
parameter file. PARAM0.MAC (or PARAN.MAC) should contain only those
parameters that are different from the standard values listed in
PARAMS.MAC. This section describes the meaning of each parameter and
its effect on the monitor configuration.
You should read each description, determine the proper value for your
configuration, and note this value on a listing of the parameter file.
You can then edit the parameter file to include these values.
Your edited parameter file should be given the name PARAM0.MAC, (or
PARAN.MAC if building an ARAP monitor).
When the new parameter file has been produced, you may follow the
normal monitor build procedure (Section 2).
The Parameter File
--- --------- ----
3.1 NTTPTY
The number of pseudo-terminals. This parameter determines the number
of PTYs available. You will need 1 for PTYCON plus 1 for each PTYCON
subjob being run, plus 1 for each simultaneous batch job being run.
Additional PTYs may be allocated for user use of PTYCON. The resident
storage requirement for a PTY is exactly the same as for a physical
terminal, i.e.,
N = 5*NTTPTY
3.2 NTTNVT
The number of Network Virtual Terminals. These devices are present
only on installations using an ARPA Monitor, with parameter NETN set
to 1. The resident storage requirement for an NVT is exactly the same
as for a physical terminal, i.e.,
N = 5*NTTNVT
3.3 SSPT
The size of the system pages table. This 2-word table holds
information about every open file and every fork. Its minimum
reasonable value is SSPT = 500 + NJOBS + 3*NFKS. It is also used for
holding information about shared file pages if there is sufficient
space. This allows a shared file page to be referenced without its
owning index block also being brought into core. Hence it is probably
most efficient to set SSPT to the value shown above plus the average
BUILD.MEM Page 8
number of shared pages in use in your system. The resident core
requirements are:
N = 2*SSPT
3.4 MAXCOR
The maximum number of physical core pages. This parameter determines
the size of the four core status tables. It should be set to at least
the maximum amount of core on your system (i.e., #K/2). The resident
core requirements for this parameter are:
N = 5*MAXCOR
3.5 NDST
The size of the drum status table. This table has one entry for each
page of swapping storage. The swapping area is used for all active
pages whether shared or private. If the swapping area becomes full,
the monitor will move shared pages back to their home address, but it
cannot move private pages. Hence, this parameter should be set to at
least the maximum number of private pages expected to be in use at one
time. The resident core requirements are:
N = 1*NDST
Note that at least this much swapping space must have been allocated
on the public file structure (PS:).
The next group of parameters refers to the configuration of peripheral
devices. These parameters take a number which is the maximu number of
units of a particular device. Each device has a parameter related to
the device name, i.e., for device "xxx", there is a parameter "xxxN".
Other symbols in the monitor are constructed by concatenating the
device name with a specific prefix or posfix.
3.6 FEN
Front End Device service. This parameter defines the number of FE
devices present. The FE devices are psuedo devices used for general
transfering of data to and from the front-end.
3.7 MTAN
Magtape service. This parameter is the number of magtape units
persent. A maximum of 8