top - download
⟦e06a41081⟧ Wang Wps File
Length: 13929 (0x3669)
Types: Wang Wps File
Notes: FIX/0000/USM/0006
Names: »3854A «
Derivation
└─⟦3b8d69e90⟧ Bits:30005794 8" Wang WCS Floppy ( A0306A )
└─ ⟦this⟧ »3854A «
WangText
3854/rt…02…FIX/0000/USM/0006
…02…APE/830630…02……02…#
FIKS DISK OPERATION
…02……02…FK 7809
APPENDIX A
FIKS DISK OPERATION
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1. INTRODUCTION ..............................
03
2. SUMMARY ...................................
04
2.1 Hardware ..............................
04
2.2 Software ..............................
06
3. FIKS DUAL DISK SYSTEM .....................
08
4. INITIALIZING OF FIKS DISK SYSTEM ..........
10
5. USE OF TOS IN FIKS DUAL DISK SYSTEM .......
11
6. SYSTEM OPERATIONAL PROCEDURES .............
12
6.1 Boot Load of FIKS .....................
13
6.2 Dualizing of Disks ....................
14
6.3 Discarding of Disks ...................
14
6.4 Disk System ...........................
15
6.5 Use of TOS ............................
16
6.5.1 BRANCH ONE, DISK ONE - use ..........
16
6.5.2 BRANCH ONE, DISK TWO - use ..........
16
6.5.3 BRANCH TWO, DISK ONE - use ..........
17
6.5.4 BRANCH TWO, DISK TWO - use ..........
18
1. I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This document gives an overview of how the FIKS Disk
System functions, and how it shall be operated. It
is meant to be read of technicians, system operator
and other persons, who interface to the FIKS Disk System.
For more detailed description refer to the following
documents.
ESP SYSTEM PSP
Product Specification, FIX/1105/PSP/0046
CR80 AMOS I/O System,
Product Specification, CSS/006/PSP/0006
CR80 DMA Link Driver,
Product Specification, CSS/006/PSP/0002
CR80 AMOS File Management System,
System Product Specification, CSS/920/SPS/0001
CR80 Disk Driver,
Product Specification, CSS/006/PSP/0005
2. S̲U̲M̲M̲A̲R̲Y̲
2.1 H̲a̲r̲d̲w̲a̲r̲e̲ (ref. Figure 1)
The disks (CDC and FLOPPY) are controlled of the interface
boards placed in the file processor. These diskcontrollers
are accessed from the file processor via the SCM-mainbus
using the IO-addresses 200,204 (=4*(#32, #33)) for
CDC and 8(=2*4) for floppy. In this way they are requested
to perform data transfers to/from the disks from/to
the disk-CACHE-CR80-memory RAM placed page 1, locations
0 - #4000). These transfers are executed using a SUBBUS.
Transferrence of data between the file- and user processor
is done via the DMA-link.
The CDC-disks (kind = MMD82, unit no = 0) consist of
two submits:
- the section accessed with movable heads (submit
no = 0), where the volume MOVHEAD is placed.
- the section accessed with fixed heads (submit no
= 1), where the volume FIXHEAD is placed.
The Floppy disk (kind = FLOPPY, unit no = 0) is in
the Node/MEDE configuration only placed in BRANCH ONE
(i.e. it can not be used of BRANCH TWO).
There is one submit (submit no = 0), where a volume
with name FLOPPY (normally) is placed.
Figure 1…01…FRONT VIEW - DISK OPERATION
2.2 S̲o̲f̲t̲w̲a̲r̲e̲ (ref. Figure 2)
When an application in the CR80-computer requests a
disk read/write, this command is sent via the IO-system
in the user processor and DMA-driver (DMA000) for the
File Management System (FMS) placed in the file processor.
The FMS translates the commands to disk-sector read/write
commands. These are handed over to the disks drivers
(CDC000, CDC001 for the CDC-disks and FDD000 for the
Floppy), which carry out the interface to the disk-controllers.
Needed data transfers between file- and userprocessor
is controlled by the FMS and executed by the DMA-driver.
When the disk-operation is finished the disk-drivers
are interrupted. They return completion to the FMS,
which forwards this information, via the DMA-drivers
and IO-system, to the application. Certain completions
(disk hardware errors that can be recovered by discarding
a disk) are handled of the system software (ESP).
Figure 2
DISK OPERATION
3. F̲I̲K̲S̲ ̲D̲U̲A̲L̲ ̲D̲I̲S̲K̲ ̲S̲Y̲S̲T̲E̲M̲
Seen from the system operational software point of
view, the FIKS dual disksystem (ref. fig. 1, Node/MEDE-config.)
consist of two logical DEVICES:
- MMDO, with volume MOVHEAD
- FIXO, with volume FIXHEAD
The devices may consist of subunits from one or both
of the disk units. If both subunits are used then DISK
̲STATUS is said to be DUAL. If only subunits from BRANCH
ONE/TWO are used, then DISK ̲STATUS is said to be ONE/TWO.
If DISK ̲STATUS is DUAL, then the disk read operations
will be performed from one of the disk units and disk
write operations on both units. In case of a hardware
failure in one of the disk units, this one is DISCARDED
and the unit left, is used as single (ONE/TWO). Later
on when the erroneuous disk is repaired, it can be
included in the disk system again - a DUALIZING of
the disk is started. All write operations are now performed
on both units while a copying of disk sectors from
the disk used all the time to the disk to be included.
When this copying is finished the units are identical,
and DISK ̲STATUS is DUAL.
Both BRANCHE's can use the disks at the same time.
If both branches were allowed to do writing on the
disk units simultaneous, then the disks would soon
be corrupted. Therefore a feature for controlling the
ability of being able to write on the disks is present.
When the FIKS-system is booted, no disk writing can
be done - every disk write operation is converted to
a dummy 'CHECK'-operation. All disk-read-operations
are executed in the usual manner. This state of the
disk system is meant to be used when a branch is STANDBY.
When the branch is going to be ACTIVE DISK-writing
is enabled. (WRTDISK).
To keep track of the different states of the disk system
a DISK ̲STATUS ̲WORD is used.
15 14 3 2 1 0 bit
no
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
B̲i̲t̲ ̲o̲n̲ ̲m̲e̲a̲n̲s̲
0: DISK ̲ONE ̲INCLUDED
1: DISK ̲TWO ̲INCLUDED
2: DISK ̲WRITE ̲ENABLED
3: DISKS ̲DUALIZING
This word is checkpointed (i.e. written to disk) to
be retrieved at next initializing of the disk system
for determination of DISK ̲STATUS.
It is noticed that in BRANCH ̲ONE correspond DISK ONE/TWO
to the IO-addresses 200/204, and in BRANCH TWO correspond
DISK ONE/TWO to the IO-addresses 204/200.
4. I̲N̲I̲T̲I̲A̲L̲I̲Z̲I̲N̲G̲ ̲O̲F̲ ̲F̲I̲K̲S̲ ̲D̲I̲S̲K̲ ̲S̲Y̲S̲T̲E̲M̲
When the FIKS-system is boot loaded BRANCH ̲ID, DISK
̲STATUS is defaulted to BRANCH ̲ONE, DISKS ̲DUAL. The
state of the disk-controllers is examined.
If the cables to the controller or the interface board
itself is missing, then no attempt to use the corresponding
disk unit is performed - the DISK ̲STATUS is set in
accordance to this. When BRANCH ̲ID id is keyed in by
the operator, DISK ̲STATUS is updated again (if BRANCH
TWO is stated). The next step in the initializing procedure
is to examine the earlier checkpointed DISK ̲STATUS
̲WORD's (one on each disk unit): By combining the obtainable
DISK ̲STATUS's- (those from the disk controllers and
the checkpointed), the largest common DISK ̲STATUS is
determined. In case DISK ̲STATUS comes out with "no
disk available" the system operator is asked to key
in a DISK ̲STATUS. If the state of the branch is going
to be ACTIVE the disk-write is enabled.
5. U̲S̲E̲ ̲O̲F̲ ̲T̲O̲S̲ ̲I̲N̲ ̲T̲H̲E̲ ̲D̲U̲A̲L̲ ̲D̲I̲S̲K̲ ̲S̲Y̲S̲T̲E̲M̲
Sometimes it is necessary to operate on the disk system
in an offline mode, i.e. under TOS-execute system for
being able to load new modules (programs, tables, etc.)
or to do some inspection of files. TOS-system is only
operating on one disk unit at a time (DISK ONE or DISK
TWO). Therefore, special precautions must be taken
when using TOS, in a dualized Node/MEDE disk system.
The checkpointed DISK ̲STATUS must be updated to reflect
the changes that have been made on the disk system.
Three programs DISK ̲ONE.C, DISK ̲TWO.C, and DISKS ̲DUAL.C
have been implemented. These programs overwrite the
checkpointed DISK ̲STATUS to be DISK-ONE, DISK-TWO,
or DISKS ̲DUAL. They are activated using 'S' - RUN 'Program'.
The program is included in the TOS-configuration command-files.
The FIKS-fileboot may be used together with
TOS-boot - no disk writing will be performed. The operations
that may be executed in this way can not be predicted,
but at least there is no risk of damaging something.
6. S̲Y̲S̲T̲E̲M̲ ̲O̲P̲E̲R̲A̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
This section deals with what a system operator has
to do in certain selected cases. All keying in is performed
on the console, - transparent Watchdog mode to the
affected branch is assumed. Keying in is underlined.
6.1 B̲o̲o̲t̲ ̲l̲o̲a̲d̲ ̲o̲f̲ ̲F̲I̲K̲S̲
B1 A̲ ," normal
B2 B̲
ERROR SWITCHOVER ...... etc.
if no response or the system does not respond as stated
then key in
I 3̲3̲ "boot from opposite
B1 A̲ "site branch
B2 B̲
the following may appear
DISK STATUS ?
= O̲E̲/T̲O̲/D̲L̲
The system has found that no disk can be used as a
result of the disk investigation performed at the disk
initializing. The operator may then choose the proper
DISK ̲STATUS by keying in OE, TO or DL(ONE, TWO or DUAL).
The DISK ̲STATUS used last time the system was FIKS-ACTIVE
can be found in earlier log printing - DISK ̲STATUS
CHANGES IS ALWAYS LOGGED:
Note: The operator has to make a decision that may
have catastrophic effect on the system in case
it is wrong. Is the situation caused by hardware
failure? Wrong BRANCH ̲ID keyed in? Uncontrolled
use of TOS-system?
If an errorreport with errorcode # 4FF (disk system
̲stopped) appears, just after bootload, then this may
be caused by an unlucky hardware error in one of the
disk unit. It is then better to exclude this unit from
the system. This is done by switching off the power
to the disk or to pull out the cable to the disk-interface
board. Close the system, exclude one of the disks and
do bootloading - if still # 4FF, try to boot with the
other disks.
6.2 D̲u̲a̲l̲i̲z̲i̲n̲g̲ ̲o̲f̲ ̲D̲i̲s̲k̲s̲
Dualizing of a disk is started by keying in the system
command.
= RUN DUALIZE ̲DISKS.c
Before this operation is started, the operator must
have some reason to believe, that the disk to be dualized,
is in working order.
When the disks are dualized a logging.
DISK ̲STATUS: DUAL
appears on the console.
Note: This procedure can only be performed on the
ACTIVE branch.
6.3 D̲i̲s̲c̲a̲r̲d̲i̲n̲g̲ ̲o̲f̲ ̲D̲i̲s̲k̲s̲
If possible to discard a disk in a dual disk system
by giving the system command
= DD O̲E̲/T̲O̲ "DISCARD ONE/TWO
In case of an errorreport with error codes
#451-#45D in BRANCH ONE
and #461-#46D in BRANCH TWO
then DISK ONE will automatically be discarded and at
error codes
#461-#46D in BRANCH ONE
and #451-#45D in BRANCH TWO
then DISK TWO will automatically be discarded.
The case shall be reported.
6.4 D̲i̲s̲k̲ ̲S̲y̲s̲t̲e̲m̲
A status report concerning the disk system may be obtained
by keying in the system command
= DM ; DISK ̲SYSTEM
and the following printout appears (eg.)
STATUS OF FIKS-SYSTEM TIME: 271441Z JUN 83
DISK-SYSTEM:
DISK VOLUME READ WRITE BUSY-MSEC FREAD FWRITE
(1) (2) (3) (4) (5) (6) (7)
ONE MOVHEAD #0B96 #011E #0001361E #0000 #0000
FIXHEAD #0555 #0257 #0000622A #0000 #0000
TWO MOVHEAD #0706 #011E #0000788B #0001 #0002
FIXHEAD #03B6 #0257 #00004D1C #0000 #0000
DISK ̲STATUS: #0007 (8)
(1): Disk unit
(2): Subunit (Volume)
(3): No. of read operations executed on subunit
(4): No. of write operations executed on subunit
(5): Milliseconds subunit have been busy doing diskoperations.
(6): No. of faulted read operations on subunit (recovered)
(7): No. of faulted write operations on subunit (recovered).
(8): DISK STATUS WORD. ref. sec. 3.…86…1 …02… …02…
…02… …02… …02…
6.5 U̲s̲e̲ ̲o̲f̲ ̲T̲O̲S̲
6.5.1 B̲R̲A̲N̲C̲H̲ ̲O̲N̲E̲/̲D̲I̲S̲K̲ ̲O̲N̲E̲ ̲-̲ ̲u̲s̲e̲
B1 6̲ ;boot load
B2 c̲
FM: S
TOS VERSION etc ;logging
#
D̲o̲ ̲B̲O̲D̲O̲ ;b̲ranch o̲ne, d̲isk
o̲ne
#
(operations)
#
C̲L̲O̲S̲E̲
6.5.2 B̲R̲A̲N̲C̲H̲ ̲O̲N̲E̲,̲ ̲D̲I̲S̲K̲ ̲T̲W̲O̲ ̲-̲ ̲u̲s̲e̲
I̲ ̲3̲3̲
B̲1̲ ̲6̲
B̲2̲ ̲C̲
(some kind of logging - depends upon the presence of
DISK ONE)
#
C̲L̲O̲S̲E̲
#
S̲Y̲S̲D̲E̲V̲ ̲N̲E̲ ̲M̲M̲D̲O̲ ̲K̲D̲ ̲2̲6̲ ̲A̲R̲ ̲2̲0̲4̲
S̲Y̲S̲D̲I̲R̲ ̲ ̲a̲ ̲*̲ ̲M̲O̲V̲H̲E̲A̲D̲ ̲*̲ ̲M̲D̲
O̲P̲E̲N̲
#
D̲O̲ ̲B̲O̲D̲T̲ ; b̲ranch o̲ne, d̲isk t̲wo
#
(operations)
#
C̲L̲O̲S̲E̲
6.5.3 B̲R̲A̲N̲C̲H̲ ̲T̲W̲O̲,̲ ̲D̲I̲S̲K̲ ̲O̲N̲E̲ ̲-̲ ̲u̲s̲e̲
I̲ ̲3̲3̲
B̲1̲ ̲6̲
B̲2̲ ̲C̲
(some kind of logging - depends upon the presence of
DISK TRO)
#
C̲L̲O̲S̲E̲
#
S̲Y̲S̲D̲E̲V̲ ̲N̲E̲ ̲M̲M̲D̲O̲ ̲K̲D̲ ̲2̲6̲ ̲A̲R̲ ̲2̲0̲4̲
S̲Y̲S̲D̲I̲R̲ ̲ ̲a̲ ̲*̲ ̲M̲O̲V̲H̲E̲A̲D̲ ̲*̲ ̲M̲D̲
O̲P̲E̲N̲
#
D̲O̲ ̲B̲O̲D̲O̲ ; b̲ranch o̲ne, d̲isk o̲ne
#
(operations)
C̲L̲O̲S̲E̲
6.5.4 B̲R̲A̲N̲C̲H̲ ̲T̲W̲O̲,̲ ̲D̲I̲S̲K̲ ̲T̲W̲O̲ ̲-̲ ̲u̲s̲e̲
B̲1̲ ̲6̲
B̲2̲ ̲C̲
FM: S
TOS VERSION etc ;logging
#
D̲o̲ ̲B̲O̲D̲T̲ ;b̲ranch o̲ne, d̲isk t̲wo
#
(operations)
#
C̲L̲O̲S̲E̲
(logging)
