Trailing-Edge
-
PDP-10 Archives
-
red405a2
-
red/red20.usr
There are no other files named red20.usr in the archive.
HARDWARE RELIABILITY TEST SYSTEM (REVISION 2)
---------------------------------------------
TABLE OF CONTENTS
-----------------
SECTION PAGE
------- ----
I. WHAT IS THE PURPOSE OF THE HARDWARE
RELIABILITY TEST SYSTEM?..............................1
II. WHAT DOES THE HARDWARE RELIABILITY
TEST SYSTEM CONTAIN?..................................2
III. WHAT HARDWARE WILL THE HARDWARE RELIABILITY
TEST SYSTEM EXERCISE?.................................4
IV. WHAT IS THE PROCEDURE TO START RUNNING
THE HARDWARE RELIABILITY TEST?........................6
V. WHAT ARE THE GOALS OF THE HARDWARE
RELIABILITY TEST SYSTEM?..............................9
VI. HOW IS DATA OBTAINED TO PROVE THE GOALS OF
THE HARDWARE RELIABILITY TEST ARE ACHIEVED?..........11
APPENDIX
--------
I. STARTING UETP........................................13
II. CREATING DISK STRUCTURES.............................19
III. TEST RESULTS.........................................25
IV. LEGAL BUGCHECKS AND BUGINFS..........................27
Page 1
SECTION I
WHAT IS THE PURPOSE OF THE HARDWARE RELIABILITY TEST SYSTEM?
________________________________________________________________
THE HARDWARE RELIABILITY TEST SYSTEM IS A DEC SUPPORTED
OPERATING SYSTEM. A HEAVY (SIMULATED) USER LOAD IS USED TO
VERIFY TOTAL SYSTEM FUNCTIONALITY. ALL 2020 SYSTEMS UNDERGO
STRINGENT CHECKOUT PROCEDURES DURING MANUFACTURE. THESE
PROCEDURES INCLUDE NUMEROUS QUALITY AND PERFORMANCE TESTS ON
INDIVIDUAL COMPONENTS AND ASSEMBLIES. IN ADDITION TO THESE
CHECKS THE SYSTEM SUCCESSFULLY COMPLETES A 48-HOUR FINAL
ACCEPTANCE TEST USING THE HARDWARE RELIABILITY TEST SYSTEM. THE
2020 HARDWARE RELIABILITY TEST SYSTEM IS ALSO UTILIZED BY THE DEC
FIELD SERVICE ENGINEER TO DEMONSTRATE TO THE CUSTOMER TWO POINTS.
FIRST, THAT THE INTEGRITY OF HIS DECSYSTEM 2020 HARDWARE HAS NOT
BEEN COMPROMISED DURING SHIPPING OR INSTALLATION. SECONDLY, THAT
HIS DECSYSTEM 2020 HARDWARE CAN SUPPORT AN OPERATING SYSTEM AND
USER LOAD THAT IS REPRESENTATIVE OF NORMAL SYSTEM OPERATION.
THE TARGET AUDIENCE OF THIS DOCUMENT IS THE CUSTOMER WHO
PURCHASES A DECSYSTEM 2020 AND THE FIELD SERVICE ENGINEER USING
THE HARDWARE RELIABILITY TEST SYSTEM. EACH SECTION FOCUSES ON A
QUESTION ABOUT THE HARDWARE RELIABILITY TEST THAT THE CUSTOMER
AND/OR FIELD ENGINEER WILL BE CONCERNED WITH. ANSWERS ABOUT THE
CONTENTS, HARDWARE TESTED, PROCEDURE TO RUN AND GOALS OF HARDWARE
RELIABILITY TESTING ARE DESCRIBED IN THE FOLLOWING TEXT.
Page 2
SECTION II
WHAT DOES THE 2020 HARDWARE RELIABILITY TEST SYSTEM CONTAIN?
_________________________________________________________________
THE 2020 HARDWARE RELIABILITY TEST SYSTEM CONTAINS THE
USER ENVIRONMENTAL TEST PACKAGE (UETP). THIS TEST PACKAGE IS THE
FOUNDATION FOR DEMONSTRATING THE HARDWARE RELIABILITY. THE UETP
SYSTEM IS USED FOR SEVERAL REASONS. FIRST, IT PROVIDES AN EASY
MEANS OF IMPLEMENTING SPECIFIC TEST PROGRAMS TO BE RUN IN
TIMESHARING UNDER BATCH. SECONDLY, IT HAS THE ABILITY TO
INTERCEPT CERTAIN ERRORS AND TO TRANSLATE THEM INTO A MORE
UNDERSTANDABLE FORM FOR THE FIELD ENGINEER RUNNING THE PACKAGE.
THIRDLY, UETP KEEPS A JOURNAL OF THE STATUS OF EACH TEST BEING
RUN (INCLUDES NUMBER OF ERRORS AND PASSES COMPLETED), ALL TEST
MESSAGES (IN FILE "RUN.LOG"), AND ALL "MAJOR" UNEXPECTED ERRORS
(IN FILE "EXCEPTION.LOG"). THIS TEST IS RUN UNDER THE TOPS20
OPERATING SYSTEM.
SEVERAL BATCH JOBS ARE SUBMITTED AND CONTROLLED BY UETP.
THESE BATCH PROGRAMS ARE WRITTEN IN A VARIETY OF LANGUAGES WHICH
MAY BE USED BY THE CUSTOMER. THE LANGUAGES INCLUDE ALGOL, BASIC,
COBOL AND FORTRAN. DBMS IS ALSO UTILIZED. BATCH PROGRAMS ARE
WRITTEN TO CONTROL THE RUNNING OF BOTH THE CPU FUNCTIONAL AND
MEMORY DIAGNOSTICS. OTHER BATCH PROGRAMS ARE RUN TO EXERCISE THE
PERIPHERALS. ALL TESTS WERE EITHER ADAPTED FROM CUSTOMER
BENCHMARKS, ORIGINATED FROM SPECIFIC DEVELOPMENT PROJECTS/GROUPS,
OR ARE DIAGNOSTICS. A BRIEF DESCRIPTION OF THE ABOVE MENTIONED
PROGRAMS FOLLOWS.
Page 3
ALGOL A MODIFIED BENCHMARK PROGRAM (WHEATSTONE TIMING TEST) WHICH
----- CHECKS THE ALGOL-SYSTEM ON INTEGER ARITHMETIC, LONG REAL
ARITHMETIC, TRIGONOMETRIC FUNCTIONS AND ARRAY HANDLING.
BASIC A MORTGAGE - TABLE CALCULATION IS DONE AND THE RESULTS ARE VERIFIED.
-----
DBMS A TEST OF THE DATA BASE MANAGEMENT SYSTEM, USING FORTRAN AND
---- THEN COBOL, CREATING A DATA BASE, QUERYING ITS CONTENTS
AND ENTERING NEW ITEMS (CUSTOMER ORDER PROCESSING).
RANCBL
------ THESE PROGRAMS ARE CHECKING DISK I/O USING COBOL AND
RANFOR FORTRAN (FORMATTED AND UNFORMATTED I/O).
------
MTAXX THIS IS A FORTRAN BASED MAGTAPE I/O TEST ON:
----- 1. SKIP FILE, SKIP RECORD, BACKSPACE AND REWIND
(INSTALLATION DEFAULT 1600 BPI PE)
2. MAGTAPE DATA INTEGRITY IN INDUSTRY COMPATIBLE
MODE: A PATTERN OF INCREASING RECORD-SIZES
AND FILE-SIZES IS WRITTEN UNTIL EOT AND VERIFIED
BY READING BACK AND COMPARING
DUPA
------ THESE 4 PROGRAMS CHECK THE NETWORK-DATAPATH (IF PRESENT) UP TO
DUPB BUT NOT INCLUDING THE MODEM (HARDWARE IS IN LOOPBACK)
------ BY SENDING A FILE INTO NETWORK AND COMPARING
DUPAB THE RECEIVED FILE WITH THE ORIGINAL ONE.
-----
TEST72
------
DIAGS THIS TEST RUNS ALL TIMESHARING CPU FUNCTIONAL DIAGNOSTICS UNDER
----- THE DIAGNOSTIC MONITOR SMMON.
MEMORY THIS TEST RUNS THE TIMESHARING CPU/MEMORY RELIABILITY DIAGNOSTIC
------ UNDER THE DIAGNOSTIC MONITOR SMMON.
LPT0 THIS PROGRAM PRINTS A "SY ALL" AND MONITR.STS AT THE COMPLETION
---- OF EACH PASS.
DN22IN THESE PROGRAMS ARE SIMILIAR TO THE DUPA,DUPB,DUPAB,TEST72 PROGRAMS.
------ INSTEAD OF SENDING A FILE INTO THE LOCAL HARWARE AND LOOPING IT
DN22OU BACK, THESE PROGRAMS SEND A FILE THROUGH THE DN22 (IF PRESENT) AND
------ LOOPBACK THE FILE THROUGH THE DN22.
Page 4
SECTION III
WHAT HARDWARE WILL THE HARDWARE RELIABILITY TEST SYSTEM EXERCISE?
_________________________________________________________________
THE HARDWARE RELIABILITY TEST SYSTEM WILL SUPPORT ANY
DECSYSTEM 2020 WHICH IS MINIMALLY CONFIGURED, TO A SUBSET (SEE
NOTE 1) OF THE MAXIMUM ALLOWABLE CONFIGURATION. THE TABLE BELOW
ESTABLISHES THE LOWER AND UPPER BOUNDS THAT COMPRISE SUPPORTABLE
CONFIGURATIONS.
2020 SYSTEM CONFIGURATION
ITEM MIN. SYSTEM TYP. SYSTEM MAX. SYSTEM
---- ----------- ----------- -----------
CPU (KS10) 1 1 1
MEMORY (64Kw Arrays) 128Kw, (2) 256Kw, (4) 512Kw, (8)
DISK, RM03/RP06 1 2 8
TAPE, TU45 OR TU77 1 1 4
COMM. LINES, SYNCHRONOUS 0 1 2
TERMINAL LINES (#DZ11's) 8 (1) 16 (2) 32 (4)
PRINTER, LP05/LP14/LP26 0 1 1
CTY, LA36 1 1 1
CARD - READER 0 0(SEE NOTE 1) 1
DN22 0 0 2
TABLE 1
-------
NOTE 1:
---- -
THE CARD READER IS NOT SUPPORTED BY THE HARDWARE RELIABILITY TEST
SYSTEM. SEE THE DOCUMENT PS:<RED>REDCOM.MEM FOR INFORMATION ABOUT
THE HARDWARE ACCEPTANCE FOR THE DN22.
Page 5
THE CPU, MEMORY AND DISK DRIVE(S) ARE CONTINUOUSLY
EXERCISED THROUGHOUT THE DEMOSTRATION. THE BATCH SYSTEM WITHIN
THE TOPS20 MONITOR ALLOWS THE PROGRAMS EXERCISING THE TAPE(S) AND
SYNCHRONOUS COMMUNICATION LINE TO BE RUN ONCE THEIR RESPECTIVE
JOBS HAVE BEEN SUBMITTED INTO THE BATCH QUEUES. THE LINEPRINTER
AND CONSOLE TERMINAL WILL HAVE "CURSORY" TESTING DONE ON THEM TO
VERIFY THEIR FUNCTIONALITY. SECTION V OF THIS DOCUMENT WILL
QUANTIFY THE GOALS TO BE OBTAINED DURING THE HARDWARE RELIABILITY
DEMONSTRATION.
Page 6
SECTION IV
WHAT IS THE PROCEDURE TO START RUNNING HARDWARE RELIABILITY?
________________________________________________________________
THE FIELD ENGINEER MUST FULLY INSTALL THE 2020 SYSTEM IN
ACCORDANCE WITH THE DECSYSTEM 2020 INSTALLATION MANUAL. THE
INSTALLATION MANUAL REQUIRES THE SYSTEM TO HAVE ALL CABLES
CONNECTED (REFERENCE SECTION 4), ALL PRE-POWER AND POWER-UP
CHECKOUTS PERFORMED (REFERENCE SECTION 5), AND THE SYSTEM
CHECKOUT COMPLETED (REFERENCE SECTION 6).
THE MEDIA ON WHICH THE HARDWARE RELIABILITY TEST SYSTEM
RESIDES IS CALLED THE "RED PACK". THE "RED PACK" IS USED BY THE
FIELD SERVICE ENGINEER TO DO THE SYSTEM CHECKOUT AS OUTLINED IN
SECTION 6 OF THE 2020 INSTALLATION MANUAL. IF FOR ANY REASON IT
IS NECESSARY FOR THE FIELD SERVICE ENGINEER TO BUILD A "RED
PACK", HE SHOULD REFERENCE "GETTING STARTED WITH RED", APPENDICES
I AND II (<RED>RED20.HLP). "GETTING STARTED WITH RED"
ILLUSTRATES THE PROCEDURE THE DEC FIELD SERVICE ENGINEER USES TO
FORMAT AND BUILD THE PACK. TO THOROUGHLY EXERCISE ALL HARDWARE
COMPONENTS OF THE SYSTEM DURING THE DEMOSTRATION IT IS NECESSARY
TO HAVE A "RED PACK" TAILORED TO MATCH THE SYSTEM CONFIGURATION.
THE USER ENVIRONMENTAL TEST PROCESS (UETP) NEEDS TO BE INSTRUCTED
AS TO; THE NUMBER OF MAGTAPE DRIVES ON THE SYSTEM, SYNCHRONOUS
COMMUNICATION CAPABILITIES, AND LINEPRINTER CHARACTERISTICS (IF
PRESENT). IF THE "RED PACK" BEING USED REPRESENTS THE SYSTEM
CONFIGURATION, PROCEED, OTHERWISE REFERENCE "GETTING STARTED WITH
RED", APPENDIX III.
Page 7
TO PREPARE FOR THE BEGINNING OF HARDWARE RELIABILITY IT
IS NECESSARY TO MOUNT FORMATTED SCRATCH PACKS ON ALL DISK DRIVES,
WITH THE EXCEPTION OF DRIVE 0 WHERE THE "RED PACK" SHOULD BE
MOUNTED. TO AVOID CONFUSION LATER, ONLY CYCLE UP DRIVE 0 AT THIS
POINT. A SCRATCH TAPE (EITHER 1200 OR 2400 FEET) WITH THE WRITE
RING INSERTED SHOULD BE MOUNTED ON ALL MAGTAPE DRIVES. THESE
DRIVES AS WELL AS THE LINEPRINTER (IF ONE EXISTS) SHOULD BE
ON-LINE. IF THE SYSTEM HAS SYNCHRONOUS COMMUNICATIONS, A BC05C
CABLE WITH A H325 WRAP AROUND PLUG SHOULD BE CONNECTED TO THE
FIRST DUP-11.
ON THE "RED PACK", UETP IS DESIGNED TO RUN AUTOMATICALLY
ONCE THE SYSTEM IS BOOTED. THIS IS TRUE, AS LONG AS THE "DO
NO-UETP" COMMAND WAS NOT ISSUED. IF THIS COMMAND WAS ISSUED OR
THERE IS ANY DOUBT OF ITS STATUS, IT WILL BE NECESSARY TO BRING
UP THE SYSTEM FROM THE "RED PACK", LOGIN (AS F-S), TYPE "ENABLE",
TYPE "DO UETP" AND WAIT FOR IT TO COME BACK WITH "Kmic". THIS
WILL RE-INSTATE THE AUTOMATED UETP START-UP. AFTER THIS IS
COMPLETED, THE 2020 SHOULD BE BROUGHT DOWN OUT OF TIMESHARING
MODE AND INTO CONSOLE MODE.
TO START UETP FOLLOW THE EXAMPLE IN APPENDIX I OF THIS
DOCUMENT. ASSUMING THE PROCEDURE OUTLINED IN THE PRECEDING TEXT
HAS BEEN FOLLOWED, AFTER APPROXIMATELY 5 MINUTES A STATUS OF THE
TESTS BEING RUN WILL BE PRINTED ON THE CONSOLE TERMINAL. AT THIS
POINT ATTACH TO THE OPERATOR ON JOB #1 WHERE UETP IS RUNNING.
THIS CAN BE DONE AS ILLUSTRATED AT THE END OF APPENDIX I.
Page 8
A SYSTEM WITH MORE THAN ONE DISK DRIVE WILL NEED DISK
STRUCTURES DEFINED TO EXERCISE ALL DRIVES. AN EXAMPLE CONTAINED
IN APPENDIX II SHOWS THE METHOD TO CREATE TWO USER STRUCTURES
(USER AND USER1) AS TWO SINGLE PACK STRUCTURES.
Page 9
SECTION V
WHAT ARE THE GOALS OF THE HARDWARE RELIABILITY TEST SYSTEM?
________________________________________________________________
THE PURPOSE OF THIS SECTION IS TO ESTABLISH THE CRITERIA
THAT WILL QUANTIFY THE GOALS OF THE HARDWARE RELIABILITY TEST
SYSTEM. AS A GENERAL STATEMENT, THERE WILL BE NO ERRORS ALLOWED
BY ANY PART OF THE 2020 SYSTEM DURING THE ENTIRE DEMONSTRATION.
TO QUALIFY THIS STATEMENT IT IS NECESSARY TO EXPLAIN THE
FOLLOWING; ERROR HANDLING AND RECOVERY, THE PARTS OF THE SYSTEM
WHICH COULD EXHIBIT THESE ERRORS, AS WELL AS THE RUNTIME AND
SYSTEM LOAD DURING THIS PERIOD.
THERE WILL BE NO ERRORS TOLERATED BY THE CPU AND ONLY
RECOVERABLE ERRORS TOLERATED BY THE DISK AND TAPE DRIVE(S). THE
HARDWARE RELIABILITY TEST SYSTEM WILL BE RUN FOR 48 CONTINUOUS
HOURS WITH A SYSTEM LOAD AVERAGE CLOSE TO 4.0 (4 JOBS DEMANDING
CPU - SERVICE AT ANY ONE INSTANT).
DUE TO THE NATURE OF ELECTROMECHANICAL MASS STORAGE
DEVICES AND THEIR MEDIA, A SCENARIO ON "HARD" AND "SOFT" ERRORS
FOLLOWS. THE OPERATING SYSTEM TRIES TO SAFEGUARD DATA TRANSFERS
ON DISKS AND TAPES VIA CHECKSUMMING. A CHECKSUM IS COMPUTED FOR
BOTH READ AND WRITE TRANSFERS. THE COMPARISON BETWEEN THE ACTUAL
CHECKSUM DONE ON A WRITE TRANSFER HAS TO REFLECT THE SAME
CALCULATED CHECKSUM WHEN THIS DATA IS READ BACK, THEREBY INSURING
DATA INTEGRITY. IF THESE CHECKSUMS DIFFER, THE MONITOR WILL
RETRY THIS FAILING DATA TRANSFER. IF THE SECOND OR FOLLOWING
Page 10
DATA TRANSFERS PRODUCE A VALID CHECKSUM COMPARISON, THE ERROR IS
RECOVERABLE. THIS ERROR IS CALLED A "SOFT ERROR". IF THE RETRY
ALGORITHM EXCEEDS THE MAXIMUM TOLERANCE OF RETRIES, THE ERROR IS
IRRECOVERABLE. THIS ERROR IS CALLED A "HARD ERROR".
THE "SOFT (RECOVERABLE) ERRORS" ARE PREDOMINANTLY CAUSED
BY ENVIRONMENTAL INFLUENCES SUCH AS DUST OR TAPE CRINKLES. THE
"HARD (IRRECOVERABLE) ERRORS" ARE TYPICALLY MEDIUM DEFECTS SUCH
AS MISSING OR CHIPPED OFF MAGNETIC OXIDE. THE DIAGNOSTIC SYSTEM
CAN BE USED TO MAPOUT UNCLEAN SPOTS ON THE DISK SURFACES. TO
RESTRAIN THE MONITOR FROM USING THESE KNOWN DEFECTIVE AREAS, THE
LOCATIONS OF THE SPOTS ARE INPUT TO THE BAT-BLOCK SYSTEM. THE
DISKS USED DURING THE HARDWARE RELIABILITY TEST WILL HAVE BEEN
MAPPED PRIOR TO USAGE.
THE I/O LOAD WILL CHANGE ACCORDING TO THE AVAILABLE MASS
STORAGE DEVICES. A SYSTEM WITH MORE THAN ONE DISK DRIVE WILL
HAVE THE I/O LOAD SPREAD TO SIMULATE TYPICAL SYSTEM USAGE. FOR A
2 DISK SYSTEM THE STRUCTURE DEFINED AS THE PUBLIC STRUCTURE (PS)
WOULD NORMALLY RECEIVE 60% OF THE LOAD AND THE OTHER STRUCTURE
THE REMAINING 40%. A 3 DRIVE SYSTEM WOULD DIVIDE THE LOAD
APPROXIMATELY 55%, 33% AND 12%. MULTIPLE TAPE DRIVES HOWEVER GET
THE SAME I/O LOAD, SINCE THEY ARE ASSIGNABLE BY THE USER.
Page 11
SECTION VI
HOW IS DATA OBTAINED TO PROVE THE GOALS OF THE HARDWARE
RELIABILITY TEST HAVE BEEN ACHIEVED?
__________________________________________________________________
TO PROVE THE GOALS OF THE HARDWARE RELIABILITY TEST HAVE
BEEN ACHIEVED IT IS NECESSARY TO EXAMINE THE STATUS OF THE
PROGRAMS BEING RUN UNDER UETP AND THE MASS STORAGE DEVICES. ONCE
AGAIN, THE DESIRED RESULTS ARE: FIRST THAT THERE WILL BE NO
ERRORS TOLERATED BY THE CPU AND SECONDLY THAT THERE WILL BE ONLY
"SOFT RECOVERABLE ERRORS" ON THE DISK AND TAPE DRIVE(S). THE
PARAGRAPHS BELOW OUTLINE THE STEPS TO ACCUMMULATE THE DATA TO
VERIFY THE RESULTS.
THE STATUS OF THE BATCH PROGRAMS BEING RUN UNDER UETP
WILL PROVIDE THE RESULTS EXHIBITED BY THE CPU. AT THE COMPLETION
OF THE 48 HOUR RUN, "ALL TESTS COMPLETED" WILL BE PRINTED ON THE
CONSOLE. ATTACH TO THE OPERATOR ON JOB #1, IF YOU HAVEN'T
ALREADY, THEN TYPE "STATUS". REFERENCING PART ONE OF APPENDIX
III, THIS ILLUSTRATES THE DESIRED CPU RESULTS AT THE END OF THE
48 HOUR DEMONSTRATION. THE NUMBER OF PASSES COMPLETED BY EACH
TEST WILL VARY WITH SYSTEM CONFIGURATIONS. THE STATUS OF ALL
PROGRAMS SHOULD BE "ENDED" AT THE CONCLUSION OF THE 48 HOUR
DEMONSTRATION. ALL TESTS SHOULD HAVE A ZERO IN THE ERROR COLUMN.
THE LOG BEING KEPT OF THE MASS STORAGE DEVICES IS IN THE
OPERATOR AREA IN THE FILE "MONITR.STS". ASSUMING YOU ARE
ATTACHED TO THE OPERATOR, FROM THE CONSOLE TYPE "EXIT" TO GET OUT
Page 12
OF UETP, THEN PRINOUT THE FILE "MONITR.STS" ON THE LINEPRINTER
(IF ONE EXISTS), OTHERWISE TYPE IT OUT ON THE CONSOLE. PART TWO
OF APPENDIX III ILLUSTRATES THE RESULTS OF A TYPICAL 48 HOUR RUN
FOR A THREE DRIVE SYSTEM. NOTE THAT WE ARE INTERESTED IN ONLY
THE LAST TWO DAYS OF DATA, MORE THAN THIS COULD BE OUTPUTTED.
THE LAST STATUS TO BE EXAMINED IS THE SYSERR ENTRIES OVER
THE PAST TWO DAYS. THIS IS DONE BY RUNNING SYSERR AND THEN
TYPING "LPT:=/ALL/BR:132/BEG:-2D" OR "TTY:=/ALL/BR:80/BEG:-2D" TO
OUTPUT TO THE LINEPRINTER OR CONSOLE RESPECTIVELY.
Page 13
APPENDIX I - STARTING UETP
--------------------------
ASSUMPTIONS:
-----------
1. A CONFIGURED RED PACK (SEE "GETTING STARTED WITH RED",
APPENDIX II & III) IS MOUNTED ON DRIVE 0, CYCLED UP AND READY
2. FORMATTED SCRATCH PACKS (SEE "GETTING STARTED WITH RED",
APPENDIX I) ARE ON ALL OTHER DRIVES
3. A SCRATCH TAPE (1200' OR 2400') IS ON ALL MAGTAPE UNITS
4. SYSTEM IS POWERED ON IN CONSOLE MODE
*********************************************************
* WE RE-BOOT THE SYSTEM TO LOAD OUR CONFIGURED MONITOR *
* BY ISSUING THE "BT" COMMAND. *
*********************************************************
KS10>BT
*******************************************************
* THE PROMPT "BOOT>" IS ANSWERED WITH JUST A CARRIAGE *
* RETURN. THUS LOADING WILL DEFAULT TO DISK 0. *
*******************************************************
BOOT>
[PS MOUNTED]
System restarting, wait...
ENTER CURRENT DATE AND TIME: 15 SEP 1978 1235
YOU HAVE ENTERED FRIDAY, 15-SEPTEMBER-1978 12:35PM,
IS THIS CORRECT (Y,N) Y
WHY RELOAD? RED BUILD
****************************************************************
* CHECKD SHOULD BE RUN IF YOU HAVE JUST COMPLETED BUILDING THE *
* RED PACK FROM MAGTAPE IN ORDER TO ASSURE THAT THE PROCESS *
* WENT CORRECTLY. IF YOU ARE RUNNING THIS PROCEDURE FROM A *
* PRESUPPLIED PACK, THIS QUESTION CAN BE ANSWERED "NO". *
* CHECKD TAKES A COUPLE OF MINUTES. *
****************************************************************
RUN CHECKD? Y
[CHECKING FILE CONSISTENCY]
Page 14
[WORKING ON STRUCTURE - PS:]
% REBUILDING SYMBOL TABLE FOR PS:<ROOT-DIRECTORY> [OK]
LOCAL COUNT OF FILE PAGES: 10932
LOCAL COUNT OF OVERHEAD PAGES: 5670
LOCAL COUNT OF USED PAGES: 16602
SYSTEM COUNT BEFORE CHECKD: 16602
SYSTEM COUNT AFTER CHECKD: 16602
THERE ARE NO LOST PAGES.
RUNNING DDMP
**********************************************************************
* THE MONITOR WILL START RUNNING SYSJOB SINCE THE RED PACK CONTAINS *
* AN OPERATOR CONTROL FILE WHICH INITIATES ALL OF THESE JOBS AND *
* STARTS UP UETP. SINCE ONLY THE RED PACK HAS BEEN CONFIGURED, UETP *
* WILL BEGIN OPERATION USING ONLY THIS DISK. APPROXIMATELY TWO *
* PAGES OF OUTPUT WILL FOLLOW, NEAR THE END OF WHICH UETP WILL *
* GENERATE A STATUS MESSAGE. AS SOON AS THIS STATUS MESSAGE HAS *
* BEEN COMPLETED TYPE ONE CONTROL C. *
**********************************************************************
JOB 0 /LOG OPERATOR XX OPERATOR
ENA
SET LOGIN PSEUDO
SET LOGIN CONSOLE
/
RUN SYS:MOUNTR
RUN SYS:INFO
RUN SYS:ORION
RUN SYS:QUASAR
RUN SYS:MAILER
RUN SYS:MAPPER
RUN SYS:LPTSPL
RUN SYS:FAL20
RUN SYS:STATUS
RUN SYS:OPER20
RUN SYS:CDRIVE
RUN SYS:SPRINT
JOB 0 /SET OPERATOR
PTYCON
GET SYSTEM:PTYCON.ATO
/
JOB 1 /LOG OPERATOR XX OPERATOR
ENA
RUN SYS:BATCON
/
JOB 2 \LOG OPERATOR XX OPERATOR
ENA
RUN SYS:FAL
\
JOB 3 \LOG OPERATOR XX OPERATOR
ENA
RUN SYS:NETCON
Page 15
\
SJ 0:
SJ 0: SYS 4145 RELEASE 4, TOPS-20 MONITOR 4(3247)
SJ 1:
SJ 1: SYS 4145 RELEASE 4, TOPS-20 MONITOR 4(3247)
SJ 2:
SJ 2: SYS 4145 RELEASE 4, TOPS-20 MONITOR 4(3247)
SJ 3:
SJ 3: SYS 4145 RELEASE 4, TOPS-20 MONITOR 4(3247)
SJ 0: @LOG OPERATOR OPERATOR
SJ 0:JOB 1 ON TTY43 24-MAR-80 17:02:08
SJ 0: @ENA
SJ 0: $^ESET LOGIN PSEUDO
SJ 1: @LOG OPERATOR OPERATOR
SJ 1: JOB 2 ON TTY44 24-MAR-80 17:02:12
SJ 3: @LOG OPERATOR OPERATOR
SJ 3: JOB 4 ON TTY46 24-MAR-80 17:02:16
SJ 3: @ENA
SJ 0: $^SET LOGIN CONSOLE
SJ 1: @ENA
SJ 2: @LOG OPERATOR OPERATOR
SJ 2: JOB 3 ON TTY45 24-MAR-80 17:02:16
SJ 3: $RUN SYS:NETCON
SJ 0: $^ESET OPERATOR
SJ 1: $RUN SYS:BATCON
SJ 2: @ENA
SJ 0: $PTYCON
SJ 2: $RUN SYS:FAL
SJ 0: PTYCON> GET SYSTEM:PTYCON.ATO
SJ 0: PTYCON>
SJ 0: PTYCON> SILENCE
[FROM OPERATOR on line 47: WARNING RED PACK MOUNTED !!]
[FROM OPERATOR on line 47: SYSTEM IN OPERATION]
SJ 0: PTYCON> W ALL
SJ 0: OPR(0) 5 OPERATOR OPR TI 0:0:8
SJ 0: PTYCON> CONN OPR
SJ 0: [CONNECTED TO SUBJOB OPR(0)]
SJ 0: ;IN CASE OF UETP AUTO-RESTART CHANGE NEXT 7 LINES
SJ 0: OPR>^X
SJ 0: PTYCON>
SJ 0: PTYCON> DEF 1 (AS) UETP
SJ 0: PTYCON> CONN UETP
SJ 0: [CONNECTED TO SUBJOB UETP(1)]
SJ 0: sys 4145 release 4, TOPS-20 Monitor 4(3247)
SJ 0: @LOG F-S
SJ 0: Job 6 on TTY50 24-Mar-80 17:03:34
SJ 0: Mon 24-Mar-80 17:03:39 Up 0:03:30
SJ 0: 1+5 Jobs Load av 1.08 0.58 0.24
SJ 0:
SJ 0:
SJ 0: APR-Serial Nr.: 4145 Micro-Code Ver.: 117 HSB-Adr.: 400 (enabled)
SJ 0:Interrupts enabled: power fail NXM Interv. timer
Page 16
SJ 0: TOPS20 paging on trap + paging enabled
SJ 0:
SJ 0: !!!!!!!!!WARNING!!!!!!!!!!!!!
SJ 0: READ THE DOCUMENT PS:<RED>BEWARE.MEM. THIS FILE CONTAINS IMPORTANT INFORMATION
SJ 0: CONCERNING THIS RELEASE OF THE "RED PACK"!!
SJ 0: End of LOGIN.CMD.1
SJ 0: @^X
SJ 0: PTYCON>
SJ 0: PTYCON> UETP-DO CLEAN
SJ 0: PTYCON>
SJ 0: **** UETP(1) 17:04:01 ****
SJ 0: DO CLEAN
SJ 0: @;<UETP.LIB>CLEAN.MIC.1, 7-Jun-79 16:40:39, EDIT BY EIBEN
SJ 0: ;cleans up UETP-directory and starts UETP via RELIAB.CMD
SJ 0:
SJ 0: DAYTIME
SJ 0: Monday, March 24, 1980 17:04:01
SJ 0: @TER NO PAGE
SJ 0: @TER WIDTH 80
SJ 0: @ENABLE
SJ 0: $CANCEL BATCH */USER:F-S
SJ 0: [No Jobs Canceled]
SJ 0: $DISABLE
SJ 0: @CONN <UETP>
SJ 0: @DIR *.ERL
SJ 0: %No such file type - *.ERL
SJ 0: @DEL *.LOG
SJ 0: DUPB.LOG.2 [OK]
SJ 0: EXCEPT.LOG.2 [OK]
SJ 0: EXCEPT.LOG.3 [OK]
SJ 0: EXCEPT.LOG.4 [OK]
SJ 0: EXCEPT.LOG.5 [OK]
SJ 0: MTA0.LOG.2 [OK]
SJ 0: RUN.LOG.2 [OK]
SJ 0: RUN.LOG.3 [OK]
SJ 0: RUN.LOG.4 [OK]
SJ 0: RUN.LOG.5 [OK]
SJ 0: TEST72.LOG.2 [OK]
SJ 0:@DEL *.ERL
SJ 0:%No such file type - *.ERL
SJ 0:@UND RUN.LOG
SJ 0: RUN.LOG.2 [OK]
SJ 0: RUN.LOG.3 [OK]
SJ 0: RUN.LOG.4 [OK]
SJ 0: RUN.LOG.5 [OK]
SJ 0: @UND EXCEPT.LOG
SJ 0: EXCEPT.LOG.2 [OK]
SJ 0: EXCEPT.LOG.3 [OK]
SJ 0: EXCEPT.LOG.4 [OK]
SJ 0: EXCEPT.LOG.5 [OK]
SJ 0:@EXP <UETP>
SJ 0: PS:<UETP> [11 pages freed]
SJ 0:@ENABLE
SJ 0: $DAYTIME
SJ 0: Monday, March 24, 1980 17:04:25
Page 17
SJ 0:$UETP
SJ 0:[24-Mar-80 17:04:32 User Environment Test Package ]
SJ 0:
SJ 0:
***************************************************************
*ACTUAL OUTPUT TO THE CTY WILL BE DIFFERENT. IT WILL APPEAR *
*AS THOUGH THE SYSJOB OUTPUT IS WRITING OVER THE UETP OUTPUT. *
*PLEASE IGNORE!! *
***************************************************************
SJ 0:UETP>TAKE RELIAB.CMD
SJ 0:
SJ 0:UETP>DEFAULT /CYCLE:48:00/TIME:1:30:00/DEPTH:VERIFICATION
SJ 0:[17:04:51 DEFAULT COMPLETED]
SJ 0:
SJ 0: UETP>ENABLE DUPB
SJ 0:[17:04:53 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE TEST72
SJ 0:[17:04:54 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>enable mta0
SJ 0:[17:04:55 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE ALGOL
SJ 0:[17:04:56 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE BASIC
SJ 0:[17:04:57 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE CBLSRT
SJ 0:[17:04:58 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE DBMS
SJ 0:[17:04:58 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE RANCBL
SJ 0:[17:04:59 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE RANFOR
SJ 0:[17:05:00 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE MEMORY
SJ 0:[17:05:01 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE DIAGS
SJ 0:[17:05:02 ENABLE COMPLETED]
SJ 0:
SJ 0:UETP>ENABLE LPT0
SJ 0:[17:05:03 ENABLE COMPLETED]
SJ 0:
SJ 0:
SJ 0:UETP>MESSAGE
Page 18
SJ 0:
SJ 0:UETP>BEGIN
SJ 0:[17:05:09 BEGIN COMPLETED]
SJ 0:
SJ 0:UETP>STATUS
SJ 0:
SJ 0:[24-Mar-80 17:05:09]
SJ 0:
SJ 0: Test Depth Status Cycle Times Error Error Start
SJ 0: name run count limit time
SJ 0: ====== ===== ======= ===== ===== ===== ===== =====
SJ 0: DUPB VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: TEST72 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: MTA0 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: ALGOL VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: BASIC VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: CBLSRT VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: DBMS VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: RANCBL VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: RANFOR VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: MEMORY VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: DIAGS VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0: LPT0 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
SJ 0:
SJ 0:
SJ 0:UETP>
SJ 0:[MICEMF - End of MIC File: <UETP.LIB>CLEAN.MIC.1 ]
SJ 0:PTYCON>
SJ 0:17:05:18 Batch-Stream 0 --Started--
SJ 0:
SJ 0:17:05:18 Batch-Stream 1 --Started--
SJ 0:
SJ 0:17:05:18 Batch-Stream 2 --Started--
SJ 0:
SJ 0:17:05:18 Batch-Stream 3 --Started--
SJ 0:OPR>
SJ 0:17:05:52 Batch-Stream 5 --Started--
SJ 0:OPR>
SJ 0:PTYCON> CONN UETP
SJ 0:[CONNECTED TO SUBJOB UETP(1)]
********************************************
* CONTROL C IS TYPED HERE. *
********************************************
*********************************************************
* AT THIS POINT SYSJOB IS STILL RUNNING SO WE MUST *
* ATTACH TO THE OPERATOR JOB. THE "ATTACH" COMMAND *
* IS USED TO CONNECT TO THE OPERATOR JOB. *
*********************************************************
@ATTACH (USER) OPERATOR (JOB #) 1
****************************************************
* CONFIRM WITH A "CARRIAGE RETURN" *
****************************************************
Page 19
[Attached to TTY43, confirm]
******************************************************************
* THE PASSWORD FOR THE OPERATOR AREA ON THE RED PACK IS "DEC-20" *
* FOLLWED BY A CARRIAGE RETURN. ANOTHER CARRIAGE RETURN MUST BE *
* TYPED IN ORDER TO DISPLAY THE "UETP>". *
******************************************************************
Password:
UETP>
*******************************************************************
* IF YOUR SYSTEM HAS MORE THAN ONE DISK DRIVE PROCEED TO *
* APPENDIX II. APPENDIX II ILLUSTRATES HOW TO CREATE DISK *
* STRUCTURES TO BE USED BY UETP. IF THERE IS ONLY ONE DISK ON *
* THE SYSTEM LET UETP RUN FOR 48 HOURS, THEN REFERENCE *
* APPENDIX III FOR TEST RESULTS. TYPING "STATUS" AT ANY TIME *
* WILL GIVE INFORMATION ABOUT THE TESTS. *
*******************************************************************
UETP>ST
[24-Mar-80 17:09:04]
Test Depth Status Cycle Times Error Error Start
name run count limit time
====== ===== ======= ===== ===== ===== ===== =====
DUPB VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
TEST72 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
MTA0 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
ALGOL VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
BASIC VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
CBLSRT VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
DBMS VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
RANCBL VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
RANFOR VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
MEMORY VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
DIAGS VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
LPT0 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
Page 20
APPENDIX II - CREATING DISK STRUCTURES
--------------------------------------
ASSUMPTIONS:
-----------
1. ALL PACKS TO BE USED FOR CREATING STRUCTURES ARE FORMATTED,
(SEE "GETTING STARTED WITH RED", APPENDIX I) MOUNTED AND CYCLED UP
2. UETP IS RUNNING AND WE ARE ATTACHED TO THAT JOB (SEE APPENDIX I)
****************************************************************
* THE PURPOSE OF ALLOWING UETP TO INITIALLY BEGIN IS TWO FOLD. *
* FIRST OF ALL IT IS A CONVENIENCE FOR MANUFACTURING CHECKOUT. *
* SECONDLY IT IS A QUICK CHECK THAT EVERYTHING IS OK PRIOR TO *
* CONFIGURING A MULTIPLE PACK PACK DISK SYSTEM. WE BRING THE *
* TESTS RUNNING UNDER UETP DOWN BY TYPING "ABORT ALL". *
****************************************************************
UETP>aboRT (TEST) all
12:56:39 [ABORT COMPLETED]
*******************************
* WE THEN EXIT FROM UETP. *
*******************************
UETP>exIT (TO MONITOR)
@enaBLE (CAPABILITIES)
$strtst
***************************************************************
* STRTST IS A UTILITY PROGRAM USED TO DISPLAY THE STATUS OF *
* THE DISK STRUCTURES ON THE SYSTEM. IN THIS CASE WE ENTER *
* THE COMMAND "SHOW DISK-DRIVES" IN ORDER TO DETERMINE WHAT *
* OUR DISK SUBSYSTEM LOOKS LIKE. *
***************************************************************
STRTST>SHOW DISK-DRIVES
Part of mounted structure
! In use by diagnostic
! ! Drive off-line
! ! ! Read error
! ! ! ! Bad BAT block
! ! ! ! ! Bad HOME block
! ! ! ! ! ! Write-protected
Ch# Un# V V V V V V V Type Units Unit# Name Alias
0 0 X . . . . . . RM03 1 0 PS PS
0 1 . . . . . X . RM03
0 2 . . . . . X . RM03
Page 21
**************************************************************
* NOTE THAT THE ONLY STRUCTURE KNOWN TO THE SYSTEM AT THIS *
* TIME IS THE RED PACK, PS. WE MUST CONFIGURE THE REMAINING *
* TWO RM03'S AS USER STRUCTURES. *
**************************************************************
STRTST>exIT (TO MONITOR)
$checkd
CHECKD>crEATE (NEW FILE SYSTEM FOR) user:
Enter alias:
How many units in this structure? 1
Channel , Drive for logical unit 0: 0,1
Number of pages to allocate for swapping? 0
Number of pages to allocate for the Front End File System? 0
Owner name?
[user: Mounted as CHECKD:]
****************************************************
* CHECKD IS USED TO INITIALIZE THE CURRENTLY *
* FORMATTED PACKS AS NAMED USER STRUCTURES. FOR *
* OUR PURPOSES WE WILL CREATE TWO USER STRUCTURES *
* (USER AND USER1) AS TWO SINGLE PACK STRUCTURES. *
****************************************************
[Dismounting structure - user:]
CHECKD>crEATE (NEW FILE SYSTEM FOR) user1:
Enter alias:
How many units in this structure? 1
Channel , Drive for logical unit 0: 0,2
Number of pages to allocate for swapping? 0
Number of pages to allocate for the Front End File System? 0
Owner name?
[user1: Mounted as CHECKD:]
[Dismounting structure - user1:]
*********************************************************
* AT THE COMPLETION OF THIS PROCESS WE EXIT FROM CHECKD *
* AND PROCEED TO MOUNT THE TWO NEW USER STRUCTURES. *
* ONCE THE TWO USER STRUCTURES HAVE BEEN MOUNTED, WE *
* USE THE TOPS-20 "DO" COMMAND TO GENERATE THE *
* DIRECTORIES FOR EACH STRUCTURE. *
*********************************************************
CHECKD>exIT (TO MONITOR)
Page 22
$smouNT (FILE STRUCTURE) user:
Waiting for structure user: to be put on line...
Structure user: mounted
$
**** P(2) 12:50:44 ****
[structure user: mounted as a 1-unit RM03 structure]
[Transaction finished at 12:50:41]
**** UETP(7) 12:50:48 ****
$smou user1:
Waiting for structure user1: to be put on line...
Structure user1: mounted
$
**** P(2) 12:51:36 ****
[structure user1: mounted as a 1-unit RM03 structure]
[Transaction finished at 12:51:34]
**** UETP(7) 12:51:41 ****
$DISABLE
********************************************************
*WE NOW ENTER THE DO USER COMMAND TO CREATE DIRECTORIES*
*FOR STRUCTURES USER: AND USER1: *
********************************************************
@DO USER.MIC.1
@;<UETP.LIB>USER.MIC.1, 7-Jun-79 16:33:01, EDIT BY EIBEN
;creates directories for second structure USER:
DAYTIME
Monday, July 30, 1979 13:56:20
@TERMINAL NO PAGE
@ENABLE
$MOUNT STRUCTURE USER:
Structure USER: mounted
$BUILD USER:<UETP>
[New]
$$PASSWORD PTEU
$$IPCF
$$ENQ
$$DEFAULT 777752
$$PROTECTION 777740
$$WORKING 9999999
$$PERMANENT 9999999
$$MAXIMUM 10
$$USER 100
$$DIRECTORY 100
$$SUBDIRECTORY 100
$$
$BUILD USER:<UETP.ALGOL>
[New]
$$FILE
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER:<UETP.BASIC>
[New]
Page 23
$$FILE
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER:<UETP.CBLSRT>
[New]
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER:<UETP.DBMS>
[New]
$$WORKING 2000
$$PERMANENT 500
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER:<UETP.RANCBL>
[New]
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER:<UETP.RANFOR>
[New]
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER:<UETP.DECNET>
[New]
$$WORKING 1000
$$PERMANENT 1000
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$DISABLE
@DISMOUNT STRUCTURE USER:
Structure USER: dismounted
@CONNECT
@DAYTIME
Monday, July 30, 1979 13:57:15
@TERMINAL PAGE
Page 24
@
[MICEMF - End of MIC File: <UETP.LIB>USER.MIC.1 ]
@KMIC
@DO USER1.MIC.1
@;<UETP.LIB>USER1.MIC.1, 7-Jun-79 16:34:31, EDIT BY EIBEN
;creates diretories for third structure USER1:
DAYTIME
Monday, July 30, 1979 14:03:18
@TERMINAL NO PAGE
@ENABLE
$MOUNT STRUCTURE USER1:
Structure USER1: mounted
$BUILD USER1:<UETP>
[New]
$$PASSWORD PTEU
$$IPCF
$$ENQ
$$DEFAULT 777752
$$PROTECTION 777740
$$WORKING 9999999
$$PERMANENT 9999999
$$MAXIMUM 10
$$USER 100
$$DIRECTORY 100
$$SUBDIRECTORY 100
$$
$BUILD USER1:<UETP.ALGOL>
[New]
$$FILE
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER1:<UETP.CBLSRT>
[New]
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER1:<UETP.DBMS>
[New]
$$WORKING 2000
$$PERMANENT 500
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER1:<UETP.RANCBL>
[New]
$$FILE
$$DEFAULT 777752
Page 25
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER1:<UETP.RANFOR>
[New]
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER1:<UETP.DECNET>
[New]
$$WORKING 1000
$$PERMANENT 1000
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$BUILD USER1:<UETP.DN22>
[New]
$$WORKING 250
$$PERMANENT 250
$$FILE
$$DEFAULT 777752
$$PROTECTION 777740
$$USER 100
$$DIRECTORY 100
$$
$DISABLE
@DISMOUNT STRUCTURE USER1:
Structure USER1: dismounted
@CONNECT
@DAYTIME
Monday, July 30, 1979 14:04:08
@TERMINAL PAGE
@
[MICEMF - End of MIC File: <UETP.LIB>USER1.MIC.1 ]
@KMIC
Page 26
*************************************************************
* AT THIS POINT THE "STRTST" PROGRAM IS USED TO DEMONSTRATE *
* THAT THE TWO USER STRUCTURES HAVE BEEN SUCCESSFULLY *
* CONFIGURED ON THE SYSTEM. *
*************************************************************
@strtst
STRTST>SHOW DISK-DRIVES
Part of mounted structure
! In use by diagnostic
! ! Drive off-line
! ! ! Read error
! ! ! ! Bad BAT block
! ! ! ! ! Bad HOME block
! ! ! ! ! ! Write-protected
Ch# Un# V V V V V V V Type Units Unit# Name Alias
0 0 X . . . . . . RM03 1 0 PS PS
0 1 X . . . . . . RM03 1 0 USER USER
0 2 X . . . . . . RM03 1 0 USER1 USER1
*********************************************
* WE THEN EXIT FROM THE "STRTST" PROGRAM *
*********************************************
STRTST>exIT (TO MONITOR)
********************************************************
*NOW WE'LL ENTER THE DO CLEAN COMMAND TO CLEAN UP THE *
*UETP DIRECTORY AND START UETP. UETP WILL RUN FOR 48 *
*HOURS!! *
********************************************************
;****YOU MIGHT HAVE TO ENTER A "KMIC" COMMAND BEFORE THE "DO CLEAN"
@DO<UETP.LIB>CLEAN.MIC
@;<UETP.LIB>CLEAN.MIC.1, 7-Jun-79 16:40:39, EDIT BY EIBEN
;cleans up UETP-directory and starts UETP via RELIAB.CMD
@DAYTIME
Monday, March 24, 1980 17:04:01
@TER NO PAGE
@TER WIDTH 80
@ENABLE
$CANCEL BATCH */USER:F-S
[No Jobs Canceled]
$DISABLE
@CONN <UETP>
@DIR *.ERL
%No such file type - *.ERL
@DEL *.LOG
DUPB.LOG.2 [OK]
EXCEPT.LOG.2 [OK]
EXCEPT.LOG.3 [OK]
EXCEPT.LOG.4 [OK]
EXCEPT.LOG.5 [OK]
MTA0.LOG.2 [OK]
RUN.LOG.2 [OK]
Page 27
RUN.LOG.3 [OK]
RUN.LOG.4 [OK]
RUN.LOG.5 [OK]
TEST72.LOG.2 [OK]
@DEL *.ERL
%No such file type - *.ERL
@UND RUN.LOG
RUN.LOG.2 [OK]
RUN.LOG.3 [OK]
RUN.LOG.4 [OK]
RUN.LOG.5 [OK]
@UND EXCEPT.LOG
EXCEPT.LOG.2 [OK]
EXCEPT.LOG.3 [OK]
EXCEPT.LOG.4 [OK]
EXCEPT.LOG.5 [OK]
@EXP <UETP>
PS:<UETP> [11 pages freed]
@ENABLE
$DAYTIME
Monday, March 24, 1980 17:04:25
$UETP
[24-Mar-80 17:04:32 User Environment Test Package ]
UETP>TAKE RELIAB.CMD
UETP>DEFAULT /CYCLE:48:00/TIME:1:30:00/DEPTH:VERIFICATION
[17:04:51 DEFAULT COMPLETED]
UETP>ENABLE DUPB
[17:04:53 ENABLE COMPLETED]
UETP>ENABLE TEST72
[17:04:54 ENABLE COMPLETED]
UETP>enable mta0
[17:04:55 ENABLE COMPLETED]
UETP>ENABLE ALGOL
[17:04:56 ENABLE COMPLETED]
UETP>ENABLE BASIC
[17:04:57 ENABLE COMPLETED]
UETP>ENABLE CBLSRT
[17:04:58 ENABLE COMPLETED]
UETP>ENABLE DBMS
[17:04:58 ENABLE COMPLETED]
UETP>ENABLE RANCBL
[17:04:59 ENABLE COMPLETED]
UETP>ENABLE RANFOR
Page 28
[17:05:00 ENABLE COMPLETED]
UETP>ENABLE MEMORY
[17:05:01 ENABLE COMPLETED]
UETP>ENABLE DIAGS
[17:05:02 ENABLE COMPLETED]
UETP>ENABLE LPT0
[17:05:03 ENABLE COMPLETED]
UETP>MESSAGE
UETP>BEGIN
[17:05:09 BEGIN COMPLETED]
*****************************************************************************
* FROM THIS POINT ON, UETP WILL CONTINUE TO SUBMIT THE VARIOUS USER LEVEL *
* JOBS AT A FREQUENCY DESIGNED TO ENSURE A VERY HEAVY COMPUTATIONAL LOAD ON *
* THE SYSTEM, VERY HIGH DISK I/O LOAD, AND A MODERATE LEVEL OF TAPE ACTIVITY*
*THE PROGRAM SHOULD RUN FOR 48 HOURS WITH NO ERRORS. SINCE UETP IS A *
*COMPLEX SET OF SOFTWARE, SOME MINOR SOFTWARE BUGS MAY BE ENCOUNTERED IN *
*ANY GIVEN RELEASE (SEE APPENDIX IV). IN NO CASE SHOULD A SYSTEM CRASH *
*OCCUR OR ANY HARD I/O ERRORS. *
*****************************************************************************
UETP>
************************************************************************
* ONCE UETP HAS BEEN INITIALIZED IT WILL GENERATE AN INITIAL STATUS *
* MESSAGE WHICH SHOWS THE TESTS TO BE RUN AND A RUNNING COUNT OF THE *
* TIMES RUN AND ERROR COUNT FOR EACH. AFTER THE INITIAL DISPLAY UETP *
* WILL RESPOND WITH ITS PROMPT "UETP>". THE STATUS COMMAND ("ST") CAN *
* BE TYPED AT ANYTIME TO DISPLAY THE CURRENT STATUS OF THE TEST. AN *
* EXAMPLE IS SHOWN BELOW. *
************************************************************************
UETP>ST
[24-Mar-80 17:09:04]
Test Depth Status Cycle Times Error Error Start
name run count limit time
====== ===== ======= ===== ===== ===== ===== =====
DUPB VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
TEST72 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
MTA0 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
ALGOL VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
BASIC VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
CBLSRT VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
DBMS VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
RANCBL VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
RANFOR VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
MEMORY VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
DIAGS VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
LPT0 VER Queued 48:00 0 0 0 24-Mar-80 17:05:04
Page 29
APPENDIX III - TEST RESULTS
---------------------------
PART I
------
UETP>ST
[26-Mar-80 17:35:04]
Test Depth Status Cycle Times Error Error Start
name run count limit time
====== ===== ======= ===== ===== ===== ===== =====
DUPB VER Ended 48:00 80 0 0 24-Mar-80 17:05:04
TEST72 VER Running 48:00 0 0 0 24-Mar-80 17:05:04
MTA0 VER Ended 48:00 8 0 0 24-Mar-80 17:05:04
ALGOL VER Ended 48:00 58 0 0 24-Mar-80 17:05:04
BASIC VER Ended 48:00 128 0 0 24-Mar-80 17:05:04
CBLSRT VER Ended 48:00 156 0 0 24-Mar-80 17:05:04
DBMS VER Ended 48:00 92 0 0 24-Mar-80 17:05:04
RANCBL VER Ended 48:00 152 0 0 24-Mar-80 17:05:04
RANFOR VER Ended 48:00 148 0 0 24-Mar-80 17:05:04
MEMORY VER Ended 48:00 140 0 0 24-Mar-80 17:05:04
DIAGS VER Ended 48:00 140 0 0 24-Mar-80 17:05:04
LPT0 VER Ended 48:00 152 0 0 24-Mar-80 17:05:04
UETP>ABORT TEST72
[ 17:36:29 ABORT COMPLETED]
[All tests complete on processor # 4145]
[26-Mar-80 17:36:30]
Test Depth Status Cycle Times Error Error Start
name run count limit time
====== ===== ======= ===== ===== ===== ===== =====
DUPB VER Ended 48:00 80 0 0 24-Mar-80 17:05:04
TEST72 VER Aborted 48:00 0 0 0 24-Mar-80 17:05:04
MTA0 VER Ended 48:00 8 0 0 24-Mar-80 17:05:04
ALGOL VER Ended 48:00 58 0 0 24-Mar-80 17:05:04
BASIC VER Ended 48:00 128 0 0 24-Mar-80 17:05:04
CBLSRT VER Ended 48:00 156 0 0 24-Mar-80 17:05:04
DBMS VER Ended 48:00 92 0 0 24-Mar-80 17:05:04
RANCBL VER Ended 48:00 152 0 0 24-Mar-80 17:05:04
RANFOR VER Ended 48:00 148 0 0 24-Mar-80 17:05:04
MEMORY VER Ended 48:00 140 0 0 24-Mar-80 17:05:04
DIAGS VER Ended 48:00 140 0 0 24-Mar-80 17:05:04
LPT0 VER Ended 48:00 152 0 0 24-Mar-80 17:05:04
UETP>EXIT
Page 30
$STATUS
MONITOR-STATUS AT: WED 26-Mar-80 17:37:32
APR-NR. : 4145 sys 4145 release 4, TOPS-20 Monitor 4(3247)
BUILT AT : Tue 19-Feb-80 13:56:05
UPTIME : 15:32:22 LOAD AV: .37 .17 .08
IDLE-TIME : 2:33:27 LOST-TIME : 0:00:53 SCHED-USE : 1:25:45
971 PAGES PHYSICAL USER CORE (PAGEABLE)
DEVICE STATUS:
CHANNEL: 0 TYPE: RH11
STATUS: ALT C
DEVICE: RM03 SER. NR. : 7299 UNIT : 0
STATUS: POSRQ
FUNCTION UNITS SOFT-ERR HARD-ERR
--------------------------------------------------------
SEEKS : 371824
READ : 1350464 0 0 (BLOCKS or 4608.
Bits)
WRITE : 1891712 0 0 (BLOCKS or 4608.
Bits)
DEVICE: RM03 SER. NR. : 6345 UNIT : 1
STATUS: POSRQ
FUNCTION UNITS SOFT-ERR HARD-ERR
--------------------------------------------------------
SEEKS : 177720
READ : 269096 2 0 (BLOCKS or 4608.
Bits)
WRITE : 1056640 0 0 (BLOCKS or 4608.
Bits)
DEVICE: RM03 SER. NR. : 5480 UNIT : 2
STATUS: POSRQ
FUNCTION UNITS SOFT-ERR HARD-ERR
--------------------------------------------------------
SEEKS : 7464
READ : 24856 0 0 (BLOCKS or 4608.
Bits)
WRITE : 28992 0 0 (BLOCKS or 4608.
Bits)
CHANNEL: 1 TYPE: RH11
STATUS:
DEVICE: TU45 SER. NR. : 627 UNIT : 0
STATUS: BOT TAPE
FUNCTION UNITS SOFT-ERR HARD-ERR
--------------------------------------------------------
READ : 216748510 0 0 (FRAMES)
WRITE : 216562340 16 0 (FRAMES)
Page 31
Page 32
APPENDIX IV - LEGAL BUGCHECKS AND BUGINFS
-----------------------------------------
THE FOLLOWING BUGINF SHOULD BE DISREGARDED
AS ANY TYPE OF SYSTEM FAILURE DURING THE 48 HOUR
DEMONSTRATION.
1) DSRLST - DATASET READY LOST