top - download
⟦e5227da2e⟧ Wang Wps File
Length: 14799 (0x39cf)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN47.00«
Derivation
└─⟦7f5d2b450⟧ Bits:30006107 8" Wang WCS floppy, CR 0170A
└─ ⟦this⟧ »~ORPHAN47.00«
WangText
.…0d….…0f….…02….
-…08…-…0e…-
,…08…,…0c…,…01…,…05…+…09…+…0a…+…0c…+…0d…+…0e…+ *…08……86…1
…02…
…02…
…02…
…02…CPS/SDS/039
…02…840601
…02……02…
USER VDU
DETAILED
DESIGN
SPECIFICATION
…02…ISSUE
1…02…CAMPS
4.2.2.4.1.1 Fuctional Specification ...
4.2.2.4.1.3.1 CANCEL ANQ IN-PUT......
4.2.2.4.1.3.2 REQUEST ANQIN-PUT........
4.2.2.4.1.3.3 REQUEST FC KEY IN-PUT..
4.2.2.4.1.3.4 CANCEL FC KEY IN-PUT..
4.2.2.41.4. Data Description..........
4.2.2.4.1.5 Module Design ..............
4.2.2.4.2 VUS ANSER Q PROCESSING .........
4.2.2.4.2.1 Functional Specification ..
4.2.2.4.2.2 Module Interface ...........
4.2.2.4.2.3 Module Component ...........
4.2.2.4.2.3.1 Delete Append CIF ......
4.2.2.4.2.4 Data Description ...........
4.2.2.4.2.5 Module Design ..............
4.2.2.4.3 Append Investigation .........
4.2.2.4.3.1 Functional Description ....
4.2.2.4.3.2 Module Interface ..........
4.2.2.4.3.3 Module Components .........
4.2.2.4.3.4 Data Description ..........
4.2.2.4.3.5 Module Desgn .............
4.2.2.4.4 VUS F/C KEY PROCESSING .........
4.2.2.4.4.1 Functional Specification ..
4.2.2.4.4.2 Module Interface ...........
4.2.2.4.4.3 Module Components .........
4.2.2.4.4. Data Description ..........
4.2.2.4.4.5 Module Design .............
4.2.2.4.5 VCO CMD PROCESSING ............
4.2.2.4.5.1 Functional Specification ..
4.2.2.4.5.2 Module Interface ..........
4.2.2.4.5.3 Module Component ..........
4.2.2.4.5.3.1 STOP ACTION ...........
4.2.2.4.5.4 Data Description ........
4.2.2.4.5.5 Module Design ...........
4.2.2.4.6 VDIA CC PROCESSING ...........
4.2.2.4.6.1 Functional Specification ..
4.2.2.4.6.2 Module Interface ..........
4.2.2.4.6.3 Module Component .........
4.2.2.4.6.4 Data Description ..........
4.2.2.4.6.5 Module Design ............
…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.2.4.7 RETR OP PROCESSING ............
4.2.2.4.7.1 Functional Specifiction ...
4.2.2.4.7.2 Module Interface ...........
4.2.2.4.7.3 Module Component ...........
4.2.2.4.7.4 Data Description ...........
4.2.2.4.7.5 Module Design ..............
…86…1 …02… …02… …02… …02…
4.2.2 U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
The U̲ser F̲unction C̲o̲ntrol (UFCO) subpackage performs
the control of all user transactions. Furthermore,
UFCO performs the direct control o the VDU dialogue.
4.2.2.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:
- System control
- Transaction accounting
- Transaction creation
- Format sequence functions
- Error Handling
Fig. 4.2.2.11 presents the functional breakdown.…86…1
…02… …02… …02… …02…
Figs. 4.2.2.1-1/5…86…1 …02… …02… …02… …02…
4.2.2.1.1 S̲y̲s̲t̲e̲m̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲1̲.̲0̲)̲
The system control functions are those which indirectly
involve the SSC package. The commands are received
from VCO.
a) Initialization (1.1)
Eecutes the function to be performed after load of
software and which must be executed before normal
operation can be initiated. Depending on the type
of initialization, different actions are taken.
An initialization command is sent to VDIA.
b)Start-Up (1.2)
Executes the function to be performed after sign-on.
The command validation table reflecting the user
capability is defined.
c) Termination (1.3)
This function provides the UFCO with the capability
of performing the followingfunctions:
- Sign-off
- Block terminal
- Ordered close-down.
d) Security Interrogation (1.4)
Requests a security interrogation to be performed
in case of release.
Executes the functions to be performed after a security
interrogation e.g. receive function keys).
4.2.2.1.2 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲c̲o̲u̲n̲t̲i̲n̲g̲ ̲(̲2̲.̲0̲)̲
The transaction accounting functions are those concerning
log and statistics.
a) Collect Data (2.1)
The data which are used for log, satistics and
other purposes are collected in sequence table.
There exists no special collecting procedures but
all data which are pertinent for UFCO will be placed
in this area.
b) Log Reporting (2.2)
The log reporting functions are those requred to
report final log records. The data which are required
in a log record are extracted from the sequence
table.
c) Statistics Reporting (2.3)
The statistics reporting functions are those required
to report statistics.
The data which arerequired in the statistics are
monthly extracted from the sequence table.
4.2.2.1.3 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲C̲r̲e̲a̲t̲i̲o̲n̲ ̲(̲3̲.̲0̲)̲
The transaction creation group includes all the functions
to be performed before a transaction may be started.
a) Receive and Valiate (3.1)
Function keys entered by a user are received from
the VDU. The received function key is validated
against a function key bit mask.
There are two bit masks.
Bit mask (1) reflects the function keys which are
allowed at the moment.
Bit mask (2) reflects the function keys which will
change the format sequence.
b) Define Next Function Key (3.2)
If a function key must be followed by another,
this is defined (i.e. RETURN shall follow COMMAND).
c) Receive Command Line (3.3)
The contnts of the VDU command line are received
via the format handler.
d) Validate Command Line (3.4)
The contents of the command line are validated.
A command is validated against the command validation
table.
Parameters are checked to be withi the correct
range.
e) Display Response Message (3.5)
These functions display a response message in the
VDU response line.
f) Execute Function Key
The functions associated with the received function
key are performed and the format sequene is changed.
g) Execute Command (3.7)
The sequence table key is looked up in the command
validation table and the format sequence is started.
h) Assign Transaction Number (3.8)
Allocates next transaction no. for this terminal.
4.2.2.1. F̲o̲r̲m̲a̲t̲ ̲S̲e̲q̲u̲e̲n̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲(̲4̲.̲0̲)̲
The format sequence functions are those functions which
are called from the format sequence table.
This table makes it possible to drive the MMI in an
automatic and flexible manner.
It defines for each screen format:
- Allowed commands and function keys
- Functions to be called corresponding to commands/F/C
Keys
- LOG, STATISTICS, SAR reporting required
- Cursor position
- Command to VDIA
- Subsequently sequence record to be executed
4.2.2.1.4.1 S̲t̲a̲r̲t̲ ̲E̲x̲e̲c̲u̲t̲i̲o̲n̲ ̲(̲4̲.̲1̲)̲
The start execution functions are those which must
be performed before a format is presented for a user.
a) Create CIF Buffer (4.1.1)
These functions are those used to interface to
the message management system.
b) Request CIF (4.1.2)
If a continue preparation command is received,
then the referenced CIF is fetched from the preparation
database.
If a recive command is received, then the first
CIF in the corresponding queue is fetched.
c) Update VDU Header (4.1.3)
These functions update the VDU header fields, classification
and terminal function.
d) Complete Append (4.1.4)
These functionsadd a section of another message
to a message under preparation.
It shall be noticed that an off-line append can
result in two security interrogations.…86…1
…02… …02… …02… …02…
e) Display Error Code (4.1.5)
These functions display a response message in the
VDU response line.
f) Determine Message Type (4.1.6)
These functions determine the format wich shall
be used for a message.
4.2.2.1.4.2 S̲t̲o̲p̲ ̲E̲x̲e̲c̲u̲t̲i̲o̲n̲ ̲(̲4̲.̲2̲)̲
The stop execution functions are those which must be
performed when a user gives up access to a CIF.
a) Dismantle CIF / Buffer (4.2.1)
These functions are those used to intrface to the
message management system.
b) Update Status (4.2.2)
The outgoing message status, release message status
and the delivery message status are updated. The
message / comment under preparation is returned
to the preparation database.
c) Update VDU Header (4.2.3)
These functions update the VDU header fields, classification
and terminal function.
4.2.2.1.4.3 Q̲u̲e̲u̲e̲ ̲R̲e̲q̲u̲e̲s̲t̲s̲ ̲(̲4̲.̲3̲)̲
The queue request functions are those concerning the
reception of messages.
a) Receive (4.3.1)
The first CIF to which the requestor has acces
is received from a given queue.
b) Delete (4.3.2)
This function removes a CIF from a queue.
c) Keep (4.3.3)
This function returns a CIF to a queue.
d) Keep and Present next (4.3.4)
This function returns a CIF to the queue from whic
it was received. The next CIF to which the requestor
has access is returned.
e) Delete and Present next (4.3.5)
This function removes a CIF from the queue from
which it was received. The next CIF to which the
requestor has access is returned.
4.2.2.1.4.4 R̲e̲q̲u̲e̲s̲t̲s̲ ̲t̲o̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲(̲4̲.̲4̲)̲
The request functions are those concerning the treatment
of messages (CIFs) and requests (buffers).
a) Send for Coordination (4.4.1)
The message is sent for coordination and the delivery
notificaion created by MDP is displayed.
b) Send for Release (4.4.2)
The message is sent to the associated release terminal.
c) Release (4.4.3)
The message is sent for local distribution and
transmission. A release notification is returned
to the drafter.
d) Retrieve / Append (4.4.4)
A retrieve equest is sent to SAR and the retrieved
CIF and/or a response message is displayed.
e) Print (4.4.5)
The CIF currently displayed on the VDU is sent
to the associated printer, or the atomal printer.
f) Defer (4.4.6)
The preparation is termnated and the CIF is sent
to the preparation database.
g) Status Request (4.4.7)
A status request is sent to UMAM and the received
CIF is displayed.
h) Send for Distribution (4.4.8)
A comment is sent for local distribution.
i) Edit / Deete Requests (4.4.9)
A request is sent to UMAM and the referenced CIF
or a response message is displayed.
4.2.2.1.5 E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
The error handling function is separated into two parts:
a) Q ̲ERROR (5.1)
This function handles error due to failure in communication
between UFCO ad its queues and decides whether or not
the processing may continue.
b) Internal (5.2)
This function handles errors due to failure in
communication between b1) the subpackages communicating
with UFCO b2) the modules within UFCO, and decides
whther or not the processing may continue.
4.2.2.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The UFCO subpackage consists of one coroutine with
operation semaphore S2 as the main waiting point.
The input to UFCO will be a command which is received
from VCO, VDIA, RER, the answer queue or the VDU.
Each command will constitute a main function and is,
as well as major function, implemented as a module.
Furthermore some common procedures and module components
exist.
Refer figure 4.2.2.2.1-2.…86…1 …02… …02… …02… …02…
Figs. 4.2.2.2-1/2…86…1 …02… …02… …02… …02…
4.2.2.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.2.3.1 D̲a̲t̲a̲ ̲F̲l̲o̲w̲
The HIPO diagrams overleaf show the data flow of UFCO.
4.2.2.3.2 C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The control logic of UFCO is shown n the module-tree
in figure 4.2.2.2-1/2.…86…1 …02… …02… …02… …02…
Diag. ID: 4.2.2.3/24…86…1 …02… …02… …02… …02…
Fig. 4.2.2.3-1…86…1 …02… …02… …02… …02… …02…
4.2.2.4 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
UFCO ̲MAIN (4.2.2.4.1)
VUS ̲ANSWER ̲Q ̲PROCESSING (4.2.2.4.2)
APPEND ̲INVESTIGATION (4.2.2.4.3)
VUS ̲F/C ̲KEY ̲PROCESSING (4.2.2.4.4)
VCO ̲CMD ̲PROCESSING(4.2.2.4.5)
VDIA ̲CC ̲PROCESSING (4.2.2.4.6)
RETR ̲OP ̲PROCESSING (4.2.2.4.7)
VUS ̲IN/OUT ̲LINE (4.2.2.4.8)
VUS ̲CMD ̲PENDING (4.2.2.4.9)
VUS ̲SEQUENCE (4.2.2.4.10)
EAXECUTE ̲FUNCTION (4.2.2.4.11)
4.2.2.4.1 U̲F̲C̲O̲ ̲M̲A̲I̲N̲
4.2.2.4.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲2̲1̲4̲1̲A̲…00…CPS/SDS/039
…00…vhn …00…JBS …00…4.2.2
…00…1̲0̲…00…0̲5̲…00…8̲2̲…00…1̲4̲…00…3̲3̲…00… ̲ ̲1̲2̲…00…5̲5̲…00… ̲4̲4̲0̲4̲7̲…00…1̲7̲…00…0̲4̲…00…8̲4̲…00…0̲9̲…00…5̲8̲…00… ̲ ̲ ̲1̲…00…52…00… ̲ ̲3243…00…3̲1̲…00…0̲1̲…00…8̲4̲…00…1̲4̲…00…5̲0̲…00…08…00…11…00…84…00…15…00…02…00…0170A…00…
53…00… ̲ ̲2̲7…00…05…00… 548…00… ̲6̲8473…00……1f……00…%…00……11……02……00……10……00……01……10……05…'…10……11……01……80…*̲J̲…15……05……00……00……00……00……00……00……01…B
2̲…00……86……00……00……00……00…+…02……00……00…+
*…0d…*…0f…*…02…*
)…08…)…0e…)
(…08…(…0c…(…01…(…05…'…09…'…0a…'…0c…'…0d…'…0e…' &…86…1
…02… …02… …02…
#
…02…CPS/SDS/039
…02…841101 …02……02…
USER VDU
DETAILED DESIGN SPECIFICATION …02…ISSUE 1…02…CAMPS
4.2.2.4.1.1 Fuctional Specification ...
4.2.2.4.1.3.1 CANCEL ANQ IN-PUT......
4.2.2.4.1.3.2 REQUEST ANQIN-PUT........
4.2.2.4.1.3.3 REQUEST FC KEY IN-PUT..
4.2.2.4.1.3.4 CANCEL FC KEY IN-PUT..
4.2.2.41.4. Data Description..........
4.2.2.4.1.5 Module Design ..............
4.2.2.4.2 VUS ANSER Q PROCESSING .........
4.2.2.4.2.1 Functional Specification ..
4.2.2.4.2.2 Module Interface ...........
4.2.2.4.2.3 Module Component ...........
4.2.2.4.2.3.1 Delete Append CIF ......
4.2.2.4.2.4 Data Description ...........
4.2.2.4.2.5 Module Design ..............
4.2.2.4.3 Append Investigation .........
4.2.2.4.3.1 Functional Description ....
4.2.2.4.3.2 Module Interface ..........
4.2.2.4.3.3 Module Components .........
4.2.2.4.3.4 Data Description ..........
4.2.2.4.3.5 Module Des
