top - download
⟦360f3a464⟧ Wang Wps File
Length: 29511 (0x7347)
Types: Wang Wps File
Notes: CPS/SDS/041
Names: »1485A «
Derivation
└─⟦e8bc85b7f⟧ Bits:30005802 8" Wang WCS floppy, CR 0105A
└─ ⟦this⟧ »1485A «
WangText
$…0c…$…05…#…0f…#…06…"…0b…"…00…"…02…"…07…!…86…1
…02…
…02… …02…
…02…CPS/SDS/041
…02…KS//811201…02……02…
PRINTER
DETAILED
DESIGN
SPECIFICATION…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲…01……06…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
1 GENERAL .......................................
1
1.1 PURPOSE AND SCOPE .........................
1
1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES
2
1.2.1 Applicable Documents ..................
2
1.2.2 Reference Documents ...................
2
1.3 TERMS AND ABBREVIATIONS ...................
3
1.3.1 Terms .................................
3
1.3.2 Abbreviations .........................
3
2 SUMMARY OF REQUIREMENTS ......................
4
2.1 PACKAGE DESCRIPTION ......................
4
2.2 PACKAGE FUNCTIONS ........................
7
2.2.1 Main Functions(Normal Operation) ......
7
2.2.1.1 Formatting and Printout ...........
7
2.2.1.2 Document Accounting ...............
7
2.2.2 Functional Responsibilities ...........
11
2.2.2.1 Start,Stop,Close Down,Resume ......
11
2.2.2.2 Preemption Control ................
11
2.2.2.3 Checkpointing and Recovery ........
12
2.2.2.4 Error Detection and Error
Handling
..........................
12
2.2.2.5 Integrity of Operation ............
12
2.2.2.6 Data Collection ...................
13
2.2.2.6.1
Log
...........................
13
2.2.2.6.2
Statistics
....................
13
2.2.2.6.3
Reports
.......................
13
2.3 CHARACTERISTICS ...........................
14
2.3.1 Timing ................................
14
2.3.2 Throughput ............................
14
2.3.3 Flexibility ...........................
14
2.3.4 Accuracy ..............................
14
3 ENVIRONMENT ...................................
15
3.1 EQUIPMENT .................................
15
3.2 SOFTWARE ..................................
15
3.2.1 System Software .......................
15
3.2.2 Develop Support Software ..............
15
3.3 INTERFACES ................................
15
3.3.1 External Interfaces ...................
15
3.3.2 Package Interfaces ....................
16
3.3.2.1 Message Distribution (MDP) ........
16
3.3.2.3 System Statics and Control (SSC) ..
16
3.3.2.4 Table Management (TMP) ............
16
3.4 FUNCTIONS MAINTAINED BY OTHER
PACKAGES ..................................
16
4 PACKAGE DESIGN ................................
17
4.1 PACKAGE Overview ..........................
17
4.1.1 Functional Specification ..............
20
4.1.1.1 Printout Control ..................
22
4.1.1.1.1 DEMCO Control Functions .......
22
4.1.1.1.2 FLASH Queue Monitoring ........
24
4.1.1.1.3 Preemption Control ............
24
4.1.1.1.4 Output Control ................
26
4.1.1.1.5 Document Accounting ...........
28
4.1.1.1.6 Transaction Accounting ........
30
4.1.1.2 Printout Execution ................
32
4.1.1.2.1 Format Control ................
32
4.1.1.2.2 Printout ......................
34
4.1.2 Software Specification ................
36
4.1.2.1 PRIP Processes ....................
36
4.1.2.1.1 PRIS Process ..................
36
4.1.2.2 PRIP Coroutines ...................
38
4.1.2.2.1 PRIS Coroutine ................
38
4.1.2.2.1.1 U̲ser P̲rinter C̲O̲ntrol
Coroutine (UPCO) ..........
38
4.1.2.2.1.2 P̲R̲inter O̲utP̲ut
Coroutine (PROP) ..........
38
4.1.2.3 Software Structure ................
39
4.1.2.3.1 UPCO Coroutine Software
Structure .....................
39
4.1.2.3.2 PROP Coroutine Software
Structure .....................
39
4.1.3 Data Flow and Control Logic ...........
50
4.1.3.1 PRIS Internal Data Flow and
Coroutine Synchronization .........
50
4.1.3.2 Normal Functional Flow
(Major Transactions) ..............
50
4.1.4 Common Package Data ...................
61
4.1.5 Common Package Procedures .............
63
4.1.6 Global Data Elements ..................
64
4.1.7 Interfaces ............................
64
4.1.7.1 External Interfaces ...............
64
4.1.7.2 Package Interfaces ................
64
4.1.7.3 Sub Package Interfaces ............
65
4.2 SUBPACKAGE SPECIFICATIONS .................
66
4.2.1 User Print Control Subpackage
Specification .........................
66
4.2.1.1 Functional Specification ..........
66
4.2.1.2 Software Structure ................
77
4.2.1.3 Data Flow and Control Logic
within UPCO .......................
81
4.2.1.4 Module Specifications .............
89
4.2.1.4.1 UPCO ̲MAIN .....................
89
4.2.1.4.2 PROCESS ̲CMD ̲Q ̲ITEM ............
95
4.2.1.4.3 UPCO ̲INITIALIZATION ............
103
4.2.1.4.4 ANALYSE ̲FLASH ̲
NOTIFICATION ..................
107
4.2.1.4.5 PROCESS ̲PROP ̲ITEM .............
111
4.2.1.4.6 PROC ̲PRINT ̲COMPLETE ̲REP .......
120
4.2.1.4.7 UPCO ̲PREEMPT ̲RESTORE ..........
127
4.2.1.4.8 FLASH ̲ITEMS ̲TO ̲MDCO ...........
134
4.2.1.4.9 PRINTING ̲PREPARATIONS .........
142
4.2.1.4.10 DETERMINE ̲PRINT ̲ITEM ̲
CATEGORY ......................
150
4.2.1.4.11 DOCUMENT ̲ACC ̲PREPARATIONS .....
153
4.2.1.4.12 TRANSACTION ̲ACCOUNTING ........
156
4.2.1.4.13 ERROR ̲REP .....................
159
4.2.1.5 Common UPCO Data ..................
161
4.2.1.6 Common UPCO Procedures ............
163
4.2.1.6.1 GET ̲MEDIUM ̲SPEED ̲PRINT ̲
PARAMETERS ....................
163
4.2.1.6.2 GET ̲LOW ̲SPEED ̲PRINT ̲
PARAMETERS ....................
164
4.2.1.6.3 SAVE ̲REFERENCES ...............
164
4.2.1.6.4 RETURN ̲ITEM ...................
167
4.2.1.6.5 DISMANTLE ̲ITEM ................
168
4.2.1.6.6 CMD ̲TO ̲PROP ...................
170
4.2.1.6.7 RECEIVE ̲CMD ...................
171
4.2.1.6.8 RECEIVE ̲PRINT ̲Q ...............
173
4.2.1.6.9 SEND ̲REP ̲TO ̲DEMCO .............
176
4.2.1.6.10 CHECK ̲VIEW ....................
177
4.2.1.7 Subpage Interface .................
180
4.2.2 P̲R̲inter O̲utP̲ut Subpackage Spec. .......
180
4.2.2.1 Functional Specification ..........
180
4.2.2.2 Software Structure ................
185
4.2.2.3 Data Flow and Control Logic
within PROP .......................
187
4.2.2.4 Module Specifications .............
192
4.2.2.4.1 PROP ̲MAIN Specification .......
192
4.2.2.4.2 ANALYSE ̲UPCO ̲CMD .............
195
4.2.2.4.3 CANCEL ̲OUTSTANDING ̲IO ̲S ......
209
4.2.2.4.4 DATA ̲CONVERSION ̲OUTPUT .......
214
4.2.2.4.5 PROCESS ̲FDR ...................
219
4.2.2.4.6
4.2.2.4.7
4.2.2.4.8
4.2.2.4.9 PROP ̲ERROR ....................
223
4.2.2.5 Common PROP Data ..................
226
4.2.2.6 Common PROP Procedures ............
226
4.2.2.6.1 PAPER ̲LOW ̲ACTIONS Spe-
cifications ...................
226
4.2.2.6.2 CONN ̲ERR ̲ACTIONS ..............
229
4.2.2.6.3 ALLOW Specifications ..........
231
4.2.2.6.4 REP ̲TO ̲UPCO ...................
234
4.2.2.6.5 SAVE ̲CONTINUATION ̲POINT ̲VALUES
237
4.2.2.6.6 RESTORE ̲CONTINUATION ̲
POINT ̲STATUS ..................
240
4.2.2.6.7 RESET ̲OUTPUT ̲BLE ̲POINTERS .....
243
4.2.2.6.8 READ ̲PFF ̲DATA .................
246
4.2.2.6.9 GET ̲QEL ̲INFO ̲DATA .............
248
4.2.2.6.10 GET ̲BUFFER ̲DATA ...............
250
4.2.2.6.11 TRANSFER ̲VIEW ̲DATA ............
252
4.2.2.6.12
4.2.2.6.13
4.2.2.6.14
4.2.2.6.15
4.2.2.7 Subpackage Interface ..............
254
4.3 MEMORY LAYOUT .............................
255…86…1 …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 Printer Package Specification for the CAMPS
project/4040 is written to fulfil the following
objectives:
1) To provide a detailed definition of the 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 and to describe their facilities.
b) The Printer Package Specification defines the functions
and software architecture of the package to a level
sufficient for a programmer to start detailed design
with a minimum of design effort.
The Printer Package constitutes one of the building
blocks of the TEP package.
For an overall description of the TEP package refer
CPS/SDS/012.
All Printer Package internal data and interfaces
are defined within this document in detail. For a
detailed data description of data external to the
Printer package and interfaces to other packages
refer 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/230/ICD/0002
CAMPS System Design Specification
CPS/SDS/001
Database Design Document
CPS/DBD/001
CAMPS Software Interface Control Document
CPS/ICD/009
Terminal Package Design Specification
CPS/SDS/012
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 Control 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
Supervisor Printer CPS/SDS/036
MDCO VDU CPS/SDS/037
MSO VDU CPS/SDS/038
USER VDU CPS/SDS/039
OCR CPS/SDS/040
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 T̲e̲r̲m̲s̲
N/A
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
PRIP TEP: P̲r̲i̲nter P̲ackage
PRIS P̲r̲inter S̲ubpackage
UPCO U̲ser P̲rinter C̲o̲ntrol
PROP P̲r̲inter O̲utp̲ut
PFF P̲rint F̲ormat F̲ile
FDR F̲ormat D̲escriptor R̲ecord
FDB F̲ormat D̲escriptor B̲uffer
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 P̲r̲i̲nter P̲ackage (PRIP) contains the software to
support the print-functions required for
Supervisor Printers,
Shared Printers,
Stand-alone Printers.
In connection with Supervisor printers PRIP has only
a slave function. The S̲upervisor P̲ri̲nter P̲ackage (SPIP)
supports the Supervisor Print functions and delegates
the items for print to the Printer Package.
At the Printer Package items will be queued in a priority
based FIFO-manner before being processed.
Items to be Processed can be:
a) Control Items:
Timeouts
DEMCO Commands
Log Acknowledges
FLASH Notifications
b) Print Items:
Messages
Comments
Message status Notifications
MSO/MDCO instructions
Service Messages
Reports
Statistics
Log records
System Information Extracts
Tables.
The Printer Package converts and formats the data before
printout. It also takes care of page accounting and
document accounting.
The Printer Package interfaces with other parts of
the Terminal Package as well as other Packages of the
CAMPS system.
Fig. 2.1-1 shows the interface between the Printer
Process, and the other TEP Processes:
Supervisor Print Process (SPRI)
VDU User Subprocess (VUS)
Further fig. 2.1-1 shows the interfaces to the other
CAMPS packages:
System Status and Control (SSC)
CAMPS System Functions (CSF)
LOG Package (LOG)
Message Distribution Package (MDP)
I/O Control (IOC)
Storage and File Management (FMS)
Table Management Package (TMP)
The numbers on figure 2.1-1 refers to the following
table:
1. Supervisor print items
2. User print items
3. DEMCO Commands and Command Completion Codes.
4. Timer requests/events,
Queue handling, Access control
5. Final transaction Log information
6. Incoming/Outgoing Messages
7. Printout Data
8. CIF-data for conversion/formatting
9. Format-data
10. Device profile data.
FIG. 2.1-1…01…INFORMATION FLOW
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 PRIP.
2.2.1 Main Functions (Normal Operation)
The main functions implemented by PRIP are
1. Formatting and printout
2. Document accounting
2.2.1.1 F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲P̲r̲i̲n̲t̲o̲u̲t̲
Some of the items queued for print contains binary
data which will have to be converted into a displayable
form before being printed.
The items do not contain all of the data to be printed.
The predefined part of it is contained in the Print
Format File (PFF) and must be merged with the variable
part to form the complete text.
The formatting also includes placing of the text so
that a nice layout is obtained. Ref. also sec. 2.2.1.2
below.
When the text has been formatted, it will be output
to the printer in blocks of upto 512 bytes.
2.2.1.2 D̲o̲c̲u̲m̲e̲n̲t̲ ̲A̲c̲c̲o̲u̲n̲t̲i̲n̲g̲
Document Accounting is to be carried out as stated
in the SRS sec. 3.2.3.7.2 for the following items:
- Messages
- Service Messages
- Comments
The layout of the document accounting is outlined in
figure 2.2.1-1 and figure 2.2.1-2.
Figure 2.2.1-1 explains the contents of the document
control number, while figure 2.2.1-2 shows the page
layout.
2 FIGURER
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 S̲t̲a̲r̲t̲,̲ ̲S̲t̲o̲p̲,̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲,̲ ̲R̲e̲s̲u̲m̲e̲
PRIP performs the above functions on command from DEMCO.
a) Start:
Initializes and starts the printing actions. Also
the Print Format file is opened. Upon completion
a report will be sent to DEMCO.
b) Stop:
Immediately stops the printing actions and closes
the Print Format File. The items, that is currently
processed, will be returned to its queue for later
processing.
Completion is reported to DEMCO.
c) Close Down:
Stops the printing actions after a specified time.
Is used to terminate the processing in an ordered
manner.
d) Resume:
Is used to resume printing actions after printer
errors.
2.2.2.2 P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
When items with Flash Precedence are queued for print
they shall start being executed within a specified
time limit unless the printer process already executes
a Flash item.
If the item being executed is of precedence lower than
flash and it cannot be completed within the time limit,
it shall be preempted. Processing of the preempted
item shall be resumed right after the preemption causing
item has been finished.
The preemption time limit is set by the Supervisor.
2.2.2.3 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
Checkpointing is performed by calling the SAVE-function
(CSF) at appropriate points, that is when print out
of an item has been completed. The queue element will
be dismantled.
On recovery some of the items queued for print may
have a flag set indicating suspected duplication. In
that case it shall be indicated on the document.
2.2.2.4 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̲
Errors detected by PRIP will be reported to SSC. Printing
actions are stopped and a DEMCO command is awaited.
If a printer error causes an error code from IOC a
Resume Command from DEMCO will be awaited.
2.2.2.5 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
PRIP shall contain credibility check to contain the
effects of corrupt or inaccurate data to the extent
this does not introduce redundant processing which
will decrease the system throughput.
It shall be a design aim that wherever possible the
consequence of a single software fault incident will
not affect more than one transaction. The detection
of an inconsistency indicating a fault, shall generate
a report and initiate re-processing from a validated
checkpoint in an attempt to recover with a minimum
of discontinuity. Only after further failures should
major recovery or operator intervention action be invoked.
2.2.2.6 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
2.2.2.6.1 L̲o̲g̲
A final log record shall be generated on interruption
or completion of printing the following item types:
- Messages
- Service Messages
- Comments
The log record shall contain the following fields:
a) Device designator
b) Transaction serial number
c) Format identification
d) Log time
e) Item reference identification
f) Exit cause
g) Classification
h) Special handling category
i) Start time of transaction
j) System Print Control Number
k) Special Handling Print Control no. (if aplicable)
2.2.2.6.2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
NA.
2.2.2.6.3 R̲e̲p̲o̲r̲t̲s̲
When completing printout of
Messages, Service Messages, or Comments,
a Delivery Status report shall be generated and sent
to UMAM.
The contents of this report are:
Item Ref. ID
"From SCD" or "From PLA#"
DTG
Status Code
Logical Device Designator
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̲
The package must be able to meet the requirements to
message processing (CPS/210/SYS/001 sec. 3.4):
The printer shall be able to operate at a speed corresponding
to 0.7 erlang of the maximum speed (120 char/sec) i.e.
0.7 x 120 = 84 char/sec.
Whenever pre-emption applies the time from receipt
of end-of-message to the availability of first character
for output shall never exceed 15 seconds including
time to discontinue transmission of pre-empted message.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The Printer Package must be able to drive the appropriate
printers at their maximum speed when required.
The fastest speed possibly required is the maximum
line speed for medium speed printers, which is 1200
bps. That is equivalent to 120 characters/sec.
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The design shall ensure that changes to formats and
format tolerances can be implemented with ease to facilitate
improvement of the document layout quality and useability.
Addition of new formats is straight forward, but software
to support the new functions will probably need to
be developed.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
Time shall be accurate within +/- 500 ms.
All other data shall be 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̲
PRIP's system software environment consists of the
following components:
- DAMOS
- CAMPS System Functions
- Storage and File Management
- I/O Control Software
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.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̲
Ref. CPS/230/ICD/0001 and CPS/230/ICD/0002
3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
3.3.2.1 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲M̲D̲P̲)̲
Comments
Incoming- and locally distributed
Outgoing -Messages will be queued for print at PRIP
by MDP
3.3.2.2 L̲o̲g̲ ̲a̲n̲d̲ ̲A̲c̲c̲o̲u̲n̲t̲a̲b̲i̲l̲i̲t̲y̲ ̲(̲L̲O̲G̲)̲
Log records collected by PRIP shall be queued to LOG.
PRIP then receives a receipt from LOG.
3.3.2.3 S̲y̲s̲t̲e̲m̲ ̲S̲t̲a̲t̲u̲s̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲S̲S̲C̲)̲
PRIP shall execute the following DEMCO (SSC software)
commands:
Start ̲SAD, Stop SAD, Close Down and Resume.
Completion of Start ̲SAD, Stop SAD and Resume commands
shall be reported to DEMCO.
3.3.2.4 T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲(̲T̲M̲P̲)̲
Table Management will be requested to deliver information
about the appropriate device profile.
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̲
Security key control.
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 P̲r̲i̲nter P̲ackage consists of one process that handles
the printout of the queued items.
The process is able to handle items for stand alone/shared-printers
as well as working as slave for the Supervisor Print
Process (SPIP)
An overview of the process is shown in fig. 4.1-1
P̲r̲i̲nter S̲ubprocess (PRIS) consists of two subpackages
(coroutines):
a) UPCO (U̲ser P̲rinter C̲o̲ntrol) which reacts upon Commands
from SSC and Flash notifications in the CMD-subqueue,
and receives items for print in the other subqueues.
It controls the other coroutine.
b) PROP (P̲r̲inter O̲utpu̲t) which reacts upon commands
from UPCO and Printer Control Signals from IOC.
It performs the actual printing
The format for printout is obtained from the P̲rint
F̲ormat F̲ile (PFF).
PRIS has two main queues:
The command Queue and the Print Queue. The Print Queue
is divided into 8 subqueues.
This structure is used because it makes it easier to
control the mutual priorities of the different items,
commands and notifications, which are queued for the
subprocess. The queues are further described in table
4.1-a.
M̲a̲i̲n̲-̲ ̲o̲r̲ ̲S̲u̲b̲-̲ ̲Q̲u̲e̲u̲e̲ ̲N̲a̲m̲e̲ ̲ ̲ ̲d̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲/̲c̲o̲n̲t̲e̲n̲t̲s̲
CMD Commands, Flash Notifications,
Timer Events
FLASH.WARN ̲SEC ̲REP Flash Items, Warning, Security
and Error Reports
IMMEDIATE Immediate items
PRIORITY Priority items
ROUTINE Routine items
OTHER REP Other reports
STATISTICS Stastistics print
LOG Log records
SYIE + TABLE System Information
Extracts and Table print.
T̲a̲b̲l̲e̲ ̲4̲.̲1̲-̲a̲ ̲Q̲u̲e̲u̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
F̲I̲G̲U̲R̲E̲ ̲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 Printer Package.
The analysis is carried out to a level where 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 subfunctions.
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.
In fig. 4.1.1-1 an overview of the PRIP functions is
shown. This first level breakdown represents a simple
grouping of the requirements outlined in section 2
and of the requirements stated in ref. 2.
The box marked PRIP DEMCO CONTROL FUNCTIONS reflects
the fact that the functions are totally controlled
by the DEMCO part of the SSC Software. Thus PRIP shall
contain functions necessary to respond to and execute
such controlling commands.
In the following subsections, each of the functions
shown in the boxes of fig. 4.1.1-1 will be broken down
into subfunctions.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲1̲-̲1̲
4.1.1.1 P̲r̲i̲n̲t̲o̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
These Functions takes care of the administrative part
of the printing actions i.e. selecting the appropriate
items to be printed, fetching accounting information,
interruption of printout execution etc.
4.1.1.1.1 D̲E̲M̲C̲O̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
In fig. 4.1.1-2 an overview of the DEMCO control functions
is depicted. DEMCO, which is a part of System Status
and Control, has the superior control of the Printer
̲Package, and therefore the control function has the
highest priority within PRIS.
The S̲t̲a̲r̲t̲ function is activated upon system start up,
restart and whenever the printer action has been stopped
by DEMCO e.g. when the related device is blocked.
The S̲t̲o̲p̲ function interrupts the printing action immediately.
It is used at blocking of the device.
The R̲e̲s̲u̲m̲e̲ function will resume printer actions interrupted
by paper out or other printer errors.
The C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲ is used when it is wished to close down
the system after a specified time. A Close Down Status
will be set, and a timer will be initiated.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲1̲-̲2̲…86…1 …02… …02… …02… …02… …02… …02…
4.1.1.1.2 F̲l̲a̲s̲h̲ ̲Q̲u̲e̲u̲e̲ ̲M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲
If the printer is temporarily not functioning e.g.
because of paper out, the arriving Flash items are
sent to MDCO.
Under normal circumstances the arriving flash items
will activate Preemption Control (ref. sec. 4.1.1.1.3)
4.1.1.1.3 P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
The subfunctions of Preemption Control is depicted
in fig. 4.1.1-3.
Preemption Control is invoked by two types of events:
1) arrival of Flash items while printing items with
priority lower than Flash.
2) arrival of Security- or Warning- Reports during
table print or print of System extract information.
When Preemption Control is activated it initiates a
timout request.
If it is not possible to finish the current item within
the specified maximum delay time, then p̲r̲e̲e̲m̲p̲t̲i̲o̲n̲ ̲s̲h̲a̲l̲l̲
b̲e̲ ̲a̲c̲t̲i̲v̲a̲t̲e̲d̲.
If the printer is temporarily stopped, e.g. because
of paper out, the invoking events will cause following
actions respectively:
1) Flash items will be sent to MDCO ref. sec. 4.1.1.1.2
2) Security- and Warning ̲Reports will be put back
in the Flash queue and their existance will be
indicated by setting of flags.
After printer-errors DEMCO ̲Functions will resume the
printing actions. If there are any preemption causing
items waiting, they will be printed first provided
that the suspended item is not itself a preemption
causing one.
When the preemption causing item has been printed,
the R̲e̲s̲t̲a̲r̲t̲ ̲P̲r̲i̲n̲t̲ Function will restart printing of
the preempted item from a suitable point.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲1̲-̲3̲
4.1.1.1.4 O̲u̲t̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
The functional breakdown of Output Control is depicted
in fig. 4.1.1-4. These functions are used to control
the printout execution.
Get Access to CIF and Give Up Access to CIF are used
in connection with accessing the print-data pointed
to by the received queue-elements.
Copy Control keeps accounts of the printed no. of copies
and provides that the right amount is printed.
Start Print is used when a new item or extra copies
of an old item is to be printed.
Abandon Print interrupts the current printing action,
and returns the queue-element to its place in the queue.
The E̲x̲c̲e̲p̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ is used when an a printer error
occurs. The Subprocess will wait for a DEMCO R̲e̲s̲u̲m̲e̲
Command.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲1̲-̲4̲
4.1.1.1.5 D̲o̲c̲u̲m̲e̲n̲t̲ ̲A̲c̲c̲o̲u̲n̲t̲i̲n̲g̲
These functions are fetching and computing relevant
parameters/information used in document accounting
and Page Header-/Trailer-s. Ref. fig. 4.1.1-5.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲1̲-̲5̲
4.1.1.1.6 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲c̲o̲u̲n̲t̲i̲n̲g̲
This is for the Printer Package limited to Log record
and Delivery Status Report generation, which is only
to be carried out after printing of Service Messages,
Messages and Comments.
The contents of the Log records are:
a) Device designator
b) Transaction serial number
c) Format identification
d) Log time
e) Item reference identification
f) Exit cause
g) Classification
h) Special handling category
i) Start time of transaction
j) System Print Control Number
k) Special Handling Print Control Number
The contents of the Delivery Status Reports are:
a) Item Ref. ID
b) "From SCD" or "From DCA#"
c) DTG
d) Status Code
e) Logical Device Designator
The Subfunctions are depicted in fig. 4.1.1-6.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲1̲-̲6̲
