USING SYSTEM FILES

The SYS arE3a includes several sample system files. The monitor uses these to create user accounts and to initialize system programs.

After you complete the procedures in Chapter 9 you can tailor these files to your installation.

o ACTDAE.SYS

This is the system's accounting file. It records the PPNs, passwords, access information, and disk quotas for users and operators. without the ACTDAE.SYS file, no one (users or operators) can log in. Chapter 11 describes how to use the REACT program to maintain this file.

o SYSJOB.INI

This file automatically starts system jobs.

described in Chapter 12.

SYSJOB.INI is o SYS'rEM. CMD

This file can be read by OPR to automatically start batch and spooling processes for GALAXY (refer to Chapter 10) .

o TTY.INI

INITIA reads this STOMPER functions.

file and initializes the CTY and TTY.INI is described in Chapter 12.

TTY Next, if you are installing a KL system, you will create the file system for the front-end. If you are installing a KS system, you will create the file system for the microprocessor. Chapter 6 describes these procedures.

BU1:LDING THE SUPPLEMENTARY PROCESSOR'S FILE SYSTEM

The KL and KS processors are each supported by another processor. The KL processor uses a PDP-II front-end for I/O, which requires space on disk for its software. The KS system uses an 8080 microprocessor that also requires disk space for storage. This chapter explains the

proc~~dure for creating these disk file systems. If you are installing a KL system, continue reading with Section 6.1. If you are installing a KS system, go directly to Section 6.2.

6.1 BUILDING THE KL FRONT-END FILE SYSTEM

To build the front-end file system, you must load the front-end from t:he front-end media, which you mounted according to the instructions in Chapter 3. The front-end software is distributed on either DECtapes or floppy diskettes. The commands that you will type to the RSX-20F command language processor, the PARSER, differ primarily in the physical device names used. The examples· used to illustrate your communication with the PARSER, if not specifically separated by appropriate headings, apply to both DECtapes and floppies. In all examples, the commands that you will type are underscored.

The following procedures assume that the front-end file system will be stored on DSKB, mounted on RPAO. In fact, you can use any structure by rE~placing DBa in the commands with DBn, where ' n' is the unit

numbE~r in RPxn. Make sure that the disk unit is write-enabled and is dual-ported between the front-end and the KL.

KL systems may have more than one CPU by implementing Synunetric Multi-Processing (SMP). In a multiple-CPU system, each CPU has a fron1:-end, and each front-end requires its own file system. If you are installing an SMP system, you must follow the steps in Section 6.1.1 and 6.1.2 for each CPU, at each CTY.

E"or DECtapes:

Firs1:, check to make sure that the DECtapes are mounted correctly.

The DECtape labelled DT-A should be mounted on DECtape drive 0, DTO:, and the unit selector switch should be set to O. The DECtape labelled DT-B should be mounted on DECtape drive 1, DTl:, and the unit selector switch should be set to 1. On both DTO: and DTl:, set the LOCAL/REMOTE switch to REMOTE and the READ/WRITE switch to WRITE ENABLE.

BUILDING THE SUPPLEMENTARY PROCESSOR'S FILE SYSTEM

CONSOLE MODE: MAINTENANCE -PAR>RESET<RET>

Initialize the front-end by running the INIalization program. First, invoke the parser by typing CTRL/\, a.nd type the following corrunands:

Mount the disk unit on which the front-end file system will reside.

Run the MOUnt program by typing the following commands:

PAR#MCR MOU<RET>

Mou>i5B6: <RET>

MOU -- MOUNT COMPLETED

MOU><CTRL/Z~

Create the front--end file system directory. Run the UFD program by typing the following commands:

<CTRIJ/\>

PAR#MCR UFD<RET>

UFD>PBO:TS;S]<RET>

The UFD program does not prompt the CTY when i t is finished. When the lights on the front panel stop flashing, the operation is complete.

Wait 30 seconds, then type CTRL/\ to invoke the parser.

If you are loading the front-end from DECtapes, you will copy the

*.TSK files into directories before copying the rest of the files. If you are loading the front-end from floppies, you will copy all of the files now. Run the PIP program to copy the files from DECtape or floppy to disk. Exit from PIP by typing CTRL/Z. Type the following commands:

For DECtapes:

<CTRL/\>

PAR#MCR PIP<RET>

PIP>DBCf: =DTO: FllACP. TSK<RET>

PIP>DBO:=DTO:PARSER.TSK<RET>

PIP>DBO:=DTl:PIP.TSK<RET>

PIP><CTRL/Z>

For floppies:

<CTRL/\>

PAR#MCR PIP<RET>

PIP>DBO:=DXO:,DXl:<RET>

PIP><CTRL/Z>

Redirect the system. Run the REDirect program to redirect the system search area (SYO:) from DECtape or floppy to disk. Type the following corrunands:

<CTRII/\~

PAR#MCR RED<RET>

RED>C>BO': =SYO : <RET>

The REDirect program does not prompt the CTY when i t is finished.

When the lights on the front panel stop flashing, the operation is complete. wait 30 seconds, then type CTRL/\ to invoke the parser.

<CTRL/\>

_ PARi

-BUILDING THE SUPPLEMENTARY P~OCESSOR'S FILE SYSTEM DECtapes or floppies and disk are logically dismounted automatically.

PIP will print warning messages about the files that already exist,

Type the following commands:

For DECtapes:

Copy the files to disk. Run PIP to copy the files from the third KLI KLI0 HARWARE ENVIRONMENT:

MCA25 CACHE PAGER

KLI -- CONFIGURATION FILE WRITTEN KLI -- BOOTSTRAP LOADED AND STARTED

BUILDING THE SUPPLEMENTARY PROCESSOR'S FILE SYSTEM

The ONCE dialogue begins automatically. The startup options are described in Appendix A. For a quick startup, use the GO startup option. If you are installing a multiple-processor KL, repeat the procedures in Section 6.1 at the console for each CPU, then go on to Chapter 9 for information about building your monitor. If you are installing a single processor KL system, go to Chapter 9 now.

If you are installing a KS system, go on to Section 6.2.