top - download
⟦6e81236d7⟧ Wang Wps File
Length: 32819 (0x8033)
Types: Wang Wps File
Notes: FIX/1000/PSP/0038, 4.1.5
Names: »5197A «
Derivation
└─⟦e48583e73⟧ Bits:30006141 8" Wang WCS floppy, CR 0514A
└─ ⟦this⟧ »5197A «
WangText
…00……00……00……00……00…E…02……00……00…E
8…09…8…0b…8…00…8…07…7…0d…7
7…06…6…0c……86…1 …02… …02… …02…
…0f…5197A/bna…02…FIX/1000/PSP/0038
…02…MLA/850529…02……02…
FIKS SYSTEM SPECIFICATION
…02……02…FK 7809…0e…
4.1.5 M̲e̲s̲s̲a̲g̲e̲ ̲E̲n̲t̲r̲y̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
4.1.5.1 F̲u̲n̲c̲t̲i̲o̲n̲s̲
The objective of the MES is to provide the interactive
terminal user the service of common message facilities.
Common MES functions are:
a. The p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ function supports the creation
of a message and its storage on the Preparation
Data Base (PDB).
b. The c̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ function supports the (logical)
transmission of a message between the message preparer's
terminal and a coordinator's terminal for comments.
c. The e̲d̲i̲t̲ function supports the modification of
the header and text lines of a message stored on
the PDB.
d. The r̲e̲l̲e̲a̲s̲e̲ function supports the outbound and/or
local distribution of a message upon approval of
an interactive releasing authority.
e. The r̲e̲a̲d̲d̲r̲e̲s̲s̲a̲l̲ function supports the release of
a message, stored on the Historical Data Base.
It allows the user to prepare a message containing
one previously released message.
f. The d̲i̲s̲p̲l̲a̲y̲ function supports the presentation
on a terminal of queue information and message
status and the presentation on a terminal of messages
from the PDB, or the Historical Data Base (HDB).
Delivery of special handling messages are also
performed by this module.
g. The d̲e̲l̲e̲t̲i̲o̲n̲ function provides the user a facility
to delete messages that he has prepared but not
released.
h. The r̲e̲t̲r̲i̲e̲v̲e̲ function supports the retrieval from
the Historical Data Base (HDB).
i. The r̲e̲t̲r̲i̲e̲v̲e̲/̲d̲i̲s̲t̲r̲i̲b̲u̲t̲e̲ ̲function supports the retrieval
from the HDB, and distribution to terminals local
to the MEDE.
O̲V̲E̲R̲V̲I̲E̲W̲ ̲O̲F̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲A̲C̲C̲E̲S̲S̲
Figure 4.1.5-1.
A message prepared and stored on the PDB is in Simplified
Message Format (SMF).
As long as the message stays in the PDB (= until release)
following functions can be performed:
- Edit the message header or text.
- Coordinate the message with another terminal operator
by sending the message and remarks to coordinator,
and receive remarks from the coordinator.
- Release message to MDS, originator terminal release
authority.
- Transfer message to release position, originator
terminal no release authority.
- Release message to MDS, releasing terminal, or
send message back to the originator with a remark.
- List message on the printer.
- Delete message, which has n̲o̲t̲ been sent for coordination,
print out or release.
When a message has been released and transferred to
the HDB it can be accessed:
- Retrieve from the HDB for print or display.
- Retrieve from the HDB for readdressing purpose.
The new message prepared becomes part of the preparation
pool.
- Retrieve from the HDB and distribute local.
A simplified transition diagram is shown below.
4.1.5.2 S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
Figure 4.1.5-2 illustrates the flow of data and control
for each of the functions supported by the MES.
When a circle encloses a number and a small letter
(e.g. (1a)), it indicates that an exception condition
may occur. Each referenced exception condition is clarified
in the diagram's legend. Potential hardware device
exception conditions, such as unrecoverable I/O errors,
are omitted from this overview flow diagram.
The use of circled numbers indicates the data and control
interfaces required to support the terminal functions.
C̲o̲m̲m̲e̲n̲t̲ ̲t̲o̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲:
Access to disk files is obtained directly via the File
Management Subsystem (FMS), IOS.
Communication with other subsystems, e.g. Message Distribution,
MDS, and the Storage Retrieval, SRS, is performed via
dedicated queues, by support from the queue monitor,
QACCESS.
In general the flow of a message through the FIKS network
is controlled by a Message Transition Control Block
(MTCB), it is created when a message is prepared and
exists during the life time of the message.
At all times the MTCB describes the status of a message,
and is is passed, logically, to the different subsystems
according to requested processing.
The MTCB processing is supported by the MTCB monitor.
Interactive terminal communication is supported by
the ITM (interactive terminal monitor).
The interactive communication is supported by the S/W
in an "issue prompt, read response mode".
For the queues accessed by the MES, see section 4.1.5.3.1.
C̲O̲M̲M̲E̲N̲T̲S̲ ̲T̲O̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 4.1.5-2.1
P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲a̲ ̲m̲e̲s̲s̲a̲g̲e̲
1. A SMF message is prepared and stored on the PDB
- Create a PDB file and MTCB for the message
- The message header is prepared according to
the SMF
- The input of the header information is controlled
by the S/W in a "prompt for input and read
response" mode
- The entered header data are validated and the
plain addressees for the given address numbers
are written to the PDB (either Danish/English).
- Accordingly the routing information and message
description (binary header/routing information/address
list) is formatted.
2. The text of the message can be entered, via text
masks, "fixed formatted" or "fill in the blanks
type".
- Get requested mask from disk
- Present mask on terminal
- Accept input for filling the mask
- Update PDB message text part with the formatted
mask and entered data
- Update message description
- The memory is purged in case of SH message.
3. Alternatively the text part of the message can
be entered (in free format from the keyboard) terminal
or the attached PTR
- Update the PDB message text part with the entered
data
- Update message description
- The memory is purged in case of SH message.
C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲a̲ ̲m̲e̲s̲s̲a̲g̲e̲
O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲p̲o̲s̲i̲t̲i̲o̲n̲
4. A message is sent for coordination to another terminal
- Request identification of the PDB message
- Get message reference.
5. The coordinator terminal position is specified
- Check given terminal id.
6. Request the comments to be sent to the coordinator
- Create a TRF file and MTCB for the remarks
- Accept the entered data as remarks
- Update the TRF accordingly
- Transfer the remarks reference to the coordinator
terminal CO queue.
C̲o̲o̲r̲d̲i̲n̲a̲t̲o̲r̲ ̲p̲o̲s̲i̲t̲i̲o̲n̲
7. The coordinator accesses the enqueued TRF remarks
from the originator and the related message
- Dequeue the entry in the CO queue
- Display MSG ̲ID
- Display single remarks line and print (queue
the message into the LP queue, for processing
by the PIP) the contents of the TRF and the
message on the PDB. In case of SH message the
memory is purged after printout.
- Flag MTCB so printout only once.
8. Request the remarks to be sent to the originator
- Create a TRF file and MTCB for the remarks
- Accept the entered data as remarks
- Update the TRF accordingly
- Enqueue the reference to the TRF at the originator
terminal LP queue, for printout.
C̲O̲M̲M̲E̲N̲T̲S̲ ̲T̲O̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 4.1.5-2.2.
P̲r̲e̲s̲e̲n̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲o̲r̲ ̲S̲t̲a̲t̲u̲s̲ ̲o̲n̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲
A message in the preparation pool for a terminal can
be accessed for print out, or status display.
Messages of special category type are not delivered
automatically at the terminal, but on operator request.
A message retrieved from the HDB for display at a terminal
is accessed via the RT queue.
The contents of the terminal precedence queues can
be presented as a queue index, upon request from terminal
operator.
D̲i̲s̲p̲l̲a̲y̲ ̲Q̲u̲e̲u̲e̲ ̲I̲n̲d̲e̲x̲
9. The precedence queues for the actual terminal are
accessed
- Request precedence queues id
- Present for each element in queue the message
description (= time of enqueing).
D̲i̲s̲p̲l̲a̲y̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲
23. The status of the messages in the PDB for that
terminal are displayed: in preparation, sent for
release, sent for coordination or sent for printout.
- Get message status
- Present status on terminal.
S̲H̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
25. The special category message is printerd on request
after the terminal operator with a legal access
right (class and SH password) has been accepted
by the system
- Read entry in SH queue
- Check legal classification of terminal against
message class
- Request SH password and validate it
- A notification is sent to the PIP either for
print out (password ok) or reroute of message
(password not ok), await response from the
PIP when this is ready for print out
- A 10 minutes time out is counted
- The PIP is notified of the event "print out",
or "reroute due to 10 min. time out", the terminal
process awaits the PIP completion
- Request and check password after print out
- The memory and file are purged after printout.
P̲D̲B̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲i̲n̲t̲ ̲O̲u̲t̲
26. A message stored in the PDB pool for a terminal
can be accessed for print out to a terminal with
a legal classification
- Check message classification against terminal
classification, and check message status
- Pass the message reference to the terminal
LP queue for print out by the PIP.
P̲r̲i̲n̲t̲ ̲O̲u̲t̲ ̲f̲r̲o̲m̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲Q̲u̲e̲u̲e̲s̲
27. Request for print out on a TP in RX/TX mode, for
entries from the precedence queues, is performed
- Notify the PIP for print out
D̲e̲l̲e̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲s̲t̲o̲r̲e̲d̲ ̲o̲n̲ ̲P̲D̲B̲
A message stored on the PDB, and not sent for release,
print out or coordination can be deleted.
The delete request can be performed on message
in the PDB pool for the terminal in question.
10. The message to be deleted is specified
- Check that message is in the PDB
- Check legal classification of terminal against
message class
- Check legal message status
- Delete message on the PDB
- In case of SH message the file is purged
- Release corresponding MTCB.
E̲d̲i̲t̲i̲n̲g̲ ̲o̲f̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲s̲t̲o̲r̲e̲d̲ ̲o̲n̲ ̲t̲h̲e̲ ̲P̲D̲B̲
A message in the preparation pool for a terminal can
be accessed for editing of the header or the text part.
The edited version of the message replaces on request
the original PDB message.
Validation of the changes applied to the message header
is performed.
21. The message to be edited is specified, and editing
is performed
- check if message is in PDB
- Check for legal access to message
- Create a TEF file and MTCB for the message
- Display message line by line, or partwise according
to operator commands
- Accept edit commands
- replace line
- accept line(s)
- accept/display line(s)
- accept header
- delete line(s)
- insert line(s)
- finish/abort
- The changes applied to the message header are
validated to be according to SMF, the MTCB
and message (TEF) address list and binary header
is updated accordingly.
- Changes to the message text are accepted as
free format, the MTCB and message (TEF) is
updated accordingly.
22. The applied changes, (= the TEF message) can be
accepted or not.
Accept changes:
- Replace logically the "old" PDB message with
the "new (= the TEF message)
- Release old PDB message file and MTCB
- In case of SH message the memory and PDB file
are purged.
Not accept changes:
- Release new message file and MTCB (= the TEF
message)
- In case of SH message the memory and TEF file
are purged.
C̲O̲M̲M̲E̲N̲T̲S̲ ̲T̲O̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 4.1.5-2.3.
R̲e̲l̲e̲a̲s̲e̲ ̲o̲f̲ ̲a̲ ̲M̲e̲s̲s̲a̲g̲e̲
O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
11. A release attempt is performed by the message originator
terminal, which has no release authority, the message
is sent for releaase by another terminal.
- Request the identification of the PDB message
- Get message reference
- Get position of releasing terminal
- Transfer, logically, the message to the release
position, terminal RL queue.
14. A release is performed to the MDS from the originator
terminal, which has release authority
- Request the identification of the message from
the PDB pool
- Get message reference
- Transfer, logically, the message to the MDS
input queue according to message precedence
- The release event is logged
- NODE/MEDE statistic updating
- The release event is logged.
R̲e̲l̲e̲a̲s̲e̲ ̲p̲o̲s̲i̲t̲i̲o̲n̲
12. The releaser accesses the enqueued PDB message
for display and accept to release
- Get message reference
- Display message on terminal
- Transfer message, logically, to the MDS input
queue according to message precedence
- The release event is logged
- Create a TRF file and MTCB for a release remark
to originator and format the remark
- Insert the remark reference into the originator
terminal LP queue, for print out.
- In case of SH message the memory is purged
- NODE/MEDE statistic updating
- The release event is logged.
13. The releaser returns the PDB message to the originator
with a remark
- Get message reference
- Display message on terminal
- Create a TRF and MTCB for a release remark
- Accept entered data as remarks to originator
- Update TRF accordingly
- Transfer the remarks to the originator terminal
LP queue for print out
- Return logically the PDB message to the PDB
pool for the originator terminal
- In case of SH message the memory is purged.
C̲O̲M̲M̲E̲N̲T̲S̲ ̲T̲O̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 4.1.5-2.4.
R̲e̲a̲d̲d̲r̲e̲s̲s̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲s̲t̲o̲r̲e̲d̲ ̲o̲n̲ ̲H̲D̲B̲
A previous released message which has been stored on
the HDB can be retrieved, and appended to a new message
prepared.
15. Prepare message in SMF and store on the PDB.
+
16. Processing is as described on figure 4.1.5-2.1.
The CLASS/SPECAT/SIC of the "old" message is used
in the "new" header.
17. The message to be retrieved is specified
- Create a pseudo MTCB for the i/F description
to be passed to the SRS
- Get retrieval keys for the identification of
the message
- Build I/F block for the SRS and enqueue to
the SRS input queue for retrieval.
The SRS performs the retrieval and returns the
reference to the message found on the HDB in the
MES RD queue.
18. The terminal process awaits the retrieval completion
- Wait SRS feed back
- Dequeue the message description
- Access the HDB message and move to the PDB,
append "old message" to "new text" part as
extention to the text
- Update the PDB message description accordingly.
The SRS validated the access rights to the message,
according to the retrieval criteria, and logs the
retrieval event.
R̲e̲t̲r̲i̲e̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲f̲r̲o̲m̲ ̲H̲D̲B̲
A previous released message which has been stored on
the HDB can be retrieved for display or print out.
19. Initiate SRS retrieval from the HDB
+
20. - Create a pseudo MTCB for the I/F description
to be passed to the SRS
- Get retrieval keys for identification of the
message
- Get output mode, for the retrieved messages,
print or display
- Build I/F block for the SRS and enqueue to
the SRS input queue for retrieval.
The SRS performs the retrieval and returns the
reference to the message(s) found on the HDB in
the specified terminal queue, display (RT queue
or print (LP queue).
The SRS performs validation of the access rights
to
the message, according to the terminal retrieval
criteria, and logs the retrieve event.
C̲O̲M̲M̲E̲N̲T̲S̲ ̲T̲O̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 4.1.5.-2.5.
R̲e̲t̲r̲i̲e̲v̲e̲/̲D̲i̲s̲t̲r̲i̲b̲u̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲s̲t̲o̲r̲e̲d̲ ̲o̲n̲ ̲H̲D̲B̲
A previous released message which has been stored on
HDB can be retrieved and distributed to terminals local
to the MEDE for print out.
21. Initiate SRS retrieval from HDB
- Create pseudo MTCB for the I/F description
to be passed to the SRS
- Get retrieval keys for identification of the
message
- Build I/F block for the SRS and enqueue to
the SRS input queue for retrieval.
22. - Request destination terminal(s) and No. of
Copies.
23. The terminal awaits the retrieval completion
- Wait for SRS feed back
- Enqueue to MDS
- The distribution is logged.
The SRS performs the retrieval and returns the
reference to the message found on the HDB in the
RT queue.
The SRS performs validation of the access rights
to the message, according to the terminal retrieval
criteria, and logs the retrieve event.…86…1
…02… …02… …02… …02…
4.1.5.3 D̲e̲s̲i̲g̲n̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
The MES is designed to execute under control of the
Interactive Terminal Monitor (ITM). There is one process
active under ITM control for each terminal that is
using MES services. The terminal processes are started
by the ESP subsystem. See figure 4.1.5-3.1, at terminal
log-on.
The MES is organized in procedures, which according
to the given input is entered, see figure 4.1.5-3.2.
The ITM module GET ̲CMD, Get command, requests the "PROC"
to be executed, and is performed until terminal log
off.
The ITM scans the operator command for procedure selection,
and afterwards the selected MES procedure performs
the appropriate handling, inclusive control of the
terminal I/O, via the ITM.
The selected procedure is active until "end of program"
is reached or the "CANCEL" key has been entered, or
a supervisor log off has been issued to the terminal,
and in all cases the system responds with a new "PROC".
The terminal process creation for VDU and teleprinter
(TP) is performed in the same way.
M̲E̲S̲ ̲M̲o̲d̲u̲l̲e̲ ̲A̲c̲t̲i̲v̲a̲t̲i̲o̲n̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
^
^ ITM
^
^
^ REPEAT
^
^ GET ̲CMD (CMD,FLAG)
^
^ BEGIN
^
^ CASE CMD OF
^
^ PREPARE
^ DISPLAY
^ RELEASE
^ DELETE
^ EDIT
^ COORDINATE
^ READDRESS
^ RETRIEVE
^ RETRIEVE ̲DISTRIBUTE
^ DISTRIBUTE
^ REPORT-HANDLING
^ CONTROL-TERMINAL
^ CONTROL-QUEUE
^ DISPLAY ̲STATUS
^ UPDATE-ANO-TABLE
^ UPDATE-USP
^ NPDN-CONNECTION
^
^ END:
^
^ UNTIL NOT FLAG
^
^ END.
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
(Note supervisor modules described in ref. 10)
Figure 4.1.5-3.2
Below is a list of the response to the "PROC" with
indication of the MES module which shall be activated.
M̲E̲S̲ ̲C̲O̲M̲M̲O̲N̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
P̲R̲E̲P̲A̲R̲E̲
PEL preparation long - English
PRL preparation long - Danish
PES preparation short - English
PRS preparation short - Danish
D̲I̲S̲P̲L̲A̲Y̲
Status:
DQI Display queue index
STA Display message status
messages:
SPH Special handling print out
DRT Display from retrieve queue
LST Print from preparation data base (PDB)
PRN Print from precedence queues (TP)
R̲E̲L̲E̲A̲S̲E̲
REL Release message (originator)
DRL Release message (releaser)
D̲E̲L̲E̲T̲E̲
DEL Delete message from PDB
E̲D̲I̲T̲
EDI Edit message on PDB
C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲
COO Originator coordinate request
DCO Coordinator request
R̲E̲A̲D̲D̲R̲E̲S̲S̲
RAD Readdress HDB message (Danish)
RAE Readdress HDB message (English)
R̲E̲T̲R̲I̲E̲V̲E̲
RTR Retrieve HDB message
R̲E̲T̲R̲I̲E̲V̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲E̲
RDT Retrieve HDB message and distribute to
local terminals.
P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the preparation of a message in
simplified message format (SMF).
Both the "short" and "long" preparation mode is performed
by this module, and the "short" by passing the code
part (= options) excluded from the "long" procedure.
The "submodule no" received via the ITM indicates if
"short" or "long" procedure has been requested.
The preparation is supported in an "issue prompt read
response mode".
H̲e̲a̲d̲e̲r̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
The entered data are validated for correct syntax and
semantic:
- action precedence
- info precedence
- from address
- to address
- exempt address
- info address
- classification
- special category
- subject indicator code
The processing is on a line by line basis and identical
on a TP and a VDU.
T̲e̲x̲t̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
The text part and the internal distribution are accepted
in free format, but the date time group is checked
for correct syntax and semantic.
- text part
- date-time-group
- internal distribution
The processing of the text description is on a line
by line basis and identical on a TP and a VDU.
The text part entering can be performed:
- characters entered in free format via the terminal
- supported by text masks of "fill in the blanks"
type or fully formatted
- characters entered in free format via the PTR.
F̲r̲e̲e̲ ̲F̲o̲r̲m̲a̲t̲ ̲I̲n̲p̲u̲t̲
The input from a TP is supported in line at a time
mode. The input from a VDU is supported in page mode.
T̲e̲x̲t̲ ̲M̲a̲s̲k̲ ̲I̲n̲p̲u̲t̲
The input from a TP is supported in a line at a time
mode. The mask is presented field by field, or line
by line according to mask type. Operator data can be
supplied to each field, when the mask is of "fill in
the blanks" type. The fields are presented line by
line.
The input from a VDU is supported in page mode. The
mask is presented and the editing facility of the VDU
supports changes performed to the mask content.
P̲T̲R̲ ̲I̲n̲p̲u̲t̲
Paper tape input can be performed from a VDU with a
PTR fixed allocated by switching on the PTR device,
and a request from the VDU keyboard.
M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲o̲n̲ ̲t̲h̲e̲ ̲P̲D̲B̲
The message prepared is stored on a PDB file, and described
by an MTCB.
The binary header on the PDB file is updated according
to the contents of the file.
The entered address information (ANO's) are replaced
on the PDB with the corresponding plain address text,
and the address information is assembled into the address
list which is written at the end of the message on
the PDB. According to the specified mode, the English
or Danish plain addresses from the RDF is used.
The address list is built in a pseudo MTCB, and in
case of more than 6 addresses, it is temporarily stored
on a disk file.
D̲I̲S̲P̲L̲A̲Y̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the presentation on a terminal
of message status or message header and text.
In addition queue index display is supported by this
module:
- display queue index
- display message status
- display message in retrieve queue
- request SH message delivery
- print from PDB
- print message in precedence queue
(TP in RX/TX mode).
Each of the functions above are implemented as code
blocks inside the display module and dispatching is
performed according to the "submodule no" received
via the ITM related to the requested procedure..
The output to the terminal is supported by the ITM
or the PIP as given below:
t̲e̲r̲m̲i̲n̲a̲l̲ ̲I̲/̲O̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
F̲u̲n̲c̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲D̲U̲/̲R̲O̲P̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲T̲P̲ ̲ ̲(̲R̲X̲/̲T̲X̲)̲
̲ ̲ ̲ ̲ ̲
procedure commands ITM ITM
display queue index ITM ITM
display message status ITM ITM
display from RT queue ITM PIP
SH message delivery PIP PIP
print from PDB PIP PIP
print from queue - PIP
R̲E̲L̲E̲A̲S̲E̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the release of a message for distribution.
- Release message (originator)
- terminal has authorization
- terminal has no authorization
- Release message (releaser)
- accept release
- deny release
Each of the two functions above are implemented as
code blocks inside the release module and dispatching
is performed according to the "submodule no" received
via the ITM.
The release remarks to be sent to originator (when
release from release position) are passed via a disk
file (TRF) described by an MTCB.
D̲E̲L̲E̲T̲E̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the deletion of message prepared
and stored in the PDB.
Only messages related to the requesting terminal and
not sent for release, print out or coordination can
be deleted.
Deletion of SH messages implies purge of the related
PDB file.
E̲D̲I̲T̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the editing of a message in the
PDB. Only messages related to the requesting terminal
and not sent for release, print out or coordination
can be edited.
The editing sequence is controlled by the S/W based
upon the operator input commands. The editing is performed
on a line by line basis, and for a given command at
a certain level the corresponding prompt is issued
and the operator response to this is analyzed for correct
format and the appropriate action is taken.
The following functions are supported:
- accept line(s) optionally display also
- accept header
- insert line(s)
- replace line
- delete line(s)
- finish/abort editing.
The performed changes can be accepted by the operator
which implies that the original message is replaced
by the edited version.
The binary header and the message description (MTCB)
are updated accordingly.
In case a SH message has been edited the "old" PDB
message is purged, if "new" is accepted and vice versa.
M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲ ̲E̲d̲i̲t̲i̲n̲g̲
Changes applied to the addresses in the message header
imply update of the address list on the PDB. The address
list of the new message header is built in the terminal
buffers and in case the size of the new address list
becomes bigger than the reserved buffer space, the
address list is temporarily stored on a disk file.
C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the coordination of a message between
two terminals, before release for distribution
- Coordinate message (originator)
- Coordinate message (coordinator)
Each of the two functions above are implemented as
code blocks inside the coordinate module and dispatching
is performed according to the "submodule no" received
via the ITM.
The remarks to be sent from the originator to the coordinator
and back are passed via a disk file (TRF) described
by a MTCB
R̲E̲A̲D̲D̲R̲E̲S̲S̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the readdressing of a HDB message.
The readdressing is in principle a preparation of a
message in SMF, with the "old" HDB message appended
to the "new" message text part.
The preparation of the "new" message is supported by
the PREPARATION module described above, the text descriptor
(class/specat/sic) from the "old" message is used in
the "new" message.
The HDB retrieval is supported by the SRS, for location
of the message, whereas the MES readdress module performs
the physical transfer of the message from the HDB to
the PDB.
The SRS checks if the terminal has retrieve right to
the message.
R̲E̲T̲R̲I̲E̲V̲E̲ ̲M̲o̲d̲u̲l̲e̲
The module supports the retrieve of a HDB message,
for display or print at a terminal.
The module supports the request from all terminals
inclusive supervisor/assistent.
The HDB retrieval is supported by the SRS for the location
of the message, whereas the MES DISPLAY module (on
request) displays the message, or the PIP prints the
message on the terminal. The SRS checks if the terminal
has retrieve right to the message (supervisor/assistant
access to all).
R̲E̲T̲R̲I̲E̲V̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲E̲
The module supports the retrieval and the distribution
of a HDB message for print at terminal(s) local to
the MEDE.
The module supports the request from all terminals
inclusive supervisor/assistant.
The HDB retrieval is supported by the SRS for the location
of the message.
The retrieved message, which is placed in the RD queue
by the SRS, is distributed to specified terminal(s)
by means of the Q-ACCESS procedure.
The SRS checks if the terminal has retrieve right
to the message (supervisor/assistant access to all).
If the message is undeliverable, an error message will
by issued at the originator terminal.
4.1.5.3.1 Q̲u̲e̲u̲e̲s̲ ̲A̲c̲c̲e̲s̲s̲e̲d̲
Following queues are accessed by the MES.
- MES feed back queue (RD)
The queue supports the I/F MES/SRS used in the
readdress and retrieve/distribute procedures by
the SRS to pass the completion status of a requested
retrieval from the HDB. The feed back given is
a message reference or error notification, described
in a MTCB or pseudo MTCB respectively.
- MDS precedence queue
The queue is accessed for insertion when a PDB
message has been released for distribution. The
entry is made according to the message precedence,
and is a reference to the related MTCB.
- SRS input queue
The queue is accessed for insertion when retrieval
request is raised to the SRS, for retrieve and
readdress purpose. The entry made is a reference
to a pseudo MTCB describing the request.
- Terminal print queue
The LP queue of the terminal is accessed for insertion
when a release/coordinate remark shall be printed.
The entry made is a reference to a pseudo MTCB
describing the remark.
- Terminal display queue
The CO queue of the terminal is accessed when a
message shall be coordinated.
The entry made is a reference to a MTCB describing
the remark to coordinator and a reference to the
message description (MTCB).
The RL queue of the terminal is accessed when a
message shall be released from the release position.
The entry made is a reference to a MTCB describing
the message.
The RT queue of the terminal is accessed when a
message retrieved from the HDB shall be displayed.
The queue contains one entry per found message,
which satisfied the retrieve criteria, or an error
notification due to illegal retrieval.
The entry made is a reference to a MTCB describing
the message on the HDB, or a pseudo MTCB given
the error.
4.1.5.3.2 D̲i̲s̲k̲ ̲F̲i̲l̲e̲ ̲A̲c̲c̲e̲s̲s̲
- P̲D̲B̲ ̲F̲i̲l̲e̲s̲
The files are used to store messages prepared and
not released.
The files are of random structure and treated as
named files.
The files are accessed when a message is prepared,
edited, coordinated, displayed and released or
deleted.
- R̲D̲F̲ ̲F̲i̲l̲e̲s̲
The files contain routing and address information.
The files are accessed to:
- validate existence of ANO and AIG
- get relation between ANO and plain address
- get relation between AIG and ANOs
- get relation between terminal id and logical
terminal number
- get relation between terminal no. and actual
logical terminal.
The files are layed out at system initialization
time.
- T̲M̲F̲ ̲F̲i̲l̲e̲s̲
The files contain text masks for use in preparation
of message text part.
The files are layed out at system initialization
time.
- T̲R̲F̲ ̲F̲i̲l̲e̲s̲
The files contain temporary stored remarks, to
be passed between terminal users, when release
and coordination of messages.
The files asre of random structure and treated
as named files.
The files are part of the PDB file pool
- T̲E̲F̲ ̲F̲i̲l̲e̲s̲
The files contain an updated version of a message
as result of an edit operation. The file replaces
the corresponding PDB file, on request.
The files are of random structure and treated as
named files.
The files are part of the PDB file pool.
- H̲D̲B̲ ̲F̲i̲l̲e̲s̲
The files contain messages released and distributed
and are accessed for retrieve and readdress purpose.
4.1.5.4 V̲i̲s̲u̲a̲l̲ ̲T̲a̲b̲l̲e̲ ̲o̲f̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲
Figure 4.1.5-4 gives an overview of the main modules
which constitutes the MES.
Other interactive terminal functions that are not related
to message entry, such as log on/log off, are provided
by the ITM.
4.1.5.5 S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲o̲v̲e̲r̲v̲i̲e̲w̲ ̲H̲I̲P̲O̲ ̲D̲i̲a̲g̲r̲a̲m̲
Figure 4.1.5-5 provides an overview of the functions
that occur in support of the basic message entry processes.
Although the functions are listed sequentially, their
execution for unrelated terminals is designed to occur
concurrently.
