Trailing-Edge
-
PDP-10 Archives
-
BB-FI82B-DD_1989
-
35,1414/hand10.doc
There are no other files named hand10.doc in the archive.
---------------------------------------------------------------------
| |
| DIGITAL EQUIPMENT CORPORATION |
| |
---------------------------------------------------------------------
| |
| PROCESS PROCEDURE |
| |
---------------------------------------------------------------------
| |
| TITLE: KLAD10-MFG-GUIDE |
| |
---------------------------------------------------------------------
APPROVAL:
ME/QA/MIS _______________________________________________
PRODUCTION _______________________________________________
MATERIALS _______________________________________________
FINANCE _______________________________________________
BUSINESS MGR _______________________________________________
---------------------------------------------------------------------
| ORIGINATOR | DOCUMENT NUMBER | REV |
| | | |
| Charlie Howard | A-AC-GENMFG-00-MR01 | A |
| | | |
_____________________________________________________________________
DIGITAL PROPRIETARY AND CONFIDENTIAL
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROPRIETARY TO
DIGITAL EQUIPMENT CORPORATION AND IS INTENDED FOR INTERNAL DEC
USE ONLY.
KLAD10-MFG-GUIDE A-AC-GENMFG-00-MR01
DOCUMENT REVISION HISTORY
----------------------------------------------------------------------
| |
| ORIGINATOR | DOCUMENT CHANGE DESCRIPTION | REV |
|_________________|_____________________________________|____________|
| | | |
| | | |
| Charlie Howard | MAR 1989 - Original Document | A |
| | | |
| | | |
| | | |
----------------------------------------------------------------------
KLAD10-MFG-GUIDE A-AC-GENMFG-00-MR01
CONTENTS
CHAPTER 1 GENERAL
1.1 PURPOSE. . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 SCOPE . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 RELEASE NOTES . . . . . . . . . . . . . . . . . . 1-1
1.3.1 DFKDA Problem . . . . . . . . . . . . . . . . . 1-1
1.3.2 KLI Dialogue Changes . . . . . . . . . . . . . . 1-1
1.3.3 Logging In On TTY . . . . . . . . . . . . . . . 1-2
1.3.4 Password Change . . . . . . . . . . . . . . . . 1-2
1.4 MINIMUN CONFIGURATION . . . . . . . . . . . . . . 1-2
CHAPTER 2 STARTING-THE-SYSTEM
2.1 BOOTING YOUR KLAD10 . . . . . . . . . . . . . . . 2-1
CHAPTER 3 STARTING-ACCEPTANCE
3.1 ASSUMPTIONS . . . . . . . . . . . . . . . . . . . 3-1
3.2 SETTING UP CI20 AND NI20 . . . . . . . . . . . . . 3-1
3.3 SETTING UP PRINTER . . . . . . . . . . . . . . . . 3-1
3.4 KERNEL.MIC . . . . . . . . . . . . . . . . . . . . 3-2
3.4.1 Parameters To KERNEL.MIC . . . . . . . . . . . . 3-2
3.4.2 Starting KERNEL.MIC . . . . . . . . . . . . . . 3-2
3.5 SAMPLE DIALOGUE . . . . . . . . . . . . . . . . . 3-2
CHAPTER 4 DURING-ACCEPTANCE
4.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . 4-1
4.2 SETTING UP A VT TERMINAL . . . . . . . . . . . . . 4-1
4.3 RUNNING SPEAR . . . . . . . . . . . . . . . . . . 4-1
4.4 RUNNING TGHA . . . . . . . . . . . . . . . . . . . 4-2
4.5 CHECKING RUN LOGS . . . . . . . . . . . . . . . . 4-2
CHAPTER 5 STOPPING-ACCEPTANCE
5.1 AUTOMATIC SHUTDOWN . . . . . . . . . . . . . . . . 5-1
5.1.1 Stopping OPSER . . . . . . . . . . . . . . . . . 5-1
5.1.2 Printing Reports . . . . . . . . . . . . . . . . 5-1
5.2 MANUAL SHUTDOWN . . . . . . . . . . . . . . . . . 5-2
5.2.1 Stopping Batch And Print Requests . . . . . . . 5-2
5.2.2 Gathering Logs And Reports . . . . . . . . . . . 5-2
5.3 REVIEW . . . . . . . . . . . . . . . . . . . . . . 5-2
CHAPTER 6 CLEAN-UP
6.1 DELETING LOGS AND REPORTS . . . . . . . . . . . . 6-1
Page 2
6.2 CLEANING UP TGHA . . . . . . . . . . . . . . . . . 6-1
CHAPTER 7 CRASHING-THE-SYSTEM
7.1 SYSETM CRASHES . . . . . . . . . . . . . . . . . . 7-1
7.2 MEMORY DUMPS . . . . . . . . . . . . . . . . . . . 7-1
7.3 STOPPING TIMESHARING . . . . . . . . . . . . . . . 7-1
7.4 FINAL SHUTDOWN . . . . . . . . . . . . . . . . . . 7-2
CHAPTER 1
GENERAL
1.1 PURPOSE.
This document is a guide used by MFG to run acceptance on 1090 and
1091 systems using KLAD10-7.04. It will describe starting the
acceptance, getting error reports and cleaning the pack when done.
This will not discuss error analysis or criteria for shipment.
1.2 SCOPE
The acceptance scripts are designed to test the KL10 kernel only. The
scripts described in this document will only test the
CPU,CI20,NI20,RPA0 and a lineprinter. Any other peripherals will have
to be run under TOPS-20 (UETP). The default monitor SYSTEM.EXE will
support these devices. It is not necessary to run MONGEN on the KLAD.
Unless you are sure of what you are doing DON'T run it.
1.3 RELEASE NOTES
1.3.1 DFKDA Problem
There is still a problem with DFKDA. It fails user mode doing a
divide instruction when certain base numbers come up. This is a
intermitent problem and will usually fail after about 2 hours.
Because of this KERNEL.MIC will not run DFKDA.
1.3.2 KLI Dialogue Changes
In the KLI dialogue the start up option QUICK has ben removed. It was
so similar to the GO option that software eng. considered it
redundant and removed it. If you were used to typing QUICK or Q you
must now type GO.
GENERAL Page 1-2
If there is no response within a minute after "why reload?" the
defaults will be used. The following shows the defaults that will be
used.
WHY RELOAD? !OTHER
DATE: !DATE OF LAST CRASH
TIME: !TIME OF LAST CRASH
STARTUP OPTION? !GO
1.3.3 Logging In On TTY
The account of [1,2] may not have "data set". This prevents loggins
on any terminal other than the CTY. You can change this by logging in
to 1,2 on the CTY and typing the followiing.
."R REACT"
REACT>"CHANGE [1,2]"
USER>"ACCESS TYPES"
ACCESS TYPES>"DATA-SET"
ACCESS TYPES>"^Z"
USER>"^Z"
REACT>"EX"
.
1.3.4 Password Change
It is no longer necessary to give a password when logging in to the
1,2 account.
1.4 MINIMUN CONFIGURATION
To bring up 7.04 You must have a KL10 with a minimum configuration of
1 dual ported RP06 and 768K of memory.
CHAPTER 2
STARTING-THE-SYSTEM
2.1 BOOTING YOUR KLAD10
To bring up monitor proceed as follows:
RSX-20F VE16-00 6:02 23-AUG-88
[SY0: REDIRECTED TO DB0:]
[DB0: MOUNTED]
KLI -- VERSION VE16-00 RUNNING
KLI -- ENTER DIALOG [NO,YES,EXIT,BOOT]?
KLI_>"ye"
KLI -- KL10 S/N: 1234., MODEL B, 60 HERTZ
KLI -- KL10 HARDWARE ENVIRNMENT:
MOS MASTER OSCILLATOR
EXTENDED ADDRESSING
INTERNAL CHANNELS
CACHE
KLI -- RELOAD MICROCODE [YES,VERIFY,NO]?
KLI_> yes
KLI -- MICROCODE VERSION 2.1[442] LOADED
KLI -- RECONFIGURE CACHE [FILE,ALL,YES,NO]?
KLI_> all
KLI -- ALL CACHES ENABLED
KLI -- CONFIGURE KL MEMORY [FILE,ALL,REVERSE,FORCE,YES,NO]?
KLI_> all
LOGICAL MEMORY CONFIGURATION.
ADDRESS SIZE INT TYPE CONTROLLER
000000000 768K 4 MF20 10
KLI -- LOAD KL BOOTSTRAP [YES,NO,FILENAME]?
KLI_> yes
KLI-- WRITE CONFIGURATION FILE [YES,NO]?
KLI>NO
KLI -- BOOTSTRAP LOADED AND STARTED
BOOT V4(76)
BOOT>klad:
[Loading from KLAD:SYSTEM.EXE[1,4]]
STARTING-THE-SYSTEM Page 2-2
###DEC10 Single-CPU - D 10-jan-89
WHY RELOAD: other "reason you want to reload"
NOTE
NOTE: You must state the reason why you are
restarting monitor. "SA" or just "other" is not
sufficient.
Date: "da-mon-yr" ;day month year
Time: "hhmm" ;24 hour clock
Startup option: "go" ;DEFAULT
###DEC10 Single-CPU - D 09:23:25 CTY system 3046
Connected to node KLAD10(77) LINE # 355
_.LOGIN 1,2
_.R OPSER
[OPRPAF PROCESSING ATO COMMAND FILE]
*****
13-MAY-80 12:13:00 - TGHA 2(6) RUNNING FIRST TIME.
*****
10:26:19(OPR)
_.
_.
10:26:22(OPR)
Files renamed:
? No file named DSK:*.LOG
_.
10:26:25(OPR)
[No Jobs canceled]
_.
10:26:27(OPR)
[No Jobs canceled]
_.
10:26:30(OPR)
OPR_>
10:26:33(OPR)
TAKE SYS:SYSTEM
10:26:33 Printer 0 -- Set Accepted --
10:26:33 Batch-Stream 0 -- Startup Scheduled --
10:26:33 Batch-Stream 1 -- Startup Scheduled --
10:26:33 Batch-Stream 2 -- Startup Scheduled --
10:26:33 Batch-Stream 3 -- Startup Scheduled --
10:26:34 --Output display for OPR modified--
10:26:34 Batch-Stream 4 -- Startup Scheduled --
10:26:39(OPR_\1)
10:26:34 Batch-Stream 5 -- Startup Scheduled --
10:26:34 Batch-Stream 6 -- Startup Scheduled --
10:26:34 Batch-Stream 7 -- Startup Scheduled --
10:26:34 Batch-Stream 8 -- Startup Scheduled --
STARTING-THE-SYSTEM Page 2-3
10:26:34 Batch-Stream 9 -- Startup Scheduled --
OPR_>
;;OPR: - PLEASE TYPE "GEN-DO KERNEL[35,1414]24,,,"
10:26:43(2)
_.
10:26:43(GEN_\2)
_.
OPR 5 1,2 OPR SL 00:00:00
GEN 12 1,2 _^C 00:00:00
!10:26:50(OPR_\2)
10:26:34 Batch-Stream 10 -- Startup Scheduled --
10:26:34 Batch-Stream 11 -- Startup Scheduled --
10:26:34 Batch-Stream 12 -- Startup Scheduled --
10:26:34 Batch-Stream 13 -- Startup Scheduled --
10:26:34 Batch-Stream 14 -- Startup Scheduled --
10:26:34 Printer 0 -- Startup Scheduled --
10:26:34 -- Volume recognition is Disabled for all tape drives --
OPR_>
!
The system is now loaded and running. To start acceptance scripts
proceed to chapter 3.
CHAPTER 3
STARTING-ACCEPTANCE
3.1 ASSUMPTIONS
The following dialogue assumes that you have just loaded the system
and the console is still running OPSER, with subjobs of OPR and GEN
active.
3.2 SETTING UP CI20 AND NI20
If You want to test the CI or NI you must make them unavailable to the
system. This will allow diagnostics to be run that test the CI or NI.
Type tho following on the CTY:
!"OPR-CONFIG REMOVE CI-0"
!"OPR-CONFIG REMOVE NI-0"
NOTE
Make sure you get a response saying that the devices
were succesfully disabled.
3.3 SETTING UP PRINTER
To test a line printer you must copy LPFORM.INI to system area. This
only has to be done once.
!"GEN-COPY LPFORM.INI[1,4]=LPFORM.INI[35,1414]"
STARTING-ACCEPTANCE Page 3-2
3.4 KERNEL.MIC
KERNEL.MIC is a mic file that will submit batch jobs to test hardware
in user mode for a specified amount of time. This is the primary tool
used by MFG to accept the KL10 CPU.
3.4.1 Parameters To KERNEL.MIC
There are 5 parameters to KERNEL.MIC. They determine hardware to be
tested and run time. You must select them in the proper order and
seperated by a comma.
EXAMPLE
A = Number of hours to run acceptance (no default)
B = "CI" enable CI test scripts (default is no CI)
C = "NI" enable NI test scripts (default is no NI)
D = "LPT" enable LPT test scripts (default is no LPT)
E = "CYC" enable cyclic tests (default is one
continuous pass)
3.4.2 Starting KERNEL.MIC
Here are two examples of starting acceptance. You should select
parameters deponding on the hardware you are testing.
To start acceptance for 24 hrs. with CI,NI, and LPT selected type
!"GEN-DO KERNEL[35,1414]24,CI,NI,LPT"
To start acceptance for 72 hrs. with no CI, no NI, and LPT selected
type !"GEN-DO KERNEL[35,1414]72,,,LPT"
3.5 SAMPLE DIALOGUE
!11:04:25(GEN) GEN-DO KERNEL[35,1414]24,CI,NI,LPT
!11:04:30(GEN)
_.SILENCE
!11:04:46(GEN)
_.SUB
STARTING-ACCEPTANCE Page 3-3
PRL1.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL1 queued, request #17, limit 0:04:00]
_.SUB
PRL2.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL2 queued, request #19, limit 0:04:00]
_.SUB
PRL3.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL3 queued, request #21, limit 0:04:00]
_.SUB
PRL4.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL4 queued, request #23, limit 0:04:00]
_.SUB
PRL5.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL5 queued, request #25, limit 0:04:00]
_.SUB
PRL6.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL6 queued, request #27, limit 0:04:00]
_.SUB
PRL7.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job PRL7 queued, request #29, limit 0:04:00]
_.SUB
MEM1.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job MEM1 queued, request #31, limit 0:04:00]
_.SUB
MEM2.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job MEM2 queued, request #33, limit 0:04:00]
_.SUB
MEM3.CTL[35,1414]/TIME:0:4:/UNIQ:0/AFTER:+00:02:,/OUT:ERROR
[Batch job MEM3 queued, request #35, limit 0:04:00]
!11:05:16(GEN)
_.SUB CON.CTL[35,1414]/TIME/UNIQ:0,/OUT:ERROR
[Batch job CON queued, request #37, limit 1:00:00]
_.SILENCE
!11:05:22(GEN)
_.
!11:05:32(OPR_\GEN)
OPR>
STARTING-ACCEPTANCE Page 3-4
!12:03:18(OPR_\GEN)
12:03:16 Batch-Stream 4 JOB #18 -- Message from
batch user --
Job PRL3 Req #21 for FAILSAFE [1,2]
PRL3.CTL (DFKDA) FINISHED
OPR>
!12:03:48(OPR_\GEN)
12:03:45 Batch-Stream 2 -- Batch error --
Job PRL1 Req #17 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:03:46 Batch-Stream 2 JOB #16 -- Message from
batch user --
Job PRL1 Req #17 for FAILSAFE [1,2]
DFKAA THRU DFKCA FINISHED
OPR>
!12:04:16(OPR_\GEN)
12:04:14 Batch-Stream 6 -- Batch error --
Job PRL5 Req #25 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:04:15 Batch-Stream 6 JOB #20 -- Message from
batch user --
Job PRL5 Req #25 for FAILSAFE [1,2]
PRL5.CTL (DFKCC) FINISHED
OPR>
!12:04:52(OPR_\GEN)
12:04:51 Batch-Stream 5 -- Batch error --
Job PRL4 Req #23 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:04:51 Batch-Stream 5 JOB #19 -- Message from
batch user --
Job PRL4 Req #23 for FAILSAFE [1,2]
PRL4.CTL (DFKDA) FINISHED
OPR>
!12:05:02(OPR_\GEN)
12:05:01 Batch-Stream 7 -- Batch error --
Job PRL6 Req #27 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:05:01 Batch-Stream 7 JOB #21 -- Message from
batch user --
Job PRL6 Req #27 for FAILSAFE [1,2]
PRL6.CTL (DFKCB) FINISHED
OPR>
!12:05:18(OPR_\GEN)
12:05:18 Batch-Stream 10 -- Batch error --
Job MEM2 Req #33 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:05:18 Batch-Stream 10 JOB #24 -- Message from
batch user --
Job MEM2 Req #33 for FAILSAFE [1,2]
MEM2.CTL (DDMMF) FINISHED
OPR>
!12:05:22(OPR_\GEN)
STARTING-ACCEPTANCE Page 3-5
12:05:22 Batch-Stream 11 -- Batch error --
Job MEM3 Req #35 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
OPR>
12:05:22 Batch-Stream 11 JOB #25 -- Message from
batch user --
Job MEM3 Req #35 for FAILSAFE [1,2]
MEM3.CTL (DDMME) FINISHED
OPR>
!12:05:37(OPR_\GEN)
12:05:37 Batch-Stream 8 -- Batch error --
Job PRL7 Req #29 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:05:37 Batch-Stream 8 JOB #22 -- Message from
batch user --
Job PRL7 Req #29 for FAILSAFE [1,2]
PRL7.CTL (DFKCA) FINISHED
OPR>
!12:05:56(OPR_\GEN)
12:05:55 Batch-Stream 9 -- Batch error --
Job MEM1 Req #31 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:05:55 Batch-Stream 9 JOB #23 -- Message from
batch user --
Job MEM1 Req #31 for FAILSAFE [1,2]
MEM1.CTL (DDMMD) FINISHED
OPR>
!12:06:30(OPR_\GEN)
12:06:29 Batch-Stream 3 -- Batch error --
Job PRL2 Req #19 for FAILSAFE [1,2]
Time limit exceeded; allowing 0:00:24 extra time
12:06:30 Batch-Stream 3 JOB #17 -- Message from
batch user --
Job PRL2 Req #19 for FAILSAFE [1,2]
PRL2.CTL (DFKBA) FINISHED.
OPR>
!12:31:29(OPR_\GEN)
12:31:28 Batch-Stream 1 JOB #15 -- Message from
batch user --
Job RPB1A Req #53 for FAILSAFE [1,2]
***ONE PASS OF DDRPI (RONLY) FOR RPB1A.CTL FINISHED***
OPR>
!12:34:12(OPR_\GEN)
12:34:12 Batch-Stream 0 JOB #14 -- Message from
batch user --
Job RPA0A Req #51 for FAILSAFE [1,2]
***ONE PASS OF DDRPI (RONLY) FOR RPA0A.CTL FINISHED***
OPR>
!12:34:26(OPR_\GEN)
12:34:26 Batch-Stream 0 JOB #14 -- Message from
batch user --
Job FINISH Req #47 for FAILSAFE [1,2]
STARTING-ACCEPTANCE Page 3-6
THE ACCEPTANCE TEST PACKAGE HAS COMPLETED
12:34:26 Batch-Stream 0 JOB #14 -- Message from
batch user --
Job FINISH Req #47 for FAILSAFE [1,2]
CHECK LOGS FOR ERROR AND TYPE ":A STOP[35,1414]"
OPR>
The above messages will be printed as the individual tests finish.
When the final message above is printed, all the tests have
completed.
To stop acceptance, go to Chapter 5.
CHAPTER 4
DURING-ACCEPTANCE
4.1 INTRODUCTION
While acceptance is running it is a good idea to monitor the run. This
chapter will decribe how to check and generate all the logs necessary to
determine if the system if running well.
4.2 SETTING UP A VT TERMINAL
If you want to use a VT terminal, you may have to set the baud rate. This
can be done on the CTY by typing "GEN-SET TTY TTY4: SPEED 9600. TTY4 is
the first line. Then login to 1,2. If you get an error saying "data not
set" refer to 1.3.3.
4.3 RUNNING SPEAR
SPEAR is an acronym for Standard Package for Error Analysis and Reporting.
SPEAR reports on the errors and events that are recorded by the operating
system. This is a very useful tool for analyzing system performance.
Running spear on KLAD10 is similar to spear on other operating systems.
For a complete description see the spear manual. The following is an
example of how to get a brief report to the tty.
."R SPEAR"
SPEAR>"RET"
RETRIEVE MODE
Event or packet file (SYS:ERROR.SYS): "<CR>"
Selection to be (INCLUDED): "<CR>"
Selection type (ALL): "<CR>"
DURING-ACCEPTANCE Page 4-2
Time from (EARLIEST): "<CR>"
Time from (LATEST): "<CR>"
Output mode (ASCII): "<CR>"
Report format (SHORT): "<CR>"
Output to (DSK:RETRIE>RPT): "TTY:"
Type <CR> to confirm (GO): "<CR>"
4.4 RUNNING TGHA
TGHA is a program that keeps track of all MOS memory modules and errors.
MOS memory can recover from single bit errors. These soft errors may only
show up in TGHA, therefore it is a good idea to check TGHA periodically
during the run. Here is an example of getting memory information from
TGHA.
."R TGHA"
TGHA>"HISTORY"
TGHA>"TRACE"
TGHA>"EXIT"
."TYPE HISTRY.LST" (This command will type the history of memory modules)
."TYPE TRACE.LST" (This command will type errors if they have occured)
4.5 CHECKING RUN LOGS
During the run there is a log of all output to the CTY. This can be useful
if something happens to the CTY or the printout is lost. To look at this
log type or print ACCEPT.LOG[1,2].
All errors that occur during execution of tests started by KERNEL.MIC are
appended to KERNEL.ERL[1,2]. This file can be typed or printed any time
during the run. This file is normally empty if no errors have occured.
There are logs of each individual test as they run. They are located in
the [1,2] area. These can also be checked anytime to see how a particular
test is running.
CHAPTER 5
STOPPING-ACCEPTANCE
5.1 AUTOMATIC SHUTDOWN
When the Specified time for acceptance runs out FINISH.CTL is submitted
automatically to perform a shutdown procedure. This will stop all the
batch jobs started by KERNEL.MIC and gather reports from SPEAR and TGHA.
The following is an example of the message that will appear at the end of
the run.
!12:34:26(OPR_\GEN)
12:34:26 Batch-Stream 0 JOB #14 -- Message from batch user --
Job FINISH Req #47 for FAILSAFE [1,2]
THE ACCEPTANCE TEST PACKAGE HAS COMPLETED
12:34:26 Batch-Stream 0 JOB #14 -- Message from batch user --
Job FINISH Req #47 for FAILSAFE [1,2]
CHECK LOGS FOR ERROR AND TYPE ":A STOP[35,1414]"
OPR>
5.1.1 Stopping OPSER
Before typing printouts, OPSER should be stopped. This will make the
printouts more readable. STOP.ATO is a command file to stop all subjobs
and close the log file. To excecute this type the following.
!":A stop[35,1414]"
After STOP.ATO is finnished the "*" prompt will appear, showing that OPSER
has no subjobs active. Type "CONTROL C" to exit OPSER.
5.1.2 Printing Reports
You are now ready to type the reports that were gathered automotically at
the end of the run. Type the following commands.
STOPPING-ACCEPTANCE Page 5-2
."TYPE ACCSUM.RPT" (Summary report from SPEAR)
."TYPE ACCBRF.RPT" (Brief report from SPEAR)
."TYPE HISTRY.LST" (History of memory modules)
."TYPE KERNEL.ERL" (Log of errors in tests run by KERNEL.MIC)
5.2 MANUAL SHUTDOWN
If for some reason the system does not stop automatically you can shut it
down manually. The first step is stopping all the tests that are running.
5.2.1 Stopping Batch And Print Requests
At the exec level type the following commands to stop all batch and print
requests.
."SUB*=/KIL"
."PRI*=/KIL"
You can make sure the jobs are stopped by Typing "Q". You should get a
response "The ques are empty".
Now it's time to get reports.
5.2.2 Gathering Logs And Reports
First you should stop OPSER. Type the following commands on the CTY.
!":A STOP[35,1414]"
*"^C"
.
Now you should be at the "." prompt. Get a SPEAR and a TGHA report on
hardcopy. Refer to chapter 4 for help.
At this point the acceptance is stopped and it's time to review the run.
5.3 REVIEW
Review all of the following reports and logs. If the run is considered
acceptable then proceed to chapter 6 to clean the pack.
KERNEL.ERL[1,2] will log all errors that occurred in KERNEL.MIC.
The SPEAR report will log errors in the hardware during the run.
STOPPING-ACCEPTANCE Page 5-3
TGHA will log all errors in MOS memory.
CHAPTER 6
CLEAN-UP
6.1 DELETING LOGS AND REPORTS
CLEAN.MIC will delete most logs and error reports generated during
acceptance. It will not however delete the TGHA data. This must be done
manually. To excecute CLEAN.MIC type the following.
."DO CLEAN.MIC[35,1414]".
6.2 CLEANING UP TGHA
To clean up TGHA you must first make sure TGHA is not running on the
system. Type "SYS" this will show all jobs running. Locate TGHA and
identify it's job number. Type the following to logout TGHA.
."R KILL"
*"KILL (JOB # OF TGHA)"
*"^C"
Now you can delete the TGHA data base typing the following.
."DEL TGHA.TRA[1,4]"
."DEL TGHA.DAT[1,4]"
The pack is now clean and the system is ready to be crashed. Go to chapter
7.
CHAPTER 7
CRASHING-THE-SYSTEM
7.1 SYSETM CRASHES
When a system crash occurs, whether intentionly by the operator or as the
result of a Stopcode error in the monitor, and the system does an auto dump
of memory, the crash is copied to the [10,1] are of the KLAD by the CRSCPY
utility. All crashes cause by the operator have a filename of SERXXX where
XXX is a unique number. Crashes caused by stopcode errors are copied to
[10,1] with the filname of YYYXXX where YYY is the stopcode, such as UIL
and XXX is a unique number. (E.G. KAF002.EXE).
CLEAN.MIC deletes all crashes with SERXXX file names but does not delete
saved crashes caused by a stopcode.
7.2 MEMORY DUMPS
In order to crash the system it is only necessary to type a _^_\ (control
backslash) on the CTY and SHU to the prompt PAR>. This will cause the
system to crash. What happens as a result of this command, depends on the
state of the operating system.
If the "SHUtdown" command is issued without stopping timesharing the system
will crash immediately, dump the contents of memory to [1,4] CRASH.EXE, and
reload the last monitor to have been booted (most likely SYSTEM.EXE). This
is the same process that occurs during a real system crash caused by a
stopcode error. It is also the same process used to do a system reload
after changing the monitor or regenerating a new monitor per MRFAT0009.
7.3 STOPPING TIMESHARING
Timesharing can be stopped with the OPR command KSYS. This will prevent an
unnecessary dump. Stop timesharing by typing the following.
."R OPR"
CRASHING-THE-SYSTEM Page 7-2
OPR>"SET KSYS NOW"
7.4 FINAL SHUTDOWN
You can now type the following commands to completly crash the system.
."^\"
PAR>"SHUT"
%DECSYSTEM-10 NOT RUNNING
BOOT>"^\"
PAR>"ABORT"
The system shutdown procedure is now complete and the system can be powered
down.