top - download
⟦9ab60b715⟧ Wang Wps File
Length: 19005 (0x4a3d)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN45.10«
Derivation
└─⟦6f17b967f⟧ Bits:30006000 8" Wang WCS floppy, CR 0035A
└─ ⟦this⟧ »~ORPHAN45.10«
WangText
e understood that for each active VDU terminal, an interface of the described type
exists, i.e. if two MDCOs are signed-in, two instances of MDCO interfaces exist, one
for each MDCO terminal position. Further, if a terminal position has access to wo
or more CAMPS functions, that terminal position or instance of the Terminal Package
will have all the interfaces described for the CAMPS functions to which access is
granted.
5.13.2.2.1 T̲r̲a̲f̲f̲i̲c̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲T̲H̲P̲)̲
The Traffic Handling Package peforms analysis of incoming and outgoing messages,
as well as routing of outgoing messages.
5.13.2.2.1.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Service Message prepared by the Supervisor are
queued by TEP in the Traffic Handling Package queue
for outgoing servce messages.
Outgoing Messages retrieved for rerun by the Supervisor
are queued by TEP in the Traffic Handling Package
queue for outgoing messages.
Incoming Service Messages which shall be presented
to the Supervisor are queued by the TrafficHandling
Package in the supervisor's queue for service messages.
Security reports, warning reports, and channel
reports for print-out at the printer(s) associated
the supervisor VDU are placed in the supervisor's
queue for reports by the TrafficHandling Package.
Refer fig. 5.13.2.2.1-1.
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to Traffic Handling.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Incoming and outgoing Messages, which are not automatically
accepted by Traffic Handling re queued for Message
Service, in the incoming respective outgoing message
service queues.
TEP places the message in the Traffic Handling
Package queue for messages having been to Message
Service. Refer fig. 5.13.2.2.1-2.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When the Release Officer releases a message, TEP places
the message in the Message Routing Queue (MRQ) of the
Traffic Handling Package.
Refer fig. 5.13.2.2.1-3.
Figs. 5.13.2.2.1-1/2/3
5.13.2.2.1.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Traffic Handling.
5.13.2.2.1.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
ACP127 messages received by the Terminal Manager from
a PTR areplaced in the Message Routing Queue (MRQ)
of the Traffic Handling Package for routing assignment.
5.13.2.2.1.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
When the Traffic Handling Package detects an outgoing
message, which shall be output on the PTP, the Traffic
andling Package queues the message to the PTP.
5.13.2.2.1.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received in format A from the OCR - Terminal
Manager are placed in the Message Routing Queue (MRQ)
of the Traffic Handling Package for Routing assignmet
and ACP127 conversion.
5.13.2.2.2 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲M̲D̲P̲)̲
The Distribution Package is responsible for internal
distribution of information.
5.13.2.2.2.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
When the Supervisor retrieves an incomig or released
message for internal re-distribution, the message
is placed by TEP in the Distribution Packages queue
assigned to this purpose.
Refer fig. 5.13.2.2.2-1.
Figure 5.13.2.2.2-1…86…1 …02… …02… …02… …02…
b) M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Incoming messages for which distribution cannot
be determined by the Distribution Package are queued
to TEP in the MDCO queue.
Distribution instructions to he Distribution Package
leading to delivery of information to a terminal
position not active are delivered in this queue
as well.
The decision for distribution made by the MDCO
is communicated to the Distribution Package, which
if the ordered ditribution can be executed, i.e.
listed terminal positions active, returns a confirmation
signal to the terminal position.
The MDCO may retrieve messages for distribution.
Such messages are by TEP queued for the Distribution
Package in the approriate queue.
The information which the MDCO requests to be printed
is queued to the Distribution Package for queuing
to the printer associated the MDCO VDU.
Refer fig. 5.13.2.2.2-2.
b) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Messages detected to be inerror by the Terminal
Manager of an OCR or PTR are by the Distribution
Package queued to the Message Service Operator.
The information for which the MSO request a print-out
at his own printer are queued to the Distribution
Package for queuing tothe printer associated with
the MSO VDU.
Incoming messages for which the MSO requests print-out
at terminal positions allocated to specified Staff
Cells are queued to the Distribution Package.
Fig. 5.13.2.2.2-2
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
TEP queues messages for coordination, messages
for release, comments, and release notifications
to be distributed to the Distribution Package.
Information or which the user requests a print-out
is queued to the Distribution Package for queuing
to the shared printer associated with the user
VDU.
The Distribution package queues information addressed
to a user position in the FLASH, IMMEDIATE, PRIORIY
or ROUTINE queue of TEP in accordance with the
precedence of the delivered information.
Refer fig. 5.13.2.2.2-3.…86…1 …02… …02… …02… …02…
Figure 5.13.2.2.2-3
5.13.2.2.2.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The Distribution Package queues information addressed,
either by SCD or device designator, to the printer
position in the FLASH, IMMEDIATE PRIORITY or ROUTINE
queue of the Printer Terminal Manager in accordance
with the precedence of the delivered information.
5.13.2.2.2.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
ACP127 messages received by the PTR - Terminal Manager
which did not successfully pas the ACP127 validation
are queued to the MSO via the Distribution Package.
5.13.2.2.2.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages for which the supervisor has specified output
on PTP are queued by the Distribution Package in the
PTP Terminal Manager quue.
5.13.2.2.2.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received by the OCR Terminal Manager, which
did not successfully pass the format A validation are
queued to the MSO via the Distribution Package.
5.13.2.2.3 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲(̲S̲A̲R̲)̲
The torage and Retrieval Package handles the storage/retrieval
of all items of information, which are stored on long
term storage.
5.13.2.2.3.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Supervisor retrieve requests are by TEP inserted
in th SAR retrieve request queue. When the SAR
Package has processed the request, the result is
placed in the Terminal Package supervisor queue
for delivery.…86…1 …02… …02… …02… …02…
When the Supervisor Terminal Manager has requested
a disk dismount, this is reported to SAR via the
SAR request queue. This request is acknowledged
by SAR by queuing an acknowlege in the proper queue.
When the Supervisor has performed a disk mount
this is communicated to SAR by the Terminal Manager.
Dump activities commanded or acknowledged by the
supervisor are communicated to the SAR by the Terminal
Manager.
Reorts, mount request reports, dump request reports
for print-out at the printer(s) associated the
supervisor VDU are placed in the Terminal Package
queue for reports by SAR.
Refer fig. 5.13.2.2.3-1.
Figure 5.13.2.2.3-1
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
When the MDCO wants to retrieve a message, TEP
inserts the retrieve request in the SAR Packages
retrieve request queue. SAR inserts th result
of the processing of the request in the MDCO delivery
queue.
Refer fig. 5.13.2.2.3-2.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to SAR.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When a user issues a retrieval or message append
request, TEP inserts the equest in SAR retrieval
request queue.
When SAR has processed the request, it inserts
the result of it in the Terminal Package delivery
queue.
When a user Terminal Manager detects a transaction
(An initial version of a message, a message relesed,
a comment transmitted) which results in information
being stored, the Terminal Manager reports the
retrieval keys and information to SAR.
Refer fig. 5.13.2.2.3-3.
5.13.2.2.3.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to SAR.
5.13.2..3.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received from the PTR are automatically
released by the Terminal Manager.
The Terminal Manager reports the retrieval key
of the message automatically released to SAR.
Figure 5.13.2.2.3-2
Figure 5.13.2.2.3-3
5.13.2.2.3.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to SAR.
5.13.2.2.3.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received from the OCR are released automatically
by the Terminal Manage. The retrieval keys of the
message are reported to SAR.
5.13.2.2.4 L̲o̲g̲ ̲a̲n̲d̲ ̲A̲c̲c̲o̲u̲n̲t̲a̲b̲i̲l̲i̲t̲y̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲L̲O̲G̲)̲
The Log and Accountability Package collects log records
reported from various package and stores them on disk.
Upon request from the Suervisor trace of log is performed
by the Log and Accountability Package.
5.13.2.2.4.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of Supervisor activities are communicated
to the Log and Accountability Package through CAMPS
Sytem Functions.
The Log and Accountability Package queues log records
to TEP for print-out at the supervisor's terminal
as they arrive.
The supervisor may request various traces of log
records. The Terminal Package queues such requests
in therequest queue of the Log and Accountability
Package.
When the Log and Accountability Package has traced
the requested log records, they are placed in the
Supervisor's queue for traced log. Then the Log
and Accountability package places a comman completion
code in the Terminal Package queue assigned to
this purpose, so that TEP can generate a command
completion report. Warning reports are placed
in the warning queue by Log and Accountability
Package. Refer fig. 5.13.2.2.4-1.
Fig. 15.13.2.2.4-1
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of MDCO activities are communicated
to the Log and Accountability Package through CAMPS
System Functions.
Refer fig. 5.1.2.2.4-2.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of MSO activities are communicated
to the Log and Accountability Package through CAMPS
System Functions.
Refer fig. 5.13.2.2.4-2.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Log records of user activities are comunicated
by the Terminal Package to the Log and Accountability
Package through CAMPS System Functions.
Refer fig. 5.13.2.2.4-2.
5.13.2.2.4.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Log records of information distributed by SCD to a
printer are communicted by the Terminal Package to
the Log and Accountability Package through CAMPS System
Functions.
5.13.2.2.4.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to log and accountability.
5.13.2.2.4.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to log and accontability.
5.13.2.2.4.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to log and accountability.…86…1 …02…
…02… …02… …02…
Figure 5.13.2.2.4-2
5.13.2.2.5 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲(̲S̲T̲P̲)̲
The Statistics Package collects statistical information
from many packages and makes statistics based on the
collected information. The Statistics Pakage extracts
on request from the supervisor specified statistics
and queues them in the supervisor's statistics print
queue.
5.13.2.2.5.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No statistics information flows from the Terminal
Packae to the Statistics Package.
The Terminal Package requests statistics from the
Statistics Package by giving a command to the Statistics
Package.
When the Statistics Package has retrieved the commanded
statistics, it queues it in the TEP statitics print
queue. Then the Statistics queues a command completion
code in the supervisor queue dedicated to this
purpose so TEP can generate a command completion
report.
Statistics information generated periodically by
the Statistics Package isqueued in the queue for
statistics print as well.
Refer fig. 5.13.2.2.5-1.
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to Statistics.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to Statistics.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The TerminalPackage collects statistics information
on user formats and communicates such statistics
records to the Statistics Package by invoking the
appropriate CAMPS system function.
Refer fig. 5.13.2.2.5-2.…86…1 …02… …02… …02… …02…
Figure 5.13.2.2.5-1
Figure 5.13.2.2.5-2
5.13.2.2.5.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The Terminal Manager collects statistics information
on formats distributed on SCDs to the printer and communicates
such statistics record to the Statistics Package by
invoking the appropriate CAMPS System Function.
5.13.2.2.5.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Statistics.
5.13.2.2.5.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Statistics.
5.13.2.2.5.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲n̲a̲g̲e̲r̲
No interface to Statistics.
5.13.2.2.6 S̲S̲&̲C̲ ̲S̲y̲s̲t̲e̲m̲
The SS&C software monitors and controls the CAMPS system,
hardware as well as software. The SS&C software acts
as operating system.
The SS&C software initializes an instance of the erminal
Package (Terminal Manager) each time the state of a
terminal changes from Unmanned to Manned/Attended.
The instance, i.e. type of Terminal Manager, activated
is device dependent.
5.13.2.2.6.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
For VDUs, the initilization procedure is similar for
all CAMPS functions, except that the supervisor function
is not handed over before the ASSIGN command has been
issued.
The Terminal Package is initiated with information
about the access rights determined by the SS&C Package
and include:
- CAMPS functions which may be accessed by the user
from te given terminal position.
- System tables which may be accessed.
The interface to the SS&C software further covers the
following special areas:
a) Error Reporting.
Errors that cannot be handled by the Terminal Package
are reported to SS&Cand appropriate action taken
here. Control will be returned from SS&C in the
cases where continued operation is possible, otherwise
switchover or restart will be performed.
b) Ordered close-down.
When a close-down command is received from SS&Cthe
following actions are taken:
1) Warning sent to all manned terminals specifying
when close-down will take place.
2) Commands are ignored when current activities
are completed and all flash messages have been
displayed.
3) Suspension o transactions still active at terminals
when warning time has elapsed.
4) Notify SS&C that close-down actions are complete.
c) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The supervisor may issue some commands to the SS&C
Package, such as integrity check, change pofile
(external channel, terminal, user). Such commands
are by TEP inserted in the command queue of the
SS&C Package.
When the SS&C Package has executed a command, it
places a command completion code in TEP queue assigned
to this purpose, so TEP can generate a command
completion report.
Repors for the supervisor generated by the SS&C
Package (e.g. system integrity check unsuccessfull)
are placed in TEP queue for supervisor reports.
Refer fig. 5.13.2.2.6-1.
d) M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No special interface.
e) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
o special interface.
f) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No special interface.
5.13.2.2.6.2 S̲t̲a̲n̲d̲ ̲A̲l̲o̲n̲e̲ ̲D̲e̲v̲i̲c̲e̲s̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲s̲
No special interfaces to the SS&C Package exist.…86…1
…02… …02… …02… …02…
Fig. 5.13.2.2.6-1…86…1 …02… …02… …02… …02…
5.13.2.2.7 T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲T̲M̲P̲)̲
TMP provides access to tables, global number series
and system parameters and validates update-requests
to these as well as ensuring coninuity and integrity
in case of system failures. Back-up/reload facilities
are also supplied. The tables accessed by TEP include:
AIG
PLA
RI
CH
SDL
SCD
SIC
Command Control Tables
ROUT MDCO Tables
Term. prof. (read via TMP, update via SS&)
User. prof. (read via TMP, update via SS&C)
Global no. series:
Document control no.
Transaction serial no.
Release serial no.
System Parameters:
TBD.
5.13.2.2.7.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
In addition to th supervisor facilities for read
and update implemented as commands, the Terminal
Package reads the relevant tables, numbers, and
system parameters required for its functions.
b) M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to TMP.
Figure 5.13.2.2.7-1…86…1 …02… …02… …02… …02…
c) M̲S̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to TMP.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Following the read TMP increments the transaction
serial no.
After release TMP increments the release serial
no.
During validation of user entries tables are accessed
by TEP.
5.13.2.2.7.2 P̲r̲i̲n̲t̲e̲r̲s̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments document control no.
5.13.2.2.7.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments release serial no.
5.13.2.2.7.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲e̲r̲
Increments document control no.
5.13.2.2.7.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments release serial no.
