gtps4m2c | System Generation |
The allocation process involves two sources of input: the IBMPAL deck and the user-defined program decks. The IBMPAL deck contains allocation statements required for TPF. The user-defined program decks contain the statements required for allocation of site-specific structures. The INDSN macro is provided, which allows up to 15 user decks to be specified.
Creating the allocator decks is the first step in the program allocation process. They are ordered lists of real-time programs (including transfer vectors) and GFS pool record ID definitions. The output of SALO is the System Allocator Table (IDSSAL), which is used by the linkage editor (LEDT) to resolve VCONs for segments, and the IPATvv, the program allocation table containing the file and core addresses of E-type programs. No actual addresses are allocated by SALO; instead, allocation is done during system initialization (CTIN). (See the TPF System Installation Support Reference for more information about the system allocator.)
The segments listed in the IBMPAL macro have no implied order based on their position in the list. Core resident and file resident allocations may appear intermixed. The older notion of core fast has been dropped in favor of making all programs with a core resident requirement as much as possible remain in central memory at all times.
Included in the allocator deck are:
See TPF System Installation Support Reference for more information.