AREA LIST

This field contains the list of FGEN and build areas for which the file should be compiled.

o UNIV.CTL

This file forces compilation of all monitor sources. It defines a path to each FGEN area to do this. Edit i t to use your FGEN areas.

9.6.2 The Bui1d Procedure

The following example shows the complete build procedure. The column to the left shows the commands that you type. The column to the right of the commands contains explanatory remarks .

. SUBMIT START<RET>

.00 COMPILE MONGEN<RET>

.SUBMIT UNIV<RET>

.00 COMPILE modulename<RET>

.00 BUILDS<RET>

9.7 CUSTOMIZING BOOT

Include this COMPILE command only if you have made changes to MONGEN.MAC.

Include the SUBMIT UNIV command only if you have submitted START.

Include DO COMPILE if you have made changes to a module. The module will be recompiled and a listing will be generated.

Compiles the monitor modules in the FGEN areas, and builds MON.EXE and TOPSI0.GLB. If you have not changed the universal files, this is the only step you need to perform.

You can run the batch control file, BOOT.CTL, as distributed, to build BOOT after you have started GALAXY (refer to Chapter 10). The following command submits the control file for batch processing:

.SUBMIT BOOT.CTL<RET>

Or, before you bring up the monitor, you can perform the individual steps manually and modify the control file to eliminate the loading procedures for hardware that does not exist at your installation.

BUILDING YOUR MONITOR

For a KS system, you can modify the control file to include a step that creates binary files or a step to start EDDT.

For a KL system, you can modify the control file to include or exclude microcode for various hardware components, as well. This procedure allows you to save space in memory, because the monitor contains all the microcode available.

Section 9.7.1 describes the procedure for KL systems.

describes the procedure for KS systems.

Section 9.7.2

9.7.1 Customizing the KL BOOT

To customize BOOT for your KL system, command:

.COMPILE/COMPILE BOOT.MAC<RET>

first enter the following

The following output will appear on your terminal:

MACRO: BTSPRM BOOT

[Assembling Boot for a KL10]

[Including DXIO/TX01 driver]

[Including TM02 driver]

[Including DX20/TX02 driver]

[Including TM78 driver]

EXIT

The files BTSPRM.UNV and BOOT.REL have been created. Next, run LINK to create BTONCE.EXE:

.R LINK<RET>

*STONCE!SAVE=BOOT/LOCALS/SYMSEG: LOW, REL:EDDT/GO<RET>

EXIT

Now, you can run BTONCE and, by providing Y or N answers to the questions, include or exclude microcode for various hardware components. Running BTONCE creates BOOT.EXE and BOOT.EXB. The BTONCE questions are as follows:

.R BTONCE<RET>

~~eate binary output file [Y/N]:

Preserve EDDT and symbols [Y/N]:

Load DX10/TXOI microcode [Y/N]:

Load DX20/TX02 microcode [Y/N]:

Load DX20/RP20 microcide [Y/N]:

Load KLIPA/CI microcode [Y/N]:

Load KLNI/NI microcode [Y/N]:

9-22

Enter Y or N, then press RETURN

Lastly, run FILDDT to create a BOOT DDT that you can use to look at BOOT in the running monitor and examine problems that you might have with your BOOT procedure. The FILDDT prompt is File:. Enter the file name BTONCE followed by the switch IS, which directs FILDDT to load the symbol table from the file. After entering the file name and switch, press RETURN:

.R FILDDT<RET>

Flle:BTONCE!S<RET>

[Extracting symbols from file DSKB:BTONCE.EXE[*.*]

[1339 Symbols loaded from file]

File:

Enter the switch /M at the File: prompt and press RETURN. The switch /M directs FILDDT to look at the running monitor. In the following discussion, note that $ represents the escape character.

Next, ente'r the command string l$U, followed by RETURN. l$U provides FILDDT with the physical page number of the CPU's EPT (Executive Process Table). $U is the commmand that sets the EPT page number in FILDDT; the EPT for CPUO occupies physical page 1.

Then, enter the command string -1,,-BTSVEC$8U, followed by RETURN.

Because i t is unlikely that the location of the assembled symbol values will match the arbitrary location selected by the monitor for BOOT, the assembled values must be 'relocated. $8U is the relocation command, and -l,,-BTSVEC is the argument to that command.

To exit from FILDDT, enter <CTRL/Z>.

created.

File:/M<RET>

[Looking at the running monitor]

l$U<RET>

-1,,-BTSVEC$8U<RET>

<CTRL!Z>

.SAVE BTDDT<RET>

Then save the BTDDT file i t

These commands create a new version of BOOT and a BTDDT that you can now load. The file must be loaded into each front-end on a multiple-processor KL system; repeat this procedure at the CTY of each processor in an SMP system. You must repeat the copying procedure every time you rebuild the front-end file system.

The following procedure shows how to load BOOT into the front-end for a single-processor KL system. It is assumed that the front-end file system resides on DSKB .

. LOG 1,2<RET>

.RUN F11<RET>

F11>PUT DSKB: [5,5]=DSKB:BOOT.EXB[10,7,BOOT]<RET>

[DSKB will be treated as RPAO]

+- RPAO: [5,5]BOOT.EXB;4076=DSKB:BOOT.EXB/IMAGE F11>EXIT<RET>

Now you can bring up your new monitor with the new BOOT.EXB file to control microcode loading by the front-end.

BUILDING YOUR MONITOR

9.7.2 Customizing the KS BOOT

To customize BOOT for your KS system, enter the following commands.

These commands set the KS feature test switch to build BOOT for KS systems. Type CTRL/Z twice to exit from COMPILE:

.COMPILE/COMPILE TTY:+DSK:BOOT.MAC<RET>

MACRO:FTKLIO==O<RET>

FTKSIO==-l<RET>

CTRL/Z CTRL/Z

Next, run LINK and create KSONCE.EXE:

.R LINK<RET>

*KSONCE/SAVE=BOOT/LOCALS/SYMSEG: LOW, REL:EDDT/GO<RET>

EXIT

Now, you can modify the control file to include a step that creates binary output files and a step to start EDDT by running KSONCE.

Include these functions by answering the following questions with YES:

.R KSONCE<RET>

Create binary output file [Y/N]:

Preserve EDDT and symbols [Y/N]:

Enter Y or N, then press RETURN

To create KSBOOT.EXE from BOOT.EXE, type the following:

.RENAME KSBOOT.EXE=BOOT.EXE<RET>

Refer to Chapter 6 for the appropriate dialogue used to copy the file to the microprocessor file system.

9-24