Figure 15. IBM System Load
The steps required to generate a complete multi-drive Monitor system are as follows.
The complete Monitor system is now on-line and operational. Detailed instructions for initial load and reload of the card and paper tape Monitor system are listed below. All loading and reloading is performed by the System Loader. System Loader error messages are listed in Appendix A.
The Monitor system for the card user is supplied on a disk cartridge and must be dumped to cards before the Initial Load procedure can be started. The dump is accomplished by loading the Monitor 2 cold start card supplied with the cartridge.
The cold start card is read in and punching begins. If the punch is a 1442-5, the first card will be blank. Throw the blank card away. If the punch runs out of cards or is not-ready as in the latter case listed above, the system executes a standard pre-operative WAIT at $PRET. Ready the punch unit and press PROGRAM START to continue. If a punch or feed error occurs, refer to the writeup on 1442 Errors and Operator Procedures in the System Library section of this manual.
The dump of the Monitor system requires approximately 3000 cards.
The user must prepare an initial load mode control card and system configuration cards (REQ) and insert these cards into the System Loader deck. These System Loader control cards must be present before the Monitor system can be loaded. An optional CORE card may also be used. See Figure 15 for the placement of these cards. The card formats are listed below.
Figure 15. IBM System Load
The following System Loader control cards are punched by the user (see Figure 15).
Load Mode Control Card. The load mode control card informs the system whether the operation is an initial load or a reload. In addition, the Assembler and/or FORTRAN Compiler can be deleted from the system through the use of the load mode control card. The load mode control card is placed behind the last card of the first part of the System Loader.
The format of the user-punched load mode control card is as follows.
| Card Column |
User Entry |
| 1-4 | MODE |
|---|---|
| 8 | I (initial load) or R (reload) |
| 12 | A (do not load Assembler) or blank (load Assembler) |
| 13 | F (do not load FORTRAN) or blank (load FORTRAN) |
Note: If FORTRAN and/or the Assembler are deleted they cannot be reloaded using the reload procedure. They must be loaded by an initial load.
System Configuration Cards (REQ). The system configuration cards are user-punched REQ cards that identify the system I/O devices that are a part of the user's system. If an REQ card specifies the 1442, columns 15-20 of that card must contain the model number, as indicated on the REQ card format chart.
The format of the REQ cards required by the System Loader are listed below. The user should punch only those cards that identify units on the system currently being generated. Punch one card for each device. Missing or extraneous REQ cards may cause initial load operations to fail. The REQ cards must be placed between the SCON card and the TERM card in the IBM system deck.
NOTES:
| Device | Card Columns | |||
|---|---|---|---|---|
| 1-3 | 9-10* | 15-20 | ||
| 1442 Card Read Punch or Card Punch | REQ | 1 | 1442-5 1442-6 1442-7 |
whichever is applicable |
| Paper Tape Reader and/or Punch | REQ | 3 | 1134 | Unit ID is optional |
| 2501 Card Reader | REQ | 4 | 2501 | |
| 1132 Printer | REQ | 6 | 1132 | |
| 1403 Printer | REQ | 9 | 1403 | |
*ISS numbers right justified. Maximum entry number ISS 20.
CORE Card (Optional). An optional user-punched control card CORE may be placed anywhere between the SCON and TERM cards in the IBM system deck. If this card is used, the calculated (actual) core size of the system is replaced by the core size defined in the CORE card. The format of the CORE card is as follows.
| User-Defined Core Size | Card Columns | |
|---|---|---|
| 1-4 | 6-8 | |
| 4K | CORE | 04K |
| 8K | CORE | 08K |
| 16K | CORE | 16K |
| 32K | CORE | 32K |
The following System Loader control cards are supplied with the IBM system (see Figure 15) and must be present in the IBM system deck on any system load.
SCON and TERM Card. These cards (supplied with the card system), together with the user-punched REQ cards, make up the system configuration deck. The system configuration deck must be included in the System Loader for any system load or reload. The format of the SCON and TERM cards are listed below.
SCON card, columns 1-4: SCON
TERM card, columns 1-4: TERM
Phase Identification Card (PHID). The PHID card contains the beginning and ending phase numbers of the various programs in the IBM system deck. All numbers in the phase ID field of the PHID card are in ascending sequence and in the order in which the system decks occur. The Resident Monitor and Cold Start Program have no phase IDs and are included in part 2 of the System Loader. The entries in the PHID card are loaded into the System Location Equivalence Table (SLET) and SLET is then used by the system as an internal directory to the Monitor programs.
The format of the PHID card is as follows.
| Card Column |
Entry |
| 1-4 | PHID |
|---|---|
| 6-8 10-12 |
Phase IDs of first and last DUP phases |
| 14-16 18-20 |
Phase IDs of first and last FORTRAN Compiler phases |
| 22-24 26-28 |
Phase IDs of first and last Assembler phases |
| 30-32 34-36 |
Phase IDs of first and last Supervisor phases |
| 38-40 42-44 |
Phase IDs of first and last Core Load Builder phases |
| 46-48 50-52 |
Phase IDs of first and last System Device Subroutine phases |
| 54-56 58-60 |
Phase IDs of first and last Core Image Loader phases |
| 66-68 | Vxx (xx is the version number) |
| 70-72 | Mxx (xx is the modification number) |
| 73-80 | Card identification and sequence number |
TYPE 81 Card. During an initial load, the type 81 card causes the principal print device and the principal I/O device entries to be placed in SLET. The Disk Communications Area (DCOM) and Location Equivalence Table (LET) are initialized and the Reload Table is established during an initial load. The IBM System Library is loaded following the reading of the type 81 card. The format of the type 81 card is as follows.
Column 3: 6 punch
Column 4: 1 punch
After the disk cartridge has been initialized by DCIP and the user-punched System Loader control cards inserted in the IBM system deck, the Monitor system is ready to load. The complete system, ready for loading, is illustrated in Figure 15. The steps necessary to perform a system load are as follows.
Switches 12-15 off, drive 0
Switch 15 on, drive 1
Switch 14 on, drive 2
Switch 14, 15 on, drive 3
Switch 13 on, drive 4
After the type 81 card has been read, the Auxiliary Supervisor calls DUP directly to store the System Library. After the last program of the System Library has been stored, the Monitor system is on disk and can be made operational by a user-initiated cold start.
The Monitor programs are divided into phases so that if changes are made within a program, only the affected phase needs to be reloaded. As in initial load, the user-punched load mode control card and REQ cards are required with the System Loader. The only difference is that the load mode control card for a reload must have an R in column 8. The programs or program phases being loaded by the reload procedure must be placed directly behind the IBM-supplied phase identification (PHID) card.
When using a 2501 Card Reader, the double-buffering procedure in the System Loader requires a blank card following the type 81 control card. The message END RELOAD will be printed by the Console Printer when the reload is completed.
If the Assembler or FORTRAN Compiler were deleted on initial load or deleted by a DUP DEFINE VOID operation, they cannot be reloaded using the reload procedure. They must be loaded by an initial load.
A useful option provided by the reload function is the ability to reconfigure a system cartridge with different I/O devices. Reconfiguration will be necessary if a system cartridge is copied from a system with a different configuration. The reload deck listed below will perform this function. (To reconfigure only, place the Type 81 card directly after the PHID card.)
SCON card
REQ cards
System reconfigured
if desired
CORE card (optional)
TERM card
*All decks must have phase ID numbers within the limits of the IDs listed on the PHID card.
During a reload operation, loading terminates with the reading of the type 81 card, and the printing of END RELOAD.
With the console Mode switch set to RUN, press PROGRAM STOP on the console.
Switches 12-15 off, drive 0
Switch 15 on, drive 1
Switch 14 on, drive 2
Switch 14, 15 on, drive 3
Switch 13 on, drive 4
In order to allow the user to load only a portion of a Monitor program, the programs are divided into phases, each identified by a sector break card. The user can load the revised phase using the reload procedure and then place the revised phase in the IBM system deck in place of the phase it replaces.
The sector break cards identifying the phases of the IBM system programs are listed below. Sector break cards (see Appendix C) have a 1 punch in column 4. The version and modification level are punched in the cards starting at column 67 (VxMxx).
| Phase Number |
Program or Program Phase Name | ID Starting in Column 73 |
|---|---|---|
| XX | RESIDENT IMAGE (Part of | ERI |
| COLD START PROGRAM System Loader) | EST | |
| DUP | ||
| 01 | DUP COMMON SUBROUTINES, CCAT | J01 |
| 02 | DUP CTRL RECORD PROCESSOR | J02 |
| 03 | DUP STORE PHASE | J03 |
| 04 | DUP *FILES, *LOCAL, *NOCAL PHASE | J04 |
| 05 | DUP DUMP PHASE | J05 |
| 06 | DUP DUMP LET/FLET PHASE | J06 |
| 07 | DUP DELETE PHASE | J07 |
| 08 | DUP DEFINE PHASE | J08 |
| 09 | DUP EXIT PHASE | J09 |
| 0A | DUP CARD I/O INTERFACE | J10 |
| 0B | DUP KEYBOARD INPUT INTERFACE | J11 |
| 0C | DUP PAPER TAPE I/O INTERFACE | J12 |
| 0D | DUP UPCOR PHASE SAVED BY DEXIT DURING STORECI | J17 |
| 0E | DUP PRINCIPAL INPUT WITH KEYBOARD | J17 |
| 0F | DUP PRINCIPAL INPUT W/O KEYBOARD | J17 |
| 10 | DUP PAPER TAPE I/O | J17 |
| 11 | DUP STORE CI | J17 |
| 12 | MODIF DUMMY PHASE | J17 |
| FORTRAN Compiler | ||
| 1F | FOR INPUT PHASE | K01 |
| 20 | FOR CLASSIFIER PHASE | K02 |
| 21 | FOR CHECK ORDER/STMNT NO. PH | K03 |
| 22 | FOR COMMON SUBR OR FUNCTION PH | K04 |
| 23 | FOR DIMENSION, REAL, INTEGER | K05 |
| 24 | FOR REAL CONSTANT PHASE | K06 |
| 25 | FOR DEFINE FILE, CALL LINK EXIT | K07 |
| 26 | FOR VARIABLE, STMNT FUNC PHASE | K08 |
| 27 | FOR DATA STATEMENT PHASE | K09 |
| 28 | FOR FORMAT STATEMENT PHASE | K10 |
| 29 | FOR SUBTRACT DECOMPOSITION PH | K11 |
| 2A | FOR ASCAN I PHASE | K12 |
| 2B | FOR ASCAN II PHASE | K13 |
| 2C | FOR DO, CONTINUE, ETC. PHASE | K14 |
| 2D | FOR SUBSCRIPT OPTIMIZE PHASE | K15 |
| 2E | FOR SCAN PHASE | K16 |
| 2F | FOR EXPANDER I PHASE | K17 |
| 30 | FOR EXPANDER II PHASE | K18 |
| 31 | FOR DATA ALLOCATION PHASE | K19 |
| 32 | FOR COMPILATION ERROR PHASE | K20 |
| 33 | FOR STATEMENT ALLOCATION PHASE | K21 |
| 34 | FOR LIST STATEMENT ALLOCATION | K22 |
| 35 | FOR LIST SYMBOL TABLE PHASE | K23 |
| 36 | FOR LIST CONSTANTS PHASE | K24 |
| 37 | FOR OUTPUT I PHASE | K25 |
| 38 | FOR OUTPUT II PHASE | K26 |
| 39 | FOR RECOVERY (EXIT) PHASE | K27 |
| ASSEMBLER | ||
| 51 | ASM INITIALIZATION PHASE | M01 |
| 52 | ASM CARD CONVERSION PHASE | M02 |
| 53 | ASM DSF OUTPUT PHASE | M03 |
| 54 | ASM INTERMEDIATE INPUT PHASE | M04 |
| 55 | ASM END STATEMENT PHASE | M05 |
| 56 | ASM ASSEMBLY ERROR PHASE | M06 |
| 57 | ASM CONTROL CARDS 1 | M07 |
| 58 | ASM CONTROL CARDS 2 | M08 |
| 59 | ASM DUMMY PH (SYST SYMBOL TBL) | M09 |
| 5A | ASM SYMBOL TABLE OPTIONS PHASE | M10 |
| 5B | ASM EXIT PHASE | M11 |
| 5C | ASM PROG HEADER MNEMONICS PH | M12 |
| 5D | ASM FILE STATEMENT PHASE | M13 |
| 5E | ASM COMMON SUBROUTINES, ASCOM | M14 |
| 5F | ASM PROG CONTROL MNEMONICS PH | M15 |
| 60 | ASM IMPERATIVE STATEMENTS PH | M16 |
| 61 | ASM DECML XFLC PROCESSING PH | M17 |
| 62 | ASM DECIMAL CONVERSION PHASE | M18 |
| 63 | ASM PROG LINKING PHASE | M19 |
| 64 | ASM DMES PROCESSING PHASE | M20 |
| 65 | ASM PUNCH CONVERSION PHASE | M21 |
| 66 | ASM INTERMEDIATE DISK OUTPUT | M22 |
| 67 | ASM SYMBOL TABLE OVERFLOW | M23 |
| SUPERVISOR | ||
| 6E | SUP PHASE 1- MONITOR CONTROL RECORD ANALYZER | N01 |
| 6F | SUP PHASE 2 - XEQ CONTROL AND PROCESSOR SUPERVISOR CONTROL RECORD PROCESSOR | N01 |
| 70 | SYSTEM DUMP-CORE -TO -PRINTER | N02 |
| 71 | AUXILIARY SUPERVISOR | N03 |
| CORE LOAD BUILDER | ||
| 78 | CORE LOAD BUILDER, PHASE 0/1 | OCB |
| 79 | CORE LOAD BUILDER, PHASE 2 | OCB |
| 7A | CORE LOAD BUILDER, PHASE 3 | OCB |
| 7B | CORE LOAD BUILDER, PHASE 4 | OCB |
| 7C | CORE LOAD BUILDER, PHASE 5 | OCB |
| 7D | CORE LOAD BUILDER, PHASE 6 | OCB |
| 7E | CORE LOAD BUILDER, PHASE 7 | OCB |
| 7F | CORE LOAD BUILDER, PHASE 8 | OCB |
| 80 | CORE LOAD BUILDER, PHASE 9 | OCB |
| 81 | CORE LOAD BUILDER, PHASE 10 | OCB |
| 82 | CORE LOAD BUILDER, PHASE 11 | OCB |
| 83 | CORE LOAD BUILDER, PHASE 12 | OCB |
| SYSTEM DEVICE SUBROUTINES, DISK I/O | ||
| 8C | SYS 1403 | PMN |
| 8D | SYS 1132 | PMN |
| 8E | SYS CONSOLE PRINTER | PMN |
| 8F | SYS 2501 | PMN |
| 90 | SYS 1442 | PMN |
| 91 | SYS 1134 | PMN |
| 92 | SYS KEYBOARD | PMN |
| 93 | SYS 2501/1442 CONVERSION | PMN |
| 94 | SYS 1134 CONVERSION | PMN |
| 95 | SYS KEYBOARD CONVERSION | PMN |
| 96 | DISKZ | PMN |
| 97 | DISK1 | PMN |
| 98 | DISKN | PMN |
| CORE IMAGE LOADER | ||
| A0 | CORE IMAGE LOADER, PHASE 1 | PMN |
| A1 | CORE IMAGE LOADER, PHASE 2 | PMN |
The tapes constituting the complete Paper Tape Monitor System, including the user-punched control record tapes are listed below.
| Tape Number |
Description |
|---|---|
| 1 | System Loader, Part 1 |
| - | Load Mode Control Record (User-punched) |
| 2 | System Loader, Part 2, with Resident Monitor and Cold Start |
| - | System Configuration Records (User-punched) |
| 3 | Phase Id. (PHID) Control Record |
| 4 | Disk Utility Program |
| 5 | FORTRAN Compiler |
| 6 | Assembler |
| 7 | Supervisor, Core Load Builder, System I/O Subroutines, Core Image Loader |
| 8 | End of System Tapes Control Record (Type 81 record) |
| 9 | Standard LIBFs and CALLs |
| 10 | Extended Precision LIBFs and CALLS |
| 11 | Common LIBFs and CALLs |
| 12 | ILS, ISS, Conversion and Utility Subroutines |
| 13 | Plotter Subroutines |
| 14 | SCA Subroutines |
| 15 | Cold Start Paper Tape Record |
| 16 | DCIP Disk Cartridge Initialization Program |
| 17 | PTUTL Paper Tape Utility Program |
| 18 | Paper Tape Reproducing Program |
| 19 | 1132/1403 Printer Core Dump from /01E0 |
| 20 | Console Printer Core Dump |
Tape 15 is used to initialize the Monitor system after it is loaded. Tapes 16-20 are stand-alone utilities and are not loaded as part of the Monitor System; however, PTUTL and DCIP are used during the loading process. Tapes 21 and 22 are the Monitor system sample programs.
NOTE: If the FORTRAN Compiler and/or the Assembler are not be be loaded during an initial load, the corressponding tapes (7 and/or 8) need not be read. If the FORTRAN Compiler and/or the Assembler are not loaded, they cannot be loaded using the reload procedure. They must be loaded by an initial load.
With the exception of the Load Mode Control Record and the System Configuration Records, all of the paper tape control records needed to load the Paper Tape Monitor System to disk storage are supplied to the user by IBM. These control records have the same functions as the corresponding IBM-supplied and user-punched control cards (see Initial Load (Card System)). The Load Mode Control record and System Configuration records must be prepared by the user. If these tapes are not prepared correctly, the System Loader will print an error message during system load (see Appendix A). A user-punched CORE record is optional.
Paper tape control records must be punched in PTTC/8 (Perforated Tape Transmission Code). The formats are the same as the previously-described card formats. Paper tape control records must be separated by one NL (new line) control character. A control record that immediately follows paper tape data not followed by an NL code must be preceded by one NL code. Delete codes may precede or follow this NL code.
To initially generate a system cartridge the necessary control records can be punched using a stand-alone paper tape utility program (PTUTL).
To load the PTUTL program tape, perform the following steps:
Switch 2-accept Keyboard input
Switch 3-punch records on the 1055 Paper Tape Punch
NOTE: Complete operating procedures for PTUTL are contained in the writeup for the System Library version of the Paper Tape Utility Program (see Paper Tape Utility (PTUTL).
Steps in preparation are:
Steps, in preparation are:
After the disk cartridge has been initialized by DCIP and the user-punched System Loader control record tapes generated, the Monitor system is ready to load. The steps necessary to perform a system load are as follows.
Switches 12-15 off, drive 0
Switch 15 on, drive 1
Switch 14 on, drive 2
Switch 14, 15 on, drive 3
Switch 13 on, drive 4
When loading tapes, position any of the delete codes following the program ID in the tape leader under the read starwheels.
Tape 1 is read in and the system WAITs at $PST4 or $PRET.
This tape is read in and the system again waits at $PST4 or $PRET.
NOTE: If the FORTRAN Compiler and/or Assembler are to be deleted, tapes 5 and/or 6 need not be loaded. Load only those System Library Tapes (9 through 14) that are required for your system.
After the last required System Library Tape has been loaded, the Monitor system is on disk and can be made operational by a user-initiated cold start.
During a reload of system programs or a system reconfiguration, all System Loader Control record tapes must be used. A typical paper tape reload would include:
Tape 1
User-punched Load Mode Control record (R for reload)
Tape 2
User-punched System Configuration tape (revised if system is being reconfigured)
Tape 3
(Revised programs or program phases)*
Tape 8
*All programs must have phase ID numbers within the limits of the IDs listed on the PHID tape.
If the Assembler or FORTRAN Compiler were deleted on initial load or deleted by a DUP DEFINE VOID operation, they cannot be reloaded using the reload procedure. They must be loaded by an initial load.
For further information regarding reload, see System Reload (Card System).
But wait, there's MORE...