Table of Contents
Advertisement
3. SOFTWARE CONFIGURATION GUIDELINES
INTRODUCTION
This chapter is intended as an aid to the system manager in
defining the system generation parameters that are required
to create an RBM system optimized for itsspecifi c applica-
tion environment. The two primary aspects of "tailorable"
system resources are main memory and secondary (disk)
storage.
MAIN MEMORY ALLOCATION
Moin memory is al located in the fol lowing manner (and as
illustrated in Figure 4):
1.
The fi rst 256 words in lower memory (the zero table)
are reserved for constants and pointers.
2.
The region from 256 to 399 (decimal) is reserved for
internal and external interrupt levels; any space not
required for interrupt levels wi
II
be used by the Moni-
tor for tab Ie space.
3.
The remainder of memory is allocated as follows=
a.
Resident RBM, to be loaded beginning at location
400 (decimal) and to include only those opti onal
routines selected by SYSGEN.
b.
Public Library (if allocated).
c.
Resident foreground (if allocated).
d.
Nonresident foreground (if allocated).
e.
Background.
At least 256 words must be allo-
cated whether or not batch is required; minimum
useful amount allocated should be the length of
the Job Control Processor (6000 words decimal)
(see Figure 5).
4.
No foreground space need be a I located for a batch-
on I y system.
The user should decide which of the areas described under
item 3, above, are more apt to need additional space in
future and make allocations accordingly. A given area
could then be expanded downward in a future SYSGEN,
into unused area space below it, and only the programs in
the reallocated area would have to be reloaded, not the
entire system.
(In Figure 4, for example, the resident
foreground might expand into the unused Public Library
area. )
RESIDENT RBM MODULES
RBM consists of both resident and nonresident modules.
Resident modules consist of functions that are frequently
10
Software Configuration Guidelines
used or which must quickly react to internal or external
events.
Nonresident modules consist of functions that are
infrequently used or for which immediate response is not
necessary.
Resident modu fes consume memory space as
the price for rapid response to internal/external events.
Nonresident modules consume response time as the pri ce for
memory space ava; lability.
Since the user has the option to select whether certain
modules are to be resident or nonresident, this chapter is
intended to provide the information necessary to make
tradeoff deci sions between memory space and response time
when either resource is critical to system performance.
NONOPTIONAL RESIDENT MODULES
The following RBM functions are unconditionally inc luded
as resident in memory.
All sizes are approximate unless
otherwise specified .
Size (decimal)
Function
Constants, pointers, transfer
vectors, interrupts, etc.
Fixed tables and nonresident-
over lay area.
Min.
275
575
(See "Resident
Max.
400
575
I/()
Vari able tables (i ncl uding
TVECT).
Tables and Routines ")
Integer Multiply;bi vide
Simulation.
I/() Interrupt Task.
PCP Interrupt Task and RBM
Control Task.
Machine Fault Task
Sigma 2
=
50
Sigma 3
=
100
Model 530
=
200
Service Routines
Total Nonoptional
(v represents variable tables)
0
300
150
50
2500
3850+v
OPTIONAL RESIDENT MODULES
175
300
150
200
2600
4440+v
The following RBM functions are included as resident in
memory if selected as an optional feature during SYSGEN.
Selection
Keyword
Function
Size
PR()TECT
Protection Task
75
P()WE R
Power ()n-()ff Tasks
250
E P.R()RSUM
li() Error and Use Count
25+4
*
I/O channe Is
Advertisement
Table of Contents
