top - download
⟦118fcc171⟧ Wang Wps File
Length: 6470 (0x1946)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN76.00«
Derivation
└─⟦8b37ca311⟧ Bits:30006109 8" Wang WCS floppy, CR 0174A
└─ ⟦this⟧ »~ORPHAN76.00«
WangText
L…00……00……00……00…L…02……00……00…L
L…06…L…07…K…0b…K…0f…K
J…08…J…0c…J…0e…J…0f…J…01…J…02…J
J…06…J…07…I…0c…I…00…I H…09…H…0b…H…0e…H…01…H…06…G…09…G…0f…G
G…06…F…0b…F…0f…F F…06…E…09…E…0d…E…01…E D…08…D…0a…D…0e…D…01…D D…07……86…1 …02… …02… …02…
…02…CPS/SDS/039
…02…820505…02……02…
USER VDU
DETAILED DESIGN SPECIFICATION…02……02…CAMPS
4.2.5 U̲s̲e̲r̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲A̲c̲c̲e̲s̲s̲ ̲M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
The U̲ser M̲essage A̲ccess M̲onitoring (UMAM) process has
the responsibility for the status collecting and status
generating. Furthermre, UMAM performs the access control
to the preparation database.
4.2.5.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The following functions are included in this subpackage
(refer figure 4.2.5.1-1):
- collect status
- generate status
- message access contro
- supervisory control functions
- error handling
FIG. 4.2.5.1-1…01…UMAM Functional Description
4.2.5.1.1 C̲o̲l̲l̲e̲c̲t̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲1̲.̲0̲)̲
Status update requests are received from VUP, SUP,
MDC and MSO in the Collect Queue. The QEL will identify
the type of status. They are:
- delivey message status
- release status
- outgoing message status
- service message status
a) Status Changes (1.1)
The referenced CIF is looked up in the PREP ̲AREA
or EXPAND AREA and status is changed. The CIF currently
referenced from the statusrecord will be dismantled
and the new CIF will be inserted.
b) Status Updating (1.2)
The received data buffer will be inserted as a
part of the delivery status.
c) Offline Append Changes (1.3)
The CIF which has requested the offline appen is
searched and status is changed to append complete.
An Append Notification is returned to the drafter.
4.2.5.1.2 G̲e̲n̲e̲r̲a̲t̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲2̲.̲0̲)̲
Two types of status are generated. They are:
- user requested status
- periodic generated status.
a) User Requested Status (2.1)
Upon rquest from a user or operator, a status is
generated. There are four types of status which
can be requested:
- outgoing message status
- message release status
- delivery status
- service message status.
Information about the terminal i looked up in the
File Directory. The relevant records are then transferred
from the status file to a temporary CIF and sent
to the requestor. the CIF is then sent to the requestor.
b) Periodic Generated Status (2.2)
A summary status is genrated each day at 00.00
hours and sent to the supervisor.
The status is generated per terminal/device
When status has been generated for all terminals/devices,
then the status files will be cleared and the file
directories will be reset.
c) Generate Service Message Status (2.3)
A service message status is generated and sent
to the requestor. The status will be generated
by sorting the EXPAND AREA, PREP AREA, COLECT AREA
and OUT AREA.
d) Generate Outgoing Message Status (2.4)
An outgoing message status is generated and sent
to the requestor. The status will be generated
by sorting the EXPAND AREA, PREP AREA, COLLECT
AREA and OUT AREA.
e) Generate Rlease Message Status (2.5)
A release message status is generated and sent
to the requestor. The status will be generated
by sorting the COLLECT AREA and RELEASE AREA.
f) Generate Delivery Status (2.6)
A delivery status is generated for the equired
terminal/device and sent to the requestor. The
status will be generated by sorting the DELIVER
AREA.
4.2.5.1.3 M̲e̲s̲s̲a̲g̲e̲ ̲A̲c̲c̲e̲s̲s̲-̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲3̲.̲0̲)
Deletion requests, edit requests and VDU page retrieval
requests inserted by a user or operator are received
in the Collect Queue.
a) Usr Deletion Request (3.1)
Depending on the message status, the deletion request
is either sent to the supervisor or the referenced
item is deleted from the Preparation File
b) Edit Request (3.2)
If the reference message is in a state where i
is available for editing, then the message is sent
to the requesting terminal. If the SEND command
is rejected by QMON due to profile fault, then
the message is deleted and a response message is
returned. If the user does not have access to the
mesage, then a response message is returned to
the requestor.
c) VDU-Page Retrieval (3.3)
If the referenced Display name can be found in
the Display table, then a copy of the stored VDU-page
will be sent to the requestor.
d) VDU-Page Storage (.4).
If the referenced Display name can be found in
the Display table, then the received CIF will be
stored in the Display Database, otherwise the received
CIF will be sent to the MDCO.
4.2.5.1.4 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲4̲.̲0̲)̲
Commands inserted by the Supervisor are received in
the Collect Queue.
a) QUEUE STATE REQUEST (4.1)
The number of messages unde preparation is calculated
and sent to the Supervisor Printer.
b) CANCEL ALL PREP QUEUES (4.2)
All messages under preparation is deleted and a
command completion report is generated.
c) CANCEL TERMINAL PREP QUEUE (4.3)
All messages under reparation for the specified
terminal is deleted. A command completion report
is generated.
d) DELETE CIF (4.4)
The specified CIF is deleted from the preparation
files and an acknowledge is returned..
4.2.5.1.5 E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲ ̲(̲5̲.̲0̲)̲
a) Quue Error Reporting (5.1).
Reports to SSC that an unexpected Queue element
has been received.
b) Internal Error Handling (5.2).
Reports to SSC that an unexpected response has
been received from SFCO or from monitor procedures
called.…86…1 …02… …02… …02… …02…
4.2.5.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
Figure 4.2.5.2-1 shows a hierarchical overview of the
software structure within UMAM. UMAM consists of one
process performing the functions listed in sction 4.2.5.1.…86…1
…02… …02… …02… …02…
FIG. 4.2.5.2-1…01…UMAM Software Structure…86…1 …02… …02… …02… …02…
4.2.5.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
4.2.5.3.1 D̲a̲t̲a̲ ̲F̲l̲o̲w̲
The HIPO diagrams overleaf show the data flow of UMAM
The dataflow between the files of UMAM is shown in
figure 4.2.5.
