top - download
⟦22837d8b8⟧ Wang Wps File
Length: 10164 (0x27b4)
Types: Wang Wps File
Notes: FIX/1200/PSP/0077
Names: »4591A «
Derivation
└─⟦0a6a0cf2a⟧ Bits:30006130 8" Wang WCS floppy, CR 0296A
└─ ⟦this⟧ »4591A «
WangText
…09……00……00……00……00…7…02……00……00…7
…0e…
4591A/aml…02…FIX/1200/PSP/0077
…02…JL/840208…02……02…#
FIKS PURGE PROCESS PSP
…02……02… FIKS
…0f…
FIKS PURGE PROCESS PSP
FIX/1200/PSP/0077
J]rgen Lindballe
Ole Eskedal
AMC (6), APE, LOL, LU, REV
…0e… FIKS S/W Mgr 840208
FIKS Conf. Mgr 840208
…0f… 1
…0f… 840208…0e…
4591A/aml…02… FIX/1200/PSP/0077
…02… JL/840208…02… ii
FIKS PURGE PROCESS PSP
…02……02… FIKS
840208 All Original Issue of
Document
…0e…
4591A/aml…02…FIX/1200/PSP/0077
…02…JL/840208…02… iii
FIKS PURGE PROCESS PSP
…02……02… FIKS
…0f…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ........................................ 1
1.1 INTRODUCTION ............................. 1
1.2 ABBREVIATIONS ............................ 1
1.3 DEFINITION OF TERMS ...................... 2
2 APPLICABLE DOCUMENTS ......................... 3
3 MODULE SPECIFICATION ......................... 4
3.1 FUNCTIONAL CAPABILITIES .................. 4
3.2 INTERFACE DESCRIPTION .................... 5
3.3 PROCESSING ............................... 6
3.3.1 The Module ........................... 6
3.3.2 Initialization ....................... 8
3.4 DATA ORGANIZATION ........................ 9
3.4.1 The Data Bases ....................... 9
3.4.2 The Queues ........................... 9
3.4.3 Buffers .............................. 9
3.4.4 Tables ............................... 9
3.4.5 Constants and Variables .............. 9
3.5 STORAGE ALLOCATION ....................... 10
3.5.1 Memory Space Requirements ............ 10
3.5.2 Disc Space Requirements .............. 10
3.6 PERFORMANCE CHARACTERISTICS .............. 10
3.7 LIMITATIONS .............................. 10
3.8 ERROR CODES .............................. 11
3.8.1 Kernel ............................... 11
3.8.2 I/O-System ........................... 11
3.8.3 QACCESS .............................. 11
3.8.4 MTCB Monitor ......................... 12
3.9 LISTING REFERENCES ....................... 12
4 QUALITY ASSURANCE ............................ 13
4.1 QUALIFICATION TESTS ...................... 13
4.2 OTHER QUALITY ASSURANCE PROVISIONS ....... 13
5 PREPARATIONS FOR DELIVERY .................... 14
1 S̲C̲O̲P̲E̲
1.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This document specifies the PURGE PROCESS (PUR) within
the FIKS application software. The design is based
on issue 5 of the Requirements Specifications.
The main task of the Purge Process is:
- to purge PDB and IMF "Special Category Messages"
before release on disc.
1.2 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
BLE Buffer Link Element
FA File Address
IMF Intermediate Message File
MTCB Message Transition Control Block
PDB Preparation Data Base
PQ Purge Queue
PUR Purge Process
SH Special Handling
1.3 D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲ ̲O̲F̲ ̲T̲E̲R̲M̲S̲
I̲N̲T̲E̲R̲M̲E̲D̲I̲A̲T̲E̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲F̲I̲L̲E̲ ̲(̲I̲M̲F̲)̲
A permanent file on disc; it consists of a number of
areas, each of which may contain a message. Messages
arriving form a neighbour node are stored here before
distribution and/or relay.
P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲D̲A̲T̲A̲ ̲B̲A̲S̲E̲ ̲(̲P̲D̲B̲)̲
A number of disc files, each file containing a prepared
message. Messages other than SH-messages are copied
to the Historical Data Base.
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1. REQUIREMENTS SPECIFICATION
FIX/0000/SPC/0002
Vol. I - III, Issue 5, 800310
2. FIKS SYSTEM DESIGN SPECIFICATION
FIX/1000/DSP/0001
Issue 5, 800507
3. FIKS SOFTWARE INTERFACE REFERENCE
FIX/0100/MAN/0003
Issue 2, 800530
4. FIKS DATA INTERFACE REFERENCE
FIX/0100/MAN/0004
Issue 2, 800530
5. CR80 AMOS KERNEL
CSS/302/PSP/0008
Issue 2, 810303
6. CR80 AMOS I/O SYSTEM
CSS/006/PSP/0006
Issue 3, 810401
7. CR80 FILE SYSTEM PSP
CSS/910/EWP/0001
Issue 2, 790226
8. SUPPORT SOFTWARE DESIGN SPECIFICATION
FIX/1103/DSP/0009
Issue 1, 801023
9. TEST REPORT FOR PURGE PROCESS
FIX/1103/TRP/0033
Issue 1
3 M̲O̲D̲U̲L̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
3.1 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲C̲A̲P̲A̲B̲I̲L̲I̲T̲I̲E̲S̲
The Purge Process takes care of purging SH messages
on the PDB and IMF enqueued to it by the last message
handling process of the N/M.
The Purge Process performs the following functions:
- An MTCB index is dequeued from the Purge Queue
(PQ), the MTCB is read and the SH-message is looked
up.
- The SH-message on disc is purged by overwriting
with zeroes (one time).
- The SH-category is removed from the MTCB.
- Checkpointing is performed.
- Queue element, MTCB and PDB file or IMF-area are
released calling QACCESS-"delete element".
3.2 I̲N̲T̲E̲R̲F̲A̲C̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The Purge Process has interface to the following queues/procedures
and files:
- Queues: I/F to "Purge Queue" (PQ) by means of
QACCESS calls.
- PDB files and IMF-areas:
MODIFY BYTES is called for overwriting with zeroes.
- MTCB Monitor:
INIT MTCB at initialization
READ MTCB
GETFILE (Look up SH File)
RELEASEFILE (via QACCESS -delete element-)
WRITEMTCB
- QACCESS
READ-NON
DELETE
- Further
FIXHEAD directory is LOOKUP'ed at initialization
time.
Note that PDP-files as well as IMF-areas are all stored
on FIXHEAD.
3.3 P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
3.3.1 T̲h̲e̲ ̲M̲o̲d̲u̲l̲e̲
The PUR consists of one module only. The main loop
is found in the figure shown onverleaf.
After having accessed the first element of the PQ,
the MTCB is read.
The length of the message is found, the disc is opened,
and the message is overwritten with zeroes.
The MTCB is updated by resetting the SPECAT- and the
CLASS-fields.
The message is checkpointed.
Finally the message is released, and the element is
deleted from the PQ.
Figure 3.3.1-1…01…The Purge Main Loop
3.3.2 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
At initialization the directories are looked up for
"FIXHEAD" and "MOVHEAD".
INIT.MTCB is called.
The main operational loop is entered waiting for queue
entries.
3.4 D̲A̲T̲A̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
3.4.1 T̲h̲e̲ ̲D̲a̲t̲a̲ ̲B̲a̲s̲e̲s̲
Not applicable.
3.4.2 T̲h̲e̲ ̲Q̲u̲e̲u̲e̲s̲
The PURGE QUEUE (PQ) is the input queue of the PUR.
It consists of one subqueue.
Each queue element points out a SH-message represented
by its MTCB.
The messages are processed on a "first in - first served"
basis.
3.4.3 B̲u̲f̲f̲e̲r̲s̲
The array ZERO-BUF (0..511) consists of 512 bytes which
are all equal to zero. It is output on appropriate
number of times when purging the message.
3.4.4 T̲a̲b̲l̲e̲s̲
Not applicable.
3.4.5 C̲o̲n̲s̲t̲a̲n̲t̲s̲ ̲a̲n̲d̲ ̲V̲a̲r̲i̲a̲b̲l̲e̲s̲
- BLE (Buffer Link Element)
- CHECKP-NAME ("CHECKP")
- FA (File Address)
- FSN (File System Name)
- VNFIX ("FIXHEAD")
- MSG-LENGTH (length of message)
- MTCB-BLOCK (MTCB-Block)
- Q-IOCB (QIOCB)
3.5 S̲T̲O̲R̲A̲G̲E̲ ̲A̲L̲L̲O̲C̲A̲T̲I̲O̲N̲
3.5.1 M̲e̲m̲o̲r̲y̲ ̲S̲p̲a̲c̲e̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Program size: 261 words
Process size:
Variables 366 words
I/O area 171 words
3.5.2 D̲i̲s̲c̲ ̲S̲p̲a̲c̲e̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
No space is occupied on disc.
3.6 P̲E̲R̲F̲O̲R̲M̲A̲N̲C̲E̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
Not applicable.
3.7 L̲I̲M̲I̲T̲A̲T̲I̲O̲N̲S̲
Not applicable.
3.8 E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲
3.8.1 K̲e̲r̲n̲e̲l̲
Not applicable.
3.8.2 I̲/̲O̲-̲S̲y̲s̲t̲e̲m̲
If cc () 0 after having called:
- GETROOT
- MODIFY-BYTES
then ERROR is called.
3.8.3 Q̲A̲C̲C̲E̲S̲S̲
If CC () 0 and CC () #0803 (queue empty) after having
called:
- READ-NON
then ERROR is called.
If CC () 0 after having called:
- DELETE
then ERROR is called.
3.8.4 M̲T̲C̲B̲ ̲M̲o̲n̲i̲t̲o̲r̲
If CC () 0 after having called:
- INITE
- READ
- GETFILE
- WRITE
- RELEASE-FILE
then ERROR is called.
3.9 L̲I̲S̲T̲I̲N̲G̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
Source listings and linker list may be obtained from
the FIKS library (FIXLIB, ref. to SCCLLD).
4 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲
4.1 Q̲U̲A̲L̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲T̲E̲S̲T̲S̲
The test of the process is described in ref. 9.
4.2 O̲T̲H̲E̲R̲ ̲Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲ ̲P̲R̲O̲V̲I̲S̲I̲O̲N̲S̲
Not applicable.
5 P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲S̲ ̲F̲O̲R̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲
Preparation of the binary object code starts with an
editing of the source text.
Then the source text is merged together with the prefix
files:
GENS.D * SWELLPREFIX.D * GENERALPARAMS.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * MONITORNAMES.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * IOSPARAMS.S
and
FIX-PREFIX.D * FIX-MONITORNAMES.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * RESIDUAL-PARAMS.S
The merge file is compiled by running the SWELL compiler,
and the listing is printed.
The object code is then linked together with other
pieces of object code by the LINKER.
Finally the binary code may be installed.
Exact instructions may be obtained from the file "INFORMATION"
in the most recent ESP-directory of FIXLIB.
