IBM 1130 User Manual page 504

SUMMARY
This section has described the seven logical areas
of core storage, with the emphasis on their overall
roles rather than on exact details. As mentioned
earlier, all quoted subroutine sizes are approximate,
and are based on a so-called "typical" commercial-
type program, coded in FORTRAN. You should not
necessarily conclude that these figures will apply to
your "typical" programs; they mayor may not.
The bulk of the material in this chapter concerns
SOCALs, LOCALs, and LINKs--how they work.
Section 90 concerns how they should be used and how
they affect program performance.
Figure 65.4 graphically summarizes what has
been covered in this chapter.
Figure 65. 5 shows a "core map", printed if you
punch an L in column 14 of the
I /
XE Q card. From
this printout you can determine the exact sizes of
some of these packages:
• The size of the Unused area is contained in
the R41 message.
Approximate
logical Sub- Typical
When
Area Area Size Present Comments
Monitor Rasident 740 words Always
Monitor
Transfer Vector
I n Core Subprog.
Subtype 0
Flipper 100 words Only if LOCAL's or
SOCAL's are used
SOCAl Overlay 1 520 words Almost always Approximate, typical
(Arithl
size will be either
- - - -
- - -
1 - - - - - -
2970 Or 2450 or 1750
Overlay 2 1750 words Almost always words
(Non-DiSk I/O)
- - - - -
- -
- - - -
Overlay 3 700 words Only if Disk I/O
(Disk I/O) is used
lOCAL lOCAL No.1 Size of Only if user in-
lOCAL No.2 largest cludes a LOCAL
LOCAL card
subprogram
lOCAL No. n
Program
Non-50CAL or
Unknown;
Always
or
lOCAL Sub-
depends on
Link
programs
program
coding
Data
Object
Mainline
Program
Common Unknown; Only if user in-
depends on cludes COMMON
program statement on
coding program
Unused
Unknown;
See the R41 message
whatever is
of the core map for
left over
exact size
Figure 65,4.
Section Subsections Page
65
20
I
00 01
• The size of the SOCAL area can be determined
from the largest value contained in the R43, R44,
and/ or R45 message.
• The size of the LOCAL area may also be
determined from the core map. If SOCALs are
present, the size of the LOCAL area is the address
of the lowest SOCAL subroutine, less the address
of the next higher non- LOCAL. In this case it
would be 170C - 1567, or, in decimal, 5900-5479
or 321 words,
• Flipper (FLIPH), if present, is always about
100 words in length.
• The sizes of the other areas--Basic, Pro-
gram, and COMMON--cannot easily be determined
from the load map.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
1/
XEQ PAYRO L 2
*F I LES ( 1, F I
LEI~)
*LOCALPAYRO,SURW,SUHZ,SUHY1,SUHY2,SUBY3
FILES ALLOCATION
1 01A3 0001 7061 FILEN
22 0000 0001 7061 01A7
STORAGE ALLOCATION
R 40 03E3 (HEX) ADDITIONAL CORE REQUIRO
R 43 01FC (HEX) ARITH/FUNC SOCAL liD CNT
R 44 06E8 (HEX) FI/O,
110
SOCAL WD (NT
R 45 02A2 (HEX) DISK FIIO SOCAL WD CNT
R 41 OOA4 (HEX) WDS UNUSED BY CORE LOAD
CALL ~RANSFER VECTOR
DATSW 1902 SOCAL 1
SUBY3 1701 LOCAL
SUBY2 17C9 LOCAL
SUBY1 17(9 LcicAL
SUBZ 1701 LOCAL
SUBW 1765 LOCAL
LIBF TRANSFER VECTOR
HOLTB lEBR SOCAL 2
EADDX 1883 SOCAL 1
XDD 1988 SOCAL 1
FARC 1966 SOCAL 1
XMD 1924 SOCAL 1
ELDX 1528·
i\lOkl'vl 1594
HOLEZ 1E52 SOCAL 2
EBCTB lE4F SOCAL 2
GETAD lE06 SOCAL 2
IFIX 1568
PAUSE 18Ee SOCAL
ESBR 18D8 SOCAL
EADD 187D soeAL
EDIV 1824 SOCAL
EMPY 17F6 SOCAL
EDVR 17DE SOCAL
FLOAT 155E
SUBSC 1540
ESTO 1516
ELD 152C
PRNTZ 1D48 SOCAL 2
CARDZ 1C9E SOCAL 2
wRTYZ 1C62 SOCAL 2
SFIO 18D9 SOCAL 2
SDFIO 1885 SOCAL 3
SYSTEM SUBROUTINES
ILS04 00C4
ILS02 00B3
ILS01 1EC2
ILSOO 1EDD
FL'"IPR 15De
1467 (HEX) IS THE EXECUTION ADDR
Figure 65,5.