top - metrics - download
⟦d66e9f1ee⟧ Wang Wps File
Length: 3243 (0xcab)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN43.00«
Derivation
└─⟦21670ed14⟧ Bits:30006224 8" Wang WCS floppy, CR 0211A
└─⟦this⟧ »~ORPHAN43.00«
WangText
9…00……00……00……00…+…02……00……00…+
*…0b…*…02…)…08…)…0e…) (…0a…(…01…'…08…'…0e…' &…0c…&…01…& &…06…%…09…%…0b…%…0e…%…00…%…02…%…06…$…09…$…0d…$…0f…$…02…$…06…#…08…#…0a…#…0c…#…0f…#…01…#
#…05…#…86…1 …02… …02… …02…
…02…CPS/SDS/010
…02…KNB/810801…02……02…
TRAFFIC HANDLING
…02……02…CAMPS
4.2.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The structure of the ACP127 Analysis Subpackage is
of uncomplex nature. It is one process receiving
messages from the analysis Queue (ANQ) in an nlimited
loop.
The ANQ is organized on FIFO basis with one subqueue
for flash and one for non-flash, plus a command subqueue
to be used by SSC and TEP (reentering MSO). Because
paging and unpaging of messages in ACP127 format is
provided within he Transport Subpackage, this subpackage
will not need to examine the text part of a message
and will therefore have a good performance that will
be satisfied with the use of a FIFO-queue. If however,
these calculations should fail when coming to eality,
the Analysis Process can be implemented as two incarnated
coroutines.
The software structure of the analysis Process will
be described in detail in the following.
As reference to this description, the functional break
down in section 4..1.1, the HIPO-diagrams and Flowgrams
in section 4.2.1.3 will be used. Also this description
will expand these sections to some extent.
The functional break-downs depicted in figures 4.2.1.1-1
to 4.2.1.1-4 are kept on a level where the break-dow
had stopped at a level ensuring that the lowest identified
software module did not exceed 250 SWELL statements.
Furthermore, the identified functions are arranged
in a logically correct order that satisfies a structured
allocation of software modles.
4.2.1.2.1 A̲C̲P̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲1̲.̲0̲)̲
This is the highest level module the function of which
is to:
a) receive queue-elements from the ANQ.
b) determine the originator of the message and based
upon this information initiate either th incoming
analysis, complete analysis or the PTR analysis.
c) when it gets control again, it will dismantle the
queue-element from the ANQ that triggers all during
the analysis sent message-views and commands to
be checkpointed.
d) befoe returning to the start-point it will send
a completion-code to the Incoming MSO command queue,
if these procedures had been involved.
4.2.1.2.2 L̲e̲v̲e̲l̲ ̲1̲ ̲M̲o̲d̲u̲l̲e̲s̲
The level 1 modules are the Incoming analysis, the
Complete analysis and the PTR nalysis modules.
They will as input receive the information associated
to the message view and the queue-element (View-info
and Queue-info).
Their functions are to control the lower level modules
from where they receive control information thatforms
the processing through that analysis.
4.2.1.2.2.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲M̲o̲d̲u̲l̲e̲ ̲(̲2̲.̲0̲)̲
On the basis of already existing information and information
supplied by the lower level modules (Info. Field, View
Info. and Queue Info.) this module willsequentially
activate the needed modules to fulfil an incoming analysis.
a) Initiate an incoming analysis:
- determine the message type
- set up pointers to the incoming analysis guide
table.
b) Determine if errors had occured during recep
