gtpm1m1cTPF V4R1 Migration Guide: 3.1 to 4.1

System Allocator (SALO) Program

Your system allocation process is simplified using the TPF 4.1 system. The system allocator (SALO) program compiles, link-edits, and runs in one job. Before this release, allocation was staged in several jobs.

You can change the characteristics of program allocations online. Beginning with this release, most of the system generation information required to run a program is merged in the allocation process. The program allocation options are simplified.

The system allocator (SALO) program is written in IBM C language and is compiled, link-edited, and run in one job in SIP Stage II. The new SALO takes input from one IBM source (IBMPAL) and up to 15 user-provided sources, which is specified on the new SIP INDSN macro. The output of SALO is two tables:

The PAT serves as the online system allocator and the program sharing table (PST), and contains the file and main storage addresses of all E-type programs. The SAL table is strictly an offline structure that is used by the TPF linkage editor (LEDT) to resolve external references within object modules.

Because the TPF 4.1 system allocator is written in IBM C language (along with other offline components such as the E-type loader and the FACE table generator), a C compiler is required for the TPF 4.1 system. See Operating Environment Requirements and Planning Information for more information about the C compilers that are supported for the TPF 4.1 system.

Running the System Allocator (SALO)

Before you can run the system allocator (SALO), you must have:

Note:
In the TPF 4.1 system, the residency of some SNA segments has changed. As a result, you need to rerun SALO (IBMPAL).

There are two different ways you can run SALO, depending on whether you run SIP Stage I, or both SIP Stages I and II.

To Run Only SIP Stage I

  1. Code EXPRS=S on the SIP GENSIP macro.
  2. Assemble the Stage I deck.
  3. Run the JCL that was produced from SIP Stage I.

To Run Both SIP Stages I and II

  1. SALO is compiled automatically, link-edited, and processed during Stage II.

When SALO runs successfully, it produces the system allocator (SAL) table and the program allocation table (PAT), which are written to disk as partitioned data sets.