top - download
⟦7c492b465⟧ Wang Wps File
Length: 29068 (0x718c)
Types: Wang Wps File
Notes: FIX/1000/PSP/038
Names: »5204A «
Derivation
└─⟦c5670ecfe⟧ Bits:30006140 8" Wang WCS floppy, CR 0516A
└─ ⟦this⟧ »5204A «
WangText
…0e……0e… 5204A/aml…02…FIX/1000/PSP/0038
…02…OK/850529…02……02…
FIKS SYSTEM SPECIFICATION
…02……02…FK7809…0f…
4.1.3 M̲D̲S̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
4.1.3.1 F̲u̲n̲c̲t̲i̲o̲n̲s̲
The MDS provides software functions that support interaction
with other NODE/MEDE subsystems and with MEDE terminals.
The functions are divided into two categories:
1. Distribution Management
2. Terminal Service
4.1.3.1.1 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
1a. It delivers an inbound message to one or to several
terminal queues according to the precedence level
of the message.
1b. It requests that the Storage and Retrieval Subsystem
enter messages into the Historical Data Base that
are inbound or which are inbound or which have
been released for outbound network distribution.
1c. It requests the Nodal Switch Subsystem to route
the message when it is for outbound distribution.
1d. It notifies the Supervisory Function Subsystem
of undeliverable messages.
1e. It makes an entry into the Message Journal when
the message is delivered to printer, or if it is
undeliverable.
1f. It delivers control messages to the Supervisory
functions Subsystem.
4.1.3.1.2 T̲e̲r̲m̲i̲n̲a̲l̲ ̲S̲e̲r̲v̲i̲c̲e̲
2a. It maintains awareness of printer accessibility.
2b. It makes the necessary formatting of a message
prior to printing it.
2c. It ensures that Special Handling messages are not
printed until the associated terminal operator
informs the Message Entry Subsystem of the correct
password.
2d. It makes an entry into the Message Journal when
printing of a message begins.
2e. It prints Transaction Log on request.
2f. It prints the Message Journal on request.
2g. It prints the Message Log on request.
2h. It performs the page formatting during printout.
2i. It prints statistics messages on request.
4.1.3.2 S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
The MDS is a queue driven subsystem. It has an input
queue consisting of seven precedence queues; S, Z,
Y, O, P, M, and R each of them serviced in FIFO order.
When an entry into the input queue is made, and it
is empty, the MDS is notified through a Signal sent
by the QACCESS Monitor.
The input queue is serviced FIFO by precedence. The
entries are dequeued by calling the QACCESS monitor,
which returns the MTCB-index.
The MDS executes until the input queue is empty. Then
it enters the wait state. It is awakened by AMOS at
the next signal from the QACCESS monitor.
Figure 4.1.3.2-1…01…MDS Input Interface
The contents of the input queue-entries are MTCB-indexes:
For narrative messages the Message Transition Control
Block, MTCB, contains:
- the disk-addres of the message
- the type of the message
- the precedence of the message
- indication that the message may require Special
Handling
For control messages, the MTCB contains:
- the category of the message
- the subcategory of the message
- information depending on category and subcategory
4.1.3.2.1 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
Figure 4.1.3.2-2 illustrates flow and control when
the MTCB, which is pointed to in the MDS-queue, references
a narrative message.
The MES and the NSS request service by enqueuing a
MTCB-index in the MDS-queue (1a & 1b).
The following description is divided into three subsections
as shown in the following Figure 4.1.3.2.1-1.
Figure 4.1.3.2-2…01…Distribution Management
Figure 4.1.3.2-2 (cont'd)…01…Delivery of Narrative Messages
4.1.3.2.1.1 E̲n̲t̲e̲r̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲i̲n̲t̲o̲ ̲t̲h̲e̲ ̲H̲D̲B̲
After reading the MTCB-index in the MDS queue (2
& 2a) the MDS determines whether the message is
a Special Handling message or not. It is done
by examination of the MTCB. If the message is
not a SH-message a request for storage on the HDB
is enqueued into the SRS1 queue (3a) by calling
the QACCESS (3). Prior to the request the MTCB
is filled with the DTG which is used as Retrieval
time. The MDS will continue processing of the
message when an AMOS system message is received
from the SRS, indicating that the message has been
stored.
4.1.3.2.1.2 O̲u̲t̲b̲o̲u̲n̲d̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The MTCB indicates if the message is intended for
outbound delivery. If so, an entry into the NSS's
input queue is requested by calling QACCESS (4).
The entry is made according to the precedence
of the message(4a).
4.1.3.2.1.3 I̲n̲b̲o̲u̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
The MTCB identifies the message as intended for
inbound delivery. Two addressing schemes exist.
The first is a list of address numbers (ANO list)
stored, as a tailor to the message text, on the
message file.
The decoding of the Address List is illustrated
in Figure 4.1.3.2-3. The terminal number of the
ANO is valdated. If the number is unknown a request
for distribution by the SFS is enqueued into the
SFS's DT-queue (5 & 5a). Otherwise the ANO is
converted to the corresponding terminal number.
The second addressing scheme used is a list of
terminal numbers stored in the MTCB. Together
with each terminal number, a number which indicates
the number of copies to be queued to the terminal,
is stored.
Figure 4.1.3.2-3…01…Addressing Scheme
Now it is examined if the message requires Special
Handling (through the MTCB).
4.1.3.2.1.3.1 I̲n̲b̲o̲u̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲N̲o̲n̲ ̲S̲H̲ ̲M̲e̲s̲s̲a̲g̲e̲
If the message is not a Special Handling message
it is tested whether the terminal operator has
a security classification greater than or equal
to that of the message. If not, an entry into
the DT-queue of the supervisor's terminal (5 &
5a) is made. If the message is of flash precedence,
and it is intended for a terminal which is logged
off or blocked, an alarm is sent to the SFS (5
& 5b). Else the QACCESS is requested to enqueue
it (7) into the precedence queue of the terminals
corresponding to the precedence of the message
(7a). This is illustrated in Figure 4.1.3.2-4.
4.1.3.2.1.3.2 I̲n̲b̲o̲u̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲S̲H̲ ̲M̲e̲s̲s̲a̲g̲e̲
If the message is a Special Handling message it
is examined if the terminal operator has a Special
Handling password and is logged on in RX/TX mode.
This is determined through examination of the
Terminal Control Block, TCB. If the operator fulfills
these requirements the QACCESS is requested (6)
to enqueue the message into the SH-queue (6a)
of the terminal. The terminal number is obtained
as described above.
If the operator had no Special Handling password,
QACCESS is requested to enqueue the message (5)
into the DT-queue (5a) of the SFS.
Figure 4.1.3.2-4…01…Terminal queues
4.1.3.2.1.3.3 R̲e̲l̲e̲a̲s̲e̲ ̲o̲f̲ ̲t̲h̲e̲ ̲Q̲u̲e̲u̲e̲ ̲E̲n̲t̲r̲y̲
The QACCESS is called to release the MTCB from
the MDS queue.
4.1.3.2.1.4 I̲n̲b̲o̲u̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Figure 4.1.3.2-5 illustrates the flow of data and
control when the queue contains a reference to
a MTCB describing a control message.
The MDS requests that QACCESS delivers the queue
entry (1). The MTCB-index (1a) points to a MTCB
which identifies a control message.
The QACCESS is requested (2) to enqueue the message
into the SF-queue of the SFS.
Figure 4.1.3.2-5…01…Delivery of Control Messages
4.1.3.2.1.5 I̲n̲b̲o̲u̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲O̲r̲b̲i̲t̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Figure 4.1.3.2-6 illustrates the flow of data anc
control when the queue entry contains a MTCB-index
where the MTCB identifies that the message is orbiting.
The MDS calls QACCESS (1) and the MTCB-index (1a)
is returned. The MDS determines that the message
is orbiting and if the message is not a Special
Handling message, a request is enqueued into the
SRS1 queue, requesting storage on the HDB by calling
QACCESS (2).
A pseudo MTCB is created and updated with parameters
describing an orbiting message. The index of the
message MTCB is inserted in the pseudo MTCB. QACCESS
is then requested to enqueue the index of the pseudo
MTCB into the DT-queue of the SFS (3 & 3a).
If the address list of the orbiting message contains
addresses belonging to this N/M the message is
distributed as described in 4.1.3.2.1.3.1-3.
Figure 4.1.3.2-6…01…Orbiting Messages
4.1.3.2.2 T̲e̲r̲m̲i̲n̲a̲l̲ ̲S̲e̲r̲v̲i̲c̲e̲
The Figure 4.1.3.2-7 illustrates the flow and control
as the Printer Interface Process (PIP) services
the terminal print queues depicted in Figure 4.1.3.2-4.
4.1.3.2.2.1 S̲e̲r̲v̲i̲c̲e̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲e̲r̲s̲
The PIP is an event driven process. This means
that the printers are serviced in the order that
the events occur.
An event is defines as an incident which transfers
synchronization and/or data information from a
process or a pheripheral device to another process.
The following event types are used to synchronize
the PIP.
- Messages (2, 3 & 8)
- Signal (1)
- I/O completion (6a)
The servicing of a printer is initiated by a signal,
identifying that an entry into an empty printer
queue-group has been made. The printer is then
serviced until its queue-group gets empty. The
queue entry with the highest precedence which has
waited the longest is read. A buffer is formatted
by requesting the I/O system to read from a disk
file.
When this event becomes the oldest, the PIP services
is next. Then PIP requests the I/O system to print
the buffer. These read/write requests are repeated
until the printout completes.
When a printer completes a printout the next queue
entry is serviced. If the queue entry concerns
a printout of a Special Handling message or if
the printer is a teleprinter in RX/TX-mode, an
AMOS-message is awaited.
The service of the printer is suspended until it
arrives.
If the next entry does not concern a printout at
a teleprinter in RX/TX-mode or a Special Handling
message this printout follows the previous immediately.
This strategy is chosen so that the printers are
utilized as effective as possible.
4.1.3.2.2.2 E̲v̲e̲n̲t̲s̲ ̲S̲u̲p̲p̲o̲r̲t̲e̲d̲ ̲b̲y̲ ̲P̲I̲P̲
MTCBs or system messages may describe one of the
following events:
- Narrative Messages Section 4.1.3.2.2.5
- Coordination Remarks - 4.1.3.2.2.6
- Remarks - 4.1.3.2.2.7
- Special Handling Print
Requests - 4.1.3.2.2.8
- Print Requests from a
Teleprinter - 4.1.3.2.2.9
- Terminal Log on Status - 4.1.3.2.2.10
- Message Journal - 4.1.3.2.2.11
- Transaction Log - 4.1.3.2.2.12
- Message Log - 4.1.3.2.2.13
Figure 4.1.3.2-7…01…Printing of Messages
4.1.3.2.2.3 B̲u̲f̲f̲e̲r̲s̲ ̲i̲n̲ ̲P̲I̲P̲
The PIP contains one buffer for each printer in
the MEDE.
4.1.3.2.2.4 F̲i̲l̲e̲s̲ ̲u̲s̲e̲d̲ ̲i̲n̲ ̲P̲I̲P̲
The PIP references the following files:
- Preparation Data Base, PDB
- Inbound Message File, IMF
- Historical Data Base, HDB
It is invisible to the PIP which file it is operating
on. This is established by the MTCB-monitor, as
the MTCB monitor keeps track of the disk address;
but it is aware of the file formats.
4.1.3.2.2.5 P̲r̲i̲n̲t̲i̲n̲g̲ ̲o̲f̲ ̲N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
When the PIP requests the QACCESS to read an element
from a specific terminal print queue (4), the queue
entry of highest precedence which has waited the
longest is returned (4a). The MTCB pointed to
in the entry is examined after the MTCB-monitor
is called (5). If it describes a narrative message
which is not a Special Handling message the following
sequence is followed:
An entry into the Message Log Report is made
when the printout is started.
In the MTCB block of the message the disk-address
and the retrieval DTG of the message is read.
A header is formatted and then the message
is read from the disk into the buffer belonging
to the printer, divided into parts equal to
the size of the buffer.
The buffer is printed on the printer (6) (ROP).
When the operation is completed it is examined
whether the message printout has been completed
or not. If not, the above standing read-from-disk
and print-on-ROP is repeated.
Finally the acceptance time stored in the binary
header and the retrieval time is formatted
and printed.
Before each read from file it is tested (in
case of a HDB file is used) that the contents
still exist.
When the printout is completed, the next entry
in the queue is serviced, if any.
If the above-mentioned request to the MTCB-monitor
returns an identification saying that the file
does not exist, the entry is ignored.
4.1.3.2.2.6 C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲R̲e̲m̲a̲r̲k̲s̲
The MTCB pointed to from the queue entry identifies
a printout of Coordination Remarks. The MTCB is
a pseudo MTCB which points to the MTCB identifying
the message in coordination. The pseudo MTCB also
points to a PDB-file containing the ORIGINATOR'S
IDENTITY text and the ORIGINATORS REMARK text.
First the ORIGINATOR'S IDENTITY text is printed
then the message is printed and finally the ORIGINATOR'S
REMARKS text is printed.
4.1.3.2.2.7 R̲e̲m̲a̲r̲k̲s̲
The MTCB identified in the queue entry is a pseudo
MTCB with a reference to a PDB-file containing
the REMARKS text.
The PDB-file is printed without any formatting.
4.1.3.2.2.8 P̲r̲i̲n̲t̲o̲u̲t̲ ̲o̲f̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Prior to the printout of a Special Handling message,
the PIP determines that the printer is idle and
that the authentication, which it receives a notice
of through a system message (2) has been completed.
The printout is performed as described in section
4.1.3.2.2.5. When the printout is completed a
system answer is returned to the MES (2a) and all
used buffers are cleared (overwritten with space
characters).
If the printout of a Special Handling message has
not been commenced before 10 minutes after the
authentication was completed, or if the authentication
fails the message is enqueued to the SFS (7) in
the DT-queue (7a).
The PIP is notified about this through a System
message from the MES (3). An answer is returned
to the MES (3a).
4.1.3.2.2.9 P̲r̲i̲n̲t̲ ̲R̲e̲q̲u̲e̲s̲t̲ ̲f̲r̲o̲m̲ ̲a̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲
The PIP ensures that a request concerning printout
on a teleprinter is received in a System message
(3), prior to printout on a teleprinter.
When the printout is completed an answer is returned
(3a).
The printout is performed as described in 4.1.3.2.2.5.
4.1.3.2.2.10 L̲o̲g̲ ̲O̲n̲/̲O̲f̲f̲ ̲o̲f̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲s̲
When a terminal is logged on or off the PIP receives
a system message (8). The PIP uses the information
about the terminal number and that it has logged
on or off to keep track of the accesible printers.
A System answer is returned (8a).
4.1.3.2.2.11 M̲e̲s̲s̲a̲g̲e̲ ̲J̲o̲u̲r̲n̲a̲l̲
If the MTCB identifies a printout of the Message
Journal the file is read sequentially into the
buffer. The type of each entry is examined. If
it identifies a printable type it is printed.
4.1.3.2.2.12 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲L̲o̲g̲
If the MTCB identifies a Transaction Log request
the buffer is formatted in accordance with the
contents of the MTCB and is then printed.
4.1.3.2.2.13 M̲e̲s̲s̲a̲g̲e̲ ̲L̲o̲g̲ ̲R̲e̲p̲o̲r̲t̲s̲
The MTCB pointed to in the LP-queue may describe
a Message Log Report. If so, a Log Line is formatted
according to the contents of the MTCB and printed
on the printer.
EX:
LOG MSG.ID DTG MESSAGE RELEASE
4.1.3.3 D̲e̲s̲i̲g̲n̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
The MDS is designed to contain two processes (the
MDS and the PIP) executing under control of the
FIKS executive.
4.1.3.3.1 Q̲u̲e̲u̲e̲s̲
The Subsystem input queues is filled with entries
by the NSS when inbound messages require delivery.
The MES makes entries in these queues when messages
are released. These may be for inbound delivery
or outbound distribution or both.
The SFS makes entries in the input queues in case
of operator initiated re-distribution of messages.
When the message is processed, entries made be
made into the following queues:
- NSS input queue, when a message must be routed
outbound on the network.
- SRS input queue, when a request for storage
on the HDB is made.
- SFS input queue, when the message is garbeled
or in case of distribution error.
- PIP input queue, when at least one of the messages
ANO's references a configured terminal.
4.1.3.3.1.1 F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲M̲D̲S̲ ̲I̲n̲p̲u̲t̲ ̲Q̲u̲e̲u̲e̲
The format of the MDS input queues is described
in Figure 4.1.3.2-1 and serviced as described in
4.1.3.2.
4.1.3.3.1.2 F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲P̲I̲P̲ ̲I̲n̲p̲u̲t̲ ̲Q̲u̲e̲u̲e̲
The format of the PIP input queues is described
in Figure 4.1.3.2-4 and serviced as described in
4.1.3.2.2.1.
4.1.3.3.2 F̲i̲l̲e̲s̲
The following files may be used:
- Message read from HDB, PDB or IMF to get addressees
from the Address List.
- Message entered into HDB, if it is not a Special
Handling or a control message.
- Message is printed from the file it resides
on, eg. HDB or PDB/IMF.
- Coordination Remarks and Release Remarks are
printed from a PDB-file.
When the MDS reads the message text or the Address
List of the file, it requests the MTCB-monitor
to deliver the actual disk identification. The
MTCB-monitor opens the file for the MDS. The MTCB-monitor
synchronizes the usage/deletion of the files.
Hereby it becomes transparent whether the file
exists on PDB/IMF or HDB.
If the file is delivered from the HDB it shall
be tested whether the file still exists by call
of TEST ̲HDB. If it is deleted the printout is
finished and the next is started.
4.1.3.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.3.4-1 depicts the two groups of functions
supported by the subsystem.
The MDS process performs the distribution management
functions and the PIP process performs the printer
service functions.
Figure 4.1.3.4-1…01…Message Distribution Subsystem…01…Visual Table of Contents
4.1.3.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̲
4.1.3.5.1 T̲h̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲,̲ ̲M̲D̲S̲
The Distribution Management Process is divided
into two modules:
- The Delivery Queuer Module (DQM)
- The Printer Queuer Module (PQM)
The DQM is the main module serving the MDS input
queues, and if needed, requests service from other
subsystems. The PQM is a procedure called by the
DQM when a message must be delivered to terminal
queue (s).
The Distribution Management handles the following
types of messages:
a. A narrative message to be delivered to a MEDE
terminal(s) and/or to the NSS.
or
b. A narrative message the security classification
of which calls for Special Handling prior to
delivery to a MEDE terminal(s).
or
c. A control message to be delivered to the Supervisory
Functions Subsystem.
or
d. A narrative message to be re-distributed to
local MEDE terminals.
or
e. An erroneously orbiting message to be delivered
to the SFS.
The actual type of a message is determined by the
examination of the Message Transition Control Block,
MTCB.
4.1.3.5.1.1 C̲o̲n̲t̲e̲n̲t̲s̲ ̲o̲f̲ ̲t̲h̲e̲ ̲I̲n̲p̲u̲t̲ ̲Q̲u̲e̲u̲e̲
The input queue contains MTCB-indexes pointing
to a real MTCB or a pseudo MTCB.
The following information in the real MTCB is used:
- "Specat", identifying if the message needs
Special Handling.
- The type of the message.
- Off-set to the Address List.
- Routing mask.
- Identification whether the entry was enqueued
by the MES or the NSS, or whether the message
has an orbit error or not.
The following information in the pseudo MTCB is
used:
- Category: identifying either a request for
local delivery of a message or a nodal error.
- Subcategory: in case the category is a nodal
error, the subcategory identifies the message
as either narrative or control.
- Additional information depending on category
and subcategory.
4.1.3.5.1.2 D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
If "type" in the real MTCB or the category and
subcategory in the pseudo MTCB indicates that the
message is a control message it is enqueued to
the Supervisory Functions Subsystems input queue.
4.1.3.5.1.3 S̲t̲o̲r̲a̲g̲e̲ ̲o̲n̲ ̲t̲h̲e̲ ̲H̲D̲B̲
If the narrative message is not a Special Handling
message, the message is enqueud into the input
queue of the Storage and Retrieval, as a request
for storage on the Historical Data Base, the MTCB
is time-tagged.
4.1.3.5.1.4 O̲u̲t̲b̲o̲u̲n̲d̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲s̲
The last word in the real MTCB indicates whether
the message is intended for outbound distribution
or not.
If it is for outbound distribution a routing mask
is generated (containing one bit for each N/M in
the FIKS system) from the Address List.
The routing mask is inserted in the MTCB before
it is queued to the NSS.
If the Address List contains any NATO - ANO's the
message is also queued to the SIP. If no SIP is
available on the N/M, the message is sent to both
colocated N/M's.
4.1.3.5.1.5 I̲n̲b̲o̲u̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
The real MTCB identifies whether the message is
for inbound delivery or not. If it is for inbound
delivery the Printer Queuer Module, PQM, is called.
The PQM performs the following:
The file containing the message contains an Address
List, which is a list of ANO's/AIG's to which the
message shall be delivered.
This Address List is read and every ANO/AIG in
the Address List is examined. For those local
to the MEDE, the ANO is converted to terminal-id.
The conversion of ANO's takes place by call of
the RDF monitor procedures.
4.1.3.5.1.5.1 E̲n̲q̲u̲e̲u̲i̲n̲g̲ ̲o̲f̲ ̲N̲o̲n̲-̲S̲H̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
If the message is not a Special Handling message
it is enqueued to the terminal queue identified
by the terminal-id. Obtained as described above.
4.1.3.5.1.5.2 E̲n̲q̲u̲e̲u̲i̲n̲g̲ ̲o̲f̲ ̲S̲H̲-̲M̲e̲s̲s̲a̲g̲e̲s̲
If the message is a Special Handling message the
terminal operator's profile is checked up on the
existance of a "Special Handling password" (contained
in the Terminal Control Block, TCB). If the operator
has a "Special Handling password" and the terminal
is logged on in RX/TX mode, the message is enqueued
into the SH-queue of the terminal.
When an entry is made into a SH-queue of the terminal
the operator at a VDU will be notified by the ITM
of its existance in the upper screen which displays
the queue status information. If the terminal
is a teleprinter the queue status information will
be printed just before the "PROC" command is issued.
If a receiver of a Special Handling message has
no "Special Handling password" the message in enqueued
into the Supervisory Function Subsystems queue
together with an alarm.
4.1.3.5.2 P̲r̲i̲n̲t̲e̲r̲ ̲S̲e̲r̲v̲i̲c̲e̲
The functions supported by the Printer Service
is processed by the Printer Interface Process.
The purpose at the PIP process is to manage the
printing of narrative messages, coordination and
release remarks and message log reports.
4.1.3.5.2.1 B̲u̲f̲f̲e̲r̲ ̲i̲n̲ ̲P̲I̲P̲
To the printout is used a single buffer for each
printer. The ROP has an internal buffer so it
will look like a continuous data stream to an observer.
The teleprinter is idle while the contents of
the file is copied to the internal buffer.
4.1.3.5.2.2 S̲u̲p̲e̲r̲v̲i̲s̲i̲o̲n̲ ̲o̲f̲ ̲t̲h̲e̲ ̲U̲s̲a̲g̲e̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲e̲r̲s̲
The Printer Interface Process receives system messages
when changes to a ROP or a teleprinter occur (e.g.
log on/off).
Prior to printout of a Special Handling message
the PIP ensures that a system message from the
MES has arrived. This contains information concerning
the authentication of the terminal operator.
If the operator's access to the message is authorized
the following sequence of the printout is used.
If he is not authorized access to the message,
it is enqueued into the input queue of the Supervisory
Function Subsystem as a request for further service.
When the printout of the SH-message is completed,
a "system answer" is returned to the MES.
4.1.3.5.2.3 S̲e̲r̲v̲i̲c̲e̲ ̲o̲f̲ ̲t̲h̲e̲ ̲P̲I̲P̲ ̲I̲n̲p̲u̲t̲ ̲Q̲u̲e̲u̲e̲
The PIP input queue is serviced FIFO by precedence.
The queue contains a MTCB-identification which
is dequeued by calling the QACCESS.
The MTCB is examined to determine whether the MTCB
concerns a message or a message log report.
4.1.3.5.2.4 Printing of Narrative Messages on ROP's and T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲s̲
̲i̲n̲ ̲R̲X̲-̲M̲o̲d̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
An entry into the Message Log Report is issued
before the printout is started. If the queue element,
dequeued as described above, is not a Special Handling
message the following sequence is followed.
The MTCB-monitor is requested to deliver the disk-address
of the message. The first part of the message
is read into the buffer belonging to the printer.
The size is equal to the buffer size. The buffer
is then printed. When the print operation is completed
it is examined whether the printout of the message
is completed or not. If not, the above read-from-file
and print-on-ROP is completed.
Finally the Retrieval and Acceptance time is printed.
If the request to the MTCB-monitor mentioned above
returns an indication that the file does not exist,
the entry is ignored.
4.1.3.5.2.5 P̲r̲i̲n̲t̲i̲n̲g̲ ̲o̲f̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Special Handling messages are not printed until
a message is received from the MES indicating a
successful completion of the security interrogation
of the terminal.
Immediately prior to printing the message an answer
to the previous authorization message is returned
to the MES. If the message remains in the print
queue for 10 minutes after the authorization message
is received, the MES sends another message to the
PIP, notifying it of the time-out condition.
The overdue message is removed from the print queue
and entered into the DT queue of the Supervisory
Terminal and an alarm is issued.
4.1.3.5.2.6 P̲r̲i̲n̲t̲ ̲R̲e̲q̲u̲e̲s̲t̲ ̲f̲r̲o̲m̲ ̲a̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲ ̲i̲n̲ ̲R̲X̲T̲X̲-̲M̲o̲d̲e̲
Prior to dequeueing an entry in the input queue
it is examined if the printer is a teleprinter.
If so, the printer is not serviced before a System
message from the MES requesting the printing is
received.
The print sequence described in 4.1.3.5.2.4 is
then performed.
An answer is returned when the printing has been
completed.
4.1.3.5.2.7 P̲r̲i̲n̲t̲ ̲o̲f̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲R̲e̲m̲a̲r̲k̲s̲
The MTCB monitor is requested to deliver the disk
address of both the remarks file and the file of
the message in coordination.
The buffer is then formatted with the part of the
remarks file concerning the terminal description,
then the message text, and finally the remarks.
The print out is performed as described in 4.1.3.5.2.4.
4.1.3.5.2.8 P̲r̲i̲n̲t̲ ̲o̲f̲ ̲R̲e̲m̲a̲r̲k̲s̲
The release remarks and the remarks from the coordinator
to the originator is printed as follows:
The MTCB monitor is requested to deliver the disk
address of the PDB-file. The file is opened; the
text is read; buffer printed; file closed.
4.1.3.5.2.9 M̲e̲s̲s̲a̲g̲e̲ ̲L̲o̲g̲ ̲R̲e̲p̲o̲r̲t̲s̲
The MTCB pointed to in the LP-queue may describe
a Message Log Report.
If so, a Log Line is formatted according to the
contents of the MTCB and printed on the printer.
4.1.3.5.2.10 E̲n̲t̲r̲i̲e̲s̲ ̲i̲n̲t̲o̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲L̲o̲g̲ ̲R̲e̲p̲o̲r̲t̲
The PIP formats a Message Log Report in a MTCB
and enqueues it into the input queue of the PIP
for print-out.
