gtpi1m75System Installation Support Reference

System Allocator

The system allocator (SALO) is an offline program that creates the system allocator (SAL) table and the program allocation table (PAT). To help with this section a few definitions are provided as follows:

dummy
Function switches can be coded on each card in the SALO input deck. If the function switch is off, the program is dummy allocated and, therefore, the program is not entered and no DASD is required. These entries reside in the SAL table only.

parent
The program in which a transfer vector is located. The parent can have multiple entry points (transfer vectors) in it.

spare
Programs allocated as spare serve as placeholders that can be defined for future application expansion. If an application is removed, the placeholders are needed to avoid a shift of the remaining applications.

transfer vector
The label name given to an entry point into a program.

SALO builds the SAL table and PAT from concatenated input decks as shown in Figure 33. The input decks contain program names and characteristics; for example, where the programs are to reside, what addressing mode they operate in, and whether they have any privileges. The input decks also contain symbol definition cards that are used to resolve V-type address constants (V-cons). As many as 16 input decks can be concatenated. The IBM input deck, IBMPAL, is concatenated first. You can specify as many as 15 more user input decks to hold user allocation information.

The output tables from SALO (SAL table and PAT) contain the information from the input decks in the form required by the linkage editor (LEDT) and online programs.

Figure 33. Operation of SALO


The SAL table:

The PAT:

To summarize, SALO is an offline tool for creating the SAL and PAT tables.