AFTER SOFTWARE INSTALLATION
3.2 SPECIAL SYSTEM DIRECTORIES
You initialize the file system during software installation. At this time, the system automatically creates nine directories on the disk that you defined as the system structure. These directories are shown in Figure
3-1:
Figure
3-1:
Special System DirectoriesAFTER SOFTWARE INSTALLATION
Sections 3.2.1 through 3.2.7 describe these directories and their use.
Section 3.2.8 describes additional directories you can create and how they are useful.
Chapter 5 also describes creating directories and includes diagrams showing the structure of directories.
3.2.1 <ROOT-DIRECTORY>
The <ROOT-DIRECTORY> contains a separate file for each first level directory on the system structure as follows:
STR:<ROOT-DIRECTORY>
STR:<SYSTEM> ... STR:<SUBSYS> ... STR:<DIRECTORY>
(where STR: is the name of the structure).
The <ROOT-DIRECTORY> is the most important directory created. Without it, directories and files cannot be accessed. You must NEVER modify this directory. The system maintains a backup---c;py of
<ROOT-DIRECTORY> that can be accessed if the original copy is destroyed. (Refer to Section 9.3, Restoring <ROOT-DIRECTORY>.)
Each structure you create in addition to the system structure has a
<ROOT-DIRECTORY>. The <ROOT-DIRECTORY> on any structure points to all the first-level directories created under the <ROOT-DIRECTORY>.
After you install the software, give the DIRECTORY command for
<ROOT-DIRECTORY>. The output on your terminal appears similar to the example below. Note that each directory is a file in the
<ROOT-DIRECTORY>. The differences between this list and the one on your terminal depend on the model system you have and the type of unbundled software you have purchased.
$DIRECTORY (OF FILES) STR:<ROOT-DIRECTORY><RET>
STR:<ROOT-DIRECTORY>
ACCOUNTS.DIRECTORY.1
BACKUP-COPY-OF-ROOT-DIRECTORY.IMAGE.1 BOOTSTRAP.BIN.!
DSKBTTBL .. !
FRONT-END-FILE-SYSTEM.BIN.!·
INDEX-TABLE.BIN.!
NEW-SUBSYS.DIRECTORY.l NEW-SYSTEM.DIRECTORY.!
OPERATOR.DIRECTORY.!
3-2
AFTER SOFTWARE INSTALLATION ROOT-DIRECTORY. DIRECTORY. 1
SPOOL. DIRECTORY. 1 SUBSYS.DIRECTORY.1 SYSTEM. DIRECTORY. 1
SYSTEM-ERROR.DIRECTORY.l UETP.DIRECTORY.1
Total of 14 Files
3.2.2 <SYSTEM>
The directory <SYSTEM> contains data and program files that the system uses during normal operation. Table 3-1 lists many of the files that appear in this directory.
Table 3-1: <SYSTEM> Files
File Name Explanation
ODVMP11.BIN 2060-MONBIG.EXE 2060-MONMAX.EXE n-CONFIG.CMD
n-SETSPD.EXE
n-SYSJOB.EXE
n-SYSJOB.RUN
Contains a dump of front-end memory after the front end crashes.
The smallest runnable monitor.
The largest runnable monitor.
Contains definitions of line speeds, system logical names, printer VFU files, magnetic tape logical unit
numbers, and additional
system-dependent parameters. These system parameters are set every time the system starts. The value n equals the latest release of TOPS-20.
Program that reads the n-CONFIG.CMD file and sets up the parameters that it contains. The value n equals the latest release of TOPS-20.
Program that runs in a process created by the monitor and takes commands from the file n-SYSJOB.RUN.
Contains processes.
commands that SYSJOB
File Name
Contains the information'necessary to validate accounts.
A large ARPANET timesharing monitor.
An
ARPANET monitor that includesProgram that creates structures and checks file-system consistency.
Contains binary system error messages.
The TOPS-20 Command Processor.
A DDT program used for debugging the front end.
Program that copies the CI-20
microcode to the file
<SYSTEM)CI-LOCAL-STORE.DUMP on the public structure. After the copying has completed, IPALOD.EXE is run.
3-4
I I·
microcode. (The microcode is contained in the file.) After the loading has automatically at the operator's console every time the system starts.Contains information about the SYSJOB program.
Contains OPR commands and is read by the OPR program at system startup.
Text file that contains the installation identifier that is written on VOLl labels for labeled tapes.
Program that analyzes and corrects MOS memory problems.
Contains information about the TGHA program.
AFTER SOFTWARE INSTALLATION 3.2.3 Restoring the Directory <SYSTEM>
If the contents of <SYSTEM> are accidentally lost .or destroyed, you can restore the directory from the TOPS-20 Installation Tape oi your latest system backup tape. (Refer to Chapter 7 for information about creating system backup tapes.) Use the procedure below to restore
<SYSTEM> directory. If you have enabled tape drive allocation, use the MOUNT command instead of the ASSIGN command. (Refer to Section 8.3 for information about using tape drive allocation.)
1. Mount the appropriate tape (in this example, it is on drive MTAO:) .
2. Give the following commands at your terminal.
@ENABLE (CAPABILITIES) <RET>
$ASSIGN (DEVICE) MTAO: <RET>
$SKIP (DEVICE) MTAO: 4 FILES <RET>
$RUN (PROGRAM) MTAO: <RET>
DUMPER> TAPE (DEVICE) MTAO: <RET>
DUMPER> RESTORE (TAPE FILES) DSK*:<*>*.*.* (TO) <SYSTEM> <RET>
DUMPER TAPE #1 , , FRIDAY I-NOV-8S 330 LOADING FILES INTO <SYSTEM>
END OF SA VESET DUMPER>EXIT <RET>
$
3.2.4 <SUBSYS>
The directory <SUBSYS> contains system programs (and their help files) that the user may want to run. The directory protection code set for
<SUBSYS> prevents users from changing the files in this directory.
Many of the file protections require users to enable WHEEL or OPERATOR capabilities to use the files. (Refer to Chapter 5· for information about directory and file protections and special capabilities.) Table 3-2 lists the programs and files commonly placed in <SUBSYS>. An asterisk precedes all unbundled software.
Table 3-2: STR:<SUBSYS> Files Programs Explanation
ACTGEN.EXE Program that takes files and creates base.
3-6
information from accounting the account validation data
Programs
Contains information about the ACTGEN program.
A file of universal symbols for USAGE accounting programs.
A file of ARPANET universal symbols.
BLISS functions needed to rebuild the Record Management Services facility (RMS-20) from AUTOPATCH.
The BASIC compiler.
Program that controls batch jobs.
Program that controls card readers.
Program that creates structures and checks file-system consistency (same as in <SYSTEM».
Contains information about the CHECKD program.
Program that makes accounting entries in the file
<ACCOUNTS>CHECKPOINT.BIN.
Contains information about the CHKPNT program.
A library file of routines for the COMND monitor call.
A file of universal symbols for the COMND monitor call.
Contains information about COBDDT.
The COBOL debugging program.
The COBOL compiler.
Contains information about the COBOL compiler.
Program that produces a cross-reference listing.
Contains information about the CREF program.
A library file
Programs
Contains data definitions for FORTRAN programs that use DIL.
Contains data definitions for FORTRAN programs that use the data transmission component of DIL.
Contains data definitions for FORTRAN programs that use the data conversion component of DIL.
Program that saves and restores the directory parameters.
Contains information about the DLUSER program.
Program that saves and restores files to and from magnetic tape.
Contains information about the DUMPER program.
Program that loads DX20 microcode.
Microcode for DX20 tape subsystem controller.
A component of the debugging program for the TOPS-20 monitor.
A line-oriented text editor.
Contains information about the EDIT program.
Program that 'listens' for DECnet file transfers.
Program that is used when copying files from the front-end file system to the TOPS-20 file system and vice versa.
Contains information about the FE program.
The debugging program for the front end.
Program that compares the contents of two files.
Contains information about the FILCOM program.
A DDT program used for examining the contents of system dumps (DUMP.CPY).
Contains information about the FORDDT program.
The FORTRAN debugging program.
3-8
Programs
Contains information about the FORMAT program.
The FORTRAN object time system (operating system
Contains information about the HELP command.
Spooling program that sends IBM-batch-job files to remote IBM host and retrieves the output.
Program that gives information to programs using IPCF.
Program that maintains COBOL single-key indexed sequential files.
Contains information about the ISAM program.
A component of the debugging program for the TOPS-20 monitor.
Program that creates, maintains, and lists the contents of COBOL library files.
Contains information about the LIBARY program.
The COBOL object-time system (operating system interface).
Contains the COBOL library subroutines.
Program that loads relocatable binary programs.
Contains information about the LINK program.
Translation RAM file for a 54-character line printer. Read by n-SETSPD.
Programs
Contains information about the MACRO assembler.
Contains system macros.
Program that sends messages to users.
Contains information about the MAIL program.
Program that receives mail from the MAIL program
Contains information about the MAKLIB program.
Program that creates a translation RAM file for line printers.
Contains information about the MAKRAM program.
Program that creates a vertical formatting unit (VFU) file.
Contains information about the MAKVFU program.
Program that loads the program-name cache. (Refer
Contains symbol definitions for monitor calls.
Program that mounts tapes and structures.
3-10
Programs
program that performs the network control (NCP) and the network control utility (NCU) .
DECnet file transfer program.
Contains information about the NFT.EXE program.
Vertical formatting unit file for line printers.
A file of universal symbols for the DECnet NSP protocol.
Program that the operator uses to interface with all jobs and devices on the system.
Contains information about the OPR program.
Program that processes messages sent by the OPR, MOUNTR, LPTSPL, QUASAR, EXEC, etc. programs.
Overlay manager for the LINK program.
The TOPS-10 Compatibility Package.
Version of PA1050 that can be used in debugging.
Contains information about the PTYCON program.
Program that manages the batch and print queues.
Program that does the central queuing and scheduling for the batch system.
Program that allows a user to read mail sent with the MAIL program.
Programs
Contains information about the RDMAIL program.
Program that marks files for migration to magnetic tape.
Contains information about the REAPER program.
Restarts COBOL programs.
Contains information about the RERUN program.
Contains SPEAR rep6rt templates.
Contains internal definitions for the RETRIEVE function of the SPEAR program.
RMS-20 used in Section 0 of memory.
RMS-20 used by COBOL V12B programs.
Routine called by BLISS and MACRO programs to initialize RMS-20.
Unsupported BLISS interface file for RMS-20.
MACRO interface file for RMS-20.
The RMS-20 file maintenance utility.
Utility program used for converting TOPS-20 files to a format used by the front end and vice versa.
Contains information about the RSXFMT program.
Program that helps with text preparation.
Contains information about the RUNOFF program.
A parameter file of symbols for the SCA inter-system communication routines.
A program that tests SCA.
DDT debugger for programs without a symbol table.
Program that interfaces between the COBOL language and the COBOL object-time system (LIBOL). (It is used with versions of COBOL up to and including version 11.)
3-12
Programs
Contains information about the SORT program.
Program that creates batch jobs from card input.
Contains information about the SYSJOB program.
Control file that creates a system backup tape.
A DIGITAL Standard Runoff index utility.
Contains information about the Tex utility.
A DIGITAL Standard Runoff utility for creating a table of contents.
Contains information about the TOC utility.
A character-oriented text editor.
DDT debugger for programs with a symbol table.
Program for printing information about directories and users.
Contains information about the ULIST program.
Program that is used during software installation to determine the integrity of files. It verifies checksums and version numbers of the .EXE files.
Program for observing system performance.
Contains information about the WATCH program.
AFTER SOFTWARE INSTALLATION Programs Explanation
*XPORT.REL Library containing the BLISS transportable I/O, memory, and string functions.
XRMS.EXE RMS-20 for use from memory sections other than Section O.
NOTE
All the .HLP files can be displayed using the HELP command; for example, the command @HELP WATCH displays the WATCH.HLP file.
3.2.5 Restoring the Directory <SUBSYS>
If the contents of <SUBSYS> are accidentally lost or destroyed, you can restore the directory from the TOPS-20 Installation Tape or your latest system backup tape. (Refer to Chapter 7 for information about creating system backup tapes.) Use the procedure below to restore the
<SUBSYS> directory. If you have enabled tape drive allocation, use the MOUNT command instead of the ASSIGN command. (Refer to Section 8.3 for information about using tape drive allocation.)
1. Mount the appropriate tape (in this example, it is on drive MTAO:)
2. Give the following commands at your terminal.
@ENABLE (CAPABILITIES) <RET>
$ASSIGN (DEVICE) MTAO: <RET>
$SKIP (DEVICE) MTAO: 4 FILES <RET>
$RUN (PROGRAM) MTAO: <RET>
DUMPER> TAPE (DEVICE) MTAO: <RET>
DUMPER> SKIP (NUMBER OF SAVESETS) 1 <RET>
DUMPER> RESTORE (TAPE FILES) DSK*:<*>*.*.* (TO)
<RET>
DUMPER TAPE # 1 , , SATURDAY, 3-NOV-84 330 LOADING FILES INTO STR:<SUBSYS>
END OF SA VESET DUMPER> EXIT <RET>
$
3-14
< SUBSYS >
AFTER SOFTWARE INSTALLATION 3.2.6 <NEW-SYSTEM> and <NEW-SUBSYS>
The first time you install the TOPS-20 software, the DLUSER program creates the directories <NEW-SYSTEM> and <NEW-SUBSYS>. They do not contain files. You can use these directories when a new release becomes available and you are updating the existing system. When DIGITAL distributes an updated monitor on the TOPS-20 Installation Tape, you restore the first two savesets from this tape to the directories <NEW-SYSTEM> and <NEW-SUBSYS> respectively. You use these directories until you feel comfortable with the new software. Should you have any problems with the new software, you can easily revert to using the old software. Appendixes A and B of the TQE§:~Q ~ M2g~! ~
!~~t!!!!t!Q~ gB!g~ detail the procedures to update one software release to another.
If you have no problems with the new monitor, and you are comfortable with it, copy all the files in the directory <NEW-SYSTEM> into the directory <SYSTEM> and all the files in the directory < NEW-SUBSYS >
into the directory <SUBSYS>. You can now delete all the files in
<NEW-SYSTEM> and <NEW-SUBSYS>. The directories <NEW-SYSTEM> and
< NEW-SUBSYS > remain empty until a new version of the TOPS-20 software is distributed.
NOTE
After you copy the new files into the directories
<SYSTEM> and <SUBSYS>, you cannot revert to the old system software unless you reinstall the system using the old monitor or backup tapes.
3.2.7 <ACCOUNTS>, <OPERATOR>, <SPOOL>, and <SYSTEM-ERROR>
<ACCOUNTS> - After installation, the directory <ACCOUNTS> contains one file, SYSTEM-DATA.BIN. This file contains all the accounting system entries for each user. If the directory <ACCOUNTS> is destroyed, the accounting system creates a new SYSTEM-DATA.BIN file.
After the first LOGIN on the system, the system creates the
<ACCOUNTS>CHECKPOINT.BIN file. This file stores accounting entries for each user during the time the user is logged in. After a user logs out, the accounting data stored in CHECKPOINT.BIN is copied to the SYSTEM-DATA.BIN file. When the system comes up after a crash, the monitor examines <ACCOUNTS>CHECKPOINT.BIN to determine which users were logged in at the time of the crash, and stores the data in CHECKPOINT.BIN in SYSTEM-DATA.BIN. Therefore, users who did not log out in the normal fashion, because of a crash, are still charged for their log-in time.
<OPERATOR) - The directory <OPERATOR> normally contains the file PTYCON.LOG. This file usually contains a record of all the activities
AFTER SOFTWARE INSTALLATION
that occur under the operator jobs that are controlled by PTYCON. The directory <OPERATOR> may also contain files the operator needs to run the system.
<SPOOL> - The directory <SPOOL> contains files that the spooling system needs before performing any input or output. They are kept in this area until they can be output to a slow-speed device such as a line printer. The file PRIMARY-MASTER-QUEUE-FILE.QUASAR is created in this directory. It contains a copy of the input queues so that they are not destroyed if the system crashes. You must either delete this file or process all entries in the queues before installing a new version of the batch system that has a different queue format. The GALAXY.DOC file-describes the new software components and tells you if the queue format has changed.
<SYSTEM-ERROR> The directory <SYSTEM-ERROR> contains the file ERROR.SYS. The ERROR.SYS file contains entries about system errors and is read by the system error recovery program, SPEAR.
3.2.8 Other Useful Directories
You may want to create additional directories for storing different versions of programs or text. Some useful directories are listed below. You should give these directories the proper protection number and make them files-only directories.
Directory and File Protection
Directories and files that are executed or read by the entire user community should not be given the default protection 777700, which allows no access. They should be given the directory protection 777740 and the file protection 777752 or 777712. (Section 5.7 describes directory and file protections.)
<NEW> The directory <NEW> can contain versions of your software that are not completely tested or that are drastically different from the current versions. If you create a directory <NEW>, users will find it more convenient if you also create the system-logical name NEW: defined as <NEW>, SYS:. This logical name allows them to run all new software by merely typing NEW: and the program name. If there is no file with the given name in <NEW>, the system uses the version currently on <SUBSYS>. (Refer to Section 3.3 for a description of logical names.)
3-16
<OLD)
By creating the directories <NEW) and <OLD>, you gradually introduce new software to system users. When a new version becomes available,
The directory <HELP> contains documents and help files that describe the system software. As
The directory <REMARKS> contains messages from users to the operator. These messages are usually
Creating the directory <REMARKS) avoids constant interruptions to the operator from users issuing PLEASE requests. The operator can read the