IBM 1130 User Manual page 698

Section
Subsections
Page
90
40
I
30 10
Discussion of Case III
This type program, although quite different from
the previous two cases, is analyzed in much the
same way:
1. The main program is split into three LINKs:
Input, Processing, and Output.
SOCAL's, LOCAL'sarwt/Oil LINK's are
used
Overlays
Used
No <>-lays Continuously, Overlays Used
• SOCAL's Limited to But Not in in between
• LOCAL's SeIdcJm..UsKt between Disk DiskR-uwrite
• LINK's Blocks StatemenIs Statemen1s
No
Disk
Program
Program will
Data will run
at run at less
Files some
basic
....... Top
"Top~n. ~",but
probably
not
enough to be
noticed.
Smalto
Program Program will Program will Program will
Medium-
will run at
run at less
run
noticeably
run
slowly;
Size
some
basic
....... 'Top beIcwv"Top
many ann
FilesN..- "Top~'. ~',but ~',but
IIIINa'IIeIIIS
of
WS
(lddle probably not
not too
much,
short distance
End of
enough
to be since overlay . will be needed.
WSI noticed. _isnottoo
flIr-..,from
datafile_.
Very
Program Program will Program will The combination
I..-ge
will run at
run Id less run slowly, of many ann
Disk some basic
than "Top
since
overlay rnovsnent:s. and
Data "Top~'. ~",but _ispro-
long dislances.
Files,
probably not
portionately will cause this
011
Small enough to be funher-..,
type
program
Files
Deep noticed. from data 1D run
con-
insideUA
file_.
siderabIy beIcwv
"Top~'.
Worst case!
Figure 90. 11.
2. Since all subprograms are called during each
pass, we try to LOCALize only those that do not
appear inside the main disk READ/WRITE loop.
3. With excessive overlays still required, we
~ttack the main program and try to shorten it or
eliminate some of the subroutines it uses.
Case 1
Temporary
files.
residing in WS,
are close to
overlay area
Case 2
File is in UA,
but still close
10 overIay_
Case
3
File is in UA,
but far
removed
from overlay
-
Figure 90. 12.
Average
ann
movement
distance