top - download
⟦8c485ee78⟧ Wang Wps File
Length: 83556 (0x14664)
Types: Wang Wps File
Notes: CPS/SDS/011
Names: »1019A «
Derivation
└─⟦9419d79aa⟧ Bits:30006037 8" Wang WCS floppy, CR 0061A
└─ ⟦this⟧ »1019A «
WangText
…00……00……00……00……00……19……02……00……00……19…
…18……0c……18……05……17……0a……17……0e……17……02……17……06……16……0c……16……02……16……06……15……09……15……0e……15……0f……15……00……15……05……14……0b……14……02……13……09……13……0d……13……01……13……07……12……0b……12……0e……12……02……12……06……11……08……11……0c……11……0d……11……02……11…
…11……05……11……06……10……0b……10……00……10… …0f……09……0f……0e……0f……05……0e……0b……0e……01……0e……06……0d……0c……86…1 …02… …02… …02…
…02…CPS/SDS/011
…02…NJ/810801…02……02…
MESSAGE DISTRIBUTION PACKAGE
DESIGN SPECIFICATION…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ......................................
6
1.1 PURPOSE AND SCOPE ........................
6
1.2 APPLICABLE DOCUMENTS AND PROJECT
REFERENCES ...............................
7
1.2.1 Applicable Documents .................
7
1.2.2 Reference Documents ..................
8
1.3 TERMS AND ABBREVIATIONS ..................
9
1.3.1 Terms ................................
9
1.3.2 Abbreviations ........................
11
2 SUMMARY OF REQUIREMENTS ......................
13
2.1 PACKAGE DESCRIPTION ......................
13
2.1.1 General Description ..................
13
2.1.2 External Interfaces ..................
13
2.1.3 Package Interfaces ...................
13
2.1.4 Chart Over Interfaces ................
14
2.2 PACKAGE FUNCTIONS ........................
16
2.2.1 Main Functions .......................
16
2.2.1.1 Distribution of Incoming Messages
16
2.2.1.2 Local Distribution of Outgoing
Messages .........................
17
2.2.1.3 Distribution of Messages for
Coordination .....................
18
2.2.1.4 Distribution of Comments .........
18
2.2.1.5 Messages/Comments Returned from
the MDCO .........................
18
2.2.1.6 Distribution of Retrieved Messages
18
2.2.1.7 Delivery Functions ...............
19
2.2.1.8 Quiet Hours Functions ............
19
2.2.2 Functional Responsibilities ..........
20
2.2.2.1 Initialization, Close Down, and
Restart ..........................
20
2.2.2.2 Check Pointing and Recovery ......
20
2.2.2.3 Error Detection and Error Handling
20
2.2.2.4 Integrity of Operation ...........
21
2.2.2.5 Data Collection ..................
21
2.2.2.6 Security .........................
21
2.3 CHARACTERISTICS ..........................
21
2.3.1 Timing ...............................
21
2.3.2 Throughput ...........................
23
2.3.4 Accuracy and Validity ................
23
3 ENVIRONMENTS .................................
24
3.1 EQUIPMENT ENVIRONMENT ....................
24
3.2 SOFTWARE ENVIRONENT ......................
24
3.2.1 System Software ......................
24
3.2.2 Development Support Software .........
24
3.3 INTERFACES ...............................
24
3.3.1 External Interfaces ..................
24
3.3.2 Package Interfaces ...................
24
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES ...
27
4 PACKAGE DESIGN ...............................
28
4.1 PACKAGE OVERVIEW ..........................
28
4.1.1 Functional Specification .............
28
4.1.2 Software Structure ...................
30
4.1.2.1 Message Distribution Process .....
30
4.1.2.2 Message Distribution Queue .......
30
4.1.2.3 Message Distribution Sub-Package .
30
4.1.3 Data Flow and Control Logic ..........
32
4.1.4 Common Data Elements .................
34
4.1.5 External Data Elements ...............
34
4.1.5.1 Shared Data Elements with THP ....
35
4.1.5.2 Shared Data Elements with TEP ....
36
4.1.6 Interfaces ...........................
43
4.1.6.1 THP Interfaces ...................
45
4.1.6.2 TEP Interfaces ...................
45
4.1.6.3 SAR Interfaces ...................
48
4.1.6.4 STP Interfaces ...................
49
4.1.6.5 TMP Interfaces ...................
49
4.2.1 Sub-Package Specification ............
51
4.2.1.1 Functional Specification .........
52
4.2.1.1.1 Incoming Messages ............
52
4.2.1.1.2 Outgoing Messages ............
59
4.2.1.1.3 Comments .....................
59
4.2.1.1.4 Message for Coordination .....
60
4.2.1.1.5 Re-Distribution of Incoming
and Outgoing Messages ........
61
4.2.1.1.6 Messages/Comments Re-Entered
after MDCO Assistance ........
61
4.2.1.1.7 MDP Functional Break-Down ....
70
4.2.1.2 Software Structure ...............
76
4.2.1.2.1 Incoming Message Distribution
Structure ....................
76
4.2.1.2.2 Message Distribution Procedure
Structure ....................
77
4.2.1.2.3 Alternative Distribution
Procedure Structure ..........
79
4.2.1.2.4 Finish Distribution Procedure
Structure ....................
80
4.2.1.3 Data Flow and Control Logic ......
86
4.2.1.3.1 Hipo Charts ..................
87
4.2.1.3.2 Flow Grams ...................
102
4.2.1.4 Sub-Package Data .................
108
4.2.1.5 Sub-Package Interfaces ...........
107
4.3 MEMORY LAY-OUT ...........................
107
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
The Package Specification for Message Distribution
CPS/SDS/011 is written to fulfil the following objectives:
a) To provide detailed definition of the package functions
and software architecture.
b) To provide user operational and development personnel
details of the ongoing analysis
c) To define in detail the interfaces with other packages
and to describe their facilities.
This SDS defines the transactions which are applicable
to the local distribution of messages inside a CAMPS
site. The local distribution includes the following
objects:
- Incoming Messages
- Outgoing Messages
- Messages for coordination
- Comments
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲ ̲A̲N̲D̲ ̲P̲R̲O̲J̲E̲C̲T̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
The following documents are applicable to the Message
Distribution Package Design Specification.
- Contract Document
Contract No. CE 80-9009-INF
- CPS/210/SYS/0001
CAMPS System Requirements
- CPS/230/ICD/0001
User Procedures and associated Formats
- CPS/230/ICD/0002
Supervisor Commands and Procedures
- CPS/SDS/001
CAMPS System Design Specification
- CPS/SDS/002
CAMPS System Funtions
- CPS/SDS/003
Message Management
- CPS/SDS/004
System Status and Control
- CPS/SDS/005
Table Management
- CPS/SDS/007
Storage and Retrieval
- CPS/SDS/008
Statistics
- CPS/SDS/010
Traffic Handling
- CPS/SDS/012
Terminal Package
- CPS/DBD/001
Data Base Design Document
- CPS/ICD/009
CAMPS Software Interface Control Document
1.2.2 R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
The following documents are listed for reference purposes
only. The listing does not constitute the contents
of the documents as System Requirements, but is intended
to serve the Contractor in providing supplementary
information in cases of interpretation of the requirements
specifically stated in System Requirements Specification:
ACS, Jul 74
ACP117, Sept, 1977, ACP 117 Supp. 16. Dec. 79
ACP121, Supp. 17. Jan 1970, 121E Jul 1970
ACP100, NATO SUPP, 1E May 1978
ACP127 NATO Supp. 3, May 1973, 127 (E) OCT 74
NASIS-APP-3 JAN 1978
ADatP-3 JAN 1975
1.3.1 T̲e̲r̲m̲s̲
Close-down Action taken to bring processing
within the system or a part there
of to a stop - can be either an
ordered sequence of steps or an
abrupt termination.
Device Designator Identification of a stand-alone
device.
Device Profile To each device a device profile
is associated.
Duty Officer Person located at the supervisor
specified terminal position during
Quiet Hours
Initialization The definition in the CPS/SDS/001
and subsequent documents are described
as follows: Brings the system from
cold or dead start into operational
use. No recovery actions are included.
The definitions replace the one
used in the CPS/210/SYS/0001: Brings
the system from cold start into
operational use.
Message Distribu- Denotes the total group of
tion Control Func- commands/procedures which may be
tion performed from a VDU with Message
Distribution Control capability.
Message View A subset of fields within a message.
Plain Language The PLA representing a
Address Headquarters.
Preparation Denotes the total group of
Functions commands/procedures which may be
performed from a VDU with Preparation
Capability.
Procedure Special part of a program. It must
be called with a "procedure call"
instruction which automatically
saves the return point.
Process Execution of a specific program
operating on a specific set of data.
The active components of the system
to which security and process control
as well as resource management is
applied.
Queue Process communication tool within
CSF.
Queue Element The elements which can be in a queue.
Queue Element The same as queue element. Used
Reference when emphasizing the function of
the queue element as the basic reference
to objects.
Queue Monitor The part of CSF supplying Queue
facilities.
Quiet Hours A supervisor specified parameter
for alternative distribution to
a Duty Officer.
Recovery Reestablishes continuity in memory
and file contents.
Staff Cell The SCD is the smallest addressable
Designator unit in one CAMPS site.
Stand alone device Medium speed teleprinter, low speed
teleprinter (PTP, PTR, ROP) OCR,
PTR, and PTP
Start up Includes all aspects of initialization,
recovery and restart.
Sub queue Part of a Main Queue.
Supervisor Person located at supervisor terminals
in CAMPS central equipment room
System Parameter A simple variable, holding part
of the system state, and controlled
by TMP.
Terminal VDU, Medium Speed Teleprinter, Low
Speed Teleprinter, Line Printer,
PTP/PTR and OCR.
Terminal Device VDU, Medium Speed Teleprinter and
Low Speed Teleprinter.
Terminal Designa- A code identifying the terminal
po-
tor sition.
Terminal Position VDU and associated (shared) ROP.
User a) Person with responsibility for
input and output of messages.
b) Person located at the user terminals
in the staff cells.
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
CAMPS Computer Aided Message Processing
System
CIF CAMPS Information File
COPSY CAMPS Operating System
CPS CAMPS
CSF CAMPS System Functions
DTG Data Time Group
HQ Headquarters
ISQ Incoming Storage Queue
MCQ MDCO Queue
MDCO Message Distribution Control
MDP Message Distribution Package
PLA# Plain Language Address Reference
Number
QEL Queue Element
SAR Storage and Retrieval
SCD Staff Cell Designator
SDL Standard Distribution List
SFM Storage and File Management Package
SIC Subject Indicator Code
SSC System Status and Control
SSN Station Serial Number
STP Statistics Package
TD Terminal Designator
TEP Terminal Package
THP Traffic Handling Package
TMP Table Management Package
TOC Time of Occurrence
VDU Visual Display Unit
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
2.1.1 G̲e̲n̲e̲r̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The Message Distribution Package (MDP) performs internal
distribution of incoming and outgoing messages, comments,
messages for coordination and specified distribution
from the Message Distribution Control (MDCO) and the
supervisor.
Internal distribution means selection of queues for
terminals, based on either headquarters and Subject
Indicator Codes (SICs) or on specification of staff-cell
designators (SCD).
The Message Distribution package receives messages
from the Traffic Handling Package (THP) and from the
Terminal Package (refer figure 2.1.4-1).
2.1.2 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
N.A.
2.1.3 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Message Distribution Package interfaces with the
following other packages
CAMPS System Functions (CSF)
Storage and File Management Package(SFM)
System Status and Control (SSC)
Table Management Package (TMP)
Storage and Retrieval (SAR)
Statistics Package (STP)
Traffic Handling Package (THP)
Terminal Package (TEP)
2.1.4 C̲h̲a̲r̲t̲ ̲O̲v̲e̲r̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Figure 2.1.4-1 shows the interfaces to MDP.
FIGURE 2.1.4-1…01…MDP INTERFACE
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The following main functions are identified.
- Distribution of incoming messages
- Local distribution of outgoing messages
- Distribution of messages for coordination
- Distribution of comments
- Distribution of messages/comments returned from
the MDCO
- Distribution of retrieved messages
- Delivery functions
- Quiet Hours functions
2.2.1.1 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Incoming plaindress messages are queued by the Traffic
Handling Package to the Message Distribution Package
for internal distribution. The distribution determination
is based on the following information.
- The headquarters to which distribution shall be
performed at this site
- Up to three subject indicator codes (SICs)
- Exercise indicator
Each headquarters, SIC combination will point out a
standard distribution list. From these lists MDP will
generate a nominal distribution list.
After generation of the nominal distribution list,
the incoming messages are either distributed to the
staff cells in the list or queued for support by the
MDCO.
Incoming messages are deferred to the MDCO for the
following reasons:
- Missing or garbled SICs
- Internal Handling Instructions
- Special Handling Instructions of category exclusive
or crypto security
- More than one Special Handling Instruction
- Supervisor parameters for distribution:
1) All incoming messages
2) All incoming messages of specified classification
3) All incoming messages except those of specified
classification
A notification explaining the reason for MDCO assistance
and the Distribution List (SCD List) as complete as
possible based on the available information is passed
on to the MDCO.
Crypto security messages normally contain a GR in FL10.
If a GR is detected by THP the message will by THP
be directed to the dedicated PTP.
2.2.1.2 L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
After Release and Station Serial Number assignment
outgoing messages are queued by Terminal Package to
the MDP for local distribution. The distribution is
specified by SCDs. The MDP distributes to the specified
staff-cells and in case of any problems in the distribution
to the MDCO.
2.2.1.3 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲o̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲
Messages in preparation may be sent for coordination.
The Terminal Package queues the message to MDP together
with a coordination SCD List. The MDP distributes to
the Coordination staff-cells.
A notification is generated and returned to the drafter
by this package. It will contain the SCDs, if any to
which distribution could not be performed. No MDCO
assistance will be performed for messages sent for
coordination.
2.2.1.4 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲m̲m̲e̲n̲t̲s̲
Comments are queued by the Terminal Package to MDP
for distribution. The distribution will be based on
an SCD list which will be queued to MDP together with
the comments. If the distribution cannot be performed
to all the SCDs in the list, the comments will be sent
to the MDCO.
2.2.1.5 M̲e̲s̲s̲a̲g̲e̲s̲/̲C̲o̲m̲m̲e̲n̲t̲s̲ ̲R̲e̲t̲u̲r̲n̲e̲d̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲M̲D̲C̲O̲
Messages/comments which have been deferred to the MDCO
are returned by Terminal Package to the MDP together
with an updated or alternative SCD list to which distribution
shall be performed. The MDCO will be notified whether
the distribution could be performed or not.
2.2.1.6 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲e̲t̲r̲i̲e̲v̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The supervisor and the MDCO can retrieve incoming and
outgoing messages and specify re-distribution to the
SCDs contained in the SCD list. The Terminal Package
will queue the message to MDP for re-distribution.
The MDP will perform distribution to the staff cells
in the SCD list. If the distribution cannot be performed
to all the SCDs in the list, the messages will be sent
to the MDCO.
2.2.1.7 D̲e̲l̲i̲v̲e̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The MDP distributes the message/comment to queues.
Each of these queues will lead to a terminal. The queues
to which distribution will be performed is identified
by means of the SCD list.
If a message is sent to a queue leading to a terminal
not having security classification or allowed special
handling categories to receive it, the queue monitor
will reject the QEL. The MDP will then queue the message
to the MDCO for selection of alternative SCDs.
If a message of precedence flash is sent to a queue
where the associated terminal is signed off, the QEL
will be rejected by the Queue monitor. The MDP will
then forward the message to the MDCO for selection
of alternative SCDs.
If a message of precedence immediate is sent to a queue
where the associated terminal is signed off, then MDP
will send a copy of the message to the MDCO.
Messages with a special handling instruction atomal
will be distributed as normal plaindress messages,
except for print, which will always be to a supervisor
specified printer.
2.2.1.8 Q̲u̲i̲e̲t̲ ̲H̲o̲u̲r̲s̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The supervisor can specify that Flash and Immediate
messages and comments shall be automatically distributed
to a Duty Officer terminal position during Quiet Hours.
For immediate messages a copy is also queued in the
recipient's terminal queues. Messages for coordination
are not queued, but the originator is notified that
the message was not delivered.
2.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
2.2.2.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲,̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲,̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
2.2.2.1.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
The MDP will initialize the MDP memory structure by
calling CSF initialization procedures.
2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
The MDP will not perform any close down procedures.
If no QEL is sent to the Message Distribution Queue
(MDQ). MPD will automatically stop processing.
2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
During restart MDP will perform initialization as described
in section 2.2.2.1.1.
2.2.2.2 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
MDP makes standby checkpoints after distribution of
all objects.
2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
If an error is detected by MDP, the message processing
will be stopped and the error will be reported to SS&C.
2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
The input from other packages will be validated to
ensure correct processing and data. If any errors are
detected, SSC will be informed.
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
The following data collection will be performed by
MDP.
- collection of statistics
- collection of retrieval keys
The collection of statistics will be performed by MDP
for incoming and outgoing messages, whereas the collection
of retrieval keys will be performed for incoming messages
only.
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
All security check and access rights will be performed
by the Queue monitor inside CSF.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲i̲m̲i̲n̲g̲
2.3.1.1 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲ ̲T̲i̲m̲e̲
The throughput time is composed by the following elements:
- CPU access time
- Monitor Call
The throughput time for the distribution cases is as
follows:
Incoming Message:
- CPU access time: 2 msec.
- Monitor call to CSF: Read Field, 1, 2, and
3
- Monitor call to TMP: Read SDLs
- Monitor call to TMP: Read SCD information
list
- Monitor call to CSF: Write SCD list
Outgoing Message, comment, and message for coordination:
- CPU access time: 1,5 msec
- Monitor call to CSF: Read Field, 1, 2, and
3
- Monitor call to TMP: Read SCD information
list
- Monitor call to CSF: Write Queue list
2.3.1.2 R̲e̲s̲p̲o̲n̲s̲e̲ ̲T̲i̲m̲e̲
Response time for MDP is only applicable for messages
for coordination and messages returned after MDCO assistance.
The drafter or the MDCO will after distribution completed
receive a response from MDP.
Response time:
- CPU access time: 1,5 msec
- Monitor call to CSF: Read Field, 1, 2, and
3
- Monitor call to TMP: Read SCD information
list
- Monitor call to CSF: Write Queue list
2.3.1.3 P̲r̲i̲o̲r̲i̲t̲i̲e̲s̲ ̲I̲m̲p̲o̲s̲e̲d̲ ̲b̲y̲ ̲I̲n̲p̲u̲t̲s̲
No priorities can be imposed by inputs. The message
distribution queue is a FiFo queue without any precedence
sub-queues. The distribution cases will therefore be
performed in the sequence of arrival to MDP.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The MDP shall support the following throughput (in
busy minute, busy hour, 24 hour period)
- 30, 530, 3000 incoming messages
- 6, 30 outgoing messages
- 6, 30 messages for coordination
- 12, 60 comments
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The control logic in MDP is built up by means of a
control word. The control modules can in this word
identify the software modules which shall be called
to perform the requested distribution. Each distribution
case has an associated control word. This means the
processing for each of the distribution cases can be
easily changed, and new modules can be incorporated
into the procedure.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲ ̲a̲n̲d̲ ̲V̲a̲l̲i̲d̲i̲t̲y̲
The MDP has no external interfaces, therefore, no validation
will be performed. The input data from other packages
are expected to be correct, but the input codes will
be validated to ensure correct processing.
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
The equipment environment of this package is the CR80D
Computer.
3.2 S̲O̲F̲T̲W̲A̲R̲E̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The MDP accesses the following components: CSF, SFM,
IOC, and SSC.
3.2.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
Ref CPS/SDS/001 section 5.18 Support Software Package
3.3 I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
N.A.
3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The MDP will have interfaces to the following packages:
- Traffic Handling Package (THP)
- Terminal Package (TEP)
- Storage and Retrieval (SAR)
- Statistics Package (STP)
- Table Management Package (TMP)
- System Status and Control (SSC)
3.3.2.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Traffic Handling Package queues incoming messages to
the MDP. Together with the message the following information
is queued:
- Message classification
- Special Handling instructions
- Action and info precedence
- Internal Handling instruction
- Headquarters indication
- SIC List
- Exercise indicator
- CIF ref#
- Release DTG
- Message length in lines
- Object identification
3.3.2.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲a̲c̲k̲a̲g̲e̲
The MDP receives the following objects from TEP.
- Messages sent for coordination
- Outgoing messages for local distribution
- Comments
- Messages returned to MDP after MDCO assistance
The objects are queued to MDP together with the following
information.
- Classification
- Special Handling instructions
- Precedence level
- Message length
- SCD list
- Object identification
3.3.2.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
MDP will create retrieval keys to SAR when distribution
is performed for an incoming message.
3.3.2.4 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲P̲a̲c̲k̲a̲g̲e̲
MDP will specify statistics information for incoming
and outgoing messages. The statistics will contain
information about the distribution.
3.3.2.5 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲P̲a̲c̲k̲a̲g̲e̲
The MDP will access TMP for the following system parameters
and tables.
- Supervisor parameters for MDCO assistance
- Quiet Hours parameter and Duty Officer Queue ID
- Queue ID for Atomal printer
- SIC table
- SCD table
3.3.2.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲y̲s̲t̲e̲m̲ ̲S̲t̲a̲t̲u̲s̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
The MDP is initialized by the SSC system.
Restart and Close down are also performed by the SSC
system.
Irrecoverable errors are returned to the SSC system.
3.4 F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲E̲D̲ ̲B̲Y̲ ̲O̲T̲H̲E̲R̲ ̲P̲A̲C̲K̲A̲G̲E̲S̲
MDP will call CSF for the following reasons:
- Checkpointing
- Control of access rights to a terminal
- Statistics correction
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
4.1.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 distribution cases, which will be performed by
MDP, will be identified in this section.
The following cases are identified:
- Incoming Messages received from THP
- Outgoing Messages received from TEP
- Comments received from TEP
- Messages for coordination received from TEP
- Re-distribution of Messages received from TEP
- Messages/comments re-entered after MDCO assistance
received from TEP.
This package will only contain one sub-package, therefore,
all further functional specification will be described
in section 4.2.1.1. The top level functional break
down is shown in figure 4.1.1-1.
FIGURE 4.1.1-1…01…MESSAGE DISTRIBUTION PACKAGE TOP LEVEL FUNCTIONAL BREAK-DOWN
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
4.1.2.1 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲s̲s̲
The message distribution procedure is performed in
a single process. The process receives messages/comments
from the Message Distribution Queue, and distributes
them to terminal queues. The distribution may possibly
be assisted by the MDCO.
For performance reasons, the process can be structured
into two similar co-routines. It can then perform distribution
on two messages in parallel.
4.1.2.2 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲Q̲u̲e̲u̲e̲
The Message Distribution Queue has two sub-queues.
One for normal messages/comments processing and one
for messages/comments returned from MDCO. The latter
has the highest priority. The Queue Profile for both
sub-queues will be the highest possible.
4.1.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲
Only one sub-package will be defined for MDP. This
sub-package will contain four control modules. The
modules are shown in the top level software structure
fig. 4.1.2.1-1. All further software structure is described
in section 4.2.1.2.
FIGURE 4.1.2-1…01…MDP SOFTWARE STRUCTURE
4.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The major components in the Data flow of MDP are shown
in the Overview HIPO diagram no. 1.
Because the MDP contains only one sub-package all further
Data Flow and control logic will be described in section
4.2.1.3.
DIAGRAM 1 OVERVIEW HIPO CHART MESSAGE DISTRIBUTION PACKAGE
4.1.4 C̲o̲m̲m̲o̲n̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
Not applicable for this package, because it contains
only one sub-package.
4.1.5 E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
This package will have shared data elements with the
following other packages:
- Traffic handling package
- Terminal package
The MDP will identify the distribution objects by the
QEL attributes. The information field associated to
these attributes will have the following elaboration
for QELs sent to MDQ.
word one byte one 01: returned after incoming
message distribution
assistance
02: returned after alternative
message distribution
assistance
03: sent for redistribution
00: else
word two byte three Queue ID for Drafter
if
and four distribution case is
message for coordination,
or queue ID for MDCO
answer queue if distribution
case is "returned messages
after MDCO assistance".
word three byte five Reference to SCD list
in
and six message view except
for distribution case
"Incoming Message".
4.1.5.1 S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲w̲i̲t̲h̲ ̲T̲H̲P̲
The following information is available for MDP, when
an incoming message is sent from THP to MDP.
- HQ mask
- SICs
- Exercise indicator
- Message classification
- Special handling instructions
- Internal handling instruction
- Precedence level
- Message length
- Item ref#
- Release DTG
The information can be found in the following way.
H̲Q̲ ̲M̲a̲s̲k̲
The HQ mask is a 1 word mask. It will be contained
in the QEL when the message is sent from THP to MDQ.
S̲I̲C̲s̲
The SICs will be contained in the text field in message
view. A pointer to the SICs inside this field is placed
in the QEL when the message is sent from THP to MDQ.
C̲I̲F̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
The following information is available in the CIF information
field.
- CIF ref. ID
- Release DTG
- Exercise indicator
- Message classification
- Special handling instructions
- Internal handling instruction
- Precedence level
M̲e̲s̲s̲a̲g̲e̲ ̲L̲e̲n̲g̲t̲h̲
The message length in number of lines is created from
the field lengths, which are contained in the view
descriptor.
4.1.5.2 S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲w̲i̲t̲h̲ ̲T̲E̲P̲
This section is divided into two sub-sections. One
sub-section to describe Data Elements sent from TEP
to MDP, and one sub-section to describe the opposite
traffic.
4.1.5.2.1 D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲f̲r̲o̲m̲ ̲T̲E̲P̲ ̲t̲o̲ ̲M̲D̲P̲
The following objects are sent from TEP to MDP
- Message sent for coordination
- Outgoing message sent for local distribution
- Comments
- Message returned to MDP after message distribution
assistance
- Retrieved message sent for re-distribution
Together with the objects, an object identification
code is sent.
For each of the objects, information can be found in
the following way:
4.1.5.2.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲n̲t̲ ̲f̲o̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲
The head 2 field in the message view will in a record
contain the SCDs to which coordination shall be performed.
Besides this, the MCB will contain the precedence level
for the message.
The record will have the following elaboration:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 bytes 30 bytes
The first integer in the record will contain the numbers
of SCDs in the record.
The maximum length of the record can be: 32 bytes.
4.1.5.2.1.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲f̲o̲r̲ ̲L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The following information is available for MDP, when
an outgoing message is sent from TEP to MDP
- Message Classification
- Special handling instructions
- Precedence level
- Message length
- SCDs to which distribution shall be performed
The information can be found in the following way.
S̲C̲D̲s̲
The head 2 field in message view will in a record contain
the SCDs to which distribution shall be performed.
The record will have the following elaboration.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 bytes 30 bytes
The first integer in the record will contain the number
of SCDs in the record.
The maximum length of the record can be: 32 bytes.
C̲I̲F̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
- Message classification
- Special handling instructions
- Precedence level
M̲e̲s̲s̲a̲g̲e̲ ̲L̲e̲n̲g̲t̲h̲
The message length is created from the field lengths,
which are contained in the view descriptor.
4.1.5.2.1.3 C̲o̲m̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The head 2 field in the message view will in a record
contain the SCDs to which the comment shall be distributed.
Besides this, the MCB will contain the precedence level
for the comment.
The record will have the following elaboration:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 bytes 30 bytes
The first integer in the record will contain the number
of SCDs in the record.
The maximum length of the record can be: 32 bytes.
4.1.5.2.1.4 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲t̲u̲r̲n̲e̲d̲ ̲t̲o̲ ̲M̲D̲P̲ ̲a̲f̲t̲e̲r̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
The message returned to MDP is divided into two groups:
- Message returned after Incoming Message distribution
assistance
- Message returned after alternative message distribution
assistance
When a message is returned to MDP after incoming message
distribution assistance, an SCD list will be contained
in a separate distribution field. This field is identical
to the distribution field which is sent to the MDCO
during incoming message distribution assistance as
described in section 4.1.5.2.2.4.
When a message is returned to MDP after alternative
message distribution assistance, the MDCO will have
created a new message view. This view will in a temporary
field contain an alternative SCD list. The field name
is called Queue list because it is changed to a queue
list in MDP. This alternative SCD list will contain
a maximum of ten SCDs.
The record will have the following elaboration:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 bytes 30 bytes
The first integer in the record will contain the number
of SCDs in the record.
The maximum length of the record can be: 32 bytes.
4.1.5.2.1.5 R̲e̲t̲r̲i̲e̲v̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲n̲t̲ ̲f̲o̲r̲ ̲R̲e̲-̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
Incoming and Outgoing messages retrieved by the MDCO
or supervisor will contain the same information as
described in section 4.1.5.1 for incoming messages
and in section 4.1.5.2.1.2 for outgoing messages.
4.1.5.2.2 D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲f̲r̲o̲m̲ ̲M̲D̲P̲ ̲t̲o̲ ̲T̲E̲P̲
This section is divided into four sub-sections:
- Data elements from MDP when distribution is performed
to terminals
- Data elements from MDP to drafter
- Data elements from MDP to Duty Officer
- Data elements from MDP to MDCO
4.1.5.2.2.1 D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲w̲h̲e̲n̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲i̲s̲ ̲P̲e̲r̲f̲o̲r̲m̲e̲d̲ ̲t̲o̲
̲T̲e̲r̲m̲i̲n̲a̲l̲s̲
During the distribution procedure a Queue list will
be created. This queue list will be contained in a
separate temporary field. Each line in the queue list
will be associated to a QEL and the line will be referenced
in this QEL. The line will among other things contain
the SCDs to which distribution shall be performed at
that terminal, and the number of copies for each SCD.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
TD/DD QUEUE ID SCDs COPY NUMBERS DELIVERY
CODE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
3 bytes 2 bytes 15 bytes 5 bytes 2 bytes
Each line will have a total length of: 27 bytes
4.1.5.2.2.2 D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲t̲o̲ ̲D̲r̲a̲f̲t̲e̲r̲
When a message is sent for coordination a QEL will,
after finished distribution, be sent to the drafter.
This record will contain the SCDs to which distribution
could not be performed.
The record will have the following elaboration:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 bytes 30 bytes
The first integer in the record will contain the number
of SCDs in the record.
The maximum length of the record can be: 32 bytes.
4.1.5.2.2.3 D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲t̲o̲ ̲D̲u̲t̲y̲ ̲O̲f̲f̲i̲c̲e̲r̲
When a message cannot be distributed during Quiet Hours
because the terminals are signed off, a QEL will after
finished distribution be sent to the Duty Officers
queue. This QEL will contain a reference to a record
in the Queue List. This record will contain the SCDs
to which distribution could not be performed.
The record will have the following elaboration:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 bytes 864 bytes
The first integer in the record will contain the number
of SCDs in the record.
The maximum length of the record can be:
Number of SCDs + number of PLAs x number of SICs x
number of SCDs x 3 bytes = 2 + 8 x 3 x 12 x 3 = 8̲6̲6̲
̲b̲y̲t̲e̲s̲
4.1.5.2.2.4 D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲ ̲t̲o̲ ̲M̲D̲C̲O̲
The messages sent to the MDCO are separated in two
groups.
- Messages sent for incoming distribution assistance
- Messages sent for alternative distribution assistance
When a message is sent for incoming distribution assistance,
the SCD list which shall be displayed will be contained
in a separate distribution field.
When a message is sent to alternative distribution
assistance, the queue list which shall be displayed,
will be contained in a separate temporary queue list
field. Each line in the queue list will contain the
following information:
- Terminal/Device Designator
- Queue ID
- SCDs to which distribution shall be performed at
this terminal
- Number of copies for each SCD
- Delivery code
The delivery code will be one of the following:
1) Delivery performed.
2) Classification too high.
3) Special handling instruction not included in profile.
4) CAMPS function not included in profile.
5) The SCD is not associated to a TD or DD.
6) Terminal signed off. (Immediate).
7) Terminal signed off. (Flash)
8) Print Atomal Message.
Each Queue Line will have the following elaboration.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
TD/DD QUEUE ID SCDs COPY NUMBERS DELIVERY
COEE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
3 bytes 2 bytes 15 bytes 5 bytes 2 bytes
Each line will have a total length of 27 bytes.
This means that if a message shall be distributed to
all terminals on one site, the queue list will get
a total length of:
4 bytes + number of terminals 72 x 27 bytes = 1948
bytes
The first integer in the queue list will contain the
number of queue lines in the queue list.
The second integer in the queue list will contain the
number of queue lines with action precedence.
4.1.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The MDP interfaces with the following other packages.
- Traffic Handling Package
- Terminal Package
- Storage and Retrieval Package
- Statistics Package
- Table Management Package
THP, TEP, and SAR interfaces with MDP by queues, whereas
MDP interfaces with STP and TMP by Monitor call. The
general interface communication mechanisms are shown
in figure 4.1.6-1.
Each number of the figure reference to a sub-section
in this section.
The MDP queue is a FIFO queue without any precedence
sub-queues.
FIGURE 4.1.6-1
4.1.6.1 T̲H̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
4.1.6.1.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲T̲H̲P̲,̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲
Incoming plaindress messages, received from the external
communication channels, will be sent from the Analysis
sub-package inside THP to MDP for distribution. The
incoming plaindress message is in format E1 when received
by MDP, except that the SCD list is not created from
the HQ/SIC/exercise information.
4.1.6.1.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲T̲H̲P̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲
Plaindress messages prepared at this CAMPS site and
which shall be distributed at the same site by HQ/SIC/exercise
information will be sent to MDP from the THP conversion
sub-package. The message format will be identical to
the message coming from the Analysis sub-package which
is described in section 4.1.6.1.1.
4.1.6.2 T̲E̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
4.1.6.2.1 O̲b̲j̲e̲c̲t̲s̲ ̲S̲e̲n̲t̲ ̲f̲o̲r̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲f̲r̲o̲m̲ ̲U̲s̲e̲r̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲s̲
The following objects will be sent for distribution
from a user position.
- Outgoing plaindress message for local distribution
- Message sent for coordination
- Comment
The outgoing plaindress message will be in Format E2
and will contain information as described in section
4.1.5.2.1.2. No response will be returned to the terminal.
The message sent for coordination will be in format
B, and will contain information as described in section
4.1.5.2.1.1. A distribution response will be returned
to the drafters, answer queue as described in section
4.1.6.2.2.
The comment will be in format G2 and will contain information
as described in section 4.1.5.2.1.3. No response will
be returned to the terminal.
4.1.6.2.2 C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲
After MDP has finished the distribution of a message
for coordination, the drafter of the message will get
a QEL in the answer queue associated to the drafters
terminal position. The information available to the
terminal position is described in section 4.1.5.2.2.2.
4.1.6.2.3 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲t̲o̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲s̲
During normal distribution, a QEL will be sent to each
terminal queue in the queue list. The QEL will be sent
to the Receive queue and will be queued by precedence.
The information available for the terminal is described
in section 4.1.5.2.2.1.
4.1.6.2.4 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲l̲a̲s̲h̲ ̲M̲e̲s̲s̲a̲g̲e̲
If the distribution object is of precedence flash,
an extra QEL will be queued to each terminal in the
queue list. The QEL will be sent to the terminal command
queue to inform the terminal process about the arrived
flash message.
4.1.6.2.5 A̲l̲t̲e̲r̲n̲a̲t̲i̲v̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲D̲u̲r̲i̲n̲g̲ ̲Q̲u̲i̲e̲t̲ ̲H̲o̲u̲r̲s̲
If a message of precedence flash or immediate is sent
or tried to be sent to a terminal which is signed-off,
a QEL will be queued to a supervisor specified Quiet
Hours position. This QEL will reference information
as described in section 4.1.5.2.2.3.
4.1.6.2.6 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲l̲a̲s̲h̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲t̲o̲ ̲D̲u̲t̲y̲ ̲O̲f̲f̲i̲c̲e̲r̲
The same procedure as described in section 4.1.6.2.4
will be performed when a message of precedence flash
is sent to the Duty Officer.
4.1.6.2.7 M̲D̲C̲O̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
If a Message/Comment needs distribution assistance,
it will be sent to the common MDCO Receive queue. It
will be queued by precedence. The QEL sent to the Receive
queue will reference information as described in section
4.1.5.2.2.4.
4.1.6.2.8 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲l̲a̲s̲h̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲t̲o̲ ̲C̲o̲m̲m̲o̲n̲ ̲M̲D̲C̲O̲ ̲Q̲u̲e̲u̲e̲
The same procedure as described in section 4.1.6.2.4
will be performed, when a message of precedence flash
is sent to the common MDCO Receive queue.
4.1.6.2.9 M̲D̲C̲O̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲
If a message has been sent for MDCO assistance during
the distribution, a QEL will be sent to that MDCO position
which has performed the assistance. The QEL will be
sent to the MDCO posistion's answer queue and it will
in the information field contain a finished distribution
code.
If MDCO assistance is needed a second time, a QEL will
reference information as described in section 4.1.5.2.2.4.
The QEL will be sent to the Answer queue.
4.1.6.2.10 M̲e̲s̲s̲a̲g̲e̲/̲C̲o̲m̲m̲e̲n̲t̲ ̲R̲e̲t̲u̲r̲n̲e̲d̲ ̲a̲f̲t̲e̲r̲ ̲M̲D̲C̲O̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
When a message is returned after MDCO assistance, the
QEL which references it, will in its information field
contain a code indicating whether the message was sent
to the MDCO for incoming distribution assistance or
alternative distribution assistance. The information
contained in the message view when returned to MDP
is described in section 4.1.5.2.1.4.
4.1.6.2.11 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲e̲d̲ ̲f̲o̲r̲ ̲R̲e̲-̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
When a message is sent to MDP for Re-distribution by
the MDCO or Supervisor, the QEL which returns it, will
in its information field contain a code which indicates
that the message is sent for Re-distribution. The information
contained in the message view when sent to MDP is described
in section 4.1.5.2.
4.1.6.3.1 S̲A̲R̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
When distribution is performed for an incoming message,
a QEL will be created for SAR and sent to ISQ. This
QEL will contain the type parameter in its information
field. (The type parameter is used by SAR to identify
the type of Retrieval keys which are delivered):
The following information will be available for SAR.
- CIF ref ID
- Classification
- Special Handling Instructions
- DTG release
- PLA ref#
- SICs
- Nominal distribution list (SCD list after incoming
message distribution assistance)
4.1.6.4.1 S̲T̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
When distribution is performed for an Incoming or outgoing
message, statistics will be created and CSF will be
called for statistics collection.
The following information will be available for STP
in MDP memory.
- Message length
- Precedence level
- Classification
- Special Handling Instructions
- Number of terminals to which distribution has been
performed
- MDCO assistance indicator
4.1.6.5.1 T̲M̲P̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
The TMP interface is separated in two parts. One containing
the system parameter used by MDP and one containing
the tables used by MDP.
The following system parameters are used by MDP.
- Supervisor specified parameters for MDCO assistance
which are:
1) All incoming messages Y/N
2) All incoming messages of specified classification
Y/N
- Test parameter for Quiet Hours and Queue ID for
Quiet Hours position
- Queue ID for Supervisor specified Atomal printer
The following tables are used by MDP:
- SIC table
- SCD table
When MDP is requesting TMP for SIC table entries the
following parameters will be available for TMP:
- From one to three SICs, each defined by three characters
- A HQ bit mask
- Exercise indicator
The key to TMP will have the following elaboration
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
EXERCISE INDICATOR HQ BIT MASK SIC…0f…1…0e… SIC…0f…2…0e… SIC…0f…3…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
When the table entries are returned to MDP the following
information is contained in each entry.
- Number of action SCDs
- Number of info SCDs
- List of SCDs
Each output record will have the following elaboration.
The first entries after the two numbers contain Action
SCDs and then Info SCDs.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
NO. OF ACTION SCDs NO. OF INFO SCDs SCD…0f…1…0e… SCD…0f…2…0e… SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
The maximum length of the tables returned will be:
866 bytes.
When MDP is requesting TMP for SCD table entries the
following parameters will be available:
- Number of SCDs
- List of SCDs
The record will have the following elaboration:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
number of SCDs SCD…0f…1…0e…, SCD…0f…2…0e… ...............SCD…0f…N…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
The maximum length of the table will be 866 bytes.
When the table information is returned to MDP the following
information is contained in each entry.
- SCD
- Terminal/Device Designator
- Queue ID
- Number of copies
Each output record will have the following elaboration.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
SCD TD/DD QUEUE ID NUMBER OF COPIES
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
4.2.1 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
As described in section 4.1.2, MDP will only contain
one sub-package. Therefore, this section will identify
all functions which shall be performed by MDP. Modules
to perform the functions will be identified down to
a level where each module will contain less than 250
source statements.
4.2.1.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 Message Distribution Package will perform distribution
to terminals in the following cases:
- Incoming messages
- Outgoing messages
- Comments
- Messages sent for coordination
- Re-distribution of incoming and outgoing messages
- Messages/comments reentered after MDCO assistance.
For each of these cases, the functions which will be
performed by this sub-package, are described in this
section. The functions are identified in two levels.
If a function of the highest level is identified in
more than one case, the function will only be described
in the first case where it arises, and hereafter it
will only be stated.
The numbers in the headings of the following subsections
refer to the functional breakdown shown in the figures
4.2.1.1-1 to 4.2.1.1-6.
4.2.1.1.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲2̲.̲0̲)̲
The following functions will be performed for an incoming
message sent from THP.
- Create an SCD list
- Test of parameters for MDCO assistance
- Create a Queue List from the SCD List
- Perform Delivery to the queues in the queue list
- Perform Delivery to atomal printer, if requested
- Perform alternative distribution to either the
Duty Officer or the MDCO if delivery cannot be
performed to all queues in the queue list
- Create statistics
- Create retrieval keys
In figure 4.2.1.1-1 the functional break down for an
incoming message is shown.
4.2.1.1.1.1 C̲r̲e̲a̲t̲e̲ ̲a̲n̲ ̲S̲C̲D̲ ̲L̲i̲s̲t̲ ̲(̲2̲.̲1̲.̲1̲)̲
When an SCD list is created the following functions
will be used:
- A function to identify the HQ/SIC/exercise information.
Up to 8 collocated headquarters may be specified.
Up to three SICs may be specified.
- A function to control the SICs. The system action
related to the identified SICs will be as follows:
SICS ACTION
AAA Neglect this SIC
ABA, ACA, ADA, Queue to MDCO
AE(X) - AZ(X) Neglect these SICs
Other SICs Normal distribution
- A function to create a SIC key by HQ/SIC/Exercise
information and to request and receive from TMP.
- A function to group the SCDs, returned from TMP
in action and info precedence.
- A function to delete duplicate SCDs and to insert
the SCD list in the distribution field of the message
view.
4.2.1.1.1.2 T̲e̲s̲t̲ ̲o̲f̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ ̲f̲o̲r̲ ̲M̲D̲C̲O̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲ ̲(̲2̲.̲1̲.̲2̲)̲
During the test of the parameters for MDCO assistance
the following functions will be used.
- A function to control the supervisor parameters
for MDCO assistance.
The parameters are as follows:
1) All incoming messages
2) All incoming messages of specified classification
3) All incoming messages except those of specified
classification
If one of the above parameters is fulfilled, the
message will be sent to the MDCO.
- A function to control an Internal Handling Instruction.
If an Internal Handling Instruction is detected,
the message will be sent to the MDCO.
- A function to control Special Handling Instructions.
The following action will be taken.
Exclusive: Send message to MDCO
Crypto security: Send message to MDCO
More than one Special Handling Instruction sends
message to MDCO, else normal distribution.
- A function to control missing or garbled SICs.
If the SICs are missing or garbled, the message
will be sent to the MDCO
- A function to check if the SCD list is empty or
not. If it is empty, the message will be sent to
the MDCO.
All the functions described above will always be performed,
and after each function an MDCO assistance code will
be updated.
If the tests show that the message shall be sent to
the MDCO the following functions will be performed.
- A function to create and send a QEL to the common
MDCO receive queue. The QEL will in its information
field contain two codes. One telling that the message
is sent for incoming Message Distribution assistance,
and the other one is the MDCO assistance code created
by the functions described above.
- If the message is of precedence flash, a function
will send a QEL to the common MDCO command queue.
If the message is returned from the MDCO, it will
be handled as described in section 4.2.1.1.6.
4.2.1.1.1.3 C̲r̲e̲a̲t̲e̲ ̲Q̲u̲e̲u̲e̲ ̲L̲i̲s̲t̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲S̲C̲D̲ ̲L̲i̲s̲t̲ ̲(̲2̲.̲2̲.̲1̲)̲
The following functions will be used when a queue list
is created.
- A function to identify and get the SCD list in
the message view
- A function to request and receive the SCD information
lists from TMP. The information list will contain
the following objects.
- Terminal/Device Designator
- Queue ID for receive queue
- Number of copies
- A function to convert the SCD information lists
to a queue list. The queue list will in each line
contain the following information.
- Terminal/Device Designator
- Queue ID for receive queue
- The SCDs to which distribution shall be performed
at that terminal
- Number of print copies for each SCD
- Space for Delivery code
- A function to insert the Queue list in a temporary
field in the message view.
4.2.1.1.1.4 P̲e̲r̲f̲o̲r̲m̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲t̲o̲ ̲t̲h̲e̲ ̲Q̲u̲e̲u̲e̲s̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲e̲d̲ ̲b̲y̲ ̲t̲h̲e̲
̲Q̲u̲e̲u̲e̲ ̲L̲i̲s̲t̲ ̲(̲2̲.̲2̲.̲2̲)̲
The following functions are used when delivery is performed.
- A function to initialize and control the delivery
loop. This loop is shown in a flow gram in section
4.2.1.3.
- A function to create and send a QEL. The QEL will
in its information field contain a reference to
the associated queue line in the queue list.
- A function to receive response from the queue monitor
and on the behalf of this response, insert the
delivery code in the associated queue line.
- If the message is of precedence immediate a function
will before delivery to each terminal check if
the terminal is signed-off. If it is signed-off
the Delivery code will be changed so the message
also will be sent to either the Duty Officer or
the MDCO if it is Quiet Hours.
- A function will send a QEL to a terminal's command
queue each time a QEL is delivered to the terminal's
flash queue.
4.2.1.1.1.5 P̲e̲r̲f̲o̲r̲m̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲t̲o̲ ̲A̲t̲o̲m̲a̲l̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲(̲2̲.̲2̲.̲3̲)̲
If the message contains a special handling instruction
of type Atomal, and if one of the queues in the Queue
list is associated to a printer, the following functions
will be used.
- A function to identify the Queue ID for the supervisor
specified Atomal printer
- A function to send a QEL and get response from
the queue monitor. On basis of the response the
delivery status in the queue list will be updated
4.2.1.1.1.6 P̲e̲r̲f̲o̲r̲m̲ ̲A̲l̲t̲e̲r̲n̲a̲t̲i̲v̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲2̲.̲3̲)̲
If the message cannot be delivered to all the queues
in the Queue List, the following functions will be
used.
- A function to check whether it is Quiet Hours or
not.
If it is not Quiet Hours, the following functions will
be used (2.3.2).
- A function to send the QEL to the common MDCO receive
queue. The QEL will in its information field contain
a code telling that the message is sent for alternative
distribution assistance.
- If the message is of precedence flash, a function
will send a QEL to the common MDCO command queue.
If the message is returned from the MDCO, it will be
handled as described in section 4.2.1.1.6.
If it is Quiet Hours, the following functions will
be performed (2.3.1).
- A function to identify the SCDs in the queue list,
to which delivery could not be performed because
the terminal was signed-off. The delivery status
will be used to identify the SCDs.
- A function to insert the SCDs in the temporary
field intended to contain the queue list. A QEL
is created which in its information field will
contain a reference to the SCDs.
- A function to identify the Duty Officer queue ID.
The QEL will be sent and a response will be received
from the Queue monitor. On basis of this response
the delivery status will be updated.
- If the Message is of precedence flash, a function
will send a QEL to the Duty Officer's command queue.
- After delivery to the Duty Officer, the Delivery
status will be examined and if alternative distribution
still is requested, the message will be sent to
the MDCO as described above.
4.2.1.1.1.7 C̲r̲e̲a̲t̲e̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲(̲2̲.̲4̲.̲1̲)̲
The following functions will be used to create statistics.
- A function to identify the following information
- Classification
- Special Handling Instructions (maximum two)
- Precedence level Action/Info
- Number of terminals to which distribution has
been performed
- Message length
- The information will be available for STP in the
MDP memory and when STP is called for statistics
collection a pointer will be provided to locate
the information.
4.2.1.1.1.8 C̲r̲e̲a̲t̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲K̲e̲y̲s̲ ̲(̲2̲.̲4̲.̲2̲)̲
The following function will be used when retrieval
keys are created.
- A function will create a QEL to SAR. The QEL will
in its information field contain a Type Code to
identify the event. The following information will
be available for SAR in the message view.
- Item ref.
- Classification
- Special handling
- DTG release
- PLA ref#
- SIC…0f…1…0e…, SIC…0f…2…0e…, SIC…0f…3…0e…
- Nominal distribution list
4.2.1.1.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲(̲3̲.̲0̲)̲
The following functions will be performed for an outgoing
message sent for local distribution by TEP.
- Create a queue list from the SCD list (3.1.1)
- Perform Delivery to the queues in the queue list
(3.1.2)
- Perform Delivery to Atomal printer, if requested
(3.1.3)
- Perform Alternative distribution to either the
Duty Officer or the MDCO, if delivery cannot be
performed to all queues in the queue list (3.2)
- Create Statistics (3.3.1)
In figure 4.2.1.1-2 the functional break-down for an
outgoing message sent for local distribution is shown.
4.2.1.1.3 C̲o̲m̲m̲e̲n̲t̲s̲ ̲(̲4̲.̲0̲)̲
The following functions will be performed for a comment
sent for distribution by TEP.
- Create a queue list from the SCD list (4.1.1)
- Perform delivery to the queues in the queue list
(4.1.2)
- Perform delivery to Atomal printer if requested
(4.1.3)
- Perform alternative distribution to either the
Duty Officer or the MDCO, if delivery cannot be
performed to all the queues in the queue list (4.2)
In figure 4.2.1.1-3 the functional break down for a
comment sent for distribution is shown.
4.2.1.1.4 M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲o̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲(̲5̲.̲0̲)̲
The following functions will be performed for a message
sent for coordination by TEP.
- Create a queue list from the SCD list (5.1.1)
- Perform coordination delivery to queues identified
by the queue list (5.1.2)
- Perform delivery to Atomal printer if requested
(5.1.3)
- Perform Coordination completion procedure (5.1.4)
In figure 4.2.1.1-4 the functional break down for a
message sent for coordination is shown.
4.2.1.1.4.1 C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲5̲.̲1̲.̲2̲)̲
The functions used for coordination delivery are the
same as for normal delivery of messages which are described
in section 4.2.1.1.1.4. Except if the message is of
precedence immediate.
- If the message is of precedence immediate a function
will before delivery to each terminal check if
it is signed-off. If it is signed-off no delivery
will be performed and the delivery code will show
that condition.
- If the terminal is signed off, Flash Messages will
automatically be refused by the Queue monitor when
sent is requested. MDP will hereafter update the
delivery code.
4.2.1.1.4.2 C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲(̲5̲.̲1̲.̲4̲)̲
The following functions will be used to perform coordination
completion.
- A function to identify the SCDs in the queue list,
to which delivery cannot be performed. The delivery
status will be used to identify the SCDs.
- A function to insert the SCDs in the temporary
field reserved to contain the queue list. A QEL
is created which in its information field will
contain a reference to the SCDs.
- A function to identify the drafters queue ID and
to send the QEL. The queue ID will be contained
in the information field of the QEL sent to MDP
from the drafter.
4.2.1.1.5 R̲e̲-̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲a̲n̲d̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
̲(̲6̲.̲0̲)̲
The following functions will be performed for messages
sent for re-distribution by TEP.
- Create Queue list from the SCD list (6.1.1)
- Perform delivery to the queues in the queue list
(6.1.2)
- Perform delivery to Atomal printer if requested
(6.1.3)
- Perform alternative distribution to either the
Duty Officer or the MDCO, if delivery cannot be
performed to all queues indicated by the queue
list (6.2)
In figure 4.2.1.1-5 the functional break down for a
message sent for re-distribution is shown.
4.2.1.1.6 M̲e̲s̲s̲a̲g̲e̲s̲/̲C̲o̲m̲m̲e̲n̲t̲s̲ ̲R̲e̲-̲E̲n̲t̲e̲r̲e̲d̲ ̲a̲f̲t̲e̲r̲ ̲M̲D̲C̲O̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
̲(̲7̲.̲0̲)̲
The following functions will be performed for messages/comments
re-entered from MDCO assistance.
- Create a queue list from the SCD list (7.1.1)
- Perform delivery to the queues in the queue list
(7.1.2)
- Perform delivery to Atomal printer if requested
(71.3)
- If delivery cannot be performed to all the queues
in the queue list, return the message/comment to
the MDCO (7.2.1)
- If no alternative distribution is needed to the
MDCO, perform finish delivery procedure to the
MDCO (7.3.1)
If the message is re-entered after incoming message
distribution assistance, the following functions will
be performed too.
- Create Statistics (7.3.2)
- Create Retrieval Keys (7.3.3)
In figure 4.2.1.1-6 the functional break down for a
re-entered message/comment after MDCO assistance is
shown.
4.2.1.1.6.1 R̲e̲t̲u̲r̲n̲ ̲M̲e̲s̲s̲a̲g̲e̲/̲C̲o̲m̲m̲e̲n̲t̲ ̲t̲o̲ ̲M̲D̲C̲O̲ ̲(̲7̲.̲2̲.̲1̲)̲
If the message/comment is returned to the MDCO for
a second alternative distribution the following functions
will be used:
- A function to identify the queue ID for the MDCO
answer queue. The queue ID will be contained in
the information field of the QEL returned from
the MDCO after the first assistance.
- A function to send a QEL to the MDCO answer queue.
The QEL will in its information field contain a
code indicating that the message/comment is sent
for alternative distribution assistance.
4.2.1.1.6.2 F̲i̲n̲i̲s̲h̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲t̲o̲ ̲M̲D̲C̲O̲ ̲(̲7̲.̲3̲.̲1̲)̲
If delivery is performed to all queues indicated by
the queue list the following function will be used.
- A function to identify the queue ID for the MDCO
answer queue. The queue ID will be contained in
the information field of the QEL returned from
the MDCO after the assistance.
- A function to send a QEL to the MDCO answer queue.
The QEL will in its information field contain a
code indicating that the message/comment is distributed
to all queues.
FIGURE 4.2.1.1-1…01…FUNCTIONAL BREAK DOWN FOR AN INCOMING…01…MESSAGE SENT FOR DISTRIBUTION
FIGURE 4.2.1.1-2…01…FUNCTIONAL BREAK DOWN FOR AN OUTGOING…01…MESSAGE SENT FOR LOCAL
DISTRIBUTION
FIGURE 4.2.1.1-3…01…FUNCTIONAL BREAK DOWN FOR A COMMENT…01…SENT FOR DISTRIBUTION
FIGURE 4.2.1.1-4…01…FUNCTIONAL BREAK DOWN FOR A…01…MESSAGE SENT FOR LOCAL COORDINATION
FIGURE 4.2.1.1-5…01…FUNCTIONAL BREAK DOWN FOR A…01…MESSAGE SENT FOR LOCAL RE-DISTRIBUTION
FIGURE 4.2.1.1-6…01…FUNCTIONAL BREAK DOWN FOR A…01…MESSAGE/COMMENT RE-ENTERED AFTER MDCO
ASSISTANCE
4.2.1.1.7 M̲D̲P̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲B̲r̲e̲a̲k̲-̲D̲o̲w̲n̲
On basis of the functional break-down for the six distribution
cases, four common control functions are identified.
- Incoming Messages Distribution
- Message Distribution
- Alternative Distribution
- Finish Distribution
A common functional break down of MDP is shown in figure
4.2.1.1.7-1, and for each of the control functions
a further break down is shown in figures 4.2.1.1.7-2
to 5.
FIGURE 4.2.1.1.7-1…01…FUNCTIONAL BREAK-DOWN FOR MESSAGE…01…DISTRIBUTION SUB-PACKAGE
FIGURE 4.2.1.1.7-2…01…FUNCTIONAL BREAK-DOWN FOR INCOMING MESSAGE…01…DISTRIBUTION
FUNCTIONS
FIGURE 4.2.1.1.7-3…01…FUNCTIONAL BREAK-DOWN FOR MESSAGE…01…DISTRIBUTION FUNCTIONS
FIGURE 4.2.1.1.7-4…01…FUNCTIONAL BREAK-DOWN FOR ALTERNATIVE…01…DISTRIBUTION FUNCTIONS
FIGURE 4.2.1.1.7-5…01…FUNCTIONAL BREAK-DOWN FOR FINISH…01…DISTRIBUTION FUNCTIONS
4.2.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
On basis of the functional break down depicted in section
4.2.1.1, this section identifies the MDP software modules.
In figure 4.2.1.2-1 the five control modules in MDP
are shown. The Main module "Message Distribution Package"
1.0 is responsible for the following functions.
- Test QEL from the Message Distribution Queue (MDQ)
- Identify the distribution case by analyzing the
QEL attributes
- Depending on the distribution case, the main module
will call the control modules on level 1 (1.1,
1.2, 1.3, 1.4, see figure 4.2.1.2-1) which are
needed to perform the requested distribution.
- Dismantle and save the QEL in CDQ
- Return to processing of the next message
The logic in the five control modules is shown in the
flow grams in section 4.2.1.3.
Through the distribution procedure, one word with control
information will be used by all modules.
In the sub-sections of this section, each of the level
1 control modules will be described together with the
underlaying modules called by the control modules.
4.2.1.2.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲1̲.̲1̲)̲
Figure 4.2.1.2-2 shows the software structure for the
incoming message distribution procedure.
The function of the control module is to provide sequential
access of the two modules "create ACD list" and "test
of parameters for MDCO assistance".
M̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲C̲r̲e̲a̲t̲e̲ ̲S̲C̲D̲ ̲L̲i̲s̲t̲ ̲(̲1̲.̲1̲.̲1̲)̲
The Module "create SCD list" (1.1.1) is responsible
for identification of HQ/SIC/exercise information and
for creation of a key to the SIC table controlled by
TMP, and to receive SDLs from TMP. This module will
call two slave modules which will perform SIC control,
grouping the SCDs in action and Info, and deletion
of duplicate SCDs.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲S̲I̲C̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲1̲.̲1̲.̲1̲)̲
The "SIC control" Module (1.1.1) is responsible for
control of the SICs as described in section 4.2.1.1.1.1.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲G̲r̲o̲u̲p̲i̲n̲g̲ ̲t̲h̲e̲ ̲S̲C̲D̲s̲ ̲a̲n̲d̲ ̲f̲o̲r̲ ̲D̲e̲l̲e̲t̲i̲o̲n̲ ̲o̲f̲ ̲D̲u̲p̲l̲i̲c̲a̲t̲e̲s̲
̲(̲1̲.̲1̲.̲1̲.̲2̲)̲
The module "grouping of SCDs in action and info and
deletion of duplicates" is responsible for grouping
the Action SCDs from the SDLs and grouping the information
SCDs from the SDLs. The next step for this module is
deletion of duplicate SCDs in the list.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲T̲e̲s̲t̲ ̲o̲f̲ ̲M̲D̲C̲O̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲ ̲(̲1̲.̲1̲.̲2̲)̲
The second module which the incoming message distribution
module will access is the "test of parameters for MDCO
assistance" module (1.1.2). This module will perform
a test with the functions as described in section 4.2.1.1.1.2.
4.2.1.2.2 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲1̲.̲2̲)̲
Figure 4.2.1.2.3 shows the software structure for the
message distribution procedure.
The control module "message distribution procedure"
(1.2) will have two functions. The first function is
sequential access of the two modules "create queue
list" and "delivery procedure". After processing of
these two modules, this control module will examine
the Delivery Status and depending on the result of
the examination, it will decide whether the two modules
"atomal print" and "coordination completion" shall
be called.
M̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲C̲r̲e̲a̲t̲e̲ ̲Q̲u̲e̲u̲e̲ ̲L̲i̲s̲t̲ ̲(̲1̲.̲2̲.̲1̲)̲
The module "create queue list" (1.2.1) is responsible
for identification of the SCD list and to request and
receive the SCD information lists from TMP. This module
will then call the module "Convert SCD information
lists to a queue list" to create a queue list.
M̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲C̲o̲n̲v̲e̲r̲t̲ ̲t̲h̲e̲ ̲S̲C̲D̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲L̲i̲s̲t̲s̲ ̲t̲o̲ ̲a̲ ̲Q̲u̲e̲u̲e̲
̲L̲i̲s̲t̲ ̲(̲1̲.̲2̲.̲1̲.̲1̲)̲
This module is responsible for the conversion of the
SCD information lists to a queue list. The queue list
will in each line contain the following information:
- Terminal/device designator
- Queue ID
- SCDs to which distribution shall be performed at
this terminal
- Number of copies for each SCD
- Space for delivery code
In the front of the list the number of lines with action
and info precedence will be stated.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲1̲.̲2̲.̲2̲)̲
The module "delivery procedure" is responsible for
delivery to each queue referenced by the queue list,
and to update the delivery status with a delivery code
for each queue. The delivery code can be one of the
following:
1) Delivery performed
2) Classification too high
3) Special handling instruction not included in terminal
profile
4) CAMPS function not included in terminal profile
5) The SCD is not associated to a TD or DD
6) Terminal signed off "Immediate"
7) Terminal signed off "Flash"
8) Print atomal message
This module will insert a pointer in the information
field to each QEL for which delivery is performed.
The pointer in QEL will point out the associated queue
line in the queue list. Special delivery for flash
and immediate as described in section 4.2.1.1.1.4 will
be performed by this module.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲A̲t̲o̲m̲a̲l̲ ̲P̲r̲i̲n̲t̲ ̲(̲1̲.̲2̲.̲3̲)̲
This module is responsible for identification of the
supervisor specified atomal printer, and to send a
QEL to the associated queue. After response from the
queue monitor the delivery status will be updated.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲(̲1̲.̲2̲.̲4̲)̲
This module is responsible for creation of a delivery
note to the drafter. This note will contain the SCDs
to which delivery could not be performed. The module
will thereafter send a QEL to the drafter's answer
queue. In the information field of the QEL will be
placed a reference to the delivery note.
4.2.1.2.3 A̲l̲t̲e̲r̲n̲a̲t̲i̲v̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲1̲.̲3̲)̲
Figure 4.2.1.2-4 shows the software structure for the
Alternative Distribution Procedure.
The control module "Alternative Distribution Procedure"
will have two functions. The first function is to check
whether it is quiet hours or normal time. If it is
quiet hours the control module will call the module
for quiet hours. After return from the quiet hours
module the control module will examine the delivery
status to check whether MDCO assistance is needed or
not. If MDCO assistance is needed the module for MDCO
assistance will be called, if it is normal time the
control module will automatically call the module for
MDCO assistance.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲Q̲u̲i̲e̲t̲ ̲H̲o̲u̲r̲s̲ ̲(̲1̲.̲3̲.̲1̲)̲
This module is responsible for creation of a Delivery
Note to the Duty Officer. This Delivery Note will contain
the SCDs to which delivery could not be performed because
the terminal was signed off. thereafter the module
will identify the Duty Officer position and then send
a QEL to the associated queue. The Delivery status
will then be updated.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲M̲D̲C̲O̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲ ̲(̲1̲.̲3̲.̲2̲)̲
This module is responsible for directing a QEL to the
MDCO position. It will control whether it shall be
sent to the common MDCO receive queue or to the answer
queue for MDCO which earlier had performed assistance.
The module will insert a code in the information field
of the QEL, indicating that it is sent for alternative
distribution assistance.
4.2.1.2.4 F̲i̲n̲i̲s̲h̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲1̲.̲4̲)̲
Figure 4.2.1.2-5 shows the software structure for the
Finish Distribution Procedure.
For the control module "Finish Distribution Procedure",
the logic is shown in the flow grams figure 4.2.1.3-6.
The control module is responsible for generation of
a finish delivery code for the MDCO, if the message
is re-entered from such a position and the distribution
was successful. If it is an incoming or outgoing message
the control module will call the module for statistics.
If it is an incoming message the module for retrieval
keys will be called too.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲(̲1̲.̲4̲.̲1̲)̲
This module is responsible for creating statistics
as described in section 4.2.1.1.1.7 and for calling
STP for statistics collection.
M̲o̲d̲u̲l̲e̲ ̲f̲o̲r̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲K̲e̲y̲ ̲(̲1̲.̲4̲.̲2̲)̲
This module is responsible that the retrieval keys
stated in section 4.2.1.1.1.8 are available for SAR,
and for sending a QEL to SAR which in this information
field will contain a key type number.
FIGURE 4.2.1.2-1…01…MESSAGE DISTRIBUTION PACKAGE…01…SOFTWARE STRUCTURE
FIGURE 4.2.1.2-2…01…INCOMING MESSAGE DISTRIBUTION…01…SOFTWARE STRUCTURE
FIGURE 4.2.1.2-3…01…MESSAGE DISTRIBUTION PACKAGE…01…SOFTWARE STRUCTURE
FIGURE 4.2.1.2-4…01…ALTERNATIVE DISTRIBUTION PROCEDURE…01…SOFTWARE STRUCTURE
FIGURE 4.2.1.2-5…01…FINISH DISTRIBUTION PROCEDURE…01…SOFTWARE STRUCTURE
4.2.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
The data flow and the control logic within this sub-package
is described in this section. The major function to
describe the flow and logic is HIPO charts. Additionally
the logic within this sub-package is described by means
of flow grams.
The procedures in the HIPO charts are identical with
the modules identified in section 4.2.1.2 and the numbers
for the procedures are assigned to the module numbers.
DIAGRAM 10.1 MESSAGE DISTRIBUTION…01…PACKAGE MDP MAIN MODULE PROCEDURE
DIAGRAM 10.2 MESSAGE DISTRIBUTION…01…PACKAGE MDP MAIN MODULE PROCEDURE
DIAGRAM 1.1 INCOMING MESSAGE DISTRIBUTION
DIAGRAM 1.2 INCOMING MESSAGE PROCEDURE
DIAGRAM 1.3 ALTERNATIVE DISTRIBUTION PROCEDURE
DIAGRAM 1.4 FINISH DISTRIBUTION PROCEDURE
HIPO CHARTS 10 PAGES
Start Distribution Loop
Read QEL from MDP
Identify Distribution case
Incoming Message? Perform Incoming Message
Distribution (1.1)
Is incoming message sent to MDCO?
Message Distribution? Perform Message
Distribution Procedure
(1.2)
Alternative Distribution? Perform Alternative
Distritution
Procedure
(1.3)
Finish Distribution? Perform Finish
Distribution
Procedure
(1.4)
Dismantle and save QEL in MDQ
END distribution loop
FLOWGRAM FOR MESSAGE DISTRIBUTION PACKAGE (1.0)
FIGURE 4.2.1.3-1
Create SCD list from PLA/SIC/exercise information (1.1.1)
Test for MDCO assistance (1.1.2)
Supervisor specified assistance
All incoming messages?
All incoming mesages of specified ? Update MDCO
assistance code
classification?
All incoming messages except
those of specified classification?
Internal Handling Instruction? Update MDCO assistance
code
Special handling instructions
Exclusive
Crypto security ? Update MDCO
assistance code
More than one spec. hand. inst.
Missing or garbled SICs? Update MDOC assistance code
Empty SCD list? Update MDCO assistance code
End test of MDCO assistance
MDCO assistance ? Send QEL with assistance
code to the common MDCO queue
Return
FLOWGRAM FOR INCOMING MESSAGE DISTRIBUTION (1.1)
FIGURE 4.2.1.3-2
Create queue list (1.2.1)
convert SCD information lists to a queue list (1.2.1.1)
Delivery procedure (1.2.2)
Examine delivery status
Is atomal print requested? Perform atomal print procedure
(1.2.3)
Is Distribtution case? perform coordination
Message for coordination completion procedure
(1.2.4)
Return
FLOWGRAM FOR MESSAGE DISTRIBUTION PROCEDURE (1.2)
FIGURE 4.2.1.3-3
Intitialize delivery loop (numbers of delivery)
Delivery loop
Message of precedence immediate Insert delivery
code
The terminal is signed-off ? Delivery not
performed
Distribution case terminal is signed
off
message for coordination
Create send QEL to terminal Receive queue
Is send rejected? Insert delivery code with reason
for rejection
Is Message of precedence flash? Send deliv. code
Terminal signed-off
Immediate
Message or precedence Immediate? Insert Delivery Code
The terminal is signed-off Terminal signed-off
Immediate
Insert deliv. code "delivery performed"
Increment loop counter
Is loop counter = numbers of delivery? ̲ ̲ ̲ EXIT delivery
End delivery loop
Return
FLOWGRAM FOR ALTERNATIVE DISTRIBUTION PROCEDURE (1.3)
FIGURE 4.2.1.3-4
Check for quiet hours
Quiet hours? Perform quiet hours procedure (1.3.1)
Examine delivery status
Delivery not performed ? Perform MDCO assistance procedure
(1.3.2)
to all terminals in
queue list
Return
FLOWGRAM FOR ALTERNAVIVE DISTRIBUTION PROCEDURE (1.3)
FIGURE 4.2.1.3-5
Re-entered message after MDCO ?
assistance for Alternative distribution
Incoming or outgoing message? Perform statistics
procedure (1.4.1)
Incoming Message? Perform Retrieval keys procedure
(1.4.2)
Re-entered message, which shall? Create and send Finish
Delivery
not be returned to the MDCO QEL to the MDCO answer
queue
Return
FLOWGRAM FOR FINISH DISTRIBUTION PROCEDURE (1.4)
FIGURE 4.2.1.3-6
4.2.1.4 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
This sub-package contains no data which only is used
by itself.
4.2.1.5 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
N.A.
4.3 M̲E̲M̲O̲R̲Y̲ ̲L̲A̲Y̲-̲O̲U̲T̲
In section 4.2.1.2 18 modules are identified. Each
of these modules are expected to contain an average
of 150 source elements.
This will give a total MDP program on 2700 source statements.
Based on an analysis of the external data elements
in section 4.1.5. It is estimated that 4k bytes will
be used for data in MDP.
The memory lay-out is shown in figure 4.3-1.
MDP PROGRAM
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Page 0
GPS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Page 60
MDP-PS
Page 63
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
MDP DATA
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Page 0
MDP-DS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Page 2
PPS
Page 63
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GPS Global Program Segment
MDP-PS Message Distribution Package Program Segment
MDP-DS Message Distribution Package Data Segment
PPS Process Program Segment
MEMORY LAYOUT…01…FIGURE 4.3-1
