top - download
⟦7a36ff2c0⟧ Wang Wps File
Length: 15992 (0x3e78)
Types: Wang Wps File
Notes: SYS/DIPA
Names: »3397A «
Derivation
└─⟦1f76ea5a7⟧ Bits:30006218 8" Wang WCS floppy, CR 0277A
└─ ⟦this⟧ »3397A «
WangText
…00……00……00……00……00…?…0a……00……00…?…0b…?…00…?
? >…08…>…09…>…0e…> =…86…1 …02… …02… …02…
…02…SYS/DIPA
…02…GJ/830311…02……02…#
DEMO IMPLEMENTATION PLAN ACCESS
…02…Issue 1.1…02…ACCESS
1̲ ̲ ̲S̲C̲O̲P̲E̲
Based upon the recent decision by US Airforce to come
and watch the ACCESS demonstration the Systems Division
shall prepare the demonstration according to the plan
described in this paper.
1.1 B̲A̲C̲K̲G̲R̲O̲U̲N̲D̲
The demonstration to be performed is outlined in document
"FLTD Manual". As it can be seen from the manual the
required scenarios are divided into mandatory (Mandatory/Evaluation)
and optional (Evaluation). We have decided to focus
on the mandatory scenarios.
The mandatory scenarios fall generally into 3 groups:
- Security
- Data Base Functions
- Recovery
In order to perform those operations we have purchased
equipment and software from 2 different companies:
- Britton Lee
- Relational Database Solutions (RDS)
Britton Lee delivers a backend computer (IDM) which
performs the relational database operations.
RDS delivers a set of application programs written
in PASCAL which gives the user the capabilities to
perform online query operations from VDU's.
2̲ ̲ ̲H̲A̲R̲D̲W̲A̲R̲E̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲
The H/W configuration suggested for the demo is schematically
shown in figure 2-1. The configuration supports 4 user
stations and the database (IDM) in a dualized PU concept.
2.1 B̲A̲S̲I̲C̲ ̲H̲A̲R̲D̲W̲A̲R̲E̲
The Basic H/W is a CAMPS System which shall be integrated
and placed at RO III ground floor.
2.2 U̲S̲E̲R̲ ̲S̲T̲A̲T̲I̲O̲N̲S̲
The 4 user stations consist of:
- a VDU, Delta Data 7260T
- a MSP, Tracor 8000.
2.3 T̲A̲P̲E̲ ̲S̲T̲A̲T̲I̲O̲N̲S̲
The tape station has to be borrowed/rented from another
division.
Likewise a tape controller is needed.
FIGURE 2-1
2.4 L̲I̲N̲E̲ ̲P̲R̲I̲N̲T̲E̲R̲
The Dataproduct line printer shall be used.
2.5 I̲D̲M̲
The IDM shall be connected to the system via 4 x V24
lines connected to 1-4 LTU's. The number of LTU's depend
upon the line speed we wish to maintain. This shall
be investigated.
2.6 H̲A̲R̲D̲W̲A̲R̲E̲ ̲B̲R̲E̲A̲K̲D̲O̲W̲N̲
A H/W Breakdown is required in order to control the
purchasing and integration efford.
3̲ ̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲
The S/W to be used for the demo (as seen now) is depicted
in figure 3-1. The configuration is very preliminary
and the necessary details shall be worked out.
3.1 O̲P̲E̲R̲A̲T̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲
The operating system shall be DAMOS extended by COPSY.
The functions of COPSY shall be
- Load processes
- Allocate TDX lines
- Start processes
- Send keep alive msg to SSC/WD
In addition WAMCO and CFH shall be completed.
FIGURE 4-1
3.2 W̲D̲
In order to support recovery (switch over) the major
functions of the WD complex shall be:
- Detect CPU error
- Switch to stand-by PU
- Reallocate TDX lines
- Assign mount disc
- Command processor start
- Communicate with the console
When S/W is loaded into a stand-by PU it shall be put
into a wait state.
3.3 A̲P̲P̲L̲I̲C̲A̲T̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲S̲S̲E̲S̲
As can be seen from figure 3-1 five major application
processes will exist in memory during execution:
- RDS PARSER 1-4
- TAPE/IDM Utility
3.3.1 R̲D̲S̲ ̲P̲A̲R̲S̲E̲R̲ ̲1̲-̲4̲
The 4 applications RDS PARSER 1-4 are one and the same
process just copied 4 times. This is done so 4 users
can be serviced since one process can only support
one user. The RDS PARSER shall be converted and changed
by RDS and CR so the program will support the FLTD.
(See the FLTD Manual).
The RDS PARSER provides the necessary
Query operations
Report writing
Security checks
Recovery
With respect to recovery the RDS PARSER shall store
on a fixed disc file (fixed head) the data input from
VDU in order to recover the input in case of CPU failure.
3.3.1.1 C̲R̲ ̲A̲c̲t̲i̲o̲n̲s̲
One person from CR shall travel to RDS and participate
in the convertion effort. The effort shall be concentrated
around I/O convertion. A PASCAL manual shall be brought
to RDS and left there.
It must be investigated how big the available space
for an application process and data is.
3.3.2 T̲A̲P̲E̲/̲I̲D̲M̲ ̲U̲t̲i̲l̲i̲t̲y̲
The utility is used to load the data base from the
user tape. (This tape has been provided by the Air
Force).
The utility shall be converted/changed by RDS and CR.
It shall be investigated if the CR80 system can support
the utility.
3.3.3 P̲r̲o̲c̲e̲s̲s̲ ̲S̲e̲l̲e̲c̲t̲
The function to facilitate the process select shall
be available in the system. This shall support the
requirement to allocate a user station to either the
RDS Parser or to the TAPE/IDM utility. It is suggested
that the VDU attention is activated in order to activate
TMS which provides the function of servicing the user
when a process shall be selected.
3.4 L̲T̲U̲X̲ ̲F̲I̲R̲M̲W̲A̲R̲E̲
The LTUX's shall be equipped with an application firmware
which will support TTY input/output plus the attention
key. The TDX system shall also be able to switch to
secondary PU (Reset Command). It shall be determined
which existing firmware can be used.
3.5 T̲A̲P̲E̲ ̲A̲N̲A̲L̲Y̲S̲I̲S̲
The tape provided by the Air Force contains among others
data. The data shall be analysed and a copy/print-out
shall be sent to RDS.
3.6 D̲R̲I̲V̲E̲R̲-̲I̲M̲P̲L̲E̲M̲E̲N̲T̲A̲T̲I̲O̲N̲
The driver shown in figure 3-1 shall support the LTU
and the function described in document "INPUT/OUTPUT
DRIVER SPECIFICATIONS", pre-release version provided
by RDS. This is possible the OC driver ?
3.7 S̲Y̲S̲T̲E̲M̲ ̲I̲N̲T̲E̲G̲R̲A̲T̲I̲O̲N̲
A boot module and a volume shall be generated.
4̲ ̲ ̲I̲D̲M̲ ̲P̲U̲R̲C̲H̲A̲S̲E̲
The IDM shall be purchased from Britton Lee.
A letter of intent shall be written and no later than
60 days later a contract shall be closed which gives
CR the option to buy additional units at OEM conditions.
5̲ ̲ ̲C̲O̲N̲T̲R̲A̲C̲T̲ ̲R̲D̲S̲
As of now a consultancy agreement exists between RDS
and CR. (See appendix A)
A new agreement shall be written and mailed to RDS.
6̲ ̲ ̲I̲N̲T̲E̲G̲R̲A̲T̲I̲O̲N̲ ̲
A system integration plan and procedure shall be established.
Likewise a Pascal Test program which performs I/O to
TDX and Disc shall be written.
7̲ ̲ ̲D̲E̲M̲O̲N̲S̲T̲R̲A̲T̲I̲O̲N̲
The demonstration which shall take place at CR on 2-3
May 83 shall be prepared. An outline shall be prepared.
The location for the demo is RO III ground floor if
power and aircondition allows it.
8̲ ̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
The organization is shown in figure 8-1. The people
indicated are asked to support the effort with maximum
attention since the schedule is very tight.
ORGANIZATION CHART
Figure 8-1
9̲ ̲ ̲S̲C̲H̲E̲D̲U̲L̲E̲
The Schedule is shown in figure 9-1.
ACCESS DEMO Sheet 1
2.1 - 3.1.5
ACCESS DEMO Sheet 2
3.1.6 - 3.3.1.2
ACCESS DEMO Sheet 3
3.3.2 - 3.7.4
ACCESS DEMO Sheet 4
4.0 - 5.0
ACCESS DEMO Sheet 5
6.0 - 7.2
A̲P̲P̲E̲N̲D̲I̲X̲ ̲A̲
Christian Rovsing A/S
February 23, 1983
Relational Database Solutions
3311 Thornwood
Pasadena, Texas 77503
Gentlemen,
S̲u̲b̲j̲e̲c̲t̲:̲ ̲ ̲ ̲C̲o̲n̲s̲u̲l̲t̲a̲n̲c̲y̲ ̲o̲n̲ ̲A̲c̲c̲e̲s̲s̲
This is to authorize Relational Database Solutions
(RDS) to perform consultancy work on the project Access.
The current maximum liability is U.S. $ 3,000.00, U.S.
Dollars Three Thousand. Before any additional money
can be spent a new authorization shall be granted by
Mr. Gert Jensen.
The consultancy work to be performed under this agreement
is mainly to convert/compile to CR80 the existing RDS
database software at Christian Rovsing Corp. in California.
The invoices shall be sent to Christian Rovsing A/S,
attention Gert Jensen along with receipts of expenditures.
Kind regards,
Gert Jensen
GJ/ae
APPENDIX B:…01……01…S̲W̲ ̲C̲A̲P̲A̲B̲I̲L̲I̲T̲I̲E̲S̲ ̲&̲ ̲A̲C̲T̲I̲V̲I̲T̲I̲E̲S̲
COPSY
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
- Started by Root
- Create
- TDX device tree for 2 LTUX (LTUX lines)
- LTU lines
- Catalogue
- TMS lines
- MAG ̲TAPE
- Load and Create
- 5 application processes
- Resume
- Application processes
- Receive
- GO ̲SB ̲ACTIVE
- Send
- KEEP ̲ALIVE messages
S̲W̲ ̲C̲h̲a̲n̲g̲e̲s̲/̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲:̲
C̲F̲H̲ SW Changes/Development:
COPSY ̲MAIN
Coroutines Creation
CFH ̲MAIN
MMD Disk assign/mount
Magtape assign
CREATE ̲PROCESSES
Data for process creation
CREATE ̲PERIPHERALS
LTU ̲LTUX line creation
Catalogue the lines
HW ̲ERROR ̲HANDLING
WDP Communication
CREATE ̲ENVIRONMENT
Segment creation
Object table design
The following coroutines will be removed:
COUNT
TEMCO
DEMCO
CEMCO
W̲A̲M̲C̲O̲
Refer watchdog.
L̲T̲U̲X̲:̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲:̲
- Reset LTUX in case of switchover
- "Attention" key handling.
W̲A̲T̲C̲H̲D̲O̲G̲:̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
- Receive keep-alive from both PUs
- Send GO ̲SB ̲ACTIVE in case of missing keep ̲alive
- Display messages received from COPSY on watchdog
VDU
S̲W̲ ̲C̲h̲a̲n̲g̲e̲s̲/̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲
PU Application SW: Part 1 of WAMCO:
- Open "OC"
- Send Keep ̲alive
- Receive GO ̲SB ̲ACTIVE
WD System SW PU ̲DRIVER in TTY ̲MODE, implemented in
test monitor, WD VDU Driver
WD application SW: Modified PU ̲HANDLER
M̲i̲s̲c̲e̲l̲l̲a̲n̲e̲o̲u̲s̲ ̲A̲c̲t̲i̲v̲i̲t̲i̲e̲s̲
System generation
- MMD volume
directories
files
- Boot Volume (SMD)
- Boot Modules
PPS Generation for application processes
P̲R̲O̲C̲E̲S̲S̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
ROOT
TMS FMS DUMMY COPSY
VDU 1 VDU 2 VDU 3 VDU 4 UTIL
A̲P̲P̲L̲I̲C̲A̲T̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲S̲S̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲c̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
Lookup of the catalogued lines:
- LTU (database)
- LTUX/VDU
- LTUX/LP
Lookup of
- Disk Files
Lookup
- Mag ̲tape
An application process can receive a start ̲up mode
identification in one of the registers.
A̲P̲P̲L̲I̲C̲A̲T̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲S̲S̲:̲ ̲P̲R̲O̲G̲R̲A̲M̲/̲D̲A̲T̲A̲ ̲S̲P̲A̲C̲E̲ ̲L̲A̲Y̲O̲U̲T̲
PROGRAM SPACE 0 ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GPS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PASCAL INTERPRETER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
64K ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DATA SPACE 0 ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
OWN DATA
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲L̲E̲V̲E̲L̲ ̲7̲ ̲D̲A̲T̲A̲ ̲ ̲ ̲ ̲ ̲ STREAMS
̲ ̲ ̲ ̲ ̲ ̲L̲E̲V̲E̲L̲ ̲8̲ ̲D̲A̲T̲A̲ ̲ ̲ ̲ ̲ ̲ I̲0S
PPS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
64K ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲P̲P̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APPENDIX C
Copsy I/F for Pascal/MT ̲UTIL
APPENDIX C:
C̲O̲P̲S̲Y̲ ̲I̲/̲F̲ ̲F̲O̲R̲ ̲P̲A̲S̲C̲A̲L̲/̲M̲T̲ ̲U̲T̲I̲L̲
U̲s̲e̲r̲ ̲p̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ in parameter file: MT ̲UTIL PARSER (1
(2
(C
(3
(R
(4
CPDIR: FILSYS*SYSVDL*PARSER ̲DIR ̲X "get ̲root+lookup
IDM : TMS*IDMX "get ̲root
ROP : TMS*ROPX "get ̲root
VDU : TMS*VDUX "get ̲root
START: COLD, RESTART
LP : TMS*LP
X = 1..4
S̲y̲s̲t̲e̲m̲ ̲p̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ (not used)
1) FILSYS*SYSVOL*SSC ̲DIR ̲INITIAL*PDS ̲USER
*PDS ̲SUPV
2) CDIR: FILSYS+SYSVOL*MD
3) VOL: SYSVOL
4) CIN: TMS*VDUX
5) CONT: TMS*VDUX
6) DIN : TMS*VDUX
APPENDIX D
Program- and Data Segement Layout
PROGRAM
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
GPS 25 KW
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲R̲T̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ 6 KW (min)
PROG 33 KW (max)
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DATA ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DATA 59 KW (max)
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲P̲P̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ 5 KW (min)
FMS ̲MOVING FILE
SYSTEM
MIR ̲MOVING MIR ̲FIXED VOLUMES
(1 MMD
DISK)
"MIRM" "MIRF" DEVICES
FILES: FILES:
SSC ̲DIR ̲INITIAL checkpoint files
PPS files trace files
SW load files parameter files
P̲A̲S̲C̲A̲L̲ ̲M̲A̲G̲ ̲T̲A̲P̲E̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
At the present time DAMOS supports a MAG ̲TAPE HANDLER
which resides in a tape controller and performs upon
request a low level operation, e.g. skip block, sense
status etc. There exists a set of SWELL utility programs
which implements a very simple mag-tape system. The
SWELL utility programs must be linked with the PASCAL
main module to form an executable module. The utility
programs must be accessed through a special PASCAL/SWELL
interface module because the PASCAL interpreter assumes
that certain registers are not changed at return from
the SWELL submodules. The process/module structure
will look as follows:
UTILITY PROCESS
PASCAL UTIL
PU PASCAL/SWELL
I/F
SWELL MAG ̲
TAPE
SE DRIVE
MAG ̲TAPE MAG ̲TAPE
CONTROL- HANDLER
LER
The SWELL mag-tape utility implements the following
actions:
INIT ̲MC (C̲C̲) TRANSPORT ̲STATUS (S̲T̲A̲T̲U̲S̲, C̲C̲)
DISABLE ̲MT (C̲C̲) REWINDMT (C̲C̲)
UNLOAD (C̲C̲) SKIP (DIRECTION, NUMBER, C̲C̲)
WRITETAPE (NO ̲BYTES, DISPLACEMENT, C̲C̲)
WRITEFM (C̲C̲)
READTAPE (NO ̲BYTES, DISPLACEMENT, C̲C̲)
The return parameters are underlined. CC denotes the
completion code. It is apparent that the existing mag
̲tape utility is very primitive and supports neither
a mag ̲tape file system nor volume/file label handling.
It is recommended that the following activities are
initiated:
- mag ̲tape utility documentation must be provided
- COPSY must know the synchronization elements
and device names
- PASCAL utility must know the exact layout of
the parameters
- PASCAL/SWELL interface module must be programmed
- the contents and the file structure of the tape
to be used for FLTD must be determined and described.
The structure of the tape can be described in a
table where each entry corresponds to a file on
the tape:
(file ̲no, first ̲block, no ̲of ̲blocks, block ̲size).
The table can be used by PASCAL mag ̲tape utility
which must keep track of the tape position.
