DEC-11-ORSRB-B-D_SYSTST_Jul75.pdf

DEC-11-ORSRB-B-D_SYSTST_Jul75.pdf
&
STS/
Reliab
Balilgli/t/alı 9
RSTS/E
System Reliability Test
Order Number DEC-11-ORSRB-B-D
Order additional copies as directed on the Software
Information page at the back of this document.
digital equipment corporation - maynard. massachusetts
First Printing, March 1975
First Revision, July 1975
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may only be used or copied in accordance to the terms of such
license. |
Digital Equipment Corporation assumes no responsibility for the use
or reliability of its software on equipment that is not supplied by
Digital.
Copyright © 1974, 1975 by Digital Equipment Corporation
The HOW TO OBTAIN SOFTWARE INFORMATION pages, located at the back of
this document, explain the various services available to Digital soft-
ware users.
The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in
preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DIGITAL DECsystem-10 MASSBUS
DEC DECtape OMNIBUS
PDP DIBOL 05/8
DECUS EDUSYSTEM PHA
UNIBUS FLIP CHIP RSTS
COMPUTER LABS FOCAL RSX
COMTEX INDAC TYPESET-8
DDT LAB-8 TYPESET-11
DECCOMM
LIMITED RIGHTS LEGEND
Contract No.
Contractor or Subcontractor: Digital Equipment Corporation
All the material contained herein is considered limited rights data
under such contract.
PREFACE
This update document describes the procedures which DIGITAL pro-
duction personnel, DIGITAL Software Support representatives, or RSTS/E
users should follow to test the reliability of RSTS/E [email protected]#2 hardware
components at the system level. This document includes the material
previously found in the addendum, order number DEC-11-ORSRB-A-DN1.
For DIGITAL production personnel, steps are described which enable
building a RSTS/E system from the standard distribution kit, creating
an operational RSTS/E system disk, and initializing all non-system
disks. Additionally, for all users of the reliability test, proce-
dures are described for creating the required files and for running
the special SYSTST control program and the peripheral exercising pro-
grams on the RSTS/E system. The document is designed to be used in
conjunction with the RSTS/E System Generation Manual, order number
DEC-11-ORGNA-A-D.
For more information on documentation, consult the RSTS/E Docu-
mentation Directory, order number DEC-11-ORDAA-A-D.
iii
CHAPTER
CHAPTER
CHAPTER
CHAPTER
1
° .
. e .
Jun SUN FH
VDNNNNNN N N
. . .
HHHHHHEL HE
.
*
.
°
»
E WN H
ww U WW WWW WW w
.
CI a о N hh. -
.
L +»
> WN +
EX A A A A SS
. *. .
U SUNHHHH H
CONTENTS
INTRODUCTION TO THE RSTS/E SYSTEM RELIABILITY
TEST
SYSTST ENVIRONMENT AND OPERATION OVERVIEW
COMPONENTS OF SYSTST
RSTS/E SYSTEM GENERATION FOR SYSTST
SYSTEM GENERATION FOR PRODUCTION TESTING
Creating the RSTS/E System - SYSGEN
Creating the System Disk for SYSTST
Installing System Patches - PATCH Option
Initializing the System Disk - DSKINT Option
Initialization of Non-System Disks - DSKINT
Building the System Files - REFRESH
Setting the Default Start Up Conditions -
DEFAULT
Starting Time Sharing Operations - START
BUILDING THE SYSTST FILES
SYSTST Build from DECpack
SYSTST Build from Magtape
SYSTST Build from DECtape
SYSTEM GENERATION FOR FIELD INSTALLATION TESTS
RUNNING THE SYSTEM RELIABILITY TEST
USING THE SYSTST CONTROL PROGRAM
Starting Subjobs
Monitoring Status of Subjobs
Attaching Subjobs to a Terminal
Using Additional SYSTST Commands
RUNNING THE SYSTEM RELIABILITY TEST
NORMAL TEST SYSTEM RESTARTING PROCEDURES
RESTARTING THE TEST SYSTEM AFTER A SYSTEM CRASH
GUIDELINES FOR USING CONTRL UNDER NORMAL TIME
SHARING
DEVICE EXERCISER ABSTRACTS
DISK EXERCISERS
DFEXER - RF11/RS11 Disk Exerciser
DKEXER - RK11/RK03/RK05 Disk Exerciser
DPEXER - RP1l1-C/[email protected] Disk Exerciser
DBEXER - RH11/RPÿ4 Disk Exerciser
DTEXER —- DECTAPE EXERCISER
MTEXER - MAGTAPE EXERCISER
CREXER - CARD READER EXERCISER
LPEXER - LINE PRINTER EXERCISER
2-15
2-15
2-19
2-20
2-22
APPENDIX A
APPENDIX B
Number
PPEXER ~ PAPER TAPE PUNCH EXERCISER
PREXER - PAPER TAPE READER EXERCISER
KBEXER - KEYBOARD EXERCISER
CPEXER - PROCESSOR EXERCISER
SPECIAL SYSGEN OPTIONS
CLOCK ?
LPn: TYPE?
ADDRESS AND VECTOR ASSIGNMENTS
FLOATING ADDRESSES
FLOATING VECTORS
FIXED ADDRESSES AND VECTORS
TABLES
SYSTST Disk Usage
DSKINT Queries and SYSTST Responses
DSKINT Queries and Responses for Non-System
Disks
vi
4-21
4-23
4-25
4-29
A-1
A-1
CHAPTER 1
INTRODUCTION TO THE RSTS/E SYSTEM RELIABILITY TEST
SYSTST is a set of BASIC-PLUS programs designed to provide a sys-
tem reliability test of RSTS/E computers. The package includes a con-
trol program, several device exerciser programs, and utility routines
required to establish the SYSTST environment. Each of the device exer-
cisers is dedicated to driving one or more units attached to a peri-
pheral controller and reporting any errors it may detect. The device
exercisers are initiated through operator commands to the control pro-
gram which is also responsible for monitoring their progress. Since
RSTS/E provides for software recovery from many hardware errors, the
error logging routines are used to provide continuous monitor level
recording of all detectable errors whether or not they are reported by
the exercisers. The error logging programs, ERRCPY, ERRDIS, ERRCRS,
and ANALYS are part of the standard RSTS/E library.
Although the SYSTST exercisers in combination with the error log-
ging routines do provide some diagnostic information, the package is
not intended to replace stand-alone diagnostic or maintenance programs.
SYSTST should be used to point out possible problems and to verify
hardware on the system level. The diagnostics must be used to identify
specific hardware malfunctions at the device level.
1.1 SYSTST ENVIRONMENT AND OPERATION OVERVIEW
SYSTST is intended to run on any RSTS/E system with a minimum of
8K words of user core. The system must be configured for all devices
to be tested. The reliability test normally consists of running simul-
taneously any set of device exercising subjobs over a period of several
hours. During the test the control program allows the operator to
initiate, terminate, and communicate with the subjobs and provides
1-1
periodic status reports on request. At the conclusion of the test, the
contents of the error log file should be printed to provide additional
diagnostic information.
1.2 COMPONENTS OF SYSTST
All SYSTST programs are included in the standard RSTS/E distribu-
tion kit. If the distribution medium is magtape, the reguired SYSTST
files are included on the reel labelled System Library and Reliabiiity
Test. If the medium is DECtape, a separate reel labelled System Reli-
ability Test is included in the kit. For disk cartridge distribution,
all SYSTST files are included on the cartridge labelled System Library
and Reliability DECpack. Required SYSTST files are listed below with a
brief description of their purpose.
TSTBLD. BAS A modified version of BUILD
TSTBLD.CTL Control file for TSTBLD.BAS
CONTRL.BAS The SYSTST control program
CONTRL.HLP HELP file for CONTRL.BAS
CPEXER. BAS CPU/EIS/FIS/FPP exerciser
DFEXER.BAS RF11/RS11 disk exerciser
DKEXER. BAS RK11/[email protected]/RK95 disk exerciser
DPEXER.BAS RP11-C/RP83 disk exerciser
KBEXER. BAS Keyboard exerciser
DTEXER.BAS DECtape exerciser
LPEXER. BAS Line printer exerciser
PREXER.BAS Paper tape reader exerciser
PPEXER.BAS Paper tape punch exerciser
CREXER.BAS Card reader exerciser
MTEXER.BAS Magtape exerciser
DBEXER.BAS RH11/RPF4 disk exerciser
The following programs are also required and are included in the
standard RSTS/E library.
LOGIN. BAS RSTS/E LOGIN program
LOGOUT.BAS RSTS/E LOGOUT program
INIT.BAS RSTS/E system initialization program
UTILTY.BAS RSTS/E system utility program
TTYSET .BAS RSTS/E program for setting terminal charac-
teristics
ERRCPY.BAS RSTS/E error logging program
ERRDIS.BAS RSTS/E error log printout program
ERRDIS.HLP HELP file for ERRDIS.BAS
ERRCRS .BAS RSTS/E crash data recovery program
ANALYS.BAS RSTS/E crash analysis program
SHUTUP .BAS RSTS/E system shutdown program
CHAPTER 2
RSTS/E SYSTEM GENERATION FOR SYSTST
SYSTST is intended for use at DIGITAL manufacturing facilities
for production testing of RSTS/E systems, at the customer site for
field installation tests, and for periodic system reliability testing.
Production testing requires generation of a RSTS/E system for the con-
This chapter provides guidelines for the
figuration to be tested.
Reference is made to
system generation at the manufacturing facility.
the RSTS/E System Generation Manual for details of the SYSGEN proce-
dure which are not duplicated in this manual.
2.1 SYSTEM GENERATION FOR PRODUCTION TESTING
Generation of RSTS/E systems has been automated as much as pos-
sible to minimize operator error and the time required to get the sys-
tem on the air. For magtape and DECtape procedures, start at Section
2.2 of the RSTS/E System Generation Manual. For disk cartridge, begin
at Section 2.3 of the same manual. After the system disk is created,
the initialization options PATCH, DSKINT, REFRESH, SETKEY, DEFAULT,
and START described in Chapter 3 of the RSTS/E System Generation Manual
are used to bring RSTS/E up to full operational status for production
testing.
2.1.1 Creating the RSTS/E System - SYSGEN
The SYSTST user should be familiar with the material in the RSTS/E
System Generation Manual before attempting the system generation.
In particular, Section 2.4 contains detailed instructions for loading
the System Generation Monitor and running the system generation batch
stream. When the batch procedure is initiated, the SYSGEN program
asks a series of hardware configuration questions. The SYSGEN auto-
matic answer capability should be used for the system generation at
the production facility. This feature serves to verify the hardware
configuration. Section 2.6 of the RSTS/E System Generation Manual in-
cludes all of the configuration questions. Normally, RSTS/E systems
should be configured only for the hardware which is installed. How-
ever, RSTS/E is tolerant of missing devices and, with a few reserva-
tions, the questions may be answered for the full hardware configura-
tion defined by the DIGITAL order even if some devices are not installed
at the manufacturing facility.
The KT1l memory management unit, the EIS option (11/48 only),
11/48 FIS or 11/45 FPP (if configured), 4fK words of memory, clock,
the console terminal, and the system disk must be installed to begin
time sharing. Since RSTS/E adapts to the amount of additional memory
available at start up time, memory may be added or removed as long as
the 49K minimum is maintained as the low 48K of physical memory.
Similarly, terminal interfaces which are configured but are not physi-
cally present at start up time are locked out and messages conveying
the keyboard numbers of the lines disabled are printed by the initiali-
zation code. If a swapping disk is configured but is not connected,
RSTS/E can be forced to swap on the system disk by appropriate re-
sponses to the REFRESH questions described in Section 2.1.6. Other
devices such as DECtape, magtape, printers, and auxiliary disks may
be configured even if they are not connected provided they are not
referenced under timesharing and are not used during the system genera-
tion. When running SYSTST, care must be taken not to run any exerciser
for a configured device which is not really there. If this is done,
RSTS/E will assume the device is present, the driver will access the
appropriate bus address, a kernel trap through 4 will occur, and the
system will crash.
During the hardware configuration questions, SYSGEN asks if any
non-supported devices are connected to the RSTS/E system. According
to the sequence for assignment of floating device addresses and vec-
tors, several non-supported devices will have their addresses and/or
vectors assigned before some of the supported devices (notably DH11).
RSTS/E conforms to the specifications for assignment of floating ad-
dresses and vectors. These specifications are included as Appendix B
of this manual. The devices which are not supported in RSTS/E are listed
below the question concerning non-supported devices in the SYSGEN ex-
ample of Section 2.6.1, RSTS/E System Generation Manual.
SYSGEN also asks which disk will be used as the system disk.
Table 2-1 lists the preferred system disk for SYSTST. Note that the
RF11 is used as a swapping disk if it is not configured as the system
disk.
SYSGEN continues with a series of questions to determine the
software configuration. For the system generation at the DIGITAL manu-
facturing facility, the default responses given in the automatic
answers are acceptable for all software options. The user need only
type the LINE FEED key to accept the automatic answer. For field in-
stallation testing (if a SYSGEN is performed) and for periodic reli-
ability testing at the customer site, the software may be tailored to
customer specification. Software requirements and guidelines for run-
ning SYSTST under these circumstances are presented in Sections 2.3
and 3.5 of this manual,
After all hardware and software configuration questions have been
answered, the batch stream proceeds to create the system as specified.
The operator is directed to mount tapes or disks as required. If SYSGEN
is permitted to use a line printer, load maps and a directory of the
LICIL tape will be printed. If a line printer is not available, the
tape directory only will be printed on the console terminal.
2-3
Table 2-1
SYSTST Disk Usage
Preferred
Disk Configuration SYSTST
Choices
RF11/RS11 platters | RK11 RK#3 | RP11-C | RH11 System Default Auxili-
(RH11/[email protected]/ or RK05 | RPg3 RPF4 Disk! Swapping ary
[email protected] drives) drives drives | drives Disk Disks
g (9) 2 1-8 g DPg None DP1-DP7
9 (9) g g 1-8 DBS None DB1-DB7
ÿ (8) 1-8 g g DK None DK1-DK7
g (g) - 1-8 g DPJ None [email protected]~DK7
DP1-DP7
B (PB) 1-8 g 1-8 DBA None DK9-DK7
DB1-DB7
1-8 g g g pr! None None
(all)
1- (1-4) g 1-8 a DP DF (DS) DP1-DP7
-8 (1-4) g g 1-8 DBO DF (DS) DB1-DB7
1-8 (1-4 - 0 й DKO DF (DS) DK1-DK7
-8 (1-4) 1-8 1-8 g DK DF (DS) DK1-DK7
DP Q-DP7
1-8 (1-4) 1-8 g 1-8 DK#@ DF (DS) DKI1-DK7
DBZ-DB7
2.1.2 Creating the System Disk for SYSTST
At this point SYSLOD or CILUS is used to create the contiguous
Core Image Library (CIL) on the system disk from the RSTS.LCL file on
tape or disk.
When DECtape or magtape media is used, SYSGEN prints
the correct SYSLOD command string to be used for the specified con-
figuration.
and write enabled before answering the SYSLOD DIALOGUE query.
completion of the load operation, SYSLOD bootstraps the RSTS/E
initialization code into memory from the newly generated CIL.
The disk to be used as the system disk must be mounted
Upon
The
load operation is performed automatically with CILUS when DECpack
software is used.
No command string need be typed.
In either case,
SYSTST does not require any special procedures in loading the CIL.
Section 2.9 of the RSTS/E System Generation Manual presents and
explains the SYSLOD and CILUS command strings which are used for the
The RH11/[email protected]/[email protected] disks can not be used as system disks.
2-4
various types of system disks and distribution media. That document
When the RSTS/E initiali-
zation code is loaded into memory it prints an identification line and
the OPTION query.
tion options to install any published patches, create the necessary file
should provide adequate reference material.
The SYSTST user must now invoke several initializa-
structures, and establish start up conditions in preparation for running
the reliability test.
2.1.3 Installing System Patches - PATCH Option
Immediately after the initialization code is bootstrapped into
memory, the PATCH option must be used to install any system patches.
Patches are published in the RSTS/E System Installation Notes and
Published patches
contain detailed instructions on the correct procedures to install
the patch.
in Section 3.2 of the RSTS/E System Generation Manual.
the monthly Software Dispatch publications.
The PATCH option of the initialization code is described
The SYSTST
user should be familiar with that material before attempting to make
any alterations to the system code.
the use of the PATCH option.
The example below demonstrates
OPTION: PATCH
MODULE NAME ? INIT
BASE ADDRESS ? 67472
A
Example only - not a
real patch
OFFSET ADDRESS 7 4724
MODULE BASE OFFSET OLD NEW?
INIT 867472 004724 100200 7104200 Single Word Patch.
INIT 867472 G04726€ XXKMXM 7 - Old contents variable.
INIT 067472 004720 @ESFTEE 7 Printed for verification only.
INIT 067472 BE4TIZ 6061000 7 “C Control/C exit
OPTION: BOOT
BOOT DEVICE ?
RETS
OFTION:
YB5B-24 TEST SYSTEM
Boot required after
patching the initialization
code to load altered INIT
code into memory.
2.1.4 Initializing the System Disk - DSKINT Option
After the SYSLOD or CILUS operation, the system disk contains
only the CIL. The DSKINT initialization option is used to write the
minimal RSTS file structure and to incorporate the CIL into this
structure. DSKINT also performs pattern tests on disk devices to
check for bad blocks and can therefore be used to supplement the tests
performed by the diagnostics and by the SYSTST disk exercisers.
The initialization of a system disk is described in Sections
3.3 through 3.3.2 of the RSTS/E System Generation Manual. That
discussion contains more information than is required to run SYSTST
but is valuable for an understanding of the option. To avoid con-
fusion at the manufacturing facility, the following description of
DSKINT sets standards for initialization of all types of system
disks. Initialization of non-system disks is covered in Sections
3.3.3 and 3.3.4.
DSKINT is run by typing DSKINT or DS in response to the initiali-
zation OPTION query. DSKINT responds by asking for the current date
and time of day and then proceeds to ask a series of questions about
the disk to be initialized. Table 2-2 lists the DSKINT queries and
the responses which should be used for SYSTST according to system
disk type.
The pattern tests are performed after YES is typed in response
to the PROCEED query. If DSKINT finds a bad block, it prints the
block number (decimal) and the contents (octal) of the disk registers
at the time the error was detected. A few bad blocks (up to 10)
might be tolerated on RK cartridges or RP packs but diagnostics should
be rerun to ensure that the drive is not at fault. If bad blocks are
detected on an RF disk, the RF11 and/or RSIl should not be accepted.
Table 2-2
DSKINT Queries and SYSTST Responses
Response for System Disk Type
DSKINT Query RF RK RP RB
DISK? RF RK RP RB
PLATTERS? (RF ONLY)! 1-8 NA NA NA
UNIT? (RK AND RP)? NA g g g
PACK ID? SYSTST SYSTST SYSTST SYSTST
PACK CLUSTER SIZE? 1 1 2 4
MFD PASSWORD? SYSTST SYSTST SYSTST SYSTST
MFD CLUSTER SIZE? 4 4 4 â
PUB, PRI, SYS? sys SYS SYS SYS
LIBRARY PASSWORD? SYSTST SYSTST SYSTST SYSTST
LIBRARY UFD CLUSTER SIZE? 4 4 4 4
PATTERNS (1-8): 2 2 2 2
PROCEED (Y OR N)? YES YES YES YES
'Enter number of RS11 platters connected to RF11 control.
‘Always unit zero for system disk.
‘The more patterns used, the better the test. Time required per
pattern = .5 minutes for RF, 2 minutes for RK, 12 minutes for
RP and RB.
Initializing the System Disk - DSKINT Example
RSTS VA50C-91 TEST SYSTEM Refer to Table 2-2 for the
correct responses to be
OPTION: DS used for the various types
DD-MMM-YY? 6-JAN-75 of system disks.
HH:MM? 1:12
DISK ? RK
UNIT ? g
PACK ID ? SYSTST
PACK CLUSTER SIZE ? 1
MFD PASSWORD ? SYSTST
MFD CLUSTER SIZE ? 2
PUB, PRI, OR SYS ? SYS
LIBRARY PASSWORD ? SYSTST
LIBRARY UFD CLUSTER SIZE ? 4
PATTERNS ? 2
PROCEED (Y OR N) ? Y
PATTERN $ 2
PATTERN # 1
OPTION:
2.1.5 Initialization of Non-System Disks - DSKINT
The DSKINT option writes the minimal RSTS file structure on non-
SYSTST requires that each non-system RK, RP and RB
drive be fitted with a cartridge or pack, readied, and write enabled
system disks.
at this time. Do not use cartridges or packs which contain useful
information since DSKINT destroys everything on these packs. Sections
3.3.3 and 3.3.4 of the RSTS/E System Generation Manual contain a general
discussion on the use of DSKINT for non-system disks. Specific instruc-
tions for SYSTST are presented below.
DSKINT is run by typing DSKINT or DS in response to the OPTION
query. The current date and time of day entered when the system disk
Typing the LINE FEED key (indicated by
<LF> in the sample dialog) is sufficient response, therefore, to the
DATE and TIME questions.
to the case of the system disk.
was initialized is retained.
The subsequent questions asked are similar
Table 2-3 lists the DSKINT queries
and responses which should be used for SYSTST according to auxiliary
disk type. Do not initialize the system disk using the responses of
Table 2-3 as this will destroy the CIL.
Table 2-3
DSKINT Queries and Responses for Non-System Disks
Response for Auxiliary Disk Type
RF, [email protected],
DSKINT Query RSB4 RK RP RB
DISK? RF RK RP RB
PLATTERS? (RF ONLY)! 1-8 (RF) NA NA NA
UNIT? (RS, RK, OR RP)? 9-7 (RS) 9-7 0-7 0-7
PACK ID? SYSTST SYSTST SYSTST SYSTST
PACK CLUSTER SIZE? 1 1 2 4
MFD PASSWORD? SYSTST SYSTST SYSTST SYSTST
MFD CLUSTER SIZE? 4 4 4 4
PUB, PRI, SYS? PUB PUB PUB PUB
FORMAT? NA YES YES YES
PATTERNS? (1-8)? 2 2 2 4
PROCEED (Y OR N)? YES YES YES YES
'Use responses from Table 2-2 if RF is the system disk. DSKINT
serves only to pattern test an RF, RS93, or RS%4 swapping disk
and is not required. |
2If RK, RP, or RB unit #, ensure that the disk is not the sys-
tem disk.
“Time required per pattern .25 minutes for RF or RS, 1 minute
for RK, 12 minutes for RP and RB.
DSKINT is used once for each disk to be exercised under SYSTST.
After all disks have been initialized, leave the packs mounted and the
drives ready and write enabled for the duration of the test.
Initializing the Auxiliary Disks ~ DSKINT Examples
OPTION: DS
DD-MMM-ŸY? <LF >
HH : MM? <LF >
RICK > ву
WA oti ; NS
UNIT ? 4
PACK ID ? SYSTST
PACK CLUSTER SIZE ? 1
MFD PASSNORD 7 SYSTST
MFD CLUSTER SIZE ? ¿
FUB, PRI, ОК 5%5 7 FUB
FORMAT ? YES
FATTERNS ? 2
PROCEED <Y OR NO ? Y
STARTING FORMAT PASS
END FORMAT PASS
PATTERN 4 2
PATTERN # 1
OPTION: DS
DO -MMM-YY> <LF>
HH: MM? <LF>
DISK ? RP
UNIT ? 8
FRCK 10 7% SYSTST
PACK CLUSTER SIZE ? 2
MFD PASSNORD 7? SYSTST
MFD CLUSTER SIZE 7 2
FUB, PRI, OR SYS ? PUR
FORMAT 7? YES
PATTERNS ? 2
FROCEED <Y OR N> 7? Y
DRIVE NOT RERDY
Time entered above is sufficient
until start up time. (See note
below on <LF> .)
Refer to Table 2-3 for correct
response for all types of
auxiliary disks.
Typing the Linefeed key is
represented by the symbolic
characters <LF >.
Drive was not powered up.
TYPE <LF> TO RETRY, ANYTHING ELSE TO АВОКТ DSKINT <LF>
DRIVE NOT RERDY
TYFE <LF> TO RETRY, ANYTHING ELSE TO ABORT DSKINT
SET RP11C FORMAT ENABLING SNITCH THEN TYPE <LF> :
STARTING FORMAT PASS
END FORMAT PRSS
DISABLE FORMAT SWITCH THEN TYPE
PATTERN 4 2
PATTERN # 1
GFTION: DS
DO-MM-Y y?
HH: MM?
DISK ? RF
PLATTERS ? 2
PACK ID ? SYSTST
FACK CLUSTER. SIZE ? 4
MFD PASSNORD 7 SYSTST
MED CLUSTER SIZE ? 2
PUB, PRI, OR SYS ? PUB
PATTERNS ? 2
PROCEED «Y OR N> ? Y
FATTERN # 2
PATTERN 4 1
Drive was not
<LF> write enabled
< LF >
< LF>
< LF >
< LF >
DSKINTing the swapping disk
is not required but it does
serve to pattern check the
disk.
2.1.6 Building the System Files - REFRESH
All RSTS systems require a number of system files during normal
time sharing operations. The files required by RSTS/E are listed
in Table 3-3 in the RSTS/E System Generation Manual together with a
functional description of each. The DSKINT of the system disk creates
the files BADB.SYS, SATT.SYS, and RSTS.CIL. The remaining system
files are created by the REFRESH option of the RSTS/E initialization
code. REFRESH permits tailoring of the system files to the needs of
each individual installation. A lengthy discussion of the options
available at REFRESH time is presented in Sections 3.4.1 and 3.4.3
of the RSTS/E System Generation Manual. SYSTST requires only a small
amount of tailoring to locate a swap file ([email protected]) on the swapping
disk (if one exists) and to create the crash dump file (CRASH.SYS).
The example below shows the preferred responses to the REFRESH
dialog for SYTST. With two exceptions, the responses shown cause
REFRESH to default the characteristics of the system files. First,
REFRESH locates the swap file on the system disk even if a swapping
disk exists unless instructed otherwise. The responses shown in the
example force [email protected] to the swapping disk. If no swapping disk is
configured, REFRESH will not ask the "DISK" query and defaults to the
system disk. Secondly, REFRESH does not create the crash dump file
unless instructed to do so. The crash dump facility should always be
enabled for SYSTST, and, hence, the file CRASH.SYS must be created at
REFRESH time. "YES" responses to the "CRASH DUMP" queries of both
the REFRESH and DEFAULT initialization options serve to enable the
crash dump and auto-restart features of RSTS/E.
Creating the System Files - REFRESH Example
OPTION: REFRESH
DD-MMM-7Y? 22-JUL-74
НН: МИ? 18:36
OLD 7 NO
FILE CURRENT REQUIRED START START
NAME REQUIRED? EXIST STATUS SIZE SIZE CLUSTER SECTOR
BADB . SYS YES SYS GK. a a
RSTS .CIL TES SYS BAC 264 2€4 4€ 49
SATT SYS YES SYS BAC c & 4 a
SNAPE . SYS YES NO CRE a sz
SWAP1 . SYS NO NO CK a a
SWAP2 . SYS NO NC GK a a
SNAP:3 . SYS NO NO ОК a a
ОМК . SYS NO NO CK a 2e
ERR . 575 NO NO GK a E
BUFF . SYS YES NO CRE a €
CRASH . SYS NO NO CK a её
Creating the System Files - REFRESH Example (Cont.)
BADS ? < ТЕ >
RESTS. CIL CHANGES 7 <LF >
SATT. SYS CHANGES ? <LF >
SWAFG. SYS CHANGES +
+
YES Type the LINE FEED key here
to accept REFRESH defaults.
SIZE ? <LF >
DISK 7 SWP
BASE ? <LF>
SWAP1. 5YS CHANGES 7 <LF>
SWAP2. SYS CHANGES 7 <LF>
SWAPZ. 5YS CHANGES ? <LF>
OVER. SYS CHANGES ? <LF >
ERR. SYS CHANGES ? <LF >
BUFF. SYS CHANGES 7 <LF >
CRASH ? YES
FILE CURRENT REQUIRED START START
NAME REQUIRED? EXIST STATUS SIZE SIZE CLUSTER SECTOR
BRDB . SYS YES SYS Ok e a
RSTS .CIL YES SYS OK 264 264 4€ 49
SATT .SYS YES SYS CK E E 4 =
SNAPO .SYS YES SWF OK ale siaz 4794 4566
SWAP1 . SYS NO NO ak a a
SNAP2 . SYS NO NO OK a a
SNAP3 .SYS NO NO ak a a
OYR .SYS NO NO GK. a E
ERR . SYS NO NO OK a. E
BUFF . SYS YES SYS CK 6 E € Г
CRASH . SYS NO SYS OK eE E le 1x
OPTION:
2.1.7 Setting the Default Start Up Conditions - DEFAULT
The DEFAULT option permits tailoring of a RSTS/E system to meet
the needs of each installation. DEFAULT is used to permanently set
the system job maximum, the maximum size of user programs, the
physical location of the BASIC-PLUS Run Time System in memory, to
lock or unlock areas of memory, and to enable the crash dump facility.
These default start up conditions are permanent in the sense that they
are preserved when the system is shut down. The same characteristics
2-11
may be set using the START option described in the next section but
the effect is temporary, i.e., in effect only for one time sharing
session.
REFRESH assumes a maximum job size of 8K when determining the
size of SWAPY.SYS. Although these limits could be changed using
DEFAULT, they are consistent with SYSTST requirements and need not
be altered. Relocation of the BASIC-PLUS Run Time System is normally
used to gain optimum advantage of fast semiconductor memory. Since
SYSTST is not really concerned with speed, there is no requirement
to locate BASIC-PLUS in any particular area of memory. Furthermore,
memory should not be locked during the reliability test. The memory
lock out feature of the DEFAULT and START options should only be used
in the case of memory failures where it is necessary to continue
operation of the RSTS/E system or to help in locating memory
problems. Finally, the crash dump facility should always be enabled
during SYSTST.
The DEFAULT code is the most critical of the RSTS/E initializa-
tion routines. Prior to using this option, the KT11 memory manage-
ment unit, physical memory above 28K, and the memory parity registers
(if any) have not been used. DEFAULT enables memory mapping and
scans the 124K of physical address space to determine the size and
location of all available memory. DEFAULT will also enable memory
parity checking to determine the association between parity registers
and the parity memory banks. If any of this hardware is not operating
properly, it is very likely that DEFAULT will fail. If a crash does
occur during execution of the DEFAULT option, the components mentioned
should be carefully checked with diagnostics.
The responses to the DEFAULT questions necessary to establish
default start up conditions as outlined above are shown in the example
below. The DEFAULT option is described in greater detail in Section
3.5 of the RSTS/E System Generation Manual.
OPTION: DEFAULT
YOU CURRENTLY HAVE: JOB MAX = 16, SWAF MAX = EK.
JOB MAX OR SWAP MAX CHANGES 7 NO
+,
CURRENT MEMORY ALLOCATION TABLE:
RDDR +6006 +64000 +10066 +14008 +206060 +24000 +0000 +4000
680000 MON MON MON MON MON MON MON MON
640000 MON MON MON MON MON MEN MON MON
1660600 MON MON MON MON ERSIC EASIC BASIC BASIC
148668 BASIC BASIC BASIC BASIC ERSIC ERSIC EHSIC ERSIC
20808098 BASIC BASIC u U LI u и и
248800 U LI u u u u u U!
200000 U u u Li Ц и LI u
2400600 U и u Li Li и Lu и
498000 QU Li Lt U Li u Н и
440000 NM NX M NxM NxM NxM NxM НАМ NAM
508000 НАМ NEM NM NX M NA M NxM HM MM
54080600 НАМ NxM NxM NxM NxM NxM Mx MH
£00000 НАМ N*M NxM N*M NxM N*M LEA NM
640008 НАМ NxM NxM NxM NxM NxM Mh NM
780080 NM NxM NxM NxM NxM NxM NxM Mit
7400060 NM NxM NxM NM 10 10 1.0 IC
TABLE OPTION 7 EXIT
YOU CURRENTLY HAYE: CRASH DUMP DISABLED.
CRASH DUMP * YES
RETS YVBSB-24 TEST SYSTEM
OPTION:
2.1.8 Starting Time Sharing Operations - START
The START option is used to put RSTS/E into a full running
state. As mentioned above, start up conditions established by
DEFAULT can be temporarily altered by the START option. Any altera-
tion applies only for the current time sharing session. If RSTS/E
is shut down and later bootstrapped from the system disk, the start
up conditions revert to those set by default. The example below
retains the start up conditions established by DEFAULT and indicates
the preferred procedure for SYSTST. Section 3.6 of the RSTS/E Sys-
tem Generation Manual provides adequate reference material for use
of the START option.
The START code is also a very critical part of the system
initialization. START will reference all configured terminal inter-
faces and disable any which do not respond. The KTll memory manage-
ment unit is activated to determine the size of available memory
(as in DEFAULT), to load the monitor and Run Time System, and to
prepare for normal time sharing. START, furthermore, loads the stack
limit register, enables parity traps for all parity memory, and
activates the system clock to begin time sharing. Terminal inter-
faces, other than that for the console terminal, and the stack limit
register have not been used up to this time. Even the clock was not
critical to the operation of the System Generation Monitor or the
other initialization routines. If the system does not come up as
shown in the example below, these components are suspect and should
be exercised with the standard diagnostics.
APTIAN: START
YOU CURRENTLY HAVE: JOE MAX = 16, SWAF MAX = EK.
JOB MAX OR SWAP MAX CHANGES 7 <LF> Line Feed <LF> is used to
retain DEFAULT start up
ANY MEMORY ALLACATICN CHANGES * <LF> conditions.
CRASH DUMP 7 <LF>
DD-MMM-YY? 22-JUL-74 Time and date should be
HH:MM? 12:18 entered here.
CANT FIND FILE OR ACCOUNT These are normal error
PROGRAM LOST - SORRY messages.
READY RSTS/E is now up and
running.
When time sharing is initiated, the system attempts to execute
the INIT system program which does not yet exist in the system
library. As a result, two error messages are printed followed by the
READY message as shown in the example. At this point, the console
terminal is logged into the system under the system library account
[1,2] and RSTS/E waits for input. In a normal system generation, the
system library would be built at this time. The files listed in
Section 1.2 comprise the library for SYSTST. Section 2.2 is concerned
with loading the SYSTST files.
2.2 BUILDING THE SYSTST FILES
The SYSTST package includes a BASIC-PLUS program (TSTBLD.BAS)
and a control file (TSTBLD.CTL) responsible for loading and compiling
the SYSTST files. It is, however, necessary to build most of the
standard RSTS/E library in addition to the SYSTST programs since
several of these programs are also used for the reliability test.
The operator need only type a few simple commands to create the
required files. The build process proceeds automatically without
tor intervention. Procedures vary slightiy with the different
distribution media. The next three sections detail the procedures
required to build the library and SYSTST files from disk cartridge,
magtape, and DECtape.
2.2.1 SYSTST Build from DECpack
If a disk cartridge software kit is used for the system genera-
tion, mount the copy of the System Library and Reliability DECpack
on RK unit 1 and write-enable the drive. Since the system library is
initially empty, a small BASIC-PLUS program must be entered to logi-
cally mount the library disk. The procedure and program is shown
below.
CANT FIND FILE OR ACCOUNT
PROGRAM LOST - SORRY
READY
NEW MOUNT
READY
18 DIM MZCZAZ>)
28 CHANGE SYSCCHRSCEZ)+CHRS(-102)+"EYSLIB") TO Mx
28 MXCOXI=26K% : MUC1Z)=6% - MXC2M)=I7
48 MUCIUI=8% 2: MYC227)=68%: MXCZ24%)=75%
50 MUC25UI=1% : MYC26%)=255% IMXC25K)=0% IF RK UNIT @
68 CHANGE MZ TO M$
70 M$=SYSCMS>
88 END
RUNNH
READY
Now that the library pack is mounted, the general RSTS/E
library programs are loaded by typing the commands shown below.
RUN DK1:BUILD
SYSTEM BUILDER
SYSTEM BUILD? YES
SYSTEM BUILD DEVICE? DK4
Standard RSTS/E library build proceeds without operator
intervention. Many messages are printed as the programs
are compiled and stored. See Section 4.2.1.1 of the
RSTS/E System Generation Manual.
BUILD COMPLETE
READY
Finally, the SYSTST files are loaded using the TSTBLD program.
build. TSTBLD proceeds without further operator action as shown below.
RUN DK1:TSTBLD
SYSTST BUILDER
SYSTST BUILD DEVICE? DK1:
^С
HELLO
RSTS VOSB-24 TEST SYSTEM JOE 2 КЕЙ
EH 1/2
FASSNORD:
JOBS)?» 1 ARE DETACHED UNDER THIS ACCOUNT
JOB NUMBER TO RTTRCH TO*
1 OTHER USER(S» ARE LOGGED IN UNDER THIS ACCOUNT
ce-JUL-74 17:26
RERDY
OLD *DK1:
READY
COMPILE
RERDY
OLD $DK1:
READY
COMPILE
RERDY
OLD $DK1 :
RERDY
COMPILE
RERDY
OLD $DK1 :
READY
COMPILE
READY
OLD $DK1
READY
COMPILE
READY
OLD $DK1:
READY
COMPILE
READY
OLD $DK1 :
READY
COMPILE
READY
OLD $DK1
READY
COMPILE
RERDY
OLD $DK1
READY
COMPILE
OLD $DK1:
READY
COMPILE
READY
OLD $DK1
READY
COMPILE
KERDY
OLD $DK1
RERDY
COMPILE
RERDY
RUN SPIP
FIP - RSTS
CONTRL
CPEXER
DFEXER
DREXER
: DPEXER
KBEXER
DTEXER
:LPEXER
: PREXER
PPEXER
: CREXER
:MTEXER
Y85B-24 TEST SYSTEM
¥CONTRL. HLP{($DK1:CONTRL. HLF /FA
470
-
READY
These messages are printed as the
TSTBLD program loads and compiles
the SYSTST files. No operator
action is required.
Spacing has been removed t
save space. |
RUN SUTILTY
“ UTILTY” SYSTEM UTILITY FEOGRAM
? LOGINS
? °C
READY
~ С
HELLO
RSTS Y8S5B-24 TEST SYSTEM JOB 2 [1,2] KEG 22-JUL-74 17:45
JOB(S> 1 ARE DETACHED UNDER THIS ACCOUNT
JOB NUMBER TO ATTACH TO? 1
ATTACHING TO JOB 1
SYSTST BUILD COMPLETE - STARTING CONTEL
** DEVICES CONFIGURED IN RSTS YESE-24 TEST SYSTEM
TYPE COUNT EXERCISER NAME
CPU 1 CFEXER
DP 2 DFEXER
DK 2 PKEXER
KB 22 KEEXER
DT 4 DTEXER
LP 2 LFEXER
FR 1 FREXER
PP 1 PFEXER
MT 4 MTEXER
PK 4 FKEXER No pseudo keyboard (PK) exerciser exists.
RJ 1 RJEXER No 2780 (RJ) exerciser exists.
SYSTEM JOB MAX = ie
CONTROL JOB MAX = és
** JOB NAME TO START OR ATTACH 7
Now that the SYSTST control program has been initiated, the full
reliability test can be run. Chapter 3 presents guidelines for
running SYSTST and includes a comprehensive example of one such test.
2.2.2 SYSTST Build from Magtape
The procedures for building the library and SYSTST files from 7 or
9 track magtape are similar to the DECpack procedures of the previous
section. All required files are included on the System Library and
Reliability Test Tape. This tape must be mounted on magtape unit 4.
Ensure that the drive is ready and the tape is at load point. The
standard library build is initiated as shown below.
CANT FIND FILE OR ACCOUNT
FROGRAM LOST - SORRY
ba Ar ger в -t NA
READY
RUN MTO:BUILD
SYSTEM BUILDER
SYSTEM BUILD? YES
SYSTEM BUILD DEVICE? MTA
Standard RSTS/E library build proceeds without operator
intervention. Messages are printed as the programs are
compiled and stored. See Section 4.2.1.1 of the RSTS/E
System Generation Manual.
BUILD COMPLETE
READY
The SYSTST files are loaded from magtape using the TSTBLD
program. The commands shown below initiate the sequence.
RUN MTO:TSTBLO
SYSTST BUILDER
SYSTST BUILD DEVICE? MT:
Messages similar to those shown in the previous section are
printed as the SYSTST files are compiled and stored. At the end of
the build operation, the SYSTST control program is run to start the
reliability test. The message below is followed by the table of
configured devices and exerciser names as shown in the previous
section.
SYSTST BUILD COMPLETE - STARTING CONTROL
After the SYSTST control program has been initiated, the full
reliability test can be run. Chapter 3 presents guidelines for
running SYSTST and includes a comprehensive example of one such test.
2-19
2.2.3 SYSTST Build from DECtape
The library and SYSTST build sequence from DECtape is essentially
the same as from magtape except that two tapes must be used. The
first step is to mount the System Library Tape (1 of 2) on DECtape
Unit 8 and write-lock the drive. The standard library programs are
loaded as shown below.
< Continuing from START >
CAN“T FIND FILE OR ACCOUNT
PROGRAM LOST - SOFFY
READY
RUN DTO: BUILD
SYSTEM BUILDER
SYSTEM BUILD? YES
SYSTEM BUILD DEVICE? DTO
Standard RSTS/E library build proceeds without operator
intervention. Messages are printed as the programs are
compiled and stored. See Section 4.2.1.1 of the RSTS/E
System Generation Manual.
BUILD COMPLETE
READY
Now remove the tape on DECtape unit ÿ and replace it with the System
Reliability Test Tape. Ensure that the drive is write-locked and then
proceed as shown below. |
RUN DTA:TSTBLD
SYSTST BUILDER
SYSTST BUILD DEVICE? DTA:
Messages similar to those shown in Section 2.2.1 of this manual
are printed as the SYSTST files are compiled and stored. At the end
of the build operation, the SYSTST control program is run to start
the reliability test.
SYSTST BUILD COMPLETE - STARTING CONTROL
Now that the SYSTST control program has been initiated, the
full reliability test can be run. Chapter 3 presents guidelines for
running SYSTST and includes a comprehensive example of one such test.
2-21
2.3 SYSTEM GENERATION FOR FIELD INSTALLATION TESTS
The SYSTST package can be used on any RSTS/E system. The system
may be configured to customer specification for field installation
tests or for periodic reliability testing. Inclusion of the extended
mathematical functions (sine, cosine, etc.) increases the effective-
ness of the processor exerciser (CPEXER) but is not required. The
card reader exerciser (CREXER) is designed to work with a MAINDEC
punched with the DECF29 card code. If the 926 or 1481 card decode
table is used, a corresponding test deck should be punched.
CHAPTER 3
RUNNING THE SYSTEM RELIABILITY TEST
This chapter explains how to run the RSTS/E System Reliability
Test. The test consists of running several device exerciser programs
as separate jobs (called subjobs) under the supervision of the SYSTST
control program CONTRL. Section 3.1 describes CONTRL and explains
the commands used to run the test. The reliability test is primarily
intended for production use. Therefore, the example reliability test
shown in Section 3.2 shows how the test should be run in the manu-
facturing environment. The subsequent two sections detail the pro-
cedures to restart a RSTS/E test system after a normal shut down and
after a system crash. Finally Section 3.5 includes guidelines for
running the SYSTST device exerciser programs at a customer RSTS/E
site.
3.1 USING THE SYSTST CONTROL PROGRAM
The SYSTST control program allows a user to run, terminate, and
monitor many programs by means of commands typed at a single terminal.
CONTRL runs automatically upon completion of building the SYSTST files
as shown by the example in Section 2.2.1. CONTRL runs from the console
keyboard which is logged into the system under account [1,2]. However,
CONTRL may be run from any terminal as long as the terminal is logged
into the system under a privileged account. If the user desires to
use CONTRL while conducting normal time sharing operations, he can
follow the guidelines presented in Section 3.5.
When CONTRL is started, it always prints a list of devices con-
figured in the system and the name of the SYSTST device exerciser pro-
gram for each type of device. Following the list, CONTRL prints a
prompting message JOB NAME TO START OR ATTACH, after which the user
can type commands to:
a. Run SYSTST device exerciser programs and RSTS/E system
programs as subjobs under CONTRL (See Section 3.1.1).
b. Monitor the status of programs (subjobs) running under
CONTRL (See Section 3.1.2).
3-1
с. Attach subjobs to a terminal (See Section 3.1.3).
d. Perform other SYSTST control functions under normal
time sharing operations (See Section 3.1.4).
The user at the manufacturing facility need be concerned only with the
commands to run programs and monitor subjobs (Sections 3.1.1 and
3.1.2).
After the configuration information is printed, CONTRL detaches
itself from the originating terminal and communicates with the operator
at that terminal through an open file. CONTRL forms command strings
based on the characters typed in response to the JOB NAME TO START OR
ATTACH query and executes a FORCE command. The Run Time System executes
the command string passed by the FORCE command as if it were typed
at the originating terminal. Since the Run Time System may interpret
anything typed at the originating terminal as part of a forced string,
the user should not type anything at the terminal except in response
to CONTRL prompting messages or messages printed by a subjob.
The CONTRL program continuously prints its prompting message to
allow the user to start as many subjobs as needed. If a command is
not entered within 60 seconds, the CONTRL program automatically enters
monitor mode and prints status reports at 60 second intervals.
If, while running in monitor mode, CONTRL determines that a sub-
job is completed, it attaches the related exerciser to the originating
terminal. The exerciser program then prints a report of error statis-
tics and a prompting message which allows the user to rerun the subjob
or log it off the system. If no response is entered within 60 seconds,
CONTRL automatically logs the subjob off the system and prints its
prompting message again.
Any subjob which is attached to the originating terminal and
expends no CPU time for a 60-second interval is automatically logged
off the system by CONTRL. CONTRL will automatically attach exercisers
to the terminal upon completion, print the necessary status reports,
and log subjobs off the system without any user intervention. Hence,
after the operator starts a number of exercisers, he need not be pre-
sent for the reliability test to proceed.
3.1.1 Starting Subjobs
The command to start a CONTRL subjob is merely the name of the
program to be run. Although CONTRL is intended to supervise operation
of SYSTST device exercisers, any BASIC-PLUS program stored under any
account on any RSTS/E device can be run as a CONTRL subjob. If the
program to be run does not reside in the public disk structure in the
account under which CONTRL is running, either a device specification
or a project-programmer specification or both may be included in the
command to start a subjob. Commands to start a CONTRL subjob should
be entered only in response to a prompting message as shown below.
** JOB NAME TO START OR ATTACH? DPEXER Start DPEXER
** JOB NAME TO START OR ATTACH? MTS :DTCOPY [100,100] Possible
3.1.2 Monitoring Status of Subjobs
Monitor commands cause CONTRL to enter monitor mode and specify
the scope and frequency of status reports. Monitor commands must begin
with a slash (/) and can include either a program name, a job number
(preceded by a pound sign (#)) or both. A colon and a decimal integer
can follow the program name or job number. The slash causes CONTRL to
enter monitor mode. If the user types a program name following the
1 = 1 1 a dal. въ = =
5 CONTRL print dil SULJOOS witli chat name.
Tae
whe Wik bd & & , WwW AY A AN
The command /ALL causes CONTRL to print a status report of all subjobs.
Alternatively, if a job number is specified in the command, CONTRL
prints a status report of that job. A colon followed by a number in
the command designates the number of seconds between status reports.
The following examples show the use of the monitor commands.
** JOB NAME TO START OR ATTACH? / Enter Monitor Mode
** JOB NAME TO START OR ATTACH? /ALL:20 Status of all jobs every 20 seconds
** JOB NAME TO START OR ATTACH? /DPEXER One status report for all jobs
named DPEXER
** JOB NAME TO START OR ATTACH? /#20:30 Status of job #20 every 30 seconds
If CONTRL is running in monitor mode, the user can cause it to print
the JOB NAME TO START OR ATTACH query by typing the CTRL/C combination
at the terminal. He can then enter a new command.
3.1.3 Attaching Subjobs to a Terminal
The user can cause CONTRL to attach a subjob to the terminal by
typing the commercial at sign (@) followed either by the program name
(if only one copy of the program is currently running) or by a pound
sign and the job number of the subjob. As a result, CONTRL attaches
the subjob to the terminal. The user may then terminate the subjob.
The following examples show the use of the attach command.
** JOB NAME TO START OR ATTACH? @DPEXER Attach DPEXER
** JOB NAME TO START OR ATTACH? @#20 Attach job #20
** JOB NAME TO START OR ATTACH? @DPEXER#20 Redundant but legal
3.1.4 Using Additional SYSTST Commands
Two additional commands are available during the reliability
test. The 4QUIT command terminates execution of CONTRL, but does
not terminate any subjobs. If any subjobs are running when CONTRL is
terminated, they continue running detached if no other action is
taken. The second command, HELP, prints instructions on the use of
the CONTRL program. (The instructions are stored in the file,
CONTRL.HLP.) The following examples show the use of both commands.
** JOB NAME TO START OR ATTACH? {QUIT Terminates CONTRL job only
** JOB NAME TO START OR ATTACH? HELP Prints a help message
NOTE
The user enters the up arrow character (t or?*)
by typing the SHIFT key and the N key simul-
taneously on an ASR 33 type terminal or by
typing the up arrow key (1) on an LA30 or
a VTOS type terminal.
3.2 RUNNING THE SYSTEM RELIABILITY TEST
This section presents a detailed example of a reliability test
performed on a test system. The console printout generated by
running the reliability test has been edited to remove extraneous
printout, and margin notes have been added wherever they might be
helpful.
Running a reliability test involves running certain RSTS/E
system programs and relevant SYSTST device exerciser programs. The
user should consult the appropriate section of Chapter 4 for informa-
tion concerning the operation of the individual device exercisers.
RSTS/E system programs are described in the RSTS/E System Manager's
Guide.
In the reliability test shown in this example, some of the errors
reported by the exercisers were real. Other errors were forced to
demonstrate what happens when an error condition is detected. The
reliability test was limited to approximately two hours to reduce the
amount of printout for documentation purposes. It is recommended
that acceptance procedures at the DEC manufacturing facility include
approximately eight hours of continuous system operation under heavy
SYSTST load.
Upon completion of the SYSTST Build program shown in Section
2.2.1, control is automatically transferred to the SYSTST control
program, which first prints a list of devices configured in the
test system and then waits for an operator command. The user can
continue running the reliability test from that point according to
the guidelines presented in the example.
ж* DEVICES CONFIGURED IN RESTS [email protected] TEST SYSTEM
TYPE COUNT EXERCISER NAME
CPU 1 CPEXER
DP 1 DFEXER
DK 2 PKEXER
KB 32 KEEXER
DT 2 CTEXER
LP 1 LFEXER
FR 1 FRENER
FP 1 FFEXER
CR 1 CREXER
MT 3 MTEXER
PK 4 FKEXER
RJ 1 RJEXER
SYSTEM JOB MAX = 16
CONTROL JOB MAX = 13
** JOB NAME TO START CR ATTACH ? ERRCFY
** LOGGING IN NEW JCE NAMED “ERRCFY?”.
ERRCPY YO5-86
DETACHING
*+ JOB NAME TO START OR ATTACH 7 UTILTY
*+ LOGGING IN NEW JOE NAMED “UTILTY”.
“UTILTY” SYSTEM UTILTY PROGRAM
? MOUNT DK1:SYSTST
? MOUNT DPB:SYSTST
? "2
READY
BYE/F
** JOB NAME TO START OR ATTACH 7 MTEXER
** LOGGING IN NEW JOB NAMED “MTEXER-.
MT*SYSTEM CONFIGURED FOR 2 DRIVE(S).
MT»*HOW MANY DRIYES DO YOU WANT TO TEST ? 1
MTxWHICH DRIVE(S) ? 9
Insure that all console
switches are up (1's)
to enable the crash dump
automatic restart features
of RSTS/E.
No exercisers are currently
available for PK or RJ.
Always run ERRCPY as the first
control subjob if it was not
run by commands in the START.CTL
file. Error logging information
will be lost if ERRCPY is not
running.
Auxiliary (non-system) disks
must be logically mounted.
See Section 6.3 of SMG for
a description of UTILTY.
Magtape and disk exercisers
run for long periods. They
should be initiated first.
First copy of MTEXER.
HT+HOW MANY FEET OF TRFE DO YOU WANT TO WRITE ? 18 Use only a few
MTxHOW MANY REPETITIONS PER DRIVE ? 40
MT*ARE DRIVE(S) 8 MOUNTED AND W/E? YES
MT+MT EXERCISER DETACHING
feet of tape
and many iter-
ations for
interaction
tests.
AME TO START OR ATTACH
hi bi E
?
+ 5
N NEW JOB NAMED “MTES
EXER Second copy of MTEXER
>
2234
MT*SYSTEM CONFIGURED FOR % DRIVES).
MT*xHON MANY DRIYES DO YOU WANT TO TEST 7 4
MT*WHICH DRIVE(S) 7 1
MT*HOW MANY FEET OF TAPE DO YOU WANT TO WRITE ? 18
MTxHOW MANY REPETITIONS PER DRIYE 7 48
MT+ARE DRIVE(S) 1 MOUNTED AND W/E? YES
HT*MT EXERCISER DETACHING
*% JOB NAME TO START DR ATTACH 7 MTEXER Third copy of MTEXER
** LOGGING IN NEW JOB NAMED “MTEXER”.
HT*SYSTEM CONFIGURED FOR X DRIVE(S).
MT+HOW MANY DRIYES DO YOU WRNT TO TEST 7 1
MT+*WHICH DRIVE(S) 7? 2
MT+HOW MANY FEET OF TAPE DO YOU WANT TO WRITE ? 14
MT+HOW MANY REPETITIONS PER DRIVE 7 48
MT*ARE DRIVE(S) 2 MOUNTED RAND W/E? YES
MT*MT EXERCISER DETACHING
»* JOB NAME TO START OR ATTACH 7 DPEXER First copy of DPEXER
** LOGGING IN NEW JOB NAMED “DPEXER”.
DP*SYSTEM CONFIGURED FOR 1 DRIVES.
DP*xHOW MANY DRIVES DO YOU WANT TO TEST ? 1
DP*WHICH DRIVE(S) ? B
DP»xONE ITERATION ON A SINGLE RF DRIVE TAKES REOUT 4 MINUTES.
DP*HOW MANY ITERATIONS DO YOU WANT TO RUN (1-93) 7 5
DP*DP EXERCISER DETACHING
w+ JOB NAME TO START OR ATTACH 7 DFEXER Second copy of DPEXER
** LOGGING IN NEW JOB NAMED “DPEXER”.
DP*SYSTEM CONFIGURED FOR 1 DRIVES.
DP*HOW MANY DRIVES DO YOU WANT TO TEST + 1
DP*WHICH DRIVE(S) ? В |
DP*ONE ITERATION ON R SINGLE RP DRIYE TAKES AENUT 4 MINUTES.
DP*HOWN MANY ITERATIONS DO YOU WANT TO RUN (1-99) 7 5
DP*DP EXERCISER DETACHING
*% JOB NAME TO START OR ATTACH ? /ALL Frequent status reports
should be printed.
++ CONTROL JOB ENTERING MONITOR MODE.
*+ STATUS OF CONTROL SUBJOB(S) AT 49:24 AM
NAME JOB NO. STATE CPU TIME
CONTRL 1 RN 2. 7
ERRCPY 2 SL “a
MTEXER 3 RN 1:32. 7
HTEXER 4 RN 1:18. 9
HTEXER 5 RN 42. 7
DPEXER 5 RN s à
DPEXER ? RN 4. 4
"CL CTRL/C exit from monitor mode.
*% JOB NAME TO START OR ATTACH ? DKEXER
First copy of DKEXER
** LOGEING IN NEW JOB NAMED “DKEXER”.
DE*SYSTEM CONFIGURED FOR 2 DRIVES.
DKxHOW MANY DRIVES DO YOU WANT TO TEST 7 1
DK*#WHICH DRIVE(S) 7 à
DE*ONE ITERATION ON A SINGLE RK DRIYE THKES REBOUT 4 MINUTES.
DK+HOW MANY ITERATIONS DO YOU WANT TO RUN (1-99) 7 5
DK*DK EXERCISER DETACHING
** JOB NAME TO START OR ATTACH 7 DKEXER
Second copy of DKEXER
*»* LOGGING IN NEW JOB NAMEC “DKEXER”.
DK*SYSTEM CONFIGURED FOR 2 DRIVES.
DE*HON MANY DRIVES DO YOU WANT TO TEST * 1
DE*WHICH DRIVE(S) 7 1
DK*ONE ITERRTION ON A SINGLE RK DRIVE THKES HEOUT 4 MINUTES.
DK*HOW MANY ITERATIONS DO YOU WANT Td RUN (1-93) 7 5
DK#DK EXERCISER DETACHING
++ JOB NAME TO START OR ATTACH 7 DTEXER
** LOGGING IN NEW JOB NAMED “DTESER-.
DT*SYSTEM CONFIGURED FOR 2 DRIVES.
DT*HOW MANY DRIVES DO YOU WANT TO TEST >
DT*WHICH DRIYVECS) 7 B,1
DT*ARE DRIVE(S? 8,1 MOUNTED HAND W/E? TES
DT*ERROR AT LINE 134 DEVICE HUNG OR WRITE LOCKED C14-JUL-74, 09:27 AM)
fun
DT*TO CONTINUE TYPE “CONT”. TO HBORT TYPE “L°. DTP was not ready.
? CONT
DT*SYSTEM CONFIGURED FOR 2 DRIVES.
DT*HON MANY DRIYES DO YOU WANT TO TEST 7 2
DT*WHHICH DRIVE(S) 7 9,1
DT*ARE DRIYECS) 8,1 MOUNTED RAND W/E? TES
DT*DT EXERCISER DETHCHING
Two copies of DTEXER could
be run to test both drives
simultaneously.
+* JOB NAME TO START OK ATTACH 7 ALL
** CONTROL JOB ENTERING MONITOR MODE.
fui
** STATUS OF CONTROL SUEJCECS) AT 43:29 AM
NAME JOE NO. STATE CF TIME
CONTRL 1 RN 4.5
ERRCPY = SL i. A
MTEXER 3 HE 1:45. €
MTEXER 4 RN 2:13. &
MTEXER 5 RN 1:57. 7
DPEXER 5 RN É. 5
DPEXER ? RN 5. 6
DKEXER 5 RN 5. =
DKEXER 9 RN 4
DTEXER 16 DT 12. a
** REATTACHING SUBJOB MTEXER
MT+ERROR AT LINE 318 :DEYICE HUNG OR WRITE LOCKED <¿14-JUL-74, 69:28 AM>
Hardware failure caused
MT*TO CONTINUE TYPE “CONT”. TO ABEORT TYPE “no MTÿ to appear unacces-
? CONT
MT*SYSTEM CONFIGURED FOR I DRIYE(S). sible. "Device Hung"
MT*HOW MANY DRIYES DO YOU WANT TO TEST 7 4 and "Magtape Select
MT+HHICH DRIVE(S) ? B érrors are most likely
MT*HOW MANY FEET OF TAPE DO YOU WANT TO WRITE 7 4g tO occur when running
MT*HOW MANY REFETITIONS FER DRIVE 7 48 several drives simul-
MT+ARE DRIVE(S) 8 MOUNTED RAND W/E? VES Pony Ly. More on
MT+MT EXERCISER DETACHING type under heavy SYSIST
load usually indicates
| that drives or control-
** JOB NAME TO START OR ATTACH 7 CPEXER ler are not up to cur-
** LOGGING IN NEW JOB NAMED *CPEXER”. rent ECO level. Consult
PDP-11 engineering.
CP*XSTARTING CPU/EIS/FIS/FPP EXERCISER
CP+ARE YOU CONFIGURED FOR EXTENDED FUNCTIONS ? HELF
CP*DURING THE RSTS/E SYSTEM GENERATION. YOU WERE RSKED WHETHER
CP+OR NOT THIS SYSTEM REQUIRED THE EXTENDED MATHEMATICAL FUNCTIONS
CP+(SINE. COSINE. ETC.). IF YO ANSWERED “YES” TO “FUNCTIONS? AT
CP+SYSGEN TIME. THEN REPLY “YES” TO THE QUERY BELOW. IF YOU
CP*ANSNERED “NO” AT SYSGEN, THEN YoU ARE NOT CONFIGURED FOR THE
CP*EXTENDED FUNCTIONS AND YOU SHOULD ANSHER “NO” BELOW. IF YOU ARE
CP*+UNSURE. THEN ANSWER “YES” AND I! WILL TRY Tn USE ONE OF THE
CP*EXTENDED FUNCTIONS. IF THE OPERATION FAILS. AN ERROR MESSAGE
CP+WILL BE PRINTED AND THIS EXERCISER WILL ABORT. SHOULD THAT
CP*DCCUR, SIMPLY TYPE “RUNMNH’ TO RERUN CFEXER AND REPLY “NO”
CP*WHEN AGAIN ASKED IF YOU ARE CONFIGURED FOR EXTENDED FUNCTIONS.
CP*ARE YOU CONFIGURED FOR EXTENDED FUNCTIONS ? YES
CP*ERCH ITERATION TRKES ABOUT 2 MINUTES
CP*HOW MANY ITERATIONS DO YOU WANT TO RUN 7 18
CP+CP EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? /ALL:60
#% CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB(S) AT 99:26 AM
NAME JOB NO. STATE CFU TIME
CONTRL 1 RN 11.5
ERRCPY 2 SL sa
MTEXER 2 RN X:87. 4
MTEXER 4 RN 2:48. 2
MTEXER > RN 2:24. 2
DPEXER 6 RN 5.0
DPEXER ? RN 6.7
DKEXER 8 RN 6. 1
DKEXER 9 RN 5.8
DTEXER 18 RN 1:59.6
CPEXER 11 RN 4. 1
** JOB NAME TO START OR ATTACH 7 FREXER CU If a paper tape punch is con-
PPEXER nected, the punch exerciser
wx LOGGING IN NEW JOE NAME “PREXER”. should be run before the
reader exerciser.
PPxSTARTING PP EXERCISER, FPP READY 7 YES
PP»*THIS TEST WILL FUNCH AR EBINARY COUNT PATTERN TAFE.
PP+THE TAPE 1S EQUIYALENT TD MAINDEC-99-D254-PT ENTITLED
PPxSPECIAL BINARY COUNT PRTTERN TAPE. EITHER THE THFE
PP*PUNCHED BY THIS EXERCISER OR THE SUPPLIED MAINDEC
PP+TAPE MAY BE USED TO TEST THE FAPER TAFE RERDER.
PPxI WILL PUNCH A LEADER AND THEN SLEEF 38 SECONDS
PP*WHILE YOU STRAIGHTEN OUT THE TAPE IN THE HOFFER.
PP*PP EXERCISER DETRCHING
** JOB NAME TO START OR ATTACH 7
** CONTROL JOB ENTERING MONITOR MODE.
** REATTACHING SUBJOE PPEXER
PP*PP EXERCISER DONE
PF+NON USE THE GENERATED TAPE TO TEST THE REHDER
PP+TO REATTACH TO CONTROL ТУРЕ “ВУЕ” ТО КЕКОМ ТУРЕ
READY
EVE/F
Tape punched is about
two inches thick so
there may be a stacking
problem.
“ RUNNH-.
#% JOB NAME TO START OR RTTACH ? FREXER
** LOGGING IN NEW JOB NAMED “PREXER”
PR*STARTING PR EXERCISER.
PR+LORD MAINDEC-98-D2G4-PT OR THE BINARY COUNT PATTERN
PR+TAPE GENERATED BY THE PUNCH EXERCISER INTO THE READER
PR*WITH THE LEADER UNDER THE READ STATION. RERDER RERDY 7 YES
PR*PR EXERCISER DETRCHING
Control job entered monitor
mode automatically after
waiting one minute for an
+* STATUS OF CONTROL SUBJOB(S) AT 89:47 AM ©Pérâtor command.
** JOB NAME TO START OR ATTACH 7
** CONTROL JOB ENTERING MONITOR MODE.
NAME JOB NO. STATE CPU TIME
CONTRL 1 RN eu. 9
ERRCPY 2 SL Su “0
MTEXER 3 RN 4:83. 5
MTEXER 4 RN 2:85. 7
MTEXER > RN 4:0%7.5
DPEXER 6 RN 9.5
DPEXER 7 RN 5. 1
DKEXER 8 RN 7.3
DKEXER 9 RN 6. 5
DTEXER 19 RN 4:27. 3
CPEXER 11 HB 1:85. 2
PREXER 12 RN 16. 8
*+ RERTTACHING SUBJOB CPEXER
CP#CPU/EIS/FIS/FPP EXERCISER DONE. TOTAL OF @ ERRORS DETECTED
CP*TO REATTACH TO CONTROL TYPE “BYE”. TO RERUN TYPE +“ RUNNH”.
If any errors are reported
by CPEXER, you may have
flaky CPU, EIS, FIS, FPP,
memory or UNIBUS.
READY
RUNNH
CP*STARTING CPU/EIS/FIS/FPP EXERCISER
CP+ARE YOU CONFIGURED FOR EXTENDED FUNCTIONS 7 YES
CP+EACH ITERATION TRKES ABOUT 2 MINUTES
CP+*HOW MANY ITERATIONS DO YOU WANT TO RUN 7 20
CPxCP EXERCISER DETACHING
3-11
++ JOB NAME TO START OR RTTACH 7 FRESER
++ CONTROL JOB ENTERING MONITOR MODE.
*% STATUS OF CONTROL SUBJOB(S) AT 49:45 AM
NAME JOB NO. STATE CALI TIME
PREXER 12 HE 16.3
ж* REATTACHING SUBJOE FPREXER
Reader jammed due to
PR+* INCORRECT NUMBER OF FANFOLDS ON PR poor mechanical ad-
justment.
PRESTARTING PR EXERCISER |
PR+LOHD MAINDEC-BÉ-CDEG4-FT OUR THE BINARY COUNT FATTERN
PRETAFPE GENERATED EY THE FUNCH ExERCIZER INTO THE READER
PR+NITH THE LERCER UNDER THE READ STATION. RERDER RERDY 7 YES
PR+*PR EXERCISER DETACHING
** JOB NAME TO START CR ATTACH + LFEXER
sek LOGGING IN NEW JOE NAME “LFEXER"
LP*SYSTEM CONFIGURED FOR 1 PRINTER(SO.
LP»XxHON MANY PRINTERS DO TOU WANT TO TEST 7 1
LP+TYPE UNIT $75 OF PRINTER(Z) TO BE TESTED + 4
LPxARE PRINTERCS) E ONLINE AND RERDY? YES
LP*HOW MANY FAGES OF OUTFUT DO TON WANT? 26
LP+LP EXERCISER DETACHING.
** JOB NAME TO START OR ATTACH 7 CREXER
** LOGGING IN NEW JOB NAME “CREXER" Just wait for any
*ж* CONTROL JOB LIMIT EXCEEDED ~ CANNOT START NEW JOE exerciser to finish.
** JOB NAME TO START OR ATTACH 7? /ALL:&M
*+ CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUEJDECS) AT 05:52 HM
NAME JOB NO. STATE CPU TIME
CONTRL 1 EN 25. 5
ERRCPY e SL au
МТЕХЕК 3 RN 4:28. 7
MTEXER 4 HB 5H £:11.14
MTEXER 5 RN 4:55. £
DPEXER 6 DF 18. 1
DPEXER 7 RN >. 2
DKEXER 3 RN 7.5
DKEXER 3 RN 7.2
DTEXER 19 RN 27.7
CPEXER 11 SL 1:25.6
PREXER 12 RN 35.6
LPEXER 1 KN 28. 1
** REATTACHING SUBJOB MTEXER
3-12
MHT*MT EXERCISER DONE FOR DRIVE(S) :1
MT*TO REATTRCH TO CONTROL TYFE EYE‘, TD KERUN TYPE 7 RUNNH”.
READY
RUNNH
MT*SYSTEM CONFIGURED FOR % DRIVE(S).
HT+HOKW MANY DRIVES DO YOU WANT TO TEST 7 1
MT*WHICH DRIVE(S) 7 1
HT+HOW MANY FEET OF TAFE DO YOU WANT TO WRITE + 186 Use lots of tape and
HTxHOW MANY REPETITIONS FER DRIME 7 4 few iterations for
MT*ARE DRIVE(S? 1 MOUNTED AND WET YES ~ data integrity test.
MT+MT EXERCISER DETACHING
xx JOB NAME TO START OR ATTACH + y
*% CONTROL JOB ENTERING MONITOR MODE.
** REATTACHING SUBJOE PREXER
PR»xPREXER DONE, ERROR COUNT= 5
PR*xTO RERTTACH TO CONTROL TYPE “BYE”. TO RERUN TYPE “ RUNNH“
READY
** РКЕХЕК WRIT EXHAUSTED. Operator did not respond
*#* CONTROL TERMINATING JOB #12 FREXER within one minute so
ner CONTRL killed this job.
EYE/F$
READY
** JOB NAME TO START OR ATTACH 7? CREXER
** LOGGING IN NEW JOB NAMED “CREXER”
CR*STARTING CARD READER EXERCISER.
CR*LOAD MAINDEC-89-D181-C LABELLED “ALPHA CARD DECK” INTO THE
CReREADER. THE DECK WILL EE READ AND YERIFIED. IF ANY ERRORS ARE
CR*DETECTED, THE EXPECTED AND ACTUAL CONTENTS OF THE ERD CARD
CR+HILL BE RECORDED IN A DISK FILE FOR LATER PRINTING ON EITHER
CR*THE CONSOLE TERMINAL OR THE LINE PRINTER. CARDS WILL BE READ
CR»xUNTIL END OF FILE OR HOPPER EMPTY 15 DETECTED. SEVERAL COPIES
CR»x0F THE MAINDEC MAY BE STACKED FOR A MORE THOROUGH TEST.
CR*CARD READER READY 7 YES
CR*CARD READER EXERCISER DETACHING
** JOB NAME TO START OR ATTACH 7 ARLL
*»* CONTROL JOB ENTERING MONITOR MODE.
+» STATUS OF CONTROL SUEJUECS) AT 14:44 AM
NAME JOE NOD. STATE CPU TIME
CONTRL 1 RN 5. =
ERRCPY 2 SL я. я
MTEXER + RN 4:47. 4
МТЕХЕК 4 RN 5:44. 2
МТЕХЕК 5 RN 2:15. 4
DPEXER 6 RN 13. 9
DPEXER 7 RN Эх
DKEXER 8 RN 5.6
DKEXER = EN 5.1
DTEXER 18 HE 5:24.5
CPEXER 11 RN 2:31. 8
CREXER 12 RN “os
LPEXER 13 RN E. x
** REATTACHING SUBJOS DTEXER
„=,
т = ki Га
y
E. от ee, vers h m.
VU TETU EACKRL ISE E vr
DUNE Fü E
DT*TO REATTACH TO CONTROL ТУРЕ
EVE”, TO RERUN TYPE “RUNNH-
READY
EvE/F
** JOB NAME TO START OR ATTACH 7 /
** CONTROL JOB ENTERING MONITOR MODE.
*% REATTACHING SUBJOB CREXER
CR*DUT OF 640 CARDS READ. ERRORS WERE DETECTED ON i CARDS.
CR*TYPE “LP:7 TO LIST ERRORS ON THE LINE PRINTER ОВ ТУРЕ “KE:
CR»*xTO LIST ERRORS ON THIS KEYECARD. This error was forced
for demonstration purposes.
CR*YOUR LISTING DEVICE 7 KB:
CARD 85 EXPECTED : DEFGHILC. <(+!—-JKLMNOPER $+); "B/STUVWRYZ\, 2.27 12345578
9:82 ="&RBCDEFGHIL. {({(+!&ABC
CARD 85 ACTUAL : DEF&HIE. CC+!-JKLMNOFER 1$%); "B/STUYWXYZN. X_>7 12345678
9: HO ="4RBCDEFGHIL. <+!4ABL
Note that the letter G (12-7 punch) was changed to
& (12 punch). This may be just dust on the read
head or marginal operation of the photo-sensor for
row 7.
CR*CARD READER EXERCISER DONE.
CR*TO REATTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “RUNNH-.
RERDY
BYE/F
** JOB NAME TO STRRT OR ATTACH ? /
*% CONTROL JOB ENTERING MONITOR MODE.
*+ REATTACHING SUBJOB LPEXER
LP+LINE PRINTER EXERCISER DONE
P+TO REATTACH TO CONTROL TYPE “BYE”. TO RERUN TYPE “RUNNH-.
READY
BYE /F
ж* JOB NAME TO START OR ATTACH 7? /ALL
*+ CONTROL JOB ENTERING MONITOR MODE.
++ STATUS OF CONTROL SUBJOECS) AT 18:18 AM
NAME JOB NO. STATE CPJ TIME
CONTRL 1 RN 35. 6
ERRCPY - 2 SL SH 8.8
MTEXER 3 HE 2:15. 2
HTEXER 4 RN 7:22. 2
МТЕХЕК 3 RN 5:25. 6
DPEXER 6 RN 11. 7
DPEXER RN 9.9
DKEXER 8 RN 9.3
DKEXER 9 RN 2.8
CPEXER 11 HB 3:82. 4
*# REATTACHING SUBJDB MTEXER
MT*MT EXERCISER DONE FOR DRIYE(S):8
MT»*TO REATTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “ RUNNH”.
READY
RUNNH
MT*SYSTEM CONFIGURED FOR 3 DRIYE(S).
MT*HOW MANY DRIYES DO YOU WANT TO TEST ? 1
HT*WHICH DRIVE(S) 7 8
MT+HOW MANY FEET OF TAPE DO YOU WANT TO WRITE ? 188
MT*HOW MANY REPETITIONS PER DRIVE 7 4
MT*ARE DRIVE(S) 8 MOUNTED AND W/E? YES
MT+MT EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? /
** CONTROL JOB ENTERING MONITOR MODE.
»* REATTACHING SUBJOB CPEXER
3-15
CP*CPU/EIS/FIS/FPP EXERCISER DONE. TOTAL OF 8 ERRORS DETECTED
CP]TO REATTACH TO CONTROL TYPE “BYE”. TO RERUN TYPE 7 RUNNH”.
READY
RUNNH
CP*STARTING CPU/EIS/FIS/FPP EXERCISER
CP*RRE YOU CONFIGURED FOR EXTENDED FUNCTIONS ? YES
CP»xERCH ITERATION TAKES ABOUT 2 MINUTES
CP»HOW MANY ITERATIONS DO YOU WANT TO RUN 7 26
CP*CP EXERCISER DETRCHING
** JOB NAME TO START OR ATTACH + KEEXER See KBEXER abstract
** LOGGING IN NEN JOB NAMED “KBEXER”. in Chapter 4.
L/ [30 + MEUDNODN EYEDAICED
IN 7 + Tx ha §| Ww .
189 Er 7 Phew" & E A
KBB * SYSTEM IS CONFIGURED FOR €%2 TERMINAL: (KES - KES1 ›
>
ox
*
ENTER TEST NAME OR TRANSFER COMMAND: /KB1:
INVALID KEYBOARD NUMBER - TRY AGAIN.
x
x
ua
+
KBB
KBB
кВа
KBB
ENTER TEST NAME OR TRANSFER COMMAND: 7KE1
KEYBORRD EXERCISER TRANSFERRING FROM [email protected] TO KEL
PLEASE ENTER SUBSEGRUENT COMMANDS FROM KB1
KEYBORRD EXERCISER DETACHING
* E * *
Keyboard tests can be performed on KBl while continuing with
normal SYSTST operation from KBQ.
** JOB NAME TO START OR ATTACH 7 /HLL
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOE(S) AT 18:16 AM
NAME JOB NO. STATE CPU TIME
CONTRL 1 RN 48. 5
ERRCPY 2 SL SH a. в
MTEXER 3 RN 2:49. 7
MTEXER 4 RN 9:18. 5
MTEXER > KN 5:44. 7
DPEXER 6 RN 12. 2
DPEXER 7 RN 14.5
DKEXER 5 RN 9.6
DKEXER 9 RN 3.4
KBEXER 18 TT 1. 2
CPEXER 11 RN T:25.6
~C
3-16
** JOB NAME TO START OR ATTACH ? KBEXER
** LOGGING IN NEW JOB NAMED “KBEXER“.
Second copy of KBEXER
RUN KBEXER
KBB * KEYBORRD EXERCISER
KBB * SYSTEM IS CONFIGURED FOR 32 TERMINALS (KE4 - KEIL )
KBO + ENTER TEST NAME OR TRANSFER COMMAND: ASCII This KBEXER will check
the console keyboard before
KBB * ROTATING ASCII CHARACTERS TEST being transferred to
another terminal.
UNSART Cd+, -. /01273456789:: C=>7GABCDEFGHIJKLMNOPSRSTUYHSTZES 77. 1 U# 57e"
” "RSE? Cx+,-. /0123456799 :; <=>?WABCDEFGHI JKLMNO PARSTU HZ Y 2 NI. 1"RS74
ES !"#$2087 E4.—. 70123456739: ; <=) ?0ABCDEFGHIJEKLMNOFCRSTUYWSYZO 1. tag
AR TYRELL Ct, 701224567893: ; <=) ?0ABCDEFGHIJKLMNOFERS TIUYWRyZ END "a
BAR 1 UNSAA CE, —. 78123456739: ; <=) ?0ABCDEFGHIJKLMNOFERSTUYWSYZO NI". 1"4
#308” "BESA C)I*x+,-. 70127456789 :;: TL
[email protected] * ENTER TEST NAME OF TRANSFER COMMAND: REPEAT
KBB * REPEAT TEST
? ABCDEFGHIJKLMNOPRRSTUYWAYZ1234567390
? ABCDEFGHIJKLMNOFERSTUYWXZ1224567598
? °C
KBB * ENTER TEST NAME OR TRANSFER COMMAND: WORST
[email protected] * ROTRTING WORST CASE (RSR3X) PATTERN TEST
CWT WAT WT W27 WA NZ WZ HZ 677 27 677 WS WY WY WZ WY We WY
TWAT WT WT WT CW WY WZ WS WY WY WY WS WY WY WY WY WA MW
NN WWW 477 WW WY LW WZ WY WY WY WT WT WY WY
“WT WS LWT WT CW ЗЫ WA CW WY WTC
KBB * ENTER TEST NAME OR TRANSFER COMMAND: P\P“\SPRCE
KBB * SPACING TEST
KBB * ENTER TEST NAME OR TRANSFER COMMAND: /KB2
KBB »* KEYBOARD EXERCISER TRANSFERRING FROM KB8 TO KB2
{BO * PLEASE ENTER SUBSEQUENT COMMANDS FROM KBZ2
[email protected] + KEYBOARD EXERCISER DETACHING.
3-17
** JOB NAME TO START OR ATTACH ? /ALL:68
++ CONTROL JOB ENTERING MONITOR MODE.
*4* STATUS OF CONTROL SUBJDB(S) AT 18:21 AM
NAME JOB NO. STRTE CPU TIME
CONTRL 1 RN 45. 4
ERRCPY 2 sL su a
MTEXER 3 RN 7:27. 2
MTEXER 4 RN 10:19. 4
MTEXER > RN 53:49. 7
DPEXER 5 RN 12.6
DPEXER 7 RN 11. 1
DKEXER 8 RN 18. 8
DKEXER 9 RN 18.8
KBEXER 19 TT <. 8
CPEXER 11 SL 4:09. 7
KBEXER 12 TT 18. 2
** REATTACHING SUBJDE MTEXER
MT»*xMT EXERCISER DONE FOR DRIYECS):2
MT+TO REATTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE 7 RUNNK”.
READY
RUNNH
MT*SYSTEM CONFIGURED FOR 2 DRIVE(S).
MT*HOW MANY DRIVES DO YOU WANT TO TEST ? 1
MT*WHICH DRIVE(S) 7 2
MT*HOW MANY FEET OF TAPE DO YOU WANT TO WRITE 7? 188
MT*HOW MANY REPETITIONS PER DRIVE ? 4
MT*ARE DRIVE(S) 2 MOUNTED AND W/E? YES
МТ*МТ EXERCISER DETRCHING
** JOB NAME TO START OR ATTACH 7? /
** CONTROL JOB ENTERING MONITOR MODE. Eo CONTROL Er ansTerred back
** REATTACHING SUBJOB KBEXER y
/CONTROL command.
KB8 * KEYBOARD EXERCISER
KBB * SYSTEM 1S CONFIGURED FOR 22 TERMINALS <KB8 - KBZ1 )
KBB * ENTER TEST NAME OR TRANSFER COMMAND: “C
READY
BYE/F
3-18
** JOB NAME TO START OR ATTACH 7 /
** CONTROL JOB ENTERING MONITOR MODE. Same here for the
** REATTACHING SUBJOB KBEXER second KBEXER.
KEO * KEYBORRD EXERCISER
KBB * SYSTEM IS CONFIGURED FOR 22 TERMINALS CKEB - KBZ1 )
KEB x ENTER TEST NAME OR TRANSFER COMMAND: SE
READY
BYE/F
** JOB NAME TO START OR ATTACH *
*% CONTROL JOB ENTERING MONITOR MODE.
+* STATUS OF CONTROL SUBJOB(S) AT 18:27 AM
NAME JOB NO. STATE CPU TIME
CONTRL 1 RN 493.6
ERRCPY 2 SL à
МТЕХЕК 3 RN 9:16. 5
MTEXER 4 RN 11:25. 4
MTEXER 3 RN 2:36. 7
DPEXER 6 RN 13. 2
DPEXER 7 RN 12.8
DKEXER 5 RN 14. 4
DKEXER 9 RN 10. 9
CPEXER 11 SL 4:46 2
^С
+ та. wash AN a — an mh dn am Ee Sm
*% JOB NAME TO START OR ATTACH 7? ERRDIS May be helpful to get an error
*% LOGGING IN NEW JOB NAMED “ERRDIS“. logging summary about half way
through the SYSTST run. See
description of ERRDIS in
ERRDIS Y5B-11 Section 6.1.3 of SMG.
INPUT FILE <<CR> FOR DEFAULT>7
OUTPUT ТО? KB:
OPTIONS? ALL/S
OFTIONS: RLL/S
FILE: SERRLOG. FIL This option lists a break-
OUTPUT: KB: down of errors by type.
AT: 18:28:21 AM, 14-JUL-74
DECTAPE ERRORS See more specific
12 analysis below.
3-19
RF11 ERRORS
a
RE11 ERRORS
a
RK11 ERRORS
a
RP11 ERRORS
8
MAGTAPE ERRORS
a
HUNG TTY ERRORS
32
TRAP THROUGH 4 ERRORS
В
PONER FAIL ERRORS
8
TRAP THROUGH 8 ERRORS
9
RESERVED INSTRUCTION ERRORS
9
JUMP TO ZERO ERRORS
В
CHECK-SUM ERRORS
В
MEMORY MANAGEMENT ERRORS
в
DH11 ERRORS
В
MEMORY PRRITY ERRORS
9
More than 1 or 2 disk errors
in a period of 2-3 hours is
indicative of disk problems.
Seek errors will show up
here but are usually recov-
erable by the system's
retrying of the operation.
Magtape parity errors are to
be expected, but excessive
errors may mean intermittent
controller, drive, or head
problems.
Excessive HUNG TTY errors
indicate terminal interface
problems. See analysis at
end of this SYSTST run.
Should not occur.
Should not occur.
Excessive UNIBUS noise and
flaky BUS repeater can cause
traps through O.
Should not occur.
Should not occur.
Can be caused by disk or
memory errors.
Should not occur. May
signal KTll problems.
Should not occur.
Memory parity errors may or
may not crash RSTS/E
depending on where they occur.
44 ERRORS LISTED OUT OF 44 LOGGED SINCE 99:12:64 AM. 14-JUL-74
OPTIONS? DT
OPTIONS:
FILE:
11 =".
QUTFUT:
AT:
DECTAPE ERROR AT 99:27:13
REPERT COUNT WAS 11 BY 89:27:14 AN.
TCST:
TCCH :
TCHC :
TCBA:
TCDT:
DT
SERRLOG. FIL
KB:
19:22:14 AM, 14-JUL-74
AH, 14-JUL -74
3904834
199382
177480
929008
238800
14-JUL-74
For a complete listing
of DECtape errors.
Note that time corre-
sponds to time printed
when error was reported
by DTEXER.
Selection error,
Unit g,
Errors were caused by the 12
normal retries of DECtape
operation when drive was
offline - can be ignored,
12 ERRORS LISTED OUT OF 44 LOGGED SINCE 99:12:44 AM. 14-JUL-74
OPTIONS? “Z
READY
BYE/F
** JOB NAME TO START OR ATTACH 7 ALL:129
ILLEGAL FILE NAME
JOB NAME TO START OR ATTACH ? /ALL:128
>»
ok
ak
ЖЖ
NAME
CONTRL
ERRCPY
MTEXER
MTEXER
MTEXER
DPEXER
DPEXER
DKEXER
DKEXER
EPEXER
CONTROL JOB ENTERING MONITOR MODE.
JOB NO.
0 O Ch SUN EH
A
=
11
** RERTTACHING SUBJOB MTEXER
STATUS OF CONTROL SUBJOB(S) RT 18:32 AM
CPU
Operator error.
TIME
5х.
18:58.
12:36.
7:17.
1%.
12.
11.
NOIRE IAD
MT*MT 2 ERROR AT LINE 348 :MAGTAPE SELECT ERROR (14-JUL-74, 10:24 AM)
MT+MAGTAPE STATUS SUMMARY
MT*LAST COMMAND WAS WRITE
NT +
MT»
МТ»
МТ»
MT»
DENSITY PARITY TRACKS
3 ODD 9
N-LOCK EOT BOT EOF
NO NO NO NO
SELECTION ERROR OCCURED
3-21
RLE
NO
This error was forced by
switching drive offline,
Error status summary will pe
printed if MTEXER has a test
file open at the time of the
error.
MT*TO CONTINUE TYPE “CONT”. TO ABORT TYFE “LC”.
? CONT
MT*SYSTEM CONFIGURED FOR + DRIYEC(S).
MT*xHOW MANY DRIVES DO YOU WANT TO TEST ? 1
HT*WHICH DRIVE(S) ? €
MT»xHOW MANY FEET OF TAFE DO YOU WANT TO WRITE 7 188
MT*ARE DRIVE(S) 2 MOUNTED AND W2E? YES
MT+MT EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? Y
** CONTROL JOB ENTERING MONITOR MODE.
** REATTACHING SUBJOB DFEXER
DP*DPEXER ERROR STATISTICS FOR DP B
DRIVE PASS FILE SIZE ERROR COUNT
DP 8 1 400 a
DP B 2 498 я
DP 8 3 448 В
DP 8 4 480 U
DP 8 3 490 в
DPX»xDP EXERCISER DONE
See discussion
of disk errors
in Section 4.1
of the manual.
DP*TO REATTACH TO CONTROL TYPE “BYE”. TO RERUN TYFE “RUNNH'.
READY
EYE/F
**% JOB NAME TO START OR ATTACH ?
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOEC(S) AT 18:37 AM
NAME JOB NO. STATE CPU TIME
CONTRL 1 RN 55.6
ERREPY 2 SL a. 8
MTEXER 3 RN 12:84. 2
MTEXER 4 RN 12:27. 2
MTEXER 3 RN 7:51. 7
DPEXER 7 HB 13.1
DKEXER 3 RN 11. 2
DKEXER 9 RN 12.8
CPEXER 11 HB 5:58. 8
** REATTACHING SUBJOB DPEXER
DRIVE PASS FILE SIZE ERROR COUNT
DP 8 1 490 a
DP 8 2 488 a
DP 8 3 488 a
DP 8 4 499 a
DP 8 5 408 8
DP*DP EXERCISER DONE
DP*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “RUNNH-.
READY
BYE/F |
»* JOB NAME TO START OR ATTACH ? /
** CONTROL JOB ENTERING MONITOR MODE.
** REATTACHING SUBJOB CPEXER
CP*CPU/EIS/FIS/FPP EXERCISER DONE. TOTAL OF @ ERRORS DETECTED
CP*XTO RERTTACH TO CONTROL TYPE “BYE”, TO ВЕКОМ TYPE “ RUNNH”.
READY
BYE/F
#*% JOB NAME TO START OR RTTACH ? DFEXER
»+ LOGGING IN NEW JOB NAMED “DFEXER-.
DF*SYSTEM IS EITHER NOT CONFIGURED FOR AN RF DISK — DFEXER is useful
DF»OR THE RF DISK 1S CONFIGURED AS À SWRPFING DISK. if RF is the
DF*DFEXER CANNOT BE USED UNDER THESE CIRCUMSTANCES. system disk.
DF*TYPE “BYE” TO RERTTACH TO CONTROL.
READY
BYE/F
wx JOB NAME TO START OR ATTACH 7 /
%% CONTROL JOB ENTERING MONITOR MODE.
** REATTACHING SUBJOB MTEXER
MT*MT EXERCISER DONE FOR DRIYE(S):1
MT»*TO REATTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE * RUNNH”.
READY
** МТЕХЕК WRIT EXHRUSTED.
»* CONTROL TERMINATING JOB #4 MTEXER
ABC
EYE/FS
READY
3-23
** JOB NAME TO START OR ATTACH >?
** CONTROL JOB ENTERING MONITOR MODE.
++ STATUS OF CONTROL SUBJOB(S) AT 18:51 AM
NAME JOB NO. STATE CPU TIME
CONTRL 1 RN 1:85. 8
ERRCPY 2 SL 8.9
MTEXER 3 RN 15:56. 9
MTEXER 5 RN 12:16. 2
DKEXER 8 RN 12. 6
DKEXER 9 RN 13.6
** REATTACHING SUBJOB DKEXER
DK*DKEXER ERROR STATISTICS FOR DK @
DRIVE PASS FILE SIZE ERROR COUNT
DK 8 1 448 a
DK 8 2 400 й
DK 8 3 490 я
DK 8 4 400 в
DK © 5 400 a
DK*DK EXERCISER DONE |
DK*TO REATTACH TO CONTROL TYPE “BYE”. TO RERUN TYPE 7 RUNNH”.
READY
** DKEXER WRIT EXHRUSTED.
*#% CONTROL TERMINRTING JOB #2 DKEXER
EC
BYE/FS
READY
*# JOB NAME TO START OR ATTACH 7 /
»* CONTROL JOE ENTERING MONITOR MODE.
#»% RERTTACHING SUBJOB DKEXER.
DK*DKEXER ERROR STATISTICS FOR DK 1
DRIVE PASS FILE SIZE ERROR COUNT
DK 1 1 498 в
DK 1 2 490 я
DK 1 3 409 a
DK 1 4 498 я
DK 1 5 498 3
DK*DK EXERCISER DONE
DK*TO REATTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE 7 RUNNH”.
READY
BYE/F
** JOB NAME TO START OR ATTACH 7
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOBCS) AT 18:57 AM
NAME JOB NO. STATE
CONTRL 1 RN
ERRCPY 2 SL
MTEXER 3 HB
MTEXER > MT
MT*MT EXERCISER DONE FOR DRIYE(S):8
CPU TIM
46:35.
15:49,
= -
We NM
MT*TO RERTTACH TO CONTROL TYPE “BYE”. TO RERUN TYPE “ RUNNH”.
READY
ВЕЧЕР
** JOB NAME TO START OR ATTACH. ? Y
** CONTROL JOB ENTERING MONITOR MODE.
*+ REATTACHING SUBJOB MTEXER
MT*MT EXERCISER DONE FOR DRIVYE(S):2
MT*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYFE * RUNNH”.
READY
++ MTEXER WAIT EXHAUSTED.
++ CONTROL TERMINATING JOB #5 MTEXER
E
EYE/FS
READY
** JOB NAME TO START OR ATTACH ?
»* CONTROL JOB ENTERING MONITOR MODE.
x* STATUS OF CONTROL SUBJOB(S) RT 11:88 AM
NAME JOB NO. STRTE
CONTRL 1 RN
ERRCPY 2 SL
** STATUS OF CONTROL SUBJOB(S) AT 11:81 AM
NAME JOB NO. STATE
CONTRL 1 RN
ERRCPY 2 SL
3-25
CPU TIME
1:95. 8
8.49
CPU TIME
1:89. 4
8.9
All exercisers
have terminated.
>C
** JOB NAME TO START OR ATTACH 7? ERRDIS Now is the time to list a
»* LOGGING IN NEW JOB NAME “ERRDIS”. full errlog report.
RUN ERRDIS
ERRDIS YSE-11
INPUT FILE <<CRb> FOR DEFAULT)?
OUTPUT TO? KB:
OPTIONS? ALL
HUNG TTY ERROR АТ 03:12:04 AM, 14-JUL-74 RSTS/E reenables hung TFY's
REPEAT COUNT HAS 1 BY 89:12:52 AM, 14-JUL-74 so these errors are not
serious. The terminal
KBW: 3 interface should be replaced
#CSR : 177564 if errors on any one keyboard
CSR: 5998909 are excessive. (e.g., KB9
READY BIT NOT SET on this machine is not in
good shape.)
HUNG TTY ERROR RT 89:16:26 AM, 14-JUL-74
REPERT COUNT WAS 1 BY 89:17:16 AM, 14-JUL-r4
HBH: a
HCSR : 177564
CSR: 903003
READY BIT NOT SET
DECTAPE ERROR AT 99:27:13 AM, 14-JUL-74
REPEAT COUNT WAS 11 BY 99:27:14 AM. 14-JUL-74
See comments on
TEST: 99484 previous printout.
TECM: 199382
TENC: 177488
TCBA: 920006
TCDT: gagOgg
Additional printouts of
HUNG TTY errors have
been deleted. Most were
KBÿ hangs.
HUNG TTY ERROR AT 18:53:17 AM. 14-JUL-74
JOB# : 3
KB# : 19
HESR: 176618
CSR: 8040090
INT. ENE. BIT NOT SET
46 ERRORS LISTED OUT OF 46 LOGGED SINCE 19:12:94 AM. 14-JUL-74
OPTIONS? KILL
This deletes the current
READY errlog file.
EYEAF
»* JOB NAME TO START OR ATTACH 7? SHUTUP
#% LOGGING IN NEW JOB NAMED “SHUTUP-.
— ae we a vv CE CA
AUTOMATIC SYSTEM SHUTDOWN PROGRAM
HOW MANY MINUTES UNTIL SYSTEM SHUTDOWN? 1
HOW MANY MINUTES BETWEEN WARNING MESSAGES? 1
1 MINUTE WARNING MESSAGE SENT
FURTHER LOGINS ARE NOW DISABLED
FINAL WARNING MESSAGE SENT
PASS 1 OF LODKING FOR STILL ACTIVE JOBS
JOB 1 FOUND STILL ACTIVE AND DETACHED
THE NEXT PASS WILL OCCUR IN 15 SECONDS
PRSS 2 OF LOOKING FOR STILL ACTIVE JUBS
NON-SYSTEM DISKS WILL NOW BE DISMOLNTED
DISK DK1 FOUND STILL MONNTED
DISK IS NON DISMOUNTED
DISK DPB FOUND STILL MONNTED
DISK 1S NOW DISMOUNTED
ALL NON-SYSTEM DISKS ARE NOW DISMOUNTED
ALL SET TO PROCEED WITH SYSTEM SHUTDOWN
FLEASE WAIT FOR THE COMPUTER TO ACTUALLY “HALT”
Disk structures may be
destroyed if system is
not taken down by
running SHUTUP. See
Section 3.2 of SMG.
SHUTUP will terminate
any jobs still active
and may be used at any
time to shut the system
down for correct
maintenance.
4.”
- Y >
WHEN IT DOES. PRESSING “CONT” WILL BOOT BRCK RSTS/E
3-27
3.3 NORMAL TEST SYSTEM RESTARTING PROCEDURES
If the user shuts down the RSTS/E test system for any reason, he
may restart it by bootstrapping the system disk as described in Appen-
dix A of the RSTS/E System Generation Manual and by typing START in
response to the OPTION query printed by the initialization code. Dur-
ing a normal start up of a RSTS/E system, the system initialization
program INIT runs automatically and accesses the START.CTL file under
the system library account [1,2]. The INIT system program and the
START.CTL file are installed in the system library when the system is
built (see Section 4.3, RSTS/E System Generation Manual).
After the system is initialized, the user must log in under a
privileged account and run the CONTRL program.
The following example shows the use of the START option and the
printout of the INIT program as it runs and causes the CONTRL program
to run. When the CONTRL program prints the query JOB NAME TO START
OR ATTACH, the user can proceed to run the system reliability test
according to the guidelines presented in Section 3.2.
RSTS ¥B5B-24 TEST SYSTEM
OPTION: START
YOU CURRENTLY HRAYE: JOB MAX = 2, SWAF MAX = 16K.
JOB MAX OR SWAP MAX CHANGES 7 <LF>
ANY MEMORY RLLOCATION CHANGES ? <LF>
CRASH DUMP? <LF>
DD-MMM-YY? 14-JUL-74
HH:MM? 12:38
SYSTEM INITIALIZATION PROGRAM
RUN SERRCPY
READY
ERRCPY YV85-86
DETACHING
LOGIN 1/2
PASSWORD: SYSTST
READY
RUN $CONTRL
3-28
** DEVICES CONFIGURED IN RSTS vaSB-24 TEST SYSTEM
TYPE COUNT EXERCISER NAME
CFU 1 CFEXER
DP e DFEXER
DK e PREXER
KB 22 KEEKER
DT 4 PTEXER
LP 1 LFEXER
PR 1 FREXER
PP 1 FFEXER
CR 1 CKEXER
MT 4 MTEXER
PK 4 FKEXER
RJ 1 RJEXER
SYSTEM JOB MAX =
CONTROL JOB MAX =
PY 1A
HO nm
** JOB NAME TO START OR ATTACH 7
3.4 RESTARTING THE TEST SYSTEM AFTER A SYSTEM CRASH
If a system crash occurs on the test system during the reliability
tests and the system halts, the user can restart the system by follow-
ing the procedures described in Section 2.2.2 of the RSTS/E System
Manager's Guide. When a system crash occurs, normally RSTS/E attempts
to perform a crash dump and to enter automatic restart, mode. Section
2.3 of the RSTS/E System Manager's Guide explains the automatic
recovery and restart facilities of the RSTS/E system. If either of
the two conditions described in Section 2.3.2 of that guide are not
fulfilled, the system simply halts at address 54 without performing a
crash dump and entering automatic restart mode.
The user can ensure that the system performs a crash dump and
enters automatic restart mode when it crashes if he follows procedures
exactly as described in this document. To be exact, he must do the
following:
a. When creating the system files as shown in Section
2.1.6 of this document, he must type YES in response
to the CRASH query to create the CRASH.SYS file.
b. When setting the default start up conditions as
described in Section 2.1.7, he must type YES in
response to the CRASH DUMP query to enable the crash
dump facility.
3-29
с. When starting the test system as described in Section
3.3, he must type the LINE FEED key in response to the
CRASH DUMP query to retain the enabling of the crash
dump facility.
d. When starting the reliability test according to the
guidelines described in Section 3.2, he must set the
CPU Switch Register to 777777 (all switches in the up
position) to enable the automatic restart facility.
If the test system halts in spite of the user having performed all of
the above steps, the probability is that two system crashes have
occurred within a minute of each other. In this case, the halt occurs
by design as explained in Section 2.3.2 of the RSTS/E System Manager's
Guide. In addition, if any of the hardware in the system is not
operating correctly, the user can expect system crashes to occur
during the reliability tests.
When the test system enters automatic restart after a system crash
or the user requests a core dump and automatic restart after a system
halt, the INIT system program runs as in the case of a normal start up
described in Section 3.3. However, when INIT runs in automatic
restart mode, it accesses the CRASH.CTL file instead of the START.CTL
file. The CRASH.CTL file included in the system library kit con-
tains commands which cause the system programs ERRCRS, ERRDIS, and
ANALYS to run. These programs recover important information on the
probable cause of the system crash.
The ERRCRS program is similar to the ERRCPY program, since it saves
error logging information in a disk file. The ERRCPY program extracts
error logging information from monitor tables in core during time
sharing operations. The ERRCRS program extracts similar error logging
information from the same monitor tables saved in the CRASH.SYS file
by means of the crash dump facility at the time of the system crash.
Hence, the ERRCRS program may recover error logging information con-
cerning hardware malfunctions which occurred prior to the system crash.
This error logging information may not have been recovered by the
ERRCPY program and may reflect the cause of the system crash.
3-30
When the ERRDIS program runs, it prints the error logging informa-
A Y? E Y TY
tion ogram. Subsequentiy, the ANALYS program
recorded by the ERRCRS pr
runs and prints a thorough analysis of the information written in the
CRASH.SYS file by the crash dump facility. When all commands in the
CRASH.CTL have been executed, the CONTRL program must be restarted
with the RUN $CONTRL command. When the CONTRL program prints the
query JOB NAME TO START OR ATTACH, the user can continue running the
system reliability test according to the guidelines presented in
Section 3.2.
The CRASH.CTL file is installed in the system library account
[1,2] when the system library files are built.
3.5 GUIDELINES FOR USING CONTRL UNDER NORMAL TIME SHARING
The examples of this and the previous chapter were directed toward
system testing at the DEC manufacturing facility. Tests performed at
the customer site when the system is installed by Field Service per-
sonnel are equally important. Sections 2.3 and 3.1 of this manual
include a few notes on the use of SYSTST for on-site testing. This
section presents a few alternative procedures which may be useful for
the installation tests.
Once the hardware has been uncrated and assembled, Field Service
personnel should use the standard diagnostics to check each component.
Neither the SYSTST exercisers nor the RSTS/E error logging routines
can be as thorough as the diagnostics in checking correct operation
of the hardware. Certain subtle hardware failures may have no affect
on the operation of the current monitor but may prevent the use of
another operating system or of a future release of RSTS/E. Installa-
tion testing, therefore, must include a thorough check of the proces-
sor and all peripherals before any attempt is made to bring up a
RSTS/E system.
When the system generation is performed for on-site testing,
refer to Section 2.3 for software options which affect the operation
of individual exercisers. The SYSGEN examples of Chapter 2, RSTS/E
System Generation Manual can serve as rough models even if specific
configuration details are altered to installation requirements.
After generating a RSTS/E system for SYSTST, the user must
build the system library. Procedures for this build are described
in Chapter 4 of the RSTS/E System Generation Manual. The standard
system library must be built. TSTBLD may be run under any account.
The files it loads and compiles do not affect other system files.
The reliability tests may be run under open time sharing.
3-32
CHAPTER 4
DEVICE EXERCISER ABSTRACTS
The SYSTST user should be familiar with the operation and limita-
tions of each of the device exercisers before attempting to run the re-
liability test. This chapter contains descriptions of each of the
exercisers included in the package.
4.1 DISK EXERCISERS
Four disk exercisers are included in the SYSTST package. DFEXER
is used to test the RF11 controller with up to eight RS11 disk platters.
DKEXER is used for testing the RK11 controller and up to eight [email protected] or
RK[email protected] DECpack cartridge drives. DPEXER tests the RP11-C controller and
up to eight [email protected] disk pack drives. DBEXER tests the RH11 controller
and up to eight RPf4 disk pack drives. The RK, RP, and RB exercisers
are capable of sequentially testing all drives or any subset of drives
connected to the controller. It is also possible to run several copies
of the same exerciser in order to test several drives simultaneously
Or to put a heavier load on any single drive.
The disk exercisers begin by asking several questions to determine
which drive(s) to test and the duration of the test. DKEXER, DPEXER,
and DBEXER ask the operator to enter the number of drives (1-8) to be
tested and the unit numbers (#-7) of those drives. All exercisers ask
the operator to enter the number of iterations (1-99) to be performed.
A disk exerciser performs pattern tests on a disk file using Rec-
ord I/O GET and PUT operations. Patterns used include all zeroes, all
ones, and two complementary one/zero patterns. The file size is com-
puted by the exerciser based on available disk space on the drive to be
tested. To limit exerciser run time, the file size is limited to a
4-1
maximum of 488 disk blocks of 256 words each. The maximum size is the
norm since SYSTST is usually run using new disks with a large amount of
free space.
After completion of the dialogue and preliminary calculations, the
disk exerciser proceeds to open and extend the file to the predetermined
size. A pattern buffer is then loaded with the first of the four pat-
terns and all file blocks are written from this buffer. Each block is
then read and compared against the known correct pattern data. This
procedure is repeated for the other three patterns. If any errors are
detected, an error count is incremented for each incorrect word. The
error count is cumulative over the four patterns. The file is deleted
after the pattern tests and the exerciser starts again if more than one
iteration was requested. Under normal conditions, a different area of
the disk is used on each successive iteration.
Upon completion of all iterations for a drive, a status report 15
printed and the exerciser proceeds to test the next drive, if any. The
operator is given the option to rerun the exerciser or to log it off the
system at the conclusion of the test for all drives.
The disk exercisers use very little processor time but do cause
considerable activity on the disk device under test and on the UNIBUS.
Some 408 write and 408 read operations are performed for each pattern
for a total of 32008 disk transfers per iteration. Additional transfers
are also required for window turns and for open, close, extend, and
delete operations. Disk and bus activity can be further increased by
running several disk exercisers. In particular, on a moving head de-
vice, arm motion is considerably increased if two or more exercisers
are used to simultaneously test the same drive.
All DIGITAL supplied disk devices have built in error checking
circuitry which should signal bad data. RSTS/E systems will perform
up to five retries when the hardware detects a soft data error. Hard
disk errors or soft errors which persist over five retries cause the
disk exercisers to abort with the message USER DATA ERROR ON DEVICE.
This condition is usually indicative of a bad disk block or a hardware
malfunction. A non-zero error count reported by the disk exercisers
indicates hardware problems which were not detected by the error
checking circuitry. Errors of this type may indicate disk or con-
troller malfunction, bus noise problems, or memory errors.
The disk exercisers do not attempt to test all controller or drive
functions and they do not access all sectors on a platter, cartridge,
or disk pack. SYSTST is intended to test system integrity and not to
exhaustively test or diagnose any type of device. However, disks which
are to be accessed under RSTS/E must be initialized to the RSTS/E file
structure using the DSKINT option at system start up time. DSKINT per-
forms pattern tests on any disk device supported under RSTS/E and can,
therefore, be used to test basic read/write access to all sectors.
Used in combination with stand-alone diagnostics, DSKINT and the SYSTST
disk exercisers can ensure a high level of confidence in the disk devices
configured in a RSTS/E system.
4-3
4.1.1 DFEXER - RF11/RS11 Disk Exerciser
The RF11/RS11 exerciser is somewhat restricted in its application
since it can only be used if the RF1ll is configured as the system
disk. User file data cannot reside on the RF1ll if it is configured
as a swapping disk. In either case, the RF11 will be exercised by
normal swapping activity if the total size of all running jobs
exceeds the available memory space. DFEXER is further restricted in
that there is no explicit way to test one particular RS11 platter.
RSTS treats a multi-platter RFll as one large disk and hence the
BASIC-PLUS program cannot easily control the physical location of
disk blocks which comprise the test file. DFEXER will test the normal
operation of the RF11 configured as a system disk and does serve
to increase bus activity. It should, therefore, be used whenever
possible despite restrictions mentioned.
DFEXER Example:
x»* JOB NAME TO START OR ATTACH ? DFEXER
** LOGGING IN NEN JOB NAMED “DFEXER”.
DF*STRRTING RF11/RS11 DISK EXERCISER
DF+ONE ITERRTION ON THE RF DISK TAKES ABOUT 4 MINUTES.
DF+ROW MANY ITERATIONS DO YOU WANT TO RUN (1-99) 2 5
CF*DF EXERCISER DETRCHING
** JOB NAME TO START OR ATTACH 7? /
** CONTROL JOB ENTERING MONITOR MODE.
xx REATTACHING SUBJOB DFEXER
LE*DFEXER ERROR STRTISTIC FOR THE RFii
DRIVE PASS FILE SIZE ERROR COUNT
DF 1 480 a
DF & 488 g
CF 3 4080 g
CF 4 488 8
BF 5 480 в
DF*DF EXERCISER DONE
DF*TO RERTTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE 7 RUNNH”.
RERDY
BYEA/F
4.1.2 DKEXER - RK11/RK923/RK095 Disk Exerciser
DKEXER will test all or any subset of [email protected]#3 or [email protected] drives
connected to the RK11 controller. All drives which are to be tested
must be fitted with a DECpack cartridge which has been initialized
to the RSTS file structure by the DSKINT initialization option. Disk
initialization is described in Sections 3.3 and 3.3.2 of the RSTS/E
System Generation Manual and guidelines for initialization of disks
for SYSTST have been presented in Sections 2.1.3 and 2.1.4 of this
manual. Assuming these procedures have been
A ча Le am
followed, DKEXER can be
run as described below.
DKEXER Example:
*»x JOB NAME TO START OR ATTACH ? DKEXER
** LOGGING IN NEW JOB NAMED “DKENER”.
DKxSYSTEM CONFIGURED FOR 2 DRIVES.
DKxHOW MANY DRIVES DO YOU WANT TO TEST ? 2
DK*WHICH DRIVECS)> ? 8,1
DK*ONE ITERRTION ON A SINGLE RK DRIVE TAKES ABOUT 4 MINUTES.
DK*HOW MANY ITERATIONS DO YOU WANT TO RUN <1-99) ? 2
DK*DK EXERCISER DETRCHING
жж JOB NAME TO START OR ATTACH ? /ALL:120
*x CONTROL JOB ENTERING MONITOR MODE.
*x STATUS OF CONTROL SUBJOB<S5> AT 84:39 PH
NRME JOB NO. STATE CPU-TIME
CONTRL 4 RN 29.9
LKEXER 18 RN 6.1
some time and several status printouts later
** RERTTACHING SUBJOB DKEXER
DK*DKEXER ERROR STATISTICS FOR DK 8
DRIVE PASS FILE SIZE ERROR COUNT
DK 8 1 408 9
DK 8 2 488 8
DK*DK EXERCISER CONTINUING ON DRIVE 1
DK*xDK EXERCISER DETACHING
»% JOB NAME TO START OR ATTACH ? /
ж* CONTROL JOB ENTERING MONITOR MODE.
** RERTTRCHING SUBJOB DKEXER
DK*DKEXER ERROR STRTISTICS FOR DK 1
DRIVE PASS FILE SIZE
DK 1 1 400
DK 1 2 488
DKX*xDK EXERCISER DONE
CK*XTO RERTTRCH TO CONTROL TYPE “BYE”,
READY
BYE/F
- di a [WN SYN J -—- она. amb dal Mh. wm. em un. dei Sn dem em mis као в 8
xx JUS NAME TO START UK ATTALH 7
ERROR COUNT
8
8
TO RERUN TYPE “ RUNNH”.
4.1.3 DPEXER - RP11-C/RP#3 Disk Exerciser
The RP11-C/[email protected] exerciser is almost identical to DKEXER. It will
test all or any subset of [email protected] drives connected to the RP11-C con-
troller. As was the case for RK drives, all RP93 drives must be fitted
with an RP93 disk pack which has been initialized using DSKINT at
system start up time. Sections 2.1.3 and 2.1.4 of this manual include
guidelines for initialization of [email protected] packs. In the previous example,
a single copy of DKEXER was used to test two RK drives. The example
below demonstrates use of two copies of DPEXER simultaneously exer-
cising a single RP93 drive.
DPEXER Example:
** JOB NAME TO START OR RTTRCH ? DPEXER
Fi t C
** LOGGING IN NEW JOB NAMED “DPEXER” test oy
DF*SYSTEM CONFIGURED FOR 1 DRIVES.
DPxHON MANY DRIVES DO YOU WANT TO TEST ? 1
DP*WHICH DRIVE(S) ? Q
DP*ONE ITERATION ON A SINGLE RP DRIVE TRKES ABOUT 4 MINUTES.
DP*HOW MANY ITERATIONS DO YOU WANT TO RUN <1-997 7? 4
DP*DP EXERCISER DETRCHING
xx JOB NAME TO START OR ATTACH ? DPENXER Second €
** LOGGING IN NEN JOB NAMED “DPEXER”. Econo BY
DP*SYSTEM CONFIGURED FOR 1 DRIVES.
DP*HOR MANY DRIVES DO YOU WANT TO TEST ? 4
DP*WHICH DRIVE<S> ? Q
DP*ONE ITERATION ON AR SINGLE RP DRIVE TAKES ABOUT 4 MINUTES.
DP*HON MANY ITERATIONS DO YOU WANT TO RUN ¿1-99 ? 4
DPxDP EXERCISER DETACHING
*« JOB NAME TO START OR ATTACH ? ¿ALL :68
*# CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB<S) RT 84:26 PH
NAME JOB NO. STATE CPU-TIME
CONTRL 3 RN 19.5
DPEXER 8 RN 7.3
DPEXER 9 DF 7.4
4-7
<some time and several status printouts later>
** STRTUS OF CONTROL SUBJOB<S> AT 85:85 РМ
NAME JOB NO. STATE CPU-TIME
CONTRL 3 RN 42. 2
DPEXER 8 RN 13.1
DPEXER 9 RN 13. 3
** RERTTRCHING SUBJOB DPEXER
DP*xXDPEXER ERROR STATISTICS FOR DP ©
DRIVE PRSS FILE SIZE ERROR COUNT
DP 6 1 468 8
DP 8 2 480 8
DP 8 3 488 8
DP © 4 488 8
DPanP EYERCICER NONE
tes . vu TR Wr $ e E FM "er В e
DP*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “7 RUNNH”.
READY
BYE/F
*x* JOB NAME TO START OR RTTRCH ? /
** CONTROL JOB ENTERING MONITOR MODE.
xx REATTACHING SUBJOB DPENXER
DPxXDPEXER ERROR STATISTICS FOR DP 8
DRIVE PASS FILE SIZE ERROR COUNT
bP 8 1 460 g
DP 8 2 488 8
РР 8 3 488 8
DP a 4 488 8
PPxDP EXERCISER DONE
DP*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE ” RUNNH”.
READY
BYE/F
*ж* JOB NAME TO START OR ATTACH ?
4.1.4 DBEXER - RH11/RPF4 Disk Exerciser
DBEXER tests any subset of (or all) RPZ4 drives connected to the
RH11 controller. All drives to be tested must be running an [email protected] disk
pack which has been initialized by the DSKINT initialization option.
Refer to Sections 3.3 and 3.3.2 of the RSTS/E System Generation Manual
for a description of DSKINT and to Sections 2.1.3 and 2.1.4 of this
manual for guidelines to initializing disks for SYSTST. Assuming
these requirements have been met, DBEXER can be run as described below.
** TNR NAME MA QMART NR AM
WF A da оч ЛЬ А e
“e Y Woh y ar A
m
** LOGGING IN NEW JOB NAMED
ог
ACH ? DBE
1 1
DBEXER'.
DB*SYSTEM CONFIGURED FOR 2 DRIVES.
DB*HOW MANY DRIVES DO YOU WANT TO TEST ? 1
DB*WHICH DRIVE(S) ? 1
DB*ONE ITERATION ON A SINGLE RB DRIVE TAKES ABOUT 4 MINUTES.
DB*HOW MANY ITERATIONS DO YOU WANT TO RUN (1-99) ? 1
DB*DB EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? /ALL:6%
* CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB(S) AT 26:45 PM
NAME JOB NO. STATE | CPU-TIME
CONTROL 8 RN 25.8
DBEXER 12 RN 7.0
** STATUS OF CONTROL SUBJOB(S) AT 86:47 PM
NAME JOB NO. STATE CPU-TIME
CONTROL 8 RN 29.7
DBEXER 12 RN 7.8
** REATTACHING SUBJOB DBEXER
DB*DBEXER ERROR STATISTICS FOR DB 1
DRIVE PASS FILE SIZE ERROR
DB 1 1 Чай й
DB*DB EXERCISER DONE
DB*TO REATTACH TO CONTROL TYPE 'BYE/F', TO RERUN TYPE 'RUNNH'
READY
** DBEXER WAIT EXHAUSTED.
** CONTROL TERMINATING JOB #12 DBEXER
++C
BYE/F$
READY
** JOB NAME TO START OR ATTACH ?
4.2 DTEXER - DECTAPE EXERCISER
DTEXER will test the TCll DECtape control and up to 8 DECtape drives.
If a single copy of DTEXER is used to test several drives, the individual
drives are exercised one at a time. Multiple copies may be used to
test several drives simul taneously.
The DECtape exerciser begins with a dialogue similar to the disk
exercisers to determine which drives are to be tested. The operator
is directed to enter the number (1-8) of drives to be tested and the
unit numbers (0-7) of those drives. Before detaching to run the test,
DTEXER will zero the tapes on all specified drives. In the detached
state, DTEXER proceeds to open a file on the unit being tested and
fills the file with floating point numbers. Out of a possible 578
tape blocks, 286 blocks are written if a 4-word math package is being
7
used. 144 blocks are wri
word math. After the file is written, it is closed and reopened for
input. Numbers written on the tape are read and checked keeping a
count of incorrect values, If at the end of the test the error count
is not zero, DTEXER will print the count before proceeding to test the
next drive.
DTEXER Example:
** JOB NAME TO START OR АТТАСН ? DTEXER
** LOGGING IN NEN JOB NAMED “DTEXER”.
DT*SYSTEM CONFIGURED FOR = DRIVES.
PT*HON MANY DRIVES DO YOU NANT TO TEST ? 2
DT*WHHICH DRIVECS) 7 8,1
DT*RARE DRIVECS? 6,1 MOUNTED AND N/E? YES
DT*DT EXERCISER DETRCHING
x* JOB NAME TO START OR ATTACH ?
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUEJORE<S? AT 84:48 FH
NAME JOE NO. STRTE CFU-TIME
CONTRL 6 RN 29.9
CTERER 12 RN 13.4
** RERTTACHING SUBJOB DTEXER
DT*DT EXERCISER DONE FOR DRIVE(S) :@8, 1
DT+TO RERTTRACH TO CONTROL TYPE "ByE,
FERDY
BYE/F
** JOB NAME TO START OR ATTACH ?
4-11
THIS PAGE PURPOSELY LEFT BLANK
4-12
4.3 MTEXER - MAGTAPE EXERCISER
The magtape exerciser is used to check normal operation of the
TM11 magtape control and up to eight [email protected] 7-track or 9-track drives
and the RH11/TM%2 magtape control and up to eight TUl6 drives. MTEXER
allows the operator to select the drive(s) to be tested, the length of
tape to be written, and the number of repetitions to be performed. On
each iteration, the tape is zeroed, a file is opened, and data is writ-
ten until the specified length of tape has been used. The tape is then
rewound, the file is opened for input, and the data is read and veri-
fied. If errors are detected, a count of the number of bytes found to
be incorrect is printed before proceeding to the next iteration.
The data pattern used is a worst case NRZ pattern for 9-track
drives. This pattern is not worst case for 7-track recording. The
pattern is loaded into a 512 byte buffer and n PUT operations are used
to write the tape. The variable n is equal to the repetition number
so that n identical records are written on repetition n. The pattern
buffer is then changed and the process continues until the required
length of tape has been written. Since the number of PUT operations
increases, tape speed increases on each successive iteration. Further-
more, the pattern base varies with n so that the contents of the pat-
tern buffer also varies on successive iterations.
Problems with TM11/TU19 magtape drives are most likely to occur
when running several drives simultaneously. It is therefore advanta-
geous, if not imperative, that one copy of MTEXER be run for each drive
on the RSTS/E system. To check for correct mechanical operation and to
ensure no interaction between drives, MTEXER should be run for only a
few feet of tape (from 5 to 1ÿ feet) but with many iterations (from
39 to 49). Running multiple copies of MTEXER forces rewinds of some
drives while read/write operations are performed on other drives.
Conversely, to ensure data integrity, a large amount of tape should be
written (from 199 to 4098 feet) with few iterations (from 1 to 5).
4-13
MTEXER Example:
** JOB NAME TO START OR ATTACH ? MTEXER
## LOGGING IN NEW JOB NAMED 'MTEXER'
MT#SYSTEM CONFIGURED FOR 8 DRIVE(S).
MT*HOW MANY DRIVES DO YOU WANT TO TEST ? 1
MT®*WHICH DRIVE(S) ? £
MT*HOW MANY FEET OF TAPE DO YOU WANT TO WRITE ? 19
MT*HOW MANY REPETITIONS PER DRIVE ? 14
MT*ARE DRIVE(S) # MOUNTED AND W/E ? YES
MT#MT EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? MTEXER — Second copy
** LOGGING IN NEW JOB NAMED 'MTEXER'.
MT*SYSTEM CONFIGURED FOR 8 DRIVE(S).
MT*HOW MANY DRIVES DO YOU WANT TO TEST ? 1
MT*WHICH DRIVE(S) ? 1
MT*HOW MANY FEET OF TAPE DO YOU WANT TO WRITE ? 18
MT#HOW MANY REPETITIONS PER DRIVE ? 18
MMéADT TADTYUITT (ON 1 MATILMITITT AAMT 7/77 0 VTO
PLL O SALLIS МХ До ал Ва W/ 11 à 1 170
MT*MT EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? MTEXER Third copy
** LOGGING IN NEW JOB NAMED 'MTEXER'.
MT*SYSTEM CONFIGURED FOR 8 DRIVE(S).
MT*HOW MANY DRIVES DO YOU WANT TO TEST ? 1
MT*WHICH DRIVE(S) ? 2
МТ*НОМ MANY FEET OF TAPE DO YOU WANT TO WRITE ? 1%
MT*HOW MANY REPETITIONS PER DRIVE ? 18
MT*ARE DRIVE(S) 2 MOUNTED AND W/E? YES
MT*ERROR AT LINE 165 :MAGTAPE SELECT ERROR (19-JUL-73,03:45 PM)
Drive was offline
MT*TO CONTINUE TYPE 'CONT', TO ABORT TYPE '“”C!,
? CONT
MT*SYSTEM CONFIGURED FOR 8 DRIVE(S).
MT*HOW MANY DRIVES DO YOU WANT TO TEST ? 1
MT¥WHICH DRIVE(S) ? 2
МТ*НОМ MANY FEET OF TAPE DO YOU WANT TO WRITE ? 1/4
MT*HOW MANY REPETITIONS PER DRIVE ? 19
MT*ARE DRIVE(S) 2 MOUNTED AND W/E? YES
MT*MT EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? /MTEXER
*%* CONTROL JOB ENTERING MONITOR MODE.
## STATUS OF CONTROL SUBJOB(S) AT 93:47 PM
NAME JOB NO. STATE CPU-TIME
MTEXER 12 RN 1:92.1
MTEXER 13 RN 45,4
MTEXER 15 RN 5.7
4-14
** RERTTRCHING SUBJOB MTEXER
MT+MT 8 ERROR AT LINE 440 :MAGTAPE SELECT ERROR “18-JUL-73, 83:47 PM)
Drive was switched
MT*MAGTAPE STATUS SUMMARY : offline to force an error.
MT*XLAST COMMAND NAS RERD Full Status printout
MT * DENSITY PRRITY TRACKS only occurs if the test
MT * 3 ODD 9 file was open at the time
MT x W-LOCK EOT BOT EOF RLE of the error.
MT % NO NO NO NO NO
MT» SELECTION ERROR OCCURED
MT*TO CONTINUE TYPE “CONT”, TO ABORT TYPE “EC”.
7 CONT
MT*SYSTEM CONFIGURED FOR 8 DRIVE(S).
MT*HOW MANY DRIVES DO YOU WANT TO TEST ? 4
MT*XWNHICH DRIVECS> ? 8
MT*HON MANY FEET OF TAPE DO YOU WANT TO WRITE ? 18
MT*HON MANY REPETITIONS PER DRIVE ? 18
MT*RRE DRIVECS> 8 MOUNTED AND N/E? YES
MT*MT EXERCISER DETRCHING
** JOB NAME TO START OR ATTACH ? /MTEXER
»* CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB:S> AT 83:48 PM
NAME JOB NO. STATE CPU-TIME
MTEXER 12 RN 1:07. 2
MTEXER 13 RN 56. 6
MTEXER 15 RN 22. 2
** RERTTACHING SUBJOB MTEXER
MT*MT EXERCISER DONE FOR DRIVE<S>:1
МТ*ТО RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “ RUNNH”.
READY
*»* MTEXER WAIT EXHAUSTED.
** CONTROL TERMINATING JOB #13 MTEXER
^^
BYE/F$
RERDY
** JOB NAME TO START OR ATTACH ? ALL
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB<S> AT 83:59 PH
NAME JOB NO. STRTE CPU-TIME
CONTRL 4 RN 23. 1
MTEXER 12 RN 2:42. 8
MTEXER 15 НВ SN 1:39. 3
** REATTRCHING SUBJOB MTEXER
MT»xMT EXERCISER DONE FOR DRIVE(S) :2
MT*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “ RUNNH”.
RERDY
BYE/F
** JOB NAME TO START OR ATTACH ? ALL
*« CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB<S> АТ 83:59 РМ
NAME JOB NO. STRATE CPU-TIME
CONTRL 4 RN 25. 9
MTEXER 12 HB 2:45. 5
** REATTACHING SUBJOB MTENER
MT*MT EXERCISER DONE FOR DRIVE<S>:8
MT*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “RUNNH".
READY
BYE/F
** JOB NAME TO START OR ATTACH ?
4-16
4.4 CREXER - CARD READER EXERCISER
The card reader exerciser tests the CR11 and CDI11 punched card
readers, CREXER is intended for use with MAINDEC-89-D1B1-C entitled
"ALPHA CARD DECK" which is supplied with the reader diagnostics, This
deck consists of 80 cards punched with a rotating character set. As
the deck is read and verified, if the data read does not agree with
the MAINDEC, the actual and expected contents of each card is recorded
in a disk file for later printing. Thus, if the MAINDEC is not
available, any card deck (punched with DECO29 or an equivalent punch)
can be read and printed for manual verification or a MAINDEC can be
punched from the listing of expected card contents.
Standard card codes for RSTS/E are listed in Appendix D of the
BASIC-PLUS Language Manual. The pattern used in the MAINDEC shifts 80
characters through all 80 column positions. Since the pattern repeats
every 80 cards, several copies of the MAINDEC can be stacked for a more
thorough test of reader operation. CREXER continues reading until a
hopper empty or end of file condition is detected. End of file is
generated with either an end of file card (12-11-0-1 punch in column
1) or with the end of file switch (1200 cpm CD11 only).
CREXER Example:
oe "Y P an ln. a e e A =
** JOB NAME TO START OR ATTACH ? CREXER
** LOGGING IN NEN JOB NAMED “CREXER“.
CR*STARTING CARD RERDER EXERCISER.
CR*L ORD MRINDEC-89-D1R1-C LABELLED “ALPHA CARD DECK” INTO THE
CR*RERDER. THE DECK WILL BE RERD AND VERIFIED. JF ANY ERRORS FRE
CR*DETECTED, THE EXPECTED AND ACTUAL CONTENTS OF THE ERD CRRD
CR*NILL BE RECORDED IN R DISK FILE FOR LATER FRINTING ON EITHER
CR*THE CONSOLE TERMINAL OR THE LINE PRINTER. CARDS WILL BE READ
CR*UÚNTIL END OF FILE OR HOFFER EMPTY 156 DETECTED. SEVERAL COFIES
CR*OF THE MAINDEC MAY BE STACKED FOR A MORE THOROUGH TEST.
CR*CARD READER RERDY ? VES
CR*CARD READER EXERCISER DETRCHING.
** JOB NAME TO START OR ATTRCH ? /
++ CONTROL JOB ENTERING MONITOR MODE.
## RERTTACHING SUBJOE CREXER
4-17
CR*0UT OF 6486 CARDS RERD, ERRORS WERE DETECTED ON 4 CARDS.
CR*TYFE LP: TO LIST ERRORS ON THE LINE FRINTER OR TYPE “KE:7
CR*TO LIST ERRORS ON THIS KEYBORRD.
CR*YOUR LISTING DEVICE ? KB: Error was forced with one bad card.
CARD 5 EXPECTED : DEFGHIC. <+1-JKLMNOFQR 194); BS TUYWNXNYZ2N, 2. >? 123456789 :#@ = "8A
ECDEFGHIE. <<+'&ARBC
CARD 5 ACTURL : DEFGHIE. €4+!-JKLMNOFOR 38+#>; "6/STUVNOYZN, #57? 123456789 :#8#@ ="EA
ECDEFGHIL. <x+!8RBC
Note that the letter G(12-7 punch) was changed to & (12 punch) and
the letter X(@-7 punch) was changed to 9(ÿ punch). This indicates
occasional dropouts on row 7 of the card. This type of problem
might be caused by dust on the head or marginal operation of the
photo sensor or amplifier for row 7.
CR*CRRD RERDER EXERCISER DONE.
CK+T0 REATTRCH TO CONTROL TYPE “BYE”, TO RERUN TYFE “RUNNR".
READY
EYE/F
*ж* JOE NAME TO START OR RTTRCH ?
4.5 LPEXER - LINE PRINTER EXERCISER
The line printer exerciser simply prints a rotating ASCII pattern
on LPll or LS1ll printers. Up to 8 printers can be sequentially tested
with one copy of LPEXER or several copies can be run simultaneously,
each exercising a different printer.
LPEXER Example:
fg pm, pm, ет va mm PE ou ad dm a 2 © _
ME TO START OR ATTACH 7 LPEXER
G IN NEN JOB NAMED “LPEXER-.
+ JOB
+ LOGGI!
n
ear
LP+SYSTEM CONFIGURED FOR 2 PRINTER(S5.
LP+HON MANY PRINTERS DO YOU WANT TO TEST 7 1
LF+TYPE UNIT #°S OF PRINTER(5> TO BE TESTED >? 8
LP+*ARE PRINTER(S> 6 ONLINE AND RERDY? YES
LP*HON MANY PAGES OF OUTPUT DO YOU WANT? 2
LP+*LF EXERCISER DETRCHING.
** JOB NAME TO START OR ATTACH ?
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB:S> AT 84:10 PM
NAME JOB NO. STRATE CPU-TIME
CONTRL 3 RN 16. 1
LFEXER 9 RN 28.1
** STATUS OF CONTROL SUBJOB<S> AT 84:11 PM
NAME JOB NO. STATE CPU-TIME
CONTRL 3 RN 16. 5
LFEXER 9 RN SH 34.8
** REATTACHING SUBJOB LPEXER
LP*LINE PRINTER EXERCISER DONE
LP*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE * RUNNH”.
RERDY
BYE/F
** JOB NAME TO START OR ATTRCH ?
THIS PAGE PURPOSELY LEFT BLANK.
PPEXER - PAPER
test the paper tape reader.
binary count pattern.
TAPE PUNCH EXERCISER
The tape consists of 32 repetitions of a
Each pattern includes all possible punches
alternating with the complement punch, i.e., (in octal) 1, 1(=376),
2,2(=375),...,376,376(=1), 377,377 (=0), 0,0(=377).
This tape is
identical to [email protected]@-D2G4~PT labelled "SPECIAL BINARY COUNT PATTERN
TAPE" supplied with the paper tape reader diagnostics.
PPEXER E
amr] Aa
Lhd IN ice
чи <
de АМА
#4 JOE NAME TO STRET OK ATIRCH ? PPEXER
*ж* LOGGING IN NEW JOB NRMED “PPEXER”,
FP*STARTING PP EXERCISER,
PP RERDY ? YES
FP*THIS TEST WILL PUNCH AR BINARY COUNT PRTTERN TRPE.
FP+*THE TRPE 15 EQUIVALENT TO MAINDEC-80-
FP*xSPECIAL BINARY COUNT PATTERN TRFE.
D2G4-PT ENTITLED
EITHER THE TAFE
FPxPUNCHED BY THIS EXERCISER OR THE SUPPLIED MAINDEC
FPR*xTRPE MAY BE USED TO TEST THE PAPER TAPE READER.
FP*I WILL PUNCH AR LERDER AND THEN SLEEF
FP*XNHILE YOU STRAIGHTEN OUT THE TAPE IN
FP+xPP EXERCISER DETRCHING
*ж* JOB NAME TO START OR ATTACH ? ALL
** CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB<S> RT 83:55
NAME JOB NO. STRTE
CONTRL 3 RN
FPEXER : 9 RN
** RERTTACHING SUBJOB PFEXER
PPxPP EXERCISER DONE
38 SECONDS
THE HOPPER.
“J
—
ile
CPU-TIME
12.5
+. 5
FPxNON USE THE GENERATED PAPER TAPE TO TEST THE READER
FP»XTO REATTACH TO CONTROL TYPE “BYE”
READY
EYE/F
*ж* JOB NAME TO START OR ATTACH ?
TO RERUN TYPE
* RUNNH”.
THIS PAGE PURPOSELY LEFT BLANK.
4-22
4.7 PREXER = PAPER TAPE READER EXERCISER
The tape generated by PPEXER or [email protected]@-D2G4-PT "SPECIAL BINARY
COUNT PATTERN TAPE" may be used with PREXER to test a paper tape reader.
PREXER reads and checks 30 repetitions of the binary count pattern
described in the previous section and then skips any remaining tape in
the reader. When end of file is encountered, PREXER reports any errors
detected. If a large number of errors are reported, the operator should
check the read station for dust and insure that the tape was correctly
loaded into the reader. PREXER will report 15360 errors if the tape is
loaded backwards. In the case of excessive errors, it may also be
necessary to manually examine a tape punched by PPEXER to insure that
the punch is functioning properly.
PREXER Example:
* JOB NAME TO START OR ATTACH ? PREXER
** LOGGING IN NEW JOB NAMED “PREXER”.
PRESTARTING PR EXERCISER.
FPR*LORD MARINDEC-00-D264-PT OR THE BINARY COUNT PATTERN.
FR*TAPE GENERATED BY THE PUNCH EXERCISER INTO THE READER
FR¥WITH THE LEADER UNDER THE READ STATION. READER READY ? YES
PR*PR EXERCISER DETACHING
*k JOB NAME TO START OR ATTACH ? /
** CONTROL JOB ENTERING MONITOR MODE.
** RERTTRCHING SUBJOB PREXER
PR+ERROR AT LINE 128 :DEYVICE HUNG OR WRITE LOCKED <B6-JUL-72, 64:82 PM)
FR:ETO CONTINUE TYPE “CONT”, TO ABORT TYPE “CC”. 7? CONT Reader was not ready.
FR*STARTING PR EXERCISER.
FR:ELORD MAINDEC-08-D264-PT OR THE BINARY COUNT PATTERN
FR*TRPE GENERATED BY THE PUNCH EXERCISER INTO THE RERDER
FRENITH THE LEADER UNDER THE READ STATION. RERDER READY ? YES
PREPR EXERCISER DETACHING
ж* JOB NAME TO START OR ATTACH ? ALL
*% CONTROL JOB ENTERING MONITOR MODE.
** STATUS OF CONTROL SUBJOB:5S> AT 84:04 PH
NAME JOB NO. STRTE CPU-TIME
CONTRL 3 RN 13. 7
FREXER 9 PR 6.8
<some time and several status printouts later>
** RERTTACHING SUBJOB PREXER
FR¥PR EXERCISER DONE, ERROR COUNT= 8
FR*TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “RUNNH”.
READY
BYE/F
+ JOB NAME TO START OR ATTACH 7?
4.8 KBEXER - KEYBOARD EXERCISER
The SYSTST keyboard exerciser is used to test local and remote
terminals connected to the RSTS/E system. Since terminals may not be
connected at the DEC manufacturing facility, KBEXER will be used
primarily at the customer site for field installation testing. KBEXER
will test only one terminal at a time but may be transíerred from one
terminal to another. Several copies of KBEXER can be run if simul-
taneous testing of several terminals is desired,
RSTS/E supports a variety of terminals including the LA38 and
LA39S DECwriters, [email protected] and VTÿ5B alphanumeric display terminals and
Teletypes. Terminals may be connected to the UNIBUS via KL11 (A-E),
0111 (А-Е), LCll or DCll single line interfaces, or the DH1l multi-
plexer. The DC11 and DH11 allow terminal characteristics to be
varied under program control. RSTS/E will default variable parameters
on these lines to ASR-33 characteristics, i.e., 110 baud, 1 start
bit, 8 data bits, 2 stop bits, and no parity. The BASIC-PLUS program
TTYSET, included in the standard library, can be used to change
terminal characteristics if necessary for test purposes. Refer to
Section 7.4 of the RSTS/E System Manager's Guide for instructions
on the use of TTYSET and procedures for setting up the TTYSET.SPD
file.
KBEXER implements four terminal tests. The SPACE test verifies
that the terminal carriage (if a carriage exists) will return reliably
from any position on the line. An ASCII pattern test verifies that the
terminal will print the standard ASCII character set in all print
positions. The WORST case pattern test forces the print head on
ASR-33 Teletypes to rotate a half revolution at every print position.
Finally the REPEAT test repeats everything typed on the terminal to
verify two way communications. Commands are entered from the terminal
being tested. One of the four tests is initiated by typing the test
name and is terminated by typing CTRL/C (“C). Instructions for use of
this exerciser are printed if the RETURN key (<CR>) or HELP is typed at
command level.
Two additional commands are provided to transfer KBEXER to another
terminal. The command /KBnn will transfer to keyboard number nn. All
subsequent commands would be entered from that terminal. In testing
remote terminals the telephone connection must be established prior to
transferring to the remote keyboard. The remote terminal should not
be logged in to the system since it would then appear busy when the
transfer is attempted. The /CONTROL command transfers KBEXER back
to the SYSTST control program.
4-25
KBEXER runs attached to the keyboard which initiated it until a
transfer command is entered. Thereafter, the job is detached and
communicates with terminals through an open file. In this detached state
the exerciser cannot be terminated by typing CTRL/C (°C), When the job
is reattached by the SYSTST control program (or by anybody else), it
can be terminated with CTRL/C (°C) and can be logged off the system by
typing BYE.
KBEXER Example:
** JOB NAME TO START OR ATTACH ? KBEXER
** LOGGING IN NEW JOB NAMED “KBERER”.
KE® * KEYBORRD EXERCISER
KB® * SYSTEM 15 CONFIGURED FOR 32 TERMINRLS (KBB - KB351 >
ENTER TEST NAME OR TRANSFER COMMAND: HELP
KBO +
KBB + THE KEYBORRD EXERCISER CAN BE USED TO TEST. ANY LOCAL OR REMOTE
KBB * TERMINAL CONNECTED TO THE RSTS/E SYSTEM. ANY OF THE FOUR TESTS
KEG + PROVIDED MRY BE INVOKED BY TYPING THE TEST NAME ON THE TERMINAL
KEB + TO BE TESTED. THE EXERCISER MAY BE TRANSFERRED FROM ONE TERMINAL
KES * TO ANOTHER BY USE OF THE TRANSFER COMMAND DESCRIBED BELOW:
Keg =» SPRCE SPRCE AND CARRIAGE RETURN TEST
KBEO * RSCII ROTATING ASCII CHARACTERS TEST
KBO * WORST NORST CASE <ASR23) PATTERN TEST
[email protected] » REPERT REPEATS WHATEVER 1S TYPED ON TERMINAL
EBB + ‘’KB21 TRANSFER EXERCISER TO KEYBORRD 21
KBB * “CONTRL TRANSFER EXERCISER BACK TO CONTROL JOE
KBB * TO STOP ANY TEST FOR COMMAND ENTRY, TYPE CONTROL/C.
EBO *É BEFORE ATTEMPTING TO TRANSFER TO A REMOTE TERMINAL,
[email protected] * THE TELEPHONE CONNECTION SHOULD BE ESTABLISHED.
KBB + ENTER TEST NAME OR TRANSFER COMMAND: ASCIJ
KBO
+
ROTATING ASCII CHARACTERS TEST
I"NBREUE” CIx+,—. 78123456789 :; <= 70ABCDEFGHIJKLMNOPORSTUVYWXYZC 17 "#4
„ NOS CIxE+,—-. 78123456789 :; <=>?GABCDEFGHIJKLMNOFORSTUYWXYZL 9. !"44
7? "ESE" LC )x+,-. 78123456789 :; <=>?0ABCDEFGHIJKLMNOFORSTUYWEAYZE 1. MH
_ / "RSE" CIx+4,—-. 70123456789 :; <=>?0ABCDEFOHIJKLMNOPQRSTUYVWXYZE NI. |!"
y=. 7 "REZA" CDx+,-. 70123456789 :; <=>?0ABCDEFGHIJKLMNOPORSTUVNAYZO 3. |
+, =. 7 "REZA" CIE+,-. 78123456789 :; <=>7?0ABCDEFGHIJ"C
KBB * ENTER TEST NAME OR TRANSFER COMMAND: SPACE
"Tw A
KBB * SPACING TEST
[email protected] »* ENTER TEST NAME OR TRANSFER COMMAND: NORST
[email protected] »* ROTATING WORST CASE «ASR33> PATTERN TEST
TNC WAT LRAT LRAT CRT WT JH HZ ZT RT CE CRP CRT WE 7 MW NP?
CWT NAT WAT LRP NAT CHT RT HZ CNT RET CRT RET WP RET RPT RPT M7 7
We WA? MAT CWE RS NAT WO N75 RZ ZH CW” CRY ZH WE" REY CN WP WP WA
We RET -W25 WN RST HT RT CNT RT NT WPT 2 NP RP NPT RPT WP We
TWAT RAT WAT LWT RTRSY PT LRT ZT RT ZT ET NP NT WNP WP
CRT WT LRT RT HAT CRT RT RP RY NA NC |
[email protected] * ЕМТЕК TEST NAME OR TRANSFER COMMAND: REPERT
НВ ГРУ ТОТИ В MAIDA Yi ti SILES
KBB * REPERT TEST
? TIRE de UITLAVRNLITIIUrFWR OD | UY
WXYZ
> RBCDEFGHIJKLMNOPORSTUVKXY?Z
7? 1234567898
? 1234567898
? 1"89487 5
? 1"89/87 ()=
? ^С
KBO * ENTER TEST NAME OR TRANSFER COMMAND: /KB5
KB8 =» KEYBORRD EXERCISER TRANSFERRING FROM KB8 TO KBS
KBB * PLERSE ENTER SUBSEQUENT COMMANDS FROM KBS
KBB »* KEYBORRD EXERCISER DETRCHING.
4-27
** JOB NAME TO START OR ATTACH ? ALL
** CONTROL JOB ENTERING MONITOR MODE.
** STRTUS OF CONTROL SUBJOB«S> AT 83:27 PM
NAME JOB NO. . STATE CPU-TIME
CONTRL 3 RN 18. 3
KBEXER 12 KB 6. 8
At this point KBEXER is detached and is ready to test KB5. The
same tests and commands are available at that keyboard except that the
exerciser cannot be terminated by typing CTRL/C (“C), At the conclusion
of tests on KB5, the exerciser can be transferred to another terminal
or back to the control program as shown below,
KBS + KEYBORRD EXERCISER
KBS * ENTER TEST NAME OR TRANSFER COMMAND: ~/CONTRL
KES * KEYBOARD EXERCISER TRANSFERRING TO CONTROL KEYBORRD
On the control keyboard KBEXER is reattached and waits for a
command. In this case, the job is logged out.
** RERTTRCHING SUBJOB KBEXER
KB8 + KEYBORRD EXERCISER
KBB + SYSTEM 1S CONFIGURED FOR 32 TERMINALS «KB8 - KB31 >
KBB * ENTER TEST NAME OR TRANSFER COMMAND: C
KERDY
BYE/F
** JOB NAME TO START OR RTTACH ?
4.9 CPEXER - PROCESSOR EXERCISER
The SYSTST processor exerciser is intended to put a heavy load
on the central processor unit (CPU). CPEXER runs compute bound for
short bursts and then sleeps for five seconds so that average proces-
sor loading is not sufficient to appreciably affect the performance
of the peripheral exercisers. CPEXER was specifically designed to
test the PDP-11/40 FIS or PDP-11/45 FPP options but also serves to
verify general CPU integrity and correct PDP-11/40 EIS operation.
The FIS and FPP hardware options are fully utilized when the ex-
tended functions (sine, cosine, etc.) are configured in the system.
Hence CPEXER asks the operator if the system is configured for extend-
ed functions. If the system does include functions, then all the
tests described below are performed. If functions are not included,
only those tests identified with an asterisk below are performed.
There is no way for a BASIC-PLUS program to trap the error which
occurs if an extended function is used but the RSTS/E system was not
configured for this feature at SYSGEN time. If there is doubt that
the functions were included, the operator should indicate that the
system does include functions. CPEXER will then try one simple
calculation, X=SIN (0.5), and will abort with the message "MISSING
SPECIAL FEATURE" if the functions were actually not configured.
CPEXER can then be rerun by simply typing "RUNNH".
The tests performed by CPEXER are described briefly below. In
most of the tests, results are compared to known correct values.
Two "grind" tests are also included to verify consistent results of
duplicate calculations. Finally a few miscellaneous tests are per-
formed which have detected hardware failures on test systems in the
past.
CPEXER Test Descriptions:
SIN (X) X=(Y/180) *PI
FOR Y=10 TO 350 STEP 10 (Degrees)
Uses SIN(X) extended function.
Results are compared to known correct values.
SIN(X)* FOR X=10 TO 350 STEP 10 (Degrees)
Uses a polynomial approximation to SINE function.
Results are compared to known correct values.
LOG (X) FOR X=10 TO 500 STEP 10
FOR X=0.1 TO 1.0 STEP O.1
Uses LOG(X) extended function.
Results are compared to known correct values.
4-29
EXP (X) FOR X= -10 TO +10 STEP 1
FOR X=-0.9 TO 0.9 STEP 0.1
Uses EXP (X) extended function.
Results are compared to known correct values.
СОК (Хх) FOR X=100 TO 5000 STEP 100
Uses SQR(X) extended function.
Results are compared to known correct values.
SQR(X) * FOR X=100 TO 5000 STEP 100
Uses Newton-Raphson method for square root.
Results are compared tc known correct values.
LOG (EXP (X) ) FOR X=1.0 TO 5000.0 STEP 3.0
Grind test for consistent results using statement:
IF EXP (LOG (EXP (LOG (EXP (LOG (EXP (LOG (EXP (LOG (X) )) )))))))
<> EXP (LOG (EXP (LOG (EXP (LOG (EXP (LOG (EXP (LOG (X) )) )))))))
THEN <error>
ATN (TAN (X) ) FOR X=-1.50 TO 1.50 STEP 0.01 |
Grind test for consistent results using statement
IF ATN (TAN (ATN (TAN (ATN (TAN (ATN (TAN (ATN (TAN (X) ) ) ) )
<> ATN (TAN (ATN (TAN (ATN (TAN (ATN (TAN (ATN (TAN (X) ) ) ) )
THEN <error>
)))))
)))))
MISC. * A=1.0/0.0
Verify floating point divide by zero trap
A%=1%/0%
Verify integer divide by zero trap
А%=60000.
Verify integer conversion error trap
IF INT(40.6621*100.+0.5)/100==40.66
THEN <correct> ELSE <error>
This calculation failed on an 11/40 system which was
having EIS problems
*These tests do not require extended functions.
CPEXER Example:
** JOB NAME TO START OR ATTACH 7? CPEXER
ж* LOGGING IN NEN JOB NAMED "CPEXER”.
CP*STRARTING CPU/EISA/FIS/FPP EXERCISER
CP*RRE YOU CONFIGURED FOR EXTENDED FUNCTIONS ? HELP
CP*DURING THE RSTSAE SYSTEM GENERATION, YOU WERE RSKED WHETHER
CP*OR NOT THIS SYSTEM REQUIRED THE EXTENDED MATHEMRTICAL FUNCTIONS
CPxCSINE, COSINE, ETC. >. IF YOU ANSNERED “YES” TO “FUNCTIONS?” AT
CP*SYSGEN TIME, THEN REPLY “YES” TO THE QUERY BELOW. IF YOU
CP*ANSNERED “NO” AT SYSGEN, THEN YOU ARE NOT CONFIGURED FOR THE
CP*EXTENDED FUNCTIONS AND YOU SHOULD ANSWER “NO” BELON. IF YOU ARE
CP*UNSURE, THEN ANSNER “YES” AND I WILL TRY TO USE ONE OF THE
CP*EXTENDED FUNCTIONS. IF THE OPERATION FRILS, AN ERROR MESSAGE
CP*WILL BE PRINTED AND THIS EXERCISER WILL RBORT. SHOULD THAT
CP»xOCCUR, SIMPLY TYPE “RUNNH” TO RERUN CPEXER AND REPLY “NO”
CP+NHEN AGRIN ARSKED IF YOU RARE CONFIGURED FOR EXTENDED FUNCTIONS.
CP*XARRE YOU CONFIGURED FOR EXTENDED FUNCTIONS ? YES
CP+*ERCH ITERATION TAKES RBOUT 2 MINUTES
СР*НОМ MANY ITERATIONS DO YOU WANT TO RUN ? 5
CPxCP EXERCISER DETACHING
** JOB NAME TO START OR ATTACH ? /ALL :68
»»* CONTROL JOB ENTERING MONITOR MODE.
xx STATUS OF CONTROL SUBJOB<S> AT 83:31 PM
NAME JOB NO. STATE CPU-TIME
CONTRL 8 RN 16. 2
CPERER 12 SL 8.9
<several status printouts later>
*ж* REATTACHING SUBJOB CPEXER
CF*CPU/EISA/FIS/FPP EXERCISER DONE. TOTAL OF 8 ERRORS DETECTED
CP+TO RERTTACH TO CONTROL TYPE “BYE”, TO RERUN TYPE “ RUNNH”.
RERDY
*ж* CPEXER WRIT EXHRUSTED.
*ж* CONTROL TERMINATING JOB #12 CPEXER
E
BYE-F$
READ?
x* JOB NAME TO START OR ATTACH ?
4-31
APPENDIX A
SPECIAL SYSGEN OPTIONS
During development of the RSTS/E system, several hidden options
were built into the SYSGEN program to assist DIGITAL development per-
sonnel with system generations and performance analysis. The hidden
options are invoked through non-standard answers to several SYSGEN
questions. Support for these features is neither expressed nor implied
by this document. The SYSGEN questions of interest are listed below
together with a brief explanation of the non-standard answers required
to invoke the special options.
A.1 CLOCK ?
L, Por C Normal responses to use the standard KW11L Line
Time Clock (L), the KW11P Programmable Clock on line
frequency (P), or the KW1lP with crystal (C).
L/STAT The modifier /STAT is used to include special
statistics gathering code in the RSTS/E monitor.
P/STAT Includes code and tables to record job and disk
access statistics. The statistics code is intended
C/STAT for performance analysis at DIGITAL and is not a
supported feature of RSTS/E.
RSTS/E standardly supports the LP11 and LS11 (dot matrix) line
printers. The printer driver is also coded to handle the LV11 electro-
static printer/plotter in print mode only. The LV1l is not a supported
device and has not been tested with the RSTS/E driver. A hidden option
is used to set the line printer characteristics to those of an LV11.
A.2 LPn: TYPE?
LP or LS Normal response for LPll or LS1ll printers.
LV
Response to set 1М11 printer characteristics.
LVil can only be used in print mode. No plot-
ting capability is provided.
APPENDIX B
ADDRESS AND VECTOR ASSIGNMENTS
The RSTS/E system assumes that all devices attached to the
PDP-1l UNIBUS have been assigned addresses and vectors according to
manufacturing standards. Several devices have so called "Floating
Addresses." This means that the presence or absence of any floating
address device will affect the assignment of addresses to other float-
ing address devices. Similarly, several devices have "Floating
Vectors." Interrupt vectors must be assigned in a specific sequence
and the presence of one type of device will affect the correct assign-
ment of interrupt vectors for other devices. There are also many
standard options which have fixed addresses and vectors. This Appendix
presents the algorithms for assignment of floating addresses and
vectors, and lists the fixed assignments for devices supported under
RSTS/E.
B.1 FLOATING ADDRESSES
Currently the floating address devices include the DJ11 Multi-
plexor, DH1l Multiplexor, DQll Synchronous Line Interface, and the DUll
Synchronous Line Interface. The following ground rules apply to these
devices and future floating address devices:
1. Only new devices will be assigned floating addresses.
Devices now in production will keep their old addresses.
2. Future devices may float both their addresses and interrupt
vectors.
3. The floating address space starts at [email protected]@10(8) and proceeds
upward to 764008 (8).
4. A gap in the address space (no slave SYNC) implies a device
does not exist.
5. The first address of a new type device will always be on a
24N word boundary, where N is the integer value of
(LOG>M+.9999999), and M is the number of device registers,
Number of Registers Possible Boundaries
In Device
1 Any Word
2 XXXXX0, XXXXX4
3,4 XXXXX0
5,6,7,8 [email protected]@, XXXX29, XXXX40, XXXX60
9 thru 16 XXXX00, xxxx4g
6. A "gap" of at least one word will be left after each type
of device, starting on the same boundary the device would
start on. Note that the gap must be at least one word in
length but may be longer than one word. Gap length is
determined by the boundary on which the next device must
begin.
7. Multiple devices of the same type must be addressed
contiguously.
Address 760010 is reserved for the first DJ11. Since the DJ11
has four registers, additional DJ11's are assigned addresses modulo
12 (base 8) immediately following the first DJ11 (i.e. 769919,
7609929, etc.). The modulo 19% (base 8) address following the last DJ11
is left empty and is known as the DJ11 gap. If there are no DJ1l's,
the gap is at 760010. If there is one DJ11, the gap will be at
760020. All gaps must be at least one word in length.
After all DJ1l addresses and the DJ11 gap are defined, the ad-
dress for the first DH11 can be assigned. DHll's have eight registers
which implies a modulo [email protected] (base 8) boundary. The address of the first
DH11 is the first modulo 28 address following the DJ11 gap. If there
are no DJ11's (DJ11 gap at 7690189), the first DH11 is assigned address
769928. Similarly, if there is one DJ11, the DJ1l gap will begin at
768028 and the next available mod 29 boundary is 7680438. All addi-
tional DH11's are assigned addresses modulo 28 immediately after the
first DH1l. The DHIl gap begins on the 298 boundary following the
last DHil.
After all DH11 addresses and the DH11 gap are defined, DQ11
addresses may be assigned. Since the DQll has four registers, a modulo
198 boundary is required. This will be the first mod 1% boundary
following the DH1ll gap. On a system with one DJ11 and one DH11, the
DH1Il gap would be at address 769969 and the first available DQll ad-
dress would be 76997%. All additional DQll's are assigned addresses
B-2
immediately following the first DQ11. The DQ11 gap address is the
mod 1f boundary following the last Doll. Again a gap of at least
one word is required.
Finally DUll addresses can be defined in a similar manner. The
DUll has four registers and requires a modulo 18 boundary, for
example, assume a system has one DJ1l, one DHll, no DQ11, and at
least one DUll. As mentioned above, the DH11 gap would be at
769968. Since there are no DQ11's, the 0011 gap must be located at
the first modulo 1ÿ boundary following the DH11 gap. The DQll gap
would, therefore, be at address 769070. The first available DU11
address would be 769193 and additional DU1il units would be assigned
mod 1f addresses immediately following the first DUIl1.
Addresses for any future floating address devices will be
assigned in a similar manner following the DU11l gap.
DO DU
2 e
8 1
a 2
8 3
a 4
DJ
OM
nS
Gi ©
- ©
ADew
.... Bos ofve Bes afew Area
seer еее. „зе ==. „(== =. =
т = = ._... 0e в яв ев ев 65 ales LE XX J aed
Aeof
AD=M
«BaF
«Bueh
pue
Be]
Don
= В" |
oma
ve...
Seen .... сте. |... «Нез ve. sees
Auf
EY
ADeH
ewe]
=BReF
..._
BB.
„Del
ofa)
«Dex
Fo
-B-L
wDuM
Po.
ean
seni
=” =. >=." uu... > E x „М = = “в тв «в = т =
Amar
=. =. =
...
AD=H
-..]
„Ве?
==.
эВем
«De!
ewe
«Boj
wDak
eFal
«Br
ef aN
= 4 = =
э-
u...
Ana
veal
«BaF
wan
AD RH
ll
==.”
„Dal
...
Ba]
= D = K
oF «|
т. М
Bel
«Den
.FeN
aHal
- че
sank
..e." ...
=... ...
-...- saw] wu. К ==] =-ek
wHAT IS THIS ?
THIS IS A SYMBOLIC TABLE OF UNIBUS
ADDRESSES FOR THE FLOATING ADDRESS
DEVICES DJ11,0D#H11, DQ11, AND DULL,
THE LETTERS A TMRU w CORRESPOND TO
UNIBUS ADDRESSES SHOWN IN THE LIST
TO THE RIGHT,
THE TABLE CONTAINS ALL POSSIBLE
COMBINATIONS OF UP TO FOUR OF EACH
TYPE OF DEVICE, THIS SHOULD COVER
MOST OF THE PDP=131 CONFIGURATIONS,
THE TABLE SHOULD NOT BE USED FOR
ANY MACHINE CONFIGURED FOR MORE
THAN FOUR DJIS,DMIS,DA'S, OR DUS,
COLUMN HEADERS ARE TME NUMBER OF
DJ11tS AND DH11'S, ROW HEADERS ARE
THE NUMBER OF DG11'S AND DUII'S,
HOW TO USE THE TABLE
DETERMINE THE NUMBER OF ODJ11'S,
Dmi1'8, DOLItS, AND DU1118 TO BE
INCLUDED IN THE HARDwuARE CONFIG.
URATION,
ne
ADO.
Fan
Ар.
fa
ADe=J
=FoK
ADJ
„Ё К
==. = |
ADJ
Fk
....
„aM
FLOATING ADDRESS TABLE
0Jit, OMi1, DO11, QUIL
2 2
a 1
2
2
2
3
re)
—
Ар = =
ВЁ = =
oes
AD
BF...
wee
AD...
Fou
ADe-
AD==
BF ma
A...
ADO
=Ё == В = =
«Ме =» E J ._...
ej.
"Нет
- eee =... =... | И д |] = = Jue
AD=N
„Ё = =
A.
Boss
ADeH
Bera.
AD
BF ew
AOL
BF we
= М =
ADeN
BF ee
How
ADeL
Fos
How М + =
.... ojos svanw теч. с... с... ses
Amal
BBesG
AD=H
Brel
ADJ
BFekK
ADSL
BFeM
= М о =
AD=N
BF=0
= М = =
AD=N
eF=0
sree
ADeL
FM
."..
А=-оЁ
Buel
ет =
AD=H
B=el
cow]
AD=N
BF «0
«Ме?
«Joe
AD=J
BF =K
...
ADN
„Ё =
„Ме Р
Je.
ADSL
BF aM
MN
ADeL
FM
eN
- we «о «в "
ADeN
BF=0
=J=Q
Au
Beal
...
AD"
Baw]
...
AD=J
BF aX
= == ||
ADN
=F=0
ADw|
ВР „М
"eN
..D
ADeL
„FM
«ММ
sal aM
woe] = К
FIND THE COLUMN CORRESPONDING TO
THE NUMBER OF DJ11'S AND DMI IS,
SCAN DOWN THIS (COLUMN FOR THE
ROW CORRESPONDING TO THE DESIRED
NUMBER OF DOLI'S AND DU11'S,
AT THE INTERSECTION POINT 13 А
4 BY a BLOCK OF SYMBOLS INCLUD=
ING DASMES AND LETTERS A THRU W,
THE LETTERS REPRESENT THE PROPER
UNIBUS ADDRESS FOR EACH DEVICE,
THE LIST TO THE RIGHT SHOWS THE
ADDRESS CORRESPONDING TO EACH
LETTER, THE DASHES INDICATE NON=
EXISTENT DEVICES, THE 4X4 BLOCK
1S INTERPRETED AS SHOwWN BELOmI
DODD
JH QU
187 AD KM
280 BF eN
JRD = H = 0
4TH - = = P
aw
e.
Bree
Cowen
А. = М
В. = =
Се =
А == М
Baal
Соч.
А = =
Bee]
Cowl
A==}H
Buel
Cond
=
ADDR
Жо < © — 00 0 6) 0 О т Ж г X11 OONMMOOT »
АЕ ==
Се = =
АР - 4)
В. = =
Cuco.
АЁ =]
Во = К
Со = =
АР =]
Reak
Coni
AF=J
| К
Cael
-..
ESSES
760010
760020
760038
760049
700057
760060
7690070
760108
760118
768128
760138
760142
7268150
768160
760178
760200
768210
760220
760238
760248
760250
760269
760270
vu
АЁ ==
ВН. =
АР = |
ВН = =
Cros
AF wl
Вне М
Се ==
AF aL
BHaM
Coal
АР «|
BHaM
С «М
...D
PAGE 1 OF 3
LE
me
ь
N »
сё A
a
Аб ="
Вне
Сэ =
Don.
AF en
BH
Clee
DL=-
AF.
ВН».
Cove
АЁ = =
Внь»
Clea
ales
AFor
8. =
Coun
Dana
АЁ = = АД = = =
ВМ- =
Cle=
Besa
Coca
О. = = 0 = = =
Аб оЁ
ВН *
С ==
DL--
AF =P
Bree
Cle
“low
АБ =.)
В. = =
С = = *
Dose
AF=N
Вне =
Clee
(0 - =
AF eN
ВМ. =
Cima
A.
Brew
AFeL
BHe=
Co.
Den.
Cove
Deva
AF =P
BH=Q
Сл. =
DLe=
Аб М
8BH=0
С =
Derm
AF =]
B==#K
Come
О. =
АЕ «Р
Вн» @
С ==
|
As.
В-- 1
С о = =
Deco
AFeL
BHeW
Cesa
AF=N
BH=0
CJ==
“ев в = Deve
AF =P
BH=Q
CJ=R
DL="
AP =N
Bra
CJ=P
О = = =
АЕ =
В. = К
Cal
PP =
AF oP
BHaQ
CJeR
a| an
AF oN
BH=0
С»?
Aman
Bea]
Coed
[> E =
AF oi
BH =M
С--^
Deco
AF =P
BMe4
CJ=-R
DLaS
АР = М
BHaQ
CJ=P
Deal
АР =
Baek
Cami
D.
AF=eN
BHaû
CJaP
owe
AF =P
BH=0
CJ=R
=Le5
Amo
Boel
C=eJ
0 - -К
АР =
В м М
CeaN
D==0
EXAMPLE
CONSIDER A SYSTEM TU Two
DJ'S, 3 D='S, 1 Das
INCLUDE
AND a DU'S,
THE COLUMN CORRESPONDING TO 2 O0JIS
AND 3 DMIS IS FOUND AT THE CENTER
OF THE TABLE, THE ROW FOR 1 DE AND
4 DU'S IS LOCATED ON PAGE 2 OF 3,
THE BLOCK AT THE INTERSECTION IS
THE ONE SHOWN TO THE LEFT BELOW,
USING THE 4 X 4 BLOCK AND TME LIST
OF ADDRESSES, THE CORRECT FLOATING
ADDRESSES CAN BE READ IMMEDIATELY,
1937 DJII в A " 700016
2ND DJ11 © B " 760029
18T DH11 « D * 766940
2ND DH1}1 в F * 760068
3RD DH11 а м 7600100
137 0011 = x * 760130
157 DULL = Mm ® 760150
2ND DULY = N " 760160
3RD Dull в O = 760178
47h DuIL = P = 76072089
5-8
ре DU
1 a
DJ
DH
vee
< «СЁ
же СЁ
"ef
те СЁ.
was
...Ñ
„CE
u...
waal
“eek
эт С =
те О»
== О»
== СР
== 06
== СЁ
- «ПС
== = М
seCF
naD6
m
=BEG
«REG
...H
=BEG
..H
...
» ВЕС
==
wesw]
con]
«BE =
..P.
«BEN
«.Fe
«REM
<eFl
«BEN
..F!
...
= ВЕН
„FI
...
= = = К
80.
De.
BG!
De.
«861
wDeJ
«BGI
wDeJ
ap т К
«861
«De J
o..."
veel
«BG.
«DH
=86J
eDHa
«BGJ
=DHK
“BGJ
=DHK
meal
«BGJ
=DHK
one]
т. = М
«ВТ.
aDes
Feu
«ВТК
О = =
fr
= ВТК
Del
эЁ = =
«ВТК
«Del
FM
«ВТК
О»
of aM
=. М
wile
Ja
„Ё = =
BIL
DJs
ef ..
«BIL
=DJM
Foe
«BIL
=D JM
oF aN
eBIL
„О.М
oFaN
..-
Aa 8
«ВК
еО =»
«В = =
= Не =
eBKM
SN
Fax
aa
«КМ
=DeN
oFwa
= М =» с»
„КМ
=D=N
«+ М =» =
BKM
eDeN
„Ё „0
= Не
«ВК
«DL
.f..
= 4 р
=BKN
ble
Fes
= Ч = =
=BKN
*DLO
af
Ha.
e BKN
«DLO
afFaP
= |4 = =
e BKN
«DLO
Fup
= М = ©
Awe
AEG
A=EG
www
A=EG
== М
cow]
A=EG
...
owe]
ema]
АеЁ =
же =
A=EH
Fe
AsEH
waf]
A~EH
va]
one,
A=EHM
..P!
mew]
...¡
ADGe
ADGI
ADGI
caw]
ADGI
=}
..e.X
ADGI
...
„=. К
...
ADGe
„= М =
ADGJ
== he
ADGJ
„< МК
ADGJ
MK
e.
ADGJ
HK
seal
..."
№ ==
ADIe
эЁ ==
ADIK
Fos
ADIK
eFel
ADIK
“Fuel
„= М
ADIK
Fuel
...
= = №
ADI»
«FJ.
ADIL
wfle
ADIL
=F JM
ADIL
wf JM
„че М
ADIL
oF JM
N
==» ()
Ca ..
ADK=
Fee
He
ADKM
Feu
"o.
ADKM
oF uN
"Ha.
ADKM
В М
wHal
ADKM
„В „М
„М „О
"ep
ADK=
FL.
He
ADKN
File
= М о =
ADKN
eFLO
«Hon
ADKN
«FLO
HeP
ADKN
=FLO
HP
..0
FLOATING ADORESS TABLE
DJ11,
ADMe
„Ё т
= М = =
elem
ADMO
Fu»
eHow
=]
ADMO
Fer
«Мое
owe
ADMO
„БР
„ней
. Je.
ADMO
„М „@
JR
ADM»
„Ё Ме
= М =
aloe
ADMP
wFihe
a "a.
jus
ADMP
#FNQ
ae.
“Jo”
ADMP,
=FNQ
HR
„Joe
ADMP
„Ё Ма
«Мей
- jus
2
9
AE.
Bees
A=EG
Brae
A-EG
Beak
A=EG
E
coal
A=EG
A."
ses]
...]
А тЁ =
В. =
ACER
ef.
ASEN
BeFl
A=EM
BeFI
...
A e EM
В 1
wow)
wen)
DMI,
2
1
ADG=
Bawa
ADGI
Bros
ADGI
Bee)
ADGI
Beau)
-.—
ADGI
Bea.
J
э == |
ADGw
В.М =
ADGJ
Bela
ADGJ
В. НК
ADGJ
ВНК
"el
ADGJ
B=HK
e.
тет М
pott,
2
2
ADle
BF ee
ADIK
BF ee
ADIK
BFel
ADIK
BF el
==."
ADIK
ВЕ. |
= М
...
ADIS
BFJ.
ADIL
BF Je
ADIL
BF JM
ADIL
BFJM
„== М
ADIL
BFJM
"…eN
=== 0
ou11
2
3
ADKe
BF en
He.
ADKM
BF we
«Mea
ADKM
BFenN
He.
ADKM
BF en
«Мей
ADKM
BFeN
„М.О
ADK»
BFLe
= М = =
= de de
ADKN
BFL=
aria
ADKN
BFLO
= М = =
ADKN
BFLO
ADKN
BFLO
aap
own)
an
ADMe
ВЁ = =
Has
eles
ADMO
Bf em
=» М = «=
- Ju.
ADMO
BF ep
„М = =
slew
ADMO
BFoP
wHal
=] = =
ADMD
BF ap
wal
a JR
ADMe
ВР М.
«Pos
Je.
ADMP
BFNe
= М = =
oles
ADMP
BENQ
= М = =
alow
ADMP
BF NG
HR
=] = =
ADMP
BFNQ
=ideR
#J=8
2 al
A=Ge
Brea
Coon
A+GI
Baer
Cena
AuGI
Bea)
Comm
A=GI
BowJ
Conk
A=GI
В. =
С.К
=== |
Aube
Bara
Coon
AG J
В.М.
Crow
A=GJ
B=HK
Corea
A=GJ
В «НК
Cowl
А= 6.)
BeHK
Cool
...M
о.
АРТ =
Вот
С = = ©
AFIK
Coma
AF IK
Brel
Como
AFIK
В--
CaaM
AF 1K
Baal
CouM
„=. = №
AFI
Bele
[ =
AFIL
Bale
Cove
AFIL
B= JM
Cuna
AFIL
BeJM
CoaN
AFIL
В.М
C=eN
eww)
РО Cai
AFKe
BMao
Coma
AF KM
Brew
Се ==
AFKM
BHaN
Conn
AF KM
BHeN
Се = 0
AFKM
BHaN
Cel
- = в
АЁК =
BHL =
Coan
AF XN
BHL=
Coon
AF KN
BHLO
Coop
AFKN
BNLO
Се «РЁ
AFP KN
BHLO
Creep
reel)
AFMo
ВН =
Clow
AFMO
BHew
Clow
AFMO
BHeP
Cle=
AFMO
BHep
CJ=0
AFMO
BHaP
CJ.
meal
AF Mg
BHNe
Clee
AFMP
BHNe
Clee
AF MP
BHNQ
Clme
AF MP
BHNQ
CJoeR
AFMP
BHNQ
CJeR
al
AFO=
BHew
Clee
“Lee
AFOQ
Brew
CJ.»
La
AFOQ
BHoR
Clea
allem
AFOQ
BHeR
CJesS
el.
AFOQ
BHaR
CJeS
wl wT
AFOs
BHPa
Clam
wLa=
AFOR
BHPe
Cima
wwe
AFOR
BHPS
Clee
oles
AFOR
BHPS
Cle?
= | = =
AFOR
ВЫРЗ
С) =?
eL .U
PAGE
AG.»
Brow
Comm
Dewan
ASGI
Ве = =
Crea
Deco
A-GI
Bes)
С = =
Deco
A=G]
Bee]
Cw=K
Dann
A=GI
Ве = ]
CœsK
==
A+Ge
Bake
[
Powe
A=GJ
Bera
Cova
Deva
AeGJ
Be WK
Coon
Dee.
A=GJ
BeHK
Cowl
Deva
А = б.]
В. НК
Coal
О.М
АР [-
Bere
Cave
Dave
AF IK
Bane
Cane
О. =
AF IK
Bewl
Love
Deva
AFIR
Ben
CœuM
Dawe
AF IK
В. = |.
ConM
О." М
АР} =
Beals
С. =
О. =! ®
AFIL
Belw
Come
Deco
AFIJL
Be JM
Cows
Dees
AFIL
B= JM
CooN
Denn
AFIL
В.) М
CaoN
Deel
2 OF 3
N a
АРК
ВН»
Comm
Don
AFKM
BHes
Crom
Deas
AFKM
BHeN
Се" =
Dena
AFKM
Brey
Ce=0
(0. =
AFKM
BHaN
Сэ = 0
DesPp
AFKe
ВН.
Cova
[> =
AFKN
BML we
Cow.
Dee.
AFKN
BHLO
Cove
Deco
AFKN
BHLO
Coop
Dana
AFKN
BHLO
CreP
De<Q
сё в
AFM»
ВН» =
Cle=
Den.
AFMO
ВН. =
С)»
Dao»
AFMO
BHeP
Cle=
[0
AFMO
BH=p
CJeQ
О. = =
AFMO
BHP
CJaG
Dæ=R
AFMe
BHNe
Claw
Deen
AFMP
BHNe
Clow
О. = =
AFMP
BHNG
oN
Dese.
AFMP
BHNQ
CJeR
Drew
AF MP
BHNQ
CJeR
Deas
> a
AFQe
BHom
С] = =
Dime
AFOG
ВМ. =
Clee
Lee
AFQQ
BH=R
С). =
Di==
AF OQ
BHaR
CJeS
ВС» *
AFOQ
BHaR
С.З
DL=T
AFO=
BHP =
Clan
DLewe
AFOR
BHP =
Claw
Dime
AFOR
BMPS
С ==
Ос."
АРОК
BHPS
С.Т
Di==
AFOR
BHPS
CJ=T
DL=V
00 DU
J a
J 1
3 2
3 3
3 4
a @
4 1
4 2
4 3
4 4
DJ
DH
wale
..De
= «Ё о
ell
wale
=...
"= СС
« «Он
=. =Ё о
+ СС
= ОМ
EI
CG
“onyx
wef]
can)
wale
cule
wofe
e...
“CH
eae
rele
Fe
CH
"01
ж = Ё =»
safe
valk
=]
wef]
.F.
«Сы
wel]
cE]
..P'_
=8E.
..fe
..-.
“BEI
..P.
..Í.
“BEI
..FJ
ene
“BET
waflJ
=» СК
BEI
ef;
-eGK
"|
= ВЕ =
== Ё =
„= О =
„= М =
= ВЕ
= чЁ =
wale
an".
ВЕ
ouFK
== =
== ЯН =
«BEJ
== ЕК
.eGl
= = М
eBEJ
FE
wel
==
ve
“BG.
He
cele
BGK
He
== Те
= ВСК
=DHL
vlan
= ВСК
=DML
== IM
wBGK
“DML
{M
эт «М
«BG.
«ОМ =
-= То
...J.
“BGL
"o
ale
„==
=BGL
= MM
wele
ее Л.
=BGL
=DHM
"IN
«.Jo
«BGL
«НМ
"IN
„= 10
as
Br
wD Je
=eFke
RIM
«DJ.
oFke
= [М
eDJN
эЁ К
+ ue в
wg iM
eDJN
eFKO
eBINM
=DJN
eFxO
...?
eBÏe
«DJ.
„ЁК
=
«BIN
«DJ»
== | =
«BIN
=DJO
oFKke
== |
eg IN
=DJO
«FKP
...-
«BIN
«DJO
«FKP
well
as
ДК =
«Die
.FMe
"Hen
=BKO
aDLe
eFMa
«Мо
=AKO
«DLP
FMa
„Мое
«ВКО
«DLP
=FMQ
How
«8K0
=DLP
<FMQ
„Ней
-BKk=
DL»
eFMe
„ММ
«ВКР
DL»
«HN
= ВКР
=DLO
„Ё Ме
«ММ
«ВКР
= 0-0
wFMR
«НМ =
«ВКР
«019
«FMR
“NS
—
PCI =
enfe
e...
A=E]
won
unbe.
A=EI
-.J
..C.
AvET
waF J
„т СК
А=ЁТ
waft
== СК
..e.,
АеЁ =
wala
wale
eae
A"EJ
"Fe
vba
an
AvEJ
wafFK
э = =
- «Мо
A=EJ
..FE
-= 6
т = 4 =
A= J
safK
owl
«ММ
ADG=
nape
wale
ADGK
wae
= 1“
ADGK
ML
mele
ADGK
ell
„JM
ADGK
„= нь
„= ТМ
„= « М
ADG®
an
„ale
walw
ADGL
„Ho
„ale
....
ADGL
„=. ММ
=. То
..J.
ADGL
„= ММ
„IN
ww Jw
ADGL
== м М
-= [М
„Jo
apie
Eje
eee
ADIM
«FJ».
.K=
- om Bn
ADIM
wF JN
rele
ADIM
=F JN
sek
ADIM
oF JN
= КО
...?
ACI»
FF J-
mu Km
fr
ADIN
„Fl
Ko
J
ADIN
»Ё 70
== К =»
=
ADIN
«FJD
e. XP
el»
ADIN
=F JD
cakP
cel à
ADKe
of Le
Ma
ADKD
File
Ma
ADKO
eFLP
„ММ
ADKO
=FLP
=HMQ
ADKO
ФЕ СР
WMO
e=.aR
ADK»
FL.
oHMe
„Мо
ADKP
„FL.
-oN-
ADKP
„FLO
„ММ
=- Ме
ADKP
FLO
«HMR
= = № =
ADKP
«FLO
эн мя
„NS
FLOATING
DJLI,
ADM=
«Ё №
whe
Ju
ADMO
эЁ М
» 40 =
ala
ADMG
«FNR
«HOw
alas
ADMQ
=FNR
«HOS
=] = =
ADMO
e ENR
=053
ola?
ApMe
„Ё Ме
0
JP»
ADMR
eN.
=JPo
ADMR
oF NS
«O.
wJPe
ADMR
«FNS
„HOT
«JPe
ADMR
=ENS
“HOT
= JPU
2
e
д=Ё =
В=еЁ =
enw
ASE!
Вей =
fe
A=E]
BeFJ
wale
ASE]
B=FJ
.eGK
A=EI
BeFJ
GM
swe
Auto
Вый =
....
....
A“EJ
BefFe
wale
- = =
A=EJ
Во? К
об.
He
A=EJ
BeFK
wail
= = Че
A=EJ
B=FK
call
„HM
DMI,
e
}
ADGe
BeMe
vale
ADGK
В.Н»
.. ie.
ADGK
B=HL
„le
ADGK
Bel
ve JM
ADGK
BehL
ew lM
...
ADG=
Bale
..l.
..J..
ADGL
Bao
wie.
..
ADGL
B=HM
le
ju
ADGL
BaHM
„= [М
wa Jo
ADGL
BeMM
..!IN
wa JO
boty,
2
2
ADle
BF Je
vale
ADIM
ВЕ) =
woke
ADIM
BF JN
cake
ADIM
BFJN
--КО
ADIM
BFJN
cKO
...P
ADI»
BFJe
cole
vole
ADIN
BF Je
vole
ADIN
BFJO
waka
wale
ADIN
BFJO
wal =
ADIN
8FJ0
=- КР
sal @
ADDRESS TABLE
DU11
2
3
ADKe
BFLe
.HMa
ADKO
BFL»
aM
ADKO
BFLP
„НМ.
ADKO
BFLP
MO
ADKO
BFLP
{MO
=. |
Арк
BFLe
те Чо
ADKP
BFLe
„нм.
..N.
ADKP
BFLQ
- HMa
= «Ме
ADKP
BFLO
MR
wale
ADKP
BFLO
siiMR
„= №3
ADMe
BF Ne
ele
alow
ADMQ
BFNe
= 40 =
alee
ADMO
BFNR
HO
saw
ADMO
BFNR
eMH0S
also
ADMO
BFNR
“0S
ele?
ADMw
BFNe
=H0-
«JP»
ADMR
BFNe
«MO.
= JP.
ADMR
BFNS
HD.
JP»
ADMR
BFNS
«HOT
JP.
ADMR
BFNS
«НОТ
«ЛРЬ
> al
Ante
Bape
Cole
Ач БК
Boke
Cole
A=GK
BeHL
Cels
А" СК
BeMl
Ce IM
A=GK
BeÜHL
CoM
...N
А" (=
Bake
Culm
wale
A*GL
Babe
Cela
e.lo.
A=GL
BoHM
Cela
sale
A=GL
В.М
Се [№
.". Jo
AGL
BexM
CeIN
.. JO
ль
АЕ] =
Ве] =
Coke
AFIM
Bele
Coke
AF IM
Be JN
Cake
AF IM
BeJN
С «КО
AF IM
a= JN
Cex0
„>
AF l=
Bale
Cake
onl =
AF IN
Bale
Coke
эт
AFIN
BeJO
Coke
Le
AFIN
BeJO
CokP
ei =
AFIN
B=J0
CekKP
vel 0
nN сё
AF Ke
BHL=
CuMa
AFKO
BHLe
CaM,
AFRO
BHLP
С.М
AFKD
BHLP
CaMQ
AFKO
BHLP
Cong
e
BH »
CoMo
Na
AFKP
BHLe
CuMo
= = М =
AFKP
BHLQ
С.М.
- = М
AFKP
BMLQ
CoM…R
„= №
AFKP
BHLO
Семя
NS
AFMe
BHNe
Суб»
AFMQ
ВЫ.
CJ0=
AFMO
BHNR
CJ.
AFMO
BHNR
cJos
AFMQ
BHNR
Cyos
raw?
AfMe
BHNe
cJ0.
.Pe
AFMR
BHNe
CJOe
чей =
AFMR
BHNS
CJ»
Po
AFMR
BHNS
CJOT
AFMR
BHNS
CJOT
=ePU
" a
AFQe
BHP»
Сб»
Lea
AFOS
BHP =
CJC.
Le.
AFOS
BHPT
Сб.
«Le.
AFOS
BHPT
CJQU
vies
AFOS
BHPT
EQU
Ley
AFQe
BHP =
Со.
wbRa
AFOT
BHpe
Со.
Rs
AFOT
BHPU
CJO.
eL Re
AFOT
BMPU
cJay
wo Re
AFOT
BHPU
cJav
„Аи
PAGE 3 OF 3
© >
AG
Вене
Cole
Dons
А" СК
В.М.
Cole
Pena
A=GK
BeHL
Cela
Dome
A=GK
BeMi
CoIM
Deus
A=GK
B=HL
Colm
DeaN
AG
Bata
Lule
Dela
A"GL
BeHs
Cole
Dele
AeGL
Ве НМ
Cola
Dela
A=GL
BekM
Се [М
Dejo
A=GL
BeHM
Cain
D= JO
aple
BeJo
Cake
Dawe
AF IM
Bade
Cake
Dawe
AF IM
В. / М
СК =
Dees
AF IM
B=JN
C=KO
Quen"
AFIM
BeJN
C=x0
Dee?
Ар =
Ве =
Ce.»
Dale
AFIN
BoJe
Cake
Lo J
AFÍN
BeJO
Cake
Dela
AFIN
B=J0
CeKP
Dele
AFIN
BeJO
CokP
DeLQ
>
AFKe
HL =
С=М о
1
AFRO
BHL =
CoM.
Deve
AFRO
BHLP
CuMa
Den.
AFRO
BHLP
CaMQ
Des.
AFRO
BMLP
CeMQ
De=R
AFK =
BML»
CH.
ON
AFKP
BHLe
CuMo
CuN.
AFKP
BHLQ
CoMo
DeNo
AFKP
BHLQ
CeMR
BaNe
AFKP
BHLQ
CeMA
DeNS
я в
AFMe
BHN=
CJO.
Dre".
AFMO
BHNe
CJO=
Dees
AFMO
BHNR
сло»
Dao»
AFMQ
BHNR
CJOS
О =»
AFMQ
BHNR
cJjos
DenT
АрМ=
BHNe
CJOs
DoPe
AFMR
BHNe
CJ.
DePo
AFMR
BHNS
CJO-
DuPe
AF MR
BHNS
CJOT
Depew
AFMR
BHNS
CJOT
DePU
- »
AFO=
ВнР®
CJQ=
DlLee
AFOS
ВНР»
CJA
OLe=
AFOS
BHPT
CJQ=
Ос."
AFOS
BHPT
cJQu
OLwe
AFOS
BMPT
CJQU
DLeV
ARO
ВН? =
CJGe
О Я.
AFOT
BHpe
Сб»
Р-Я»
AFOT
BHPU
CJA»
OLR»
AFOT
BHPU
cJav
oLRe
AFOT
BwPU
cJav
OLA»
B.2 FLOATING VECTORS
Many devices have floating vectors. The vector assignment se-
quence is normally the same sequence as that in which the devices
enter production. A vector of a new hardware option is not inserted
before the vector for a device that is already in production. Gaps
in the vector assignments are not required. The floating vectors
begin at address [email protected]@ and proceed continuously upwards. The vector
assignment sequence for current devices is defined below.
First Next Vector | Max # BR
Device Address Addr. Size Units | Level RSTS/E Notes
DC11 1740800 +18 19 32 BR5
KL11, DLIlA, B| 176589 +18 19 16 BR4 NON-CONSOLE
DP11 174778 -18 19 32 BR5 2788 ONLY
DM11A 175988 +18 19 16 BR5 NOT SUPPORTED
DN11 175209 +18 4 16 BR4 NOT SUPPORTED
DM11BB 178588 +10 4 16 BR4
DR11A, C 167778 -10 19! 32 BRS NOT SUPPORTED
PA611 READER 172698 + 4 4! 16 BR4 NOT SUPPORTED
PA611 PUNCH 172788 + 4 4 ! 16 BR4 NOT SUPPORTED
DT11 (DTÿ3-FP) | 174288 + 2 18! 8 BR7 NOT SUPPORTED
DX11 176288 +40 18 4 BR4 NOT SUPPORTED
DL11C, D, E 175618 +18 18! 31 BR4
DJ11 FLOAT +18 18! 16 BR4 NOT SUPPORTED
DH11 FLOAT +28 18! 16 BR5
GT 49 172808 28! BR4 NOT SUPPORTED
LPS11 179489 +49 38! 14 BR5,6 | NOT SUPPORTED
DQ11 FLOAT +18 18 16 BR5 NOT SUPPORTED
KW11W 172489 NA 18! 1 NOT SUPPORTED
DU11 FLOAT +19 19! 16 BR5 2788 ONLY
Floating address and vector devices which are not supported under
RSTS/E must be identified during system generation so that the system
is configured for the correct addresses and vectors.
'The first vector for the first device of this type must always be on
a 19(8) boundary.
B.3 FIXED ADDRESSES AND VECTORS
The table below lists the devices supported
have fixed addresses and vectors.
under RSTS/E which
Device Address Vector BR Level RSTS/E Notes
RC11/RC64 177448 218 BR5 UP TO 4 PLATTERS
RF11/RS11 177468 284 BRS UP TO 8 PLATTERS
RK11/[email protected]/RKG5 177488 228 BRS UP TO 8 DRIVES
RP11C/RPB2/RPO3 176719 254 BR5 UP TO 8 DRIVES
RH11/RS93/RSB4 172948 284 BR5 UP TO 4 DRIVES
RH11/RPG4 176788 254 BR5 UP TO 8 DRIVES
RX11/RX01 177178 264 BR5 UP TO 8 DRIVES
TC11 177348 214 BR6 UP TO 8 DRIVES
TM11/TU18 172528 224 BR5 UP TO 8 DRIVES
RH11/[email protected]/TUl6 172449 224 BR5 UP TO 8 DRIVES
LP11, LS11 (LPG) 177514 288 BR4 UP TO 8 PRINTERS
(LP1) 164984 178 BR4 DEPENDING ON
(LP2) 164814 174 BR4 SPEED.
(LP3) 164924 270 BR4
(LP4) 164934 274 BR4
(LPS) 164944 774 BR4
(LP6) 164954 778 BR4
(LP7) 1648964 764 BR4
CR11, CM11 177168 239 BR5
CD11 177168 238 BR4 NEW ADDRESS!
CD11 (172468) 239 BR4 OLD ADDRESS!
KW11L 177546 108 BR6
KW11P 172549 194 BR6
KG11 178788 NONE NONE 2789 ONLY
KL11, DL11A, DL11B | 177568 69 BR4 CONSOLE INTERFACE
'The CD11 address was changed by CD11 ECO number 13.
INDEX
Address and vector assignments,
B-1
Addresses, floating device, 2-3,
B-1
Attaching exerciser programs, 3-4
Automatic restart, 3-30
Bad block, 2-6
a .
+ +
Building the system £
+1
LAC
Building the SYSTST file
Sr
5,
Un cd
2-1
2-1
Card reader exerciser, CREXER,
4-17
Commands, control program, 3-2
Configuration,
disk, 2-4
minimum, 2-2
software, 2-3
CONTRL, See control program
Control file (TSTBLD.CTL), 2-15
Control program (CONTRL), 1-1, 3-1
commands, 3-2
guidelines for using the, 3-31
starting the, 3-1
terminating the, 3-4
CPEXER processor exerciser, 4-29
Creating the system disk, 2-4
CREXER, card reader exerciser,
4-17
DBEXER RH11/RP04 disk exerciser,
DECtape exerciser, DTEXER, 4-10
DECtape, SYSTST build from, 2-20
DEFAULT example, 2-13
DEFAULT option, 2-11
Default start-up conditions,
setting the, 2-11
Device exerciser abstracts, 4-1
Device exercisers, 1-1
Devices, missing, 2-2
DFEXER, RF11/RS11 disk exerciser,
4-4
Disk cartridge, SYSTST build from,
2-15
Disk configuration, 2-4
Disk exercisers, 4-1
Disks, non-system, initializing,
2-8
DKEXER, RK11/RK03/RKO5 disk
exerciser, 4-5
DPEXER, RP11-C/RP03 disk
exerciser, 4-7
DSKINT example, 2-7
DSKINT option, 2-6
DSKINT queries, 2-7, 2-8
DTEXER DECtape exerciser, 4-10
Exercisers, device, 1-1
Exercisers, disk, 4-1
Exerciser programs,
attaching, 3-4
running, 3-5
starting, 3-3
status of, 3-3
Fixed addresses and vectors, B-8
Floating addresses, B-1
Floating address table, B-4, B-5,
B-6
Floating device addresses, 2-3
Floating vectors, 2-3, B-7
Generation, system, 2-2
Guidelines for using CONTRL, 3-31
Initializing non-system disks, 2-8
Initializing the system disk, 2-6
Keyboard exerciser, KBEXER, 4-25
KBEXER, keyboard exerciser, 4-25
Line Printer exerciser, LPEXER, 4-19
LPEXER, Line Printer exerciser, 4-19
Magtape exerciser, MTEXER, 4-13
Magtape, SYSTST build from, 2-19
Minimum configuration, 2-2
Missing devices, 2-2
MTEXER, magtape exerciser, 4-13
Non-supported devices, 2-3
Non-system disks, initializing, 2-8
Option,
DEFAULT,
DSKINT,
PATCH, 2-5
REFRESH, 2-10
START, 2-13
Options, special SYSGEN, A-1
2-11
2-6
Paper tape punch exerciser, PPEXER,
4-21
INDEX-1
Paper tape reader exerciser,
PREXER, 4-23
PATCH example, 2-5
PATCH option, 2-5
Pattern tests, 4-2
Pound sign (#), 3-3
PPEXER paper tape punch exerciser,
4-21
PREXER, paper tape reader exer-
ciser, 4-23
Processor exerciser, CPEXER, 4-29
REFRESH example, 2-10
REFRESH option, 2-10
Reliability test, 1-1
Restart, automatic, 3-30
Restarting the system test, 3-28
Restarting the system test after
a crash, 3-29
RF11/RS11 disk exerciser, DFEXER,
4-4
RH11/RP04 disk exerciser, DBEXER,
4-9
RK11/RK03/RKO5 disk exerciser,
DKEXER, 4-5
RP11-C/RP03 disk exerciser,
DPEXER, 4-7
Running exerciser programs, 3-5
Running the system reliability
test, 3-1
Setting the default start up
conditions, 2-11
Slash (/), 3-3
Software configuration, 2-3
Special SYSGEN options, A-1
START example, 2-14
Starting exerciser programs, 3-3
Starting the control program,
CONTRL, 3-1
Starting time sharing, 2-13
START option, 2-13
Status of exerciser programs,
SYSGEN, 2-2
special options, A-1
System disk,
creating the, 2-4
initializing the, 2-6
System files, building the,
System generation, 2-2
System patches, 2-5
System reliability test, running
the, 3-1
System test files, See SYSTST
System test programs, See SYSTST
System test, restarting after a
crash, 3-29
System test, restarting the,
SYSTST build,
from DECtape, 2-20
from disk cartridge,
from magtape, 2-19
SYSTST files, building the,
SYSTST programs, 1-2
SYSTST system test, 1-1
3-3
2-10
3-28
2-15
2-15
Terminal interfaces, 2-2
Terminating the control program,
CONTRL, 3-4
Time sharing, starting,
TSTBLD.CTL, control file,
TSTBLD program, 2-16
2-13
2-15
Vector assignments, address and,
B-1
Vectors and fixed addresses,
Vectors, floating, 2-3, B-7
B-8
INDEX-2
HOW TO OBTAIN SOFTWARE INFORMATION
SOFTWARE NEWSLETTERS, MAILING LIST
The Software Communications Group, located at corporate headquarters in
Maynard, publishes software newsletters for the various DIGITAL products.
Newsletters are published monthly, and keep the user informed about cus-
tomer software problems and solutions, new software products, documenta-
tion corrections, as well as programming notes and techniques.
There are two similar levels of service:
. The Software Dispatch
The Digital Software News
The Software Dispatch is part of the Software Maintenance Service. This
service applies to the following software products:
PDP-9/15
RSX-11D
DOS/BATCH
RSTS/E
DECsystem-10
A Digital Software News for the PDP-11 and a Digital Software News for
the PDP-8/12 are available to any customer who has purchased PDP-11 or
PDP-8/12 software.
A collection of existing problems and solutions for a given software
system is published periodically. A customer receives this publication
with his initial software kit with the delivery of his system. This
collection would be either a Software Dispatch Review or Software Per-
formance Summary depending on the system ordered.
A mailing list of users who receive software newsletters is also main-
tained by Software Communications. Users must sign-up for the news-
letter they desire. This can be done by either completing the form sup-
plied with the Review or Summary or by writing to:
Software Communications
Р.О. Вох Е
+ NI TILA
Maynard, Massachusetts 01754
SOFTWARE PROBLEMS
Questions or problems relating to DIGITAL's software should be reported
as follows:
North and South American Submitters:
Upon completion of Software Performance Report (SPR) form remove last
copy and send remainder to:
Software Communications
P.O. Box F
Maynard, Massachusetts 01754
The acknowledgement copy will be returned along with a blank SPR form
upon receipt. The acknowledgement will contain a DIGITAL assigned SPR
number. The SPR number or the preprinted number should be referenced in
any future correspondence. Additional SPR forms may be obtained from
the above address.
All International Submitters:
Upon completion of the SPR form, reserve the last copy and send the re-
mainder to the SPR Center in the nearest DIGITAL office. SPR forms are
also available from our SPR Centers.
PROGRAMS AND MANUALS
Software and manuals should be ordered by title and order number. In the
United States, send orders to the nearest distribution center.
Digital Equipment Corporation Digital Equipment Corporation
Software Distribution Center Software Distribution Center
146 Main Street 1400 Terra Bella
Maynard, Massachusetts 01754 Mountain View, California 94043
Outside of the United States, orders should be directed to the nearest
Digital Field Sales Office or representative.
USERS SOCIETY
DECUS, Digital Equipment Computers Users Society, maintains a user ex-
change center for user-written programs and technical application infor-
mation. The Library contains approximately 1,900 programs for all
DIGITAL computer lines. Executive routines, editors, debuggers, special
functions, games, maintenance and various other classes of programs are
available.
DECUS Program Library Catalogs are routinely updated and contain lists
and abstracts of all programs according to computer line:
. PDP-8, FOCAL-8, BASIC-8, PDP-12
. PDP-7/9, 9, 15
. PDP-11, RSTS-11
. PDP-6/10, 10
Forms and information on acquiring and submitting programs to the DECUS
Library may be obtained from the DECUS office.
In addition to the catalogs, DECUS also publishes the following:
DECUSCOPE -The Society's technical newsletter, published bi-monthly,
aimed at facilitating the interchange of technical in-
formation among users of DIGITAL computers and at dis-
seminating news items concerning the Society. Circula-
tion reached 19,000 in May, 1974.
PROCEEDINGS OF -Contains technical papers presented at DECUS Symposia
THE DIGITAL held twice a year in the United States, once a year
EQUIPMENT USERS in Europe, Australia, and Canada. :
SOCIETY
MINUTES OF THE -A report of the DECsystem-10 sessions held at the two
DECsystem-10 United States DECUS Symposia.
SESSIONS
COPY-N-Mail -A monthly mailed communique among DECsystem-10 users.
LUG/SIG -Mailing of Local User Group (LUG) and Special Interest
Group (SIG) communique, aimed at providing closer
communication among users of a specific product or
application.
Further information on the DECUS Library, publications, and other DECUS
activities is available from the DECUS offices listed below: |
DECUS DECUS EUROPE
Digital Equipment Corporation Digital Equipment Corp. International
146 Main Street | (Europe)
Maynard, Massachusetts 01754 Р.О. Box 340
1211 Geneva 26
Switzerland
RSTS/E
System Reliability Test
DEC-11-ORSRB-B-D
READER'S COMMENTS
NOTE: This form is for document comments only. Problems
with software should be reported on a Software
Problem Repcrt (SPR) form (see the HOW TO OBTAIN
SOFTWARE INFORMATION page).
Did you find errors in this manual? If so, specify by page.
Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.
— c— === AEE MES CS UU ET SE EEE DD GEES GEES whee EEE o — o — Sask Gay Gan — U— MIR ENT GTR GEM MANE WED NA A E aes ama
©
с
=
1.2
E
|2
-©
о
5 Is there sufficient documentation on associated system programs
м required for use of the software described in this manual? If not,
8 what material is missing and where should it be placed?
Ф
a
Please indicate the type of user/reader that you most nearly represent.
[] Assembly language programmer
[J] Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
ООО
Non-programmer interested in computer concepts and capabilities
Name Date
Organization
Street
City State Zip Code
or
Country
If you do not require a written reply, please check here. a
EN EE MES TIES AEE CUT PE CE WAGE UU A ee I AS A CU A US A A A PA o MU A A SES SEE ESS me
Fold Here
Do Not Tear - Fold Here and Staple
FIRST CLASS
PERMIT NO. 33
MAYNARD, MASS.
BUSINESS REPLY MAIL
NO POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES
Postage will be paid by:
Software Communications
Р. O. Вох Е
Maynard, Massachusetts 01754
DIGITAL EQUIPMENT CORPORATION
MAYNARD, MASSACHUSETTS 01754
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement