top - download
⟦d5303778c⟧ Wang Wps File
Length: 27446 (0x6b36)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN67.08«
Derivation
└─⟦11f497f33⟧ Bits:30005812 8" Wang WCS floppy, CR 0119A
└─ ⟦this⟧ »~ORPHAN67.08«
WangText
W…00……00……00……00…C…0a……00……00…C…0b…C B…0e…A…09…A…0f…A @…09…@…0d…2
2…06…2…07…1…08…1…0d…1…01…1…05…1…06…0…09…0…0a…0…01…0…06…0…07…/…0c…/…0d…/…01…/…06….…0a….…0b….…00…. .…05….…06….…07…-…08…-…09…-…00…-…02…-
- …86…1 …02… …02… …02…
…02…CPS/SDS/036
…02…KS/820208…02……02…
SUPERVISOR PRINTER
DETAILED DESIGN SPECIFICATION…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ........................................
1.1 PURPOSE AND SCOPE ..........................
1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES
1.2.1 Applicable Documents ..................
1.2.2 Project Referencs .....................
1.3 TERMS AND ABBREVIATIONS ....................
1.3.1 Abbreviations ..........................
1.3.2 Terms ..................................
2 SUMMARY OF REQUIREMENT .........................
2.1 PACKAGE DESCRIPTION ........................
2.2 PACKAGE FUNCTIONS ..........................
2.1.1 Main Functions (Normal Operation) ......
2.2.2 Functional Responsibilities ............
2.2.2.1 Initialiation, Close Down, and
Restart ............................
2.2.2.2 Check Pointing and Recovery ........
2.2.2.3 Error Detecting and Error Handling .
2.2.2.4 Integrity of Operation .............
2.2.2.5 Dta Collection (Log, Statistics,
and Reports) .......................
2.2.2.6 Security ...........................
2.3 CHARACTERISTICS ............................
2.3.1 Timing .................................
2.3.2 Throughput .............................
2.3.3 Flexibility ............................
2.3.4 Accuracy ...............................
3 ENVIRONMENTS ..................................
3.1 EQUIPMENT .................................
3.2 SOFTWARE ...................................
3.2.1 Equipment ..............................
3.2.2 Development Support Software ...........
3.3 INTERFACES .................................
3.3.1 External Software ......................
3.3.2 Package Interface ......................
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES .....
4 PACKAGE DESIGN ................................
4.1 PACKAGE OVERVIEW ...........................
4.1.1 Functional Overview ....................
4.1.2 Software Specification .................
4.1.3 Data Flow and Control Logic ............
.1.4 Common Package Data ....................
4.1.5 Comon Package Procedures ...............
4.1.6 Global Data ............................
4.1.7 Interfaces .............................
4.1.7.1 External Interfaces ...............
4.1.7.2 Package Interfaces .................
4.1.7.3 Sub-Package Interfaces .............
4.2 SUBPACKAGE SPECIFICATONS ...................
4.2.1 Supervisor Print Control Subpackage
(SPICO) ...............................
4.2.1.1 Functional Specification ...........
4.2.1.2 Software Structure .................
4.2.1.3 Data Flow and Control Logic ........
4.2.1.4 Module Specifications ..............
4.2.1.4.1 SPICO ̲MAIN Specification .......
4.2.1.5 Common SPICO Data ..................
4.2.1.6 Common SPICO Procedures ............
4.2.1.6.1 INIT ̲RECEIVE ̲FROM ̲SPIP ̲CMDQ Spec
4.2.1.6.2 CMD ̲TO ̲DELCO Spec .............
4.2.1.7 Subpackage Interfaces ..............
4.2.2 Delivery Control Subpackage ............
4.2.2.1 Functional Specification ...........
4.2.2.2 DELCO Software Structure ...........
4.2.23 Data Flow and Control Logic ........
4.2.2.4 Module Specifications ..............
4.2.2.4.1 DELCO ̲MAIN Spec. ...............
4.2.2.4.2 INITIALIZE ̲DELCO Spec. .........
4.2.2.4.3 PROC ̲SPICO ̲ITEMS Spec. ........
4.2.2.4.4 PROC ̲RESCO ̲ITEMS Spec. .........
4.2.2.4.5 PROC ̲SYSTEM ̲CALL Spec. .........
4.2.2.4.6 PROC ̲ANSQ ̲ITEM Spec. ...........
4.2.2.4.7 DELIVER ̲ITEM Spec. .............
4.2.2.4.8 DELIVER ̲REQUET Spec. ..........
4.2.2.4.9 DELCO ̲REPLY Spec. ..............
4.2.2.5 Common DELCO Data ..................
4.2.2.6 Common DELCO Procedures ...........
4.2.2.6.1 REPLY ̲TO ̲OUTST ̲REQ Spec. .......
4.2.2.6.2 GET ̲MMS ̲WARNING Spec. ..........
4.2.2.6.3 DELIVERY ̲QUEUE ̲BLOCKED ̲ACTIONS .
4.2.2.6.4 FLASH ̲CHECK Spec. ..............
4.2.2.6.5 INITRECEIVE ̲FROM ̲SPIP ̲ANSQ ....
4.2.2.6.6 RECEIVE ̲ITEM Spec. .............
4.2.2.6.7 INIT ̲RECEIVE ̲ITEM Spec. ........
4.2.2.6.8 DELCO ̲CMD ̲TO ̲RESCO Spec. .......
4.2.2.6.9 DELCO ̲CC ̲TO ̲SPICO ..............
4.2.2.7 Subpackage Interfaces ..............
4.2.3 Request Control Subpackage ............
4.2.3.1 Functional Specification ...........
4.2.3.2 RESCO Software Structure ...........
4.2.3.3 Data Flow and Control Logic ........
4.2.3.4 RESCO Module Specifications ........
4.2.3.4.1 RSCO MAIN Specifications ......
4.2.3.4.2 PROC REQQ ITEM Specification ...
4.2.3.4.3 GEN PROFILE PRINT Specification
4.2.3.4.4 GEN SYSTEM PARAMETER PRINT Spec.
4.2.3.4.5 DELCO ITEM PROCESSING Spec. ....
4.2.3.4.6 QSTP CYCLE Specification .......
4.2.3.4.7 GEN TABLE PRINT Specification .
4.2.3.4.7.1 Functional Specification ...
4.2.3.4.7.2 Interface ..................
4.2.3.4.7.3 Module Components .........
4.2.3.4.7.3.1 TABLE PRINT CYCLE ......
4.2.3.4.7.4 Data Description ...........
4.2.3.4.7.5 Module Design ..............
4.2.3.5 Common Subpackage Data .............
4.2.3.6.1 INIT RECEIE FROM SPIP REQQ Spec
4.2.3.6.1.1 Functional Specification ..
4.2.3.6.1.2 Interface ..................
4.2.3.6.1.3 Data Description ...........
4.2.3.6.1.4 Procedure Design ...........
4.2.3.62 PWLT CYCLE SPECIFICATION .......
4.2.3.6.2.1 Functional Specification ...
4.2.3.6.2.2 Interface .................
4.2.3.6.2.3 Data Description ...........
4.2.3.6.2.4 Procedure Design ...........
4.2.3.6.3 CMPT CYCLE Specification ......
4.2.3.6.4 PRINT ITEM TO DELCO
Specification .................
4.2.3.6.5 RESERV DELIVERY BUFFER
Specification .................
4.2.3.6.6 RESCO CLEAN UP Specification ...
4.2.3.7 Coroutine Interfaces ...............
4.2.3.7.1 DELCO RESCO Interfaces .........
4.2.3.7.2 RESCODELCO Interfaces .........
4.2.4 SPIP Initialisation Subpackage .........
4.2.4.1 Functional Specification ...........
4.2.4.1.1 Start up informtion
Interpretation (1.0) ...........
4.2.4.1.2 SPIP Sotware
initialization (2.0) ...........
4.2.4.2 Software Structure .................
4.2.4.2.1 Process Start (1.0) ............
4.2.4.2.2 SPIP Subprocess Init (2.0) .....
4.2.4.3 Dataflow and Contro Logic .........
4.2.4.4 SPIP Initialization Module
Specifications .....................
4.2.4.4.1 PROCESS START Specification ....
4.2.4.4.2 SPICO SUBPROCESS Init
Specification ..................
4.2.4.5 Common Subpackage Data .............
4.2.4.6 Common Subpackage Procedures .......
4.2.4.7 Subpackage Interfaces ..............
4.3 Memory Layout ............................
…86…1 …02… …02… …02… …02…
…02…
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̲
a) The Supervisor Printer Package Specification for
the CAMPS project/4040 is written to fulfil the
following objectives:
1) To provide a etailed definition of the Supervisor
Printer Package function and Software architecture.
2) To provide user operational and development personnel
with details of the ongoing analysis.
3) To define in detail the interfaces with other
packages nd to describe their facilities.
b) The Supervisor Printer Package Specification defines
the functions and software architecture of the
package to a level sufficient for a programmer
to start coding.
The Supervisor Printer Package constitutes ne of
the building blocks of the TEP package.
For an overall description of the TEP package refer
CPS/SDS/012.
All Supervisor Printer Package internal data and
interfaces are defined within this document in detail.
For a detailed data descripion of data external to
the Supervisor Printer Package and interfaces to
other packages refer to the Database Design Document
(CPS/DBD/001)and the relevant interface documents.
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̲
CAMPS System Requirement Specification
CPS/210/SYS/0001
Supervisor Commands and Procedures
CPS/20/ICD/0002
CAMPS System Design Specification
CPS/SDS/001
Database Design Document
CPS/DBD/001
CAMPS Software Interface Control Document
CPS/ICD/009
1.2.2 R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
DOCUMENT NAME DOCUMENT NUMBER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
CAMPS System Functions CPS/SDS/024
Message Management CPS/SDS/025
System Status and Control CPS/SDS/029
Table Managment CPS/SDS/026
Input/Output Cotrol CPS/SDS/028
Storage and Retrieval CPS/SDS/030
Statistics CPS/SDS/031
Logging CPS/SDS/032
Traffic Handling CPS/SDS/033
Message Distribution CPS/SDS/034
Supervisor VDU CPS/SDS/035
MDCO VDU CPS/SDS/037
MSO VDU CPS/SDS/038
USER VDU CPS/SS/039
OCR CPS/SDS/040
Printer CPS/SDS/041…86…1
…02… …02… …02…
…02…
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
TEP T̲e̲rminal
P̲ackage
SPRI S̲upervisor P̲r̲i̲nter
Package
SPIP S̲upervisor P̲ri̲nter
P̲rocess
SPICO S̲upervisor P̲ri̲nt
C̲o̲ntrol Subpakage
DELCO D̲e̲l̲ivery C̲o̲ntrol
Subpackage
RESCO R̲e̲ques̲t C̲o̲ntrol
Subpackage
PRIP P̲r̲i̲nter P̲ackage
PRIS P̲r̲i̲nter S̲ubprocess
SUP S̲upervisor
VDU̲
P̲ackage
SVUP S̲upervisor V̲DU̲
P̲rocess
VUP V̲DU
U̲ser
P̲ackage
VUS V̲DU
U̲ser
S̲ubprocess
UMAM U̲ser M̲essage A̲cess
and M̲onitoring
SSC S̲ystem
S̲tatus
and
C̲ontrol
DEMCO D̲e̲vice M̲anagement
and C̲o̲ntrol
CSF C̲amps
S̲ystem
F̲unctions
MDP M̲essage
D̲istribution
P̲ackage
TMP T̲able
M̲anagement
P̲ackage
STP S̲t̲atistics
P̲ackage
THP T̲raffic
H̲andling
P̲ackage
SYIE S̲Y̲tem I̲nformation
E̲xtracts
ASM A̲bbreviated
S̲ervice
M̲essage
1.3.2 T̲e̲r̲m̲s̲
N/A
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̲
The S̲upervisor P̲R̲I̲nter Package (SPRI) contains the
software to support the functions required for Supervisor
Printers.
Th Supervisor Printer Package and the Printer Package
(ref. CPS/SDS/041) has a master/slave relationship,
where the Supervisor Printer Package acts as the master.
It keeps account of the Supervisor Printer Configuration
and delivers the arriving Prin items in accordance
with this to the Printer Package. The Supervisor Printer
Process additionally generates print items, which are
also delivered in accordance with the Supervisor Printer
Configuration.
The Printer Package works as a slave for te Supervisor
Printer Package. It takes care of formatting and printout
of the items delivered by the Supervisor Printer Package.
Print items to be delivered by Supervisor Printer Package
are:
a) Arriving items:
Reports
Log CIF'S
Log Trac CIF'S
Statistics Print
Service Messages
Catalogue Display Print
Status Print
b) Generated items:
SYstem Information Extract Print
Table Print
The Supervisor Printer Package interfaces to the Printer
Package and to other parts of te Terminal Package as
well as other Packages within the CAMPS System.
The interfaces are shown on figure 2.1-1.
The numbers refer to the table below.
1. Items for print, Flash notifications, Print replies.
2. Items for print, Table print- an SYIE print - requests,
SPIP ̲ACK's and Supervisor Commands.
3. Status print items (from UMAM), Status item requests.
4. SSC Commands, Warning-Security- and Error-reports,
SSC Command Acknowledges.
5. Warning-reports for print
6. Log CIFs fo print, Log print replies
7. Warning reports, Channel reports and Service messages.
8. Statistics CIFs, Statistics print replies.
TABLE 2.1-1…86…1 …02… …02… …02… …02…
SPRI uses the CAMPS System Functions and has access
to several tables via Table Management Package
Figure 2.1-1
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
This section outlines the functions to be performed
by SPRI.
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲N̲o̲r̲m̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲)̲
The Main Functions implemented by SPRI are:
1. Dlivery of print items
2. Generation of Table- and SYIE- print items.
3. Keep account of Printer Configuration
2.2.1.1 D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲ ̲I̲t̲e̲m̲s̲
All supervisor print items are delivered to the appropriate
printer (Supervisor, Report, LOG, Staistics) according
to the present configuration. The configuration is
set by supervisor, and can be changed dynamically.
2.2.1.2 G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲T̲a̲b̲l̲e̲-̲ ̲a̲n̲d̲ ̲S̲Y̲I̲E̲-̲P̲r̲i̲n̲t̲ ̲I̲t̲e̲m̲s̲
When the supervisor requests printout of a table or
of SYstem InformationExtracts. SPRI shall generate
these print items from information contained in the
various tables ,System Parameters etc.
2.2.1.3 K̲e̲e̲p̲ ̲A̲c̲c̲o̲u̲n̲t̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
To ensure correct delivery SPRI must always be aware
of the current supervisr printer configuration.
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̲
Initialization is invoked by SSC when the process is
started up.
Close Down is performed oncommand from SSC.
Restart actions are for SPRI the same as Initialization
actions.
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̲
N/A.
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̲
SPRI is designed so that errors are detected at an
early stage.
All etected errors, i.e. System Call errors, Queue
errors, internal software errors, etc, are handled
by using the CSF procedures ANALYZE ̲ERROR and SEND
̲GARBLE.
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 error detection and error handling functions descried
in section 2.2.2.3 ensures that errors are detected
and handled properly.
Single and minor software errors do not decrease system
throughput. Only severe errors cause major recovery
or invoke operator intervention.
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
N/A.
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
SPRI is trusted software as it does, select printer
to print Password list and command print.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲m̲i̲n̲g̲
N/A.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
SPRI is able to generate and/or delivery print items
at a rate so that PRIP can fulfil its throughput requirements
(ref. SDS 041 - sec. 2.3.2). This is achieved by sending
print items to the printer processes so whn an item
has been printed and the printer process acknowledges
this, the next print item is already available for
print out.
2.3.3. F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The design ensures that changes to formats and format
tolerances can be implemented with ease to fcilitate
improvement of the document layout quality and useability.
The design allows that two additional precedence levels
can easily be implemented.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
Time is accurate within +/- 500 ms.
All other data are exact.
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
The equipment environment of this package is the CR80D
Computer.
3.2 S̲O̲F̲T̲W̲A̲R̲E̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
SPRI's system software environment cosists of the following
components:
- DAMOS
- CAMPS System Functions
- SSC
- TMP
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̲
Development software is standard DAMOS and TOS (Terminal
Operating System) resident in a single CR80D configuration.
3.3I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲a̲n̲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̲
Ref. CPS/ICD/009
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̲
N/A.
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̲
The Supervisor Printer Package (SPRI) consists of one
process called the Supervisor Printer Process (SPIP).
SPIP contains the software or handling print queued
for the supervisor printers and distributing it to
the appropriate Printer Subprocess (PRIS), which performs
the actual printout.
The Supervisor Print Process (SPIP) consists of three
subpackages (coroutines):
a) SPICO Supervisor Print Control) which reacts upon
SSC commands, Supervisor Commands, and controls
the other coroutines.
b) DELCO (Delivery Control) which reacts upon commands
from SPICO, input from the Supervisor Print Queue,
the Report Queue, the Log rint Queue, the Statistics
Print Queue, and the Answer Queue. From RESCO it
receives information for delivery to the Supervisor
Printer and to UMAM.
DELCO distributes items for print to the printer
subprocess currently assigned for the various tpes
of print. For Print of Flash precedence, DELCO
signals the appropriate PRIS by command to the
Command Queue for the process.
c) RESCO (Request Control) which receives the following
print requests from the Supervisor VDU Process
(SVUP):
Sysem Information Extract Requests
Table Print Requests
and obtains the requested items by request to TMP
o UMAM. When obtained, the items are passed to
DELCO for delivery to the appropriate Printer Process.
Communication with other packages (aart from Monitor
Calls) is done via queues. SPIP has 7 main queues:
1) Command Queue:
Close Down command from SSC, flash notifiations,
configuration change notifications,printq cancelled
notifications and printq unblocked notifications.
2) Anwer Queue:
Replies from PRIS. When SPIP wants a notification
from PRIS upon completion of processing of an item,
the Send Request, Send Reply mechanism is used.
3) Report Queue:
Reports and Service Messages sent by other packages
for print t the Report Printer. The Report Queue
consists of 7 subqueues - one for reports, one
for each precedence level and two for future extentions.
4) Supervisor Print Queue:
This consists of six subqueues. One for each precedence
level and two forpossible extensions. Items for
print at the supervisor printer are sent to this
queue.
5) Log Print Queue:
LOG CIFs sent from the LOG package for print at
the LOG printer.
6) Statistics Print Queue:
Statistics information sent from the Satistics
Package for print at the Statistics Printer.
7) Request Queue:
Print requests sent from the Supervisor VDU package
to be generated by RESCO and sent for print at
the Supervisor Printer.
Figure 4.1-1
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̲
This section contains an analysis of the main functions
to be performed by the Supervisor Printer Package.
The analysis is carried out to a levelwhere subfunctions
with self-contained implementation considerations may
be isolated, thereby reducing the complexity to be
grasped at one time.
Furthermore, the aim of the analysis is to identify
precisely concurrency and priorities of subfunctins.
The analysis does not include the package functions
derivable from the functional responsibilities described
in section 2.2.2. These functions will be analysed
and described for each identified subfunction in section
4.2 of this document.
I figure 4.1.1-1 an overview of the SPRI functions
is shown. This first level breakdown represents a simple
grouping of the requirements outlined in section 2.
In the following subsections, each of the functions
shown in the boxes of figure 4.1.1- will be broken
down into subfunctions.
Figure 4.1.1-1…86…1 …02… …02… …02… …02…
4.1.1.1 E̲x̲e̲c̲u̲t̲e̲ ̲S̲S̲C̲ ̲a̲n̲d̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
4.1.1.1.1 C̲a̲r̲r̲y̲ ̲O̲u̲t̲ ̲C̲o̲m̲m̲a̲n̲d̲ ̲A̲c̲t̲i̲o̲n̲s̲
When a command arrives, the actions required are carried
out.
4.1.1.1.2 S̲e̲n̲d̲ ̲C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲m̲p̲l̲e̲t̲o̲n̲
On completion of some of the commands, a command completion
is sent.
4.1.1.2 K̲e̲e̲p̲ ̲A̲c̲c̲o̲u̲n̲t̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
SPIP reads the system parameters containing the Supervisor
Printer Configuration at initialization and when the
configuratin is changed.
4.1.1.3 D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲ ̲I̲t̲e̲m̲s̲
All items queued for print at SPIP are delivered to
the appropriate printer subqueue.
4.1.1.3.1 D̲e̲t̲e̲r̲m̲i̲n̲e̲ ̲D̲e̲v̲i̲c̲e̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
The appropriate printer device designator is determined
from informaion about the printer configuration and
the actual item type.
4.1.1.3.2 S̲e̲n̲d̲ ̲P̲r̲i̲n̲t̲ ̲I̲t̲e̲m̲
When the destination printer device is determined,
the item is sent to it.
4.1.1.4 G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲T̲a̲b̲l̲e̲-̲ ̲a̲n̲d̲ ̲S̲Y̲I̲E̲-̲P̲r̲i̲n̲t̲ ̲I̲t̲e̲m̲s̲
When the Supervisor has entered a Table print or a
SYIE-Print command at his terminal, the supervisor
VDU process sends a reques to SPIP, which takes care
of generation and delivery of the print item.
4.1.1.4.1 D̲e̲t̲e̲r̲m̲i̲n̲e̲ ̲R̲e̲q̲u̲e̲s̲t̲ ̲T̲y̲p̲e̲
Upon arrival of a Table- or -SYIE-print request the
type of request is determined.
4.1.1.4.2 G̲e̲t̲ ̲R̲e̲q̲u̲e̲s̲t̲e̲d̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
The Table-enties, the system parameters or other data
which form the requested print item is accessed by
system calls, or by requests to UMAM.
4.1.1.4.3 L̲o̲a̲d̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲I̲n̲t̲o̲ ̲B̲u̲f̲f̲e̲r̲
In order to be sent for print, the data is loaded into
a buffer.
4.1.1..4 R̲e̲q̲u̲e̲s̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲
The Request Control Function takes care thet only one
request is being processed at a time and that all data
are delivered correctly i.e. in the correct order.
Most of the requested items can not be contained in
a single buffe and therefore a double buffering mechanism
is used between SPIP and PRIS.
This double buffering mechanism is also controlled
by the Request Control Function
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
In this section the software structure of SPRI is described.
The allocation of functions onto processes and coroutines
is explained based on the analses in section 4.1.1.
Figure 4.1.2-1 shows the mapping of functions onto
processes and coroutines.
4.1.2.1 S̲P̲R̲I̲ ̲P̲r̲o̲c̲e̲s̲s̲e̲s̲
The S̲upervisor P̲R̲I̲nter Package consists of one process.
This process is called SPIP (Supervisor Printer Process)
The esponsibilities and the queue structure of SPIP
are described earlier in sec. 4.1. An overview of SPIP
is shown in Fig. 4.1-1.
4.1.2.2 S̲P̲R̲I̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲s̲
The characteristics of the coroutine software component
type is described in CSF.DDS (CDS/SD/024-sec.2.2.1.5)
and therefore it shall not be repeated here.
Fig. 4.1.2-1 Functional Breakdown - Main Functions.
4.1.2.2.1 S̲P̲I̲P̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲s̲
SPIP consists of three coroutines.
4.1.2.2.1.1 S̲P̲I̲C̲O̲ ̲(̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲P̲r̲i̲n̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲)̲
SPICO reacts upon SSC commands, FLASH Notifications,
Supervisor Comands and items from DELCO. SPICO controls
the other coroutines. It receives all input via the
S1 semaphore and signals the S2 semaphore.
4.1.2.2.1.2 D̲E̲L̲C̲O̲ ̲(̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲C̲o̲n̲t̲r̲o̲l̲)̲
DELCO delivers the items queued in the REP, SUP,LOG
and STAT Queues t the appropriate printers. Items generated
by RESCO are also delivered.
Replies from PRIS are received in the ANS queue. Replies
to requests originated by RESCO are delivered to RESCO
via the S3 semaphore.
SPICO Commands and other input items ae received in
the S2 semaphore. DELCO signals semaphores S1 and S3
in order to communicate with SPICO and RESCO.
4.1.2.2.1.3 R̲E̲S̲C̲O̲ ̲(̲R̲e̲q̲u̲e̲s̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲)̲
RESCO receives its input from the S3 semaphore. These
inputs are supervisor print requests fro the REQQ (Request
Queue) and SPICO commands and PRIS-replies passed on
by DELCO.
RESCO generates the items requested by the supervisor
and passes them on to DELCO for delivery. RESCO signals
S2 and waits for S3.
4.1.2.3 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
In the preceding subsections of section 4.1.2, the
processes and coroutines of SPRI have been isolated,
and the functions to be performed by these softare
components identified.
The software structure for each component (i.e. coroutine)
will be outlined in the following subsections. The
description of the software structure will mainly be
in the form of software structure charts and references
hould be made to the functional specification given
in section 4.1.1. The denotation used in section 4.1.1
has as far as possible been used in the software structure
charts, with the purpose of highlighting the close
relationship. Thus the identifiation of programme tasks
is given in narrative English and not as programme
or procedure names.
4.1.2.3.1 S̲P̲I̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The software structure of the Supervisor Print Control
coroutine is outlined in by fig. 4.1.2-2.
Fig. 4.1.2-2 SPICO-structure.
4.1.2.3.2 D̲E̲L̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The software structure of the Delivery Control Coroutine
is outlined in fig. 4.1.2-3
Fig. 4.1.2-3 DELCO Structure
4.1.2.3.3 R̲E̲S̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲
The software structure of the Request Control Coroutine
is outlined in fig. 4.1.2-4.
