gtps4m0iSystem Generation

System Initialization Overview

TPF system initialization includes the assembly of the system programs and laying out the database, application programs, system records, and application records. In essence, the system programs are used to manage the resources used by application programs and application records. Procedures in addition to the MVS assembly program are also required. An outline of the initialization process is as follows:

  1. Unpack the tapes received from the IBM program information distribution center. This means placing the contents of the tapes on MVS libraries. See the unpacking guide for more information; details are not included here.
    Note:
    To perform a system initialization program (SIP) process on the TPFDF product, unpack the tapes received from the IBM program information center. This means placing the contents of the tapes in MVS libraries. See the unpacking guide for more information; details are not included here.
  2. Compile and link the FACE table generator. (See Compiling the FACE Table Generator for more information about compiling the FACE table generator.)
  3. Create a SIP stage I input deck.
    Note:
    See TPFDF Installation and Customization for more information about defining the TPFDF product.
  4. Code a RIAT table.
    Note:
    See TPFDF Installation and Customization for more information about coding a RIAT table when performing a SIP process on the TPFDF product.
  5. Code a system allocator input deck that contains the names of any user application code.
  6. Run the FACE table generator to create a FACE table and other database-related information.
  7. Assemble the SIP stage I deck to create a SIP stage II deck.
  8. Run SIP stage II. This creates the keypoints and macros, assembles and compiles the necessary segments, builds the CP, runs the system allocator, and so on.

The TPF system provides the user with the following facilities in order to generate the required communication network records. The first of these (SIP) is always required and the others are optional depending on the communication line disciplines being supported.

Because all communications are handled by the basic subsystem in an MDBF environment, the communication database is generated only for the BSS and is not relevant to other subsystems.

System Initialization Package

The system initialization package (SIP) provides a set of macros that are coded by the user to select function and specify parameters relating to the following communication functions:

Many of the program records SIP produces contain information about the previously mentioned network functions. Some program records are in the form of system keypoints, whereas other program records reside in the program area of the database.

Non-SNA Communication Keypoint Records

The non-SNA communication keypoint records consist of the communication control unit keypoint status records (PKST) and the system communication keypoint records (SCK). SCK and PKST keypoint records are created by the SCK and PKST generation program as input to the system test compiler (STC). STC creates pilot tapes that are loaded to the online modules by the data loader. These records reside in the fixed file area.

SNA Communication Tables

The SNA communication tables are defined using the SNAKEY macro. See TPF ACF/SNA Network Generation for more information.

C Language Support

ISO-C support is installed during several phases of the SIP process. TPF C language support, in general, depends on a C compiler and its associated libraries. The C compiler needs to be installed before the TPF system. ISO-C support requires allocation for records that hold or manage C programs. Allocation of records for ISO-C is reflected in RAMFIL statements used to lay out the database and define the FACE table. The amount of storage needed for C programs in main storage is reflected in the CORREQ macro, which handles main storage structure requirements. ISO-C library load modules are created as a part of stage II of the installation process. SIP stage II creates 2 library load modules: the TPFAPI library CTAL and the standard C library CISO. Procedures for creating load modules are installation-specific and must be created before application programmers can reliably use ISO-C support.