top - download
⟦78db5412f⟧ Wang Wps File
Length: 28363 (0x6ecb)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN67.08«
Derivation
└─⟦2c95d9416⟧ Bits:30006059 8" Wang WCS floppy, CR 0091A
└─ ⟦this⟧ »~ORPHAN67.08«
WangText
B…0d…B…05…A…0f…@…08…@…00…@ ?…86…1
…02…
…02…
…02…
…02…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ......................................
10
1.1 PURPOSE ...................................
10
1.2 APPLICABLE DOCUMENTS AND PROJECT
REFERENCES ................................
10
1.2.1 Applicable Documents ..................
10
1.2.2 roject References ....................
11
1.3 TERMS AND ABBREVIATIONS ...................
11
1.3.1 Terms .................................
11
1.3.2 Abbreviations .........................
12
2 SUMMARY OF REQUIREMENTS ......................
13
2.1 PACKAGE DESCRIPTION .......................
13
2.1.1 General Concept .......................
13
2.1.1.1 Online Storage ....................
13
2.1.1.2 Offline Storage ...................
14
2.1..3 Subject to Storage ................
14
2.1.1.4 Storage and Retrieval Keys ........
14
2.1.1.5 Retrieval .........................
14
2.1.1.5.1 Online Retrieval ..............
15
2.1.1.5.2 Offline Retrieval ............
15
2.2 PACKAGE FUNCTIONS .........................
15
2.2.1 Main Functions ........................
15
2.2.1.1 Online Storage ....................
15
2.2.1.2 Offline Storage (Dump) ............
18
2.2.1.3 Retrival .........................
20
2.2.1.3.1 Online Retrieval ..............
20
2.2.1.3.2 Offline Retrieval .............
21
2.2.2 Functional Responsibilities ...........
23
2.2.2.1 Initialization, Close Down and
Restart ...........................
23
2.2.2.1.1 Initialization ................
23
2.2.2.1.2 Close Down ....................
24
2.2.2.1.3 Restart .......................
24
2.2.2.2 Checkpointing and Recovery .......
24
2.2.2.2.1 Checkpointing .................
24
2.2.2.2.2 Recovery ......................
24…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
2.2.2.3 Error Detection and
Error Handling ....................
25
2.2.2.3.1 Error Detectio ...............
25
2.2.2.3.2 Error Handling ................
25
2.2.2.4 Integrity of Operation ............
26
2.2.2.5 Data Collection ...................
26
2.2.2.6 Security ..........................
26
2.3 CHAACTERISTICS ..........................
26
2.3.1 Timing ................................
26
2.3.1.1 Response Time to Queries ..........
27
2.3.1.2 Response Time to Dump .............
28
2.3.1.3 Priorities Related to Input.......
28
2.3.1.4 Traffic Load ......................
29
2.3.1.5 Interleaving STP ..................
30
2.3.2 Throughput ............................
30
2.3.3 Flexibility ...........................
30
2.3.4 Accuray of Input Data ................
30
3 ENVIRONMENT ...................................
31
3.1 EQUIPMENT ENVIRONMENT .....................
31
3.2 SOFTWARE ENVIRONEMT .......................
31
3.2.1 System Software ......................
31
3.2.2 Development Software ..................
31
3.3 INTERFACES ................................
32
3.3.1 External Interfaces ...................
32
3.3.2 Package Interfaces ....................
32
3.3.2.1 Storage Interface .................
32
3.3.2.2 On-Line Retrieval Interface .......
32
3.3.2.3 Off-Line Retrieval Interface ......
33
3.3.2.4 Dump Retrieval Interface ..........
33
3.3.2.5 Supervisor Command Interface .....
33
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES ....
35
4 PACKAGE DESIGN ................................
36
4.1 PACKAGE OVERVIEW ..........................
36
4.1.1 Functional Specifications .............
36
4.1.1.1 Storage of Messages ...............
38
4.1.1.2 On-Line Retrieval .................
38
4.1.1.3 Off-Line Retrieval ................
38
4.1.1.4 Dump ..............................
39
4.1.1.5 Perform Supervisor Commands ......
39
4.1.2 Software Structure ....................
40
4.1.3 Data Flow and Control Logic ...........
42
.1.3.1 Package Control Data Elements .....
42
4.1.3.2 Data Flow Logic ...................
46
4.1.4 Common Data Elements (Internal) .......
48
4.1.4.1 On-Line Catalogue .................
48
4.1.4.2 Off-Line Catalogue ...............
51
4.1.4.3 Volume Table ......................
53
4.1.5 External Data Elements ................
56
4.1.5.1 Storage Keys During Storage .......
56
4.1.5.2 Retrieval keys During Retrieval ...
56
4.1.5.3 Return Data After a Retrieval .....
56
4.1.5.3.1 Return Code ...................
57
4.1.5.3.2 Catalogue Information .........
57
4.1.5.4 Supervisor Command Data ...........
57
4.1.5.4.1 Volume File Entry ............
57
4.1.5.4.2 Volume File Entry .............
57
4.1.5.5 Printer Data Elements .............
57
4.1.6 Interfaces ............................
57
4.1.6.1 External Interfaces ...............
57
4.1.6.2 Package Intrfaces ................
58
4.1.6.2.1 SAR/TEP Interface .............
58
4.1.6.2.2 SAR/MDP Interface .............
59
4.1.6.2.3 SAR/THP Interface .............
59
4.1.6.2.4 SAR/LOG Interface .............
59
4..6.3 Sub-Package Interfaces ............
60
4.1.6.3.1 Storage Sub-Package Interfaces
60
4.1.6.3.2 On-Line Retrieval Sub-Package
Interfaces ....................
60
4.1.6.3.3 Off-Line Retrieval Sub-Package
Interfaces ....................
60
4.1.6.3.4 Dump Sub-Package Interfaces ...
61
4.1.6.3.5 Supervisor Command Sub-Package
Interfaces ....................
61…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.1 On-Line Storage Specification..........
67
4.2.1.1 Functional Specification ..........
67
.2.1.1.1 Reception of Storage Requests .
69
4.2.1.1.2 Retrieval Key Pick-Up .........
69
4.2.1.1.3 Emptying Collect Area .........
69
4.2.1.1.4 Update On-Line Catalogue ......
70
4.2.1.1.5 Complete Storage .............
70
4.2.1.2 Sub-Package Software Structure ....
70
4.2.1.3 Data Flow and Control Logic .......
73
4.2.1.4 Sub-Package Data ..................
79
4.2.1.4.1 Control Area ..................
79
4.2.1.4.2 Data Aea .....................
79
4.2.1.5 Sub-Package Interfaces ............
81
4.2.1.6 Sub-Package Initialization ........
81
4.2.2 On-Line Retrieval Specifications ......
81
4.2.2.1 Functional Specificaion ...........
81 4.2.2.1.1 Receive Retrieval Requests
.... 83
4.2.2.1.2 On-Line/Off-Line Retrieval
Separation ....................
83
4.2.2.1.3 On-Line/Catalogue Consult .....
84
4.2.2.1.4 Access Check ..................
8
4.2.2.1.5 Retrieval of CIF ..............
86
4.2.2.1.6 Delivery of Retrieval Result ..
87
4.2.2.2 On-Line Retrieval Software
Structure .........................
87
4.2.2.3 Data Flow and Control Logic .......
89
4.2.2.4 Sub-Package Data ..................
92
4.2.2.5 Sub-Package Interfaces ............
93
4.2.2.6 On-Line Retrieval Initialization ..
93
4.2.3 Off-Line Retrieval Specifications .....
94
4.2.3.1 Functional Speification ..........
94
4.2.3.1.1 Activate Off-Line Retrieval ...
96
4.2.3.1.2 Off-Line Volume Determination .
96
4.2.3.1.3 Test of Mounted Volume ........
96
4.2.3.1.4 Volume Mount ..................
97
4.2.31.5 Off-Line Catalogue Consult ....
97
4.2.3.1.6 Access Check ..................
97
4.2.3.1.7 Retrieve CIF ..................
97
4.2.3.1.8 Delivery of Retrieval Result ..
98
4.2.3.1.8.1 Volume Mount Refusal ......
98…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.3.1.8.2 Access Check Failure ......
98
4.2.3.1.8.3 CIF Not Found .............
99
4.2..1.8.4 CIF Found .................
99
4.2.3.2 Software Structure ................
99
4.2.3.3 Data Flow and Control Logic .......
101
4.2.3.3.1 Control Elements ..............
101
4.2.3.3.2 Control Logic ................
101
4.2.3.4 Sub-Package Data ..................
104
4.2.3.5 Sub-Package Interfaces ............
104
4.2.3.5.1 Off-Line-Count ................
104
4.2.3.5.2 Off-Line-Disk-Lock ............
104
4.2.3.5.3 Lock-Table....................
104
4.2.3.5.4 Off-Line-Retrieval-Susp. ......
105
4.2.3.6 Sub-Package Initialization ........
105
4.2.4 Dump Specifications ...................
105
4.2.4.1 Functional Specification ..........
105
4.2.4.1.1 Receive Dump Requests ......... 107
4.2.4.1.2 Check Mounted Volume ..........
107
4.2.4.1.3 Volume Mount Procedure ........
107
4.2.4.1.4 Dump Procedure ................
108
4.2.4.2 Software Structure ...............
108
4.2.4.3 Data Flow and Control Logic .......
110
4.2.4.3.1 MMS Main Control ..............
110
4.2.4.3.2 TEP Main Control ..............
110
4.2.4.3.3 Dump Control...................
110
4.2.4.3.3.1 Perorm Dump on Usual
Volume Control ............
113
4.2.4.3.3.2 Perform Dump on New
Volume Control ............
117
4.2.4.4 Sub-Package Data ..................
118
4.2.4.5 Sub-Package Interfaces ...........
118
4.2.4.5.1 Off-Line-Disk-Lock ............
118
4.2.4.5.2 Lock-Table ....................
118
4.2.4.5.3 Lock-Cat ......................
118
4.2.5 Supervisor Command Specifications .....
118
4.2.5.1 Functonal Specification ..........
118
4.2.5.1.1 Receive and Detect Command ....
122
4.2.5.1.2 Off-Line Retrieval Off ........
122
4.2.5.1.3 Off-Line Retrieval On .........
122
4.2.5.1.4 Off-Line Retrieval Suspended ..
122…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.5.1.5 Request Volume Table Entry ....
122
4.2.5.1.6 Request Volume Table Contents .
123
4.25.1.7 Delete Volume Table Entry .....
123
4.2.5.1.8 Start-Up Command ..............
123
4.2.5.1.9 Close Down Command ............
123
4.2.5.2 Software Structure ................
124
4.2.5.3 Data Flow and Control Logic ......
126
4.2.5.3.1 Main Module Control Logic .....
126
4.2.5.3.2 Command Control Logic .........
128
4.2.5.3.2.1 Off-Line Retrieval Off
Control Logic .............
128
4.2.5.3.2.2 Off-Line Retrieval On
Control Logic ............. 128
4.2.5.3.2.3 Off-Line Retrieval Susp.
Control Logic .............
128
4.2.5.3.2.4 Volume Table Entry Control
Logic .....................
128
4.2.5.3.2.5 Volum Table Contents
Control Logic .............
128
4.2.5.3.2.6 Delete Volume Entry
Control Logic .............
128
4.2.5.3.2.7 Start-Up Command Control
Logic .....................
129
4.2.53.2.8 Close-Down Command Control
Logic .....................
129
4.2.5.4 Sub-Package Data ..................
138
4.2.5.5 Sub-Package Interfaces ............
138
4.2.5.5.1 Lock-Table Interface ..........
139
42.5.5.2 Off-Line-Retrieval-Susp.
Control Logic .................
139
4.2.5.5.3 Off-Line-Retrieval-On/Off
Control Logic .................
139
4.3 MEMORY LAYOUT .............................
139
4.3.1 Program Aea ..........................
139
4.3.2 Main Memory Data Area .................
140
4.3.3 On-Line Disk Data Area ................
140
4.3.4 Off-Line Disk Data Area ...............
140
APPENDIX A .......................................
144
A.1 SPECIFIC STORAGE AND RETRIEVAL KEYS .......
144
A.1.1 Incoming Message After Analysis ....... 144
A.1.2 Incoming Message After Selection
of Nominal Distribution List ..........
144
A.1.3 First Draft ...........................
145
A.1.4 Comments .............................
145
A.1.5 Release Notification ..................
145
A.1.6 Released Messages .....................
145
A.1.7 Released Messages after Assignment of
Transaction Keys ......................
146
A.1.8 Log Items ............................
146…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̲
The Package Specification for Storage and Retrieval
Package (SAR) CPS/SDS/007 is written to fulfil the
following objectives:
1) To provide etailed definition of the package function
and software architecture.
2) To provide user operational and development personnel
details of the ongoing analysis.
3) To define in detail the interfaces with other packages
and to describe their faciities.
The specification contains a description of the package
to a level of a few software statements as lowest detail.
Higher level design specification can be found in the
document system design listed in the next section,
applicable documens.
All interfaces and data are described in this specification
and contained in the software Interface Control Document
and Database Design Document respectively.
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̲
he following documents represent a baseline for this
specification:
- CPS/210/SYS/0001
CAMPS System Requirements
- CPS/SDS/001
CAMPS System Design Specification…86…1 …02… …02…
…02… …02…
1.2.2 P̲r̲o̲j̲e̲c̲t̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
Reference documents are as follows:
- CPS/230/ICD/0001
User Procedures and Associated Formats
- CPS/230/ICD/002
Supervisor Commands and Procedure
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̲
Dump: Transferring messages and transactions
from on-line disk to off-line disk.
Off-Line Disk: Disk volume used for storage of mssages
and transactions.
Item: Messages and transactions stored
and retrieved by SAR.
Cross Office
Delay: Time from the creation of a message
to the departure from the site or
time of reception on the site until
presentation on terminal positin.
Interleaving: Interruption at ordinary SAR functions
i.e. on-line storage, on-line retrieval,
off-line retrieval, dump and supervisor
commands.
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
ISQ Incoming Storage Queue
RRQ Retrieval request Queue
FIFO First In First Out
SFM Storage and File Management Package
QEL Queue Element
OROF Off-Line Rerieval Off
ORON Off-Line Retrieval On
ORSU Off-Line Retrieval Suspended
VOCL Volume Control List
VOIL Volume Identification List
VONM Volume Naming
VODL Volume Deletion
SCQ Supervisor Command Queue
MAQ Mount Acknowledge Queue
DCQ Dump Commnd Queue
CIF CAMPS Information Field
ISTOQ Incoming Storage Time-Out Queue
APP Application
TD Terminal Designator
RC5 Return Code 5
PD Preliminary Design
SP.PD Sub-Package Preliminary Design
MMS Message Management System
IS Intermediate Sorage
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
This chapter includes the requirements pertinent to
SAR at package level.
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̲ ̲C̲o̲n̲c̲e̲p̲t̲
SAR provides functioal capabilities for on-line storage
of all incoming and outgoing messages in an intermediate
storage (up to a few days depending on traffic and
assigned disk space and allowed fill rate). After that,
the CIFs are kept for a period of at least 30 das on
offline disk volumes (long term storage).
SAR supports retrieval of CIFS from the intermediate
storage within a specified time limit.
Retrieving off-line is possible within a time limit
to be specified measured from when off-line volume
ismounted. The functions carried out by SAR are then:
- Retrieve on-line
- Store on-line
- Store off-line
- Retrieve off-line
2.1.1.1 O̲n̲-̲L̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲
The on-line CIFs handled by SAR are on-line resident
for at least 24 hours. On-line storae is characterized
by the fact that no mounting of physical media is required
to retrieve the CIF. Actual time span for on-line storage
is in the order of days.
2.1.1.2 O̲f̲f̲-̲L̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲
An off-line storage process is carried out by dumping
CIF to an off-line volume, when they have been on-line
resident for at least 24 hours. Off-line strage may
require, that a media must be loaded prior to retrieval.
2.1.1.3 S̲u̲b̲j̲e̲c̲t̲ ̲t̲o̲ ̲S̲t̲o̲r̲a̲g̲e̲
Data for storage and retrieval are operational and
service messages except for the categories: security
classification CTS, special handling ATOMAL an any
encrypted message. Further data messages are stored
only for reruns. The CIFs for on-line storage are
as follows:
First draft, Released messages, Incoming analysed +
possible corrected messages, Release notifications
and Comment submitted
2.1.1.4 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲K̲e̲y̲s̲
The CIFs for storage are catalogued under a combination
of the keys: TOC (time of occurrence), TOC window,
DTG (release), ORIG. HQ., ITEM REF ID, CHANNEL ID,
CHANNEL SERIAL NUMBER, STATION ID, STATION SERIALNUMBER,
FILE TIME, SICs. Retrieval of the CIFs is achieved
by combining the search keys depending on the category
of CIF.
2.1.1.5 R̲e̲t̲r̲i̲e̲v̲a̲l̲
Retrieval of stored CIF using a combination of the
previous mentioned key can be achieved from both on-ine
or off-line storage media.
2.1.1.5.1 O̲n̲-̲L̲i̲n̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
The on-line disk contains the on-line CIFs which can
be retrieved to a terminal position which has already
gained knowledge of the CIF by either havin prepared
it or previously received. Exception is that the supervisor
can retrieve all stored information.
2.1.1.5.2 O̲f̲f̲-̲L̲i̲n̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
The off-line CIFs reside on a number of off-line volumes
which are mounted when an off-line retrieval proces
is in progress.
2.2 P̲A̲C̲K̲A̲G̲E̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
The next two sub-sections 2.2.1 and 2.2.2 contain a
functional description under normal operations and
special circumstances respectively.
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Main functions included in SAR are:
on-line storage
- on-line retrieval
- off-line retrieval
- off-line storage (dump)
2.2.1.1 O̲n̲-̲L̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲
Storage on-line means storage on intermediate storage
of CIFs which have completed processing. The five categories
of items for storge are stored according to the events
listed below:
Incoming Messages.
Storage after succesful passing analysis including
possible correction by message service.
Released Messages
Storage when the positive release decision has been
given by the releasing officer.
First Draft
Storage after completion of new message preparation
format .
Comments
Storage after completion of new comment preparation
format G1.
Release Notifications
Storage after completion of the release decision
Log CIFs
Storage after completion of a log CIF, i.e. every 10
minutes
The packages responible for the above mentioned actions
initiate a storage process as described next.
During step 1a-d, the application modules request SAR
to initiate a storage process by queuing a request
in the incoming storage queue (ISQ). The on-line catalogu
is updated for each storage process with a new entry
(2) and upon this completion, SAR requests MMS to store
the respective item by issuing a STORE ITEM command
(3) with input parameter View Reference. Application
is acknowledged of storage compleion (4). The on-line
storage process is depicted overleaf in figure 2.2.1.1-1.
Fig. 2.2.1.1-1…86…1 …02… …02… …02… …02…
2.2.1.2 O̲f̲f̲-̲L̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲(̲D̲u̲m̲p̲)̲
The communication during an off-line dump is carried
out as shown on figure 2.2.1.2-1. Incarnation is achieved
by either MMS (1a) or Supervisor oprator (2). MMS sends
an intermediate storage warning to SAR. Supervisor
(TEP) sends a perform dump command until time specified
to SAR. The on-line catalogue is consulted to determine
which CIFs to dump (3a) (3b) according to the TOC field
in each IF entry. Dumping the CIFs are carried out
sectionwise through the following sequence of actions:
- Dump CIF command for MMS (3c)
- Dump CIF completion code for SAR (3d)
- Update off-line catalogue (3e)
- Update on-line catalogue (3f)
- Clea item command for MMS (3g)
Total completion of the dump process is acknowledged
to TEP (supervisor) report printer (3h).
figure 2.2.1.2-1
2.2.1.3 R̲e̲t̲r̲i̲e̲v̲a̲l̲
Refer figure 2.2.1.3-1.
Retrieval of the previously stored information takes
place from either on-line volume or off-line by placing
a retrieve command in theretrieve request queue (RRQ)
of SAR, which then returns one out of three things
to the requesting application.
a) A view ref. referencing the retrieved CIF
b) Completion code telling the reason for improper
completion
c) Catalogue informationfor display
2.2.1.3.1 O̲n̲-̲L̲i̲n̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
a) R̲e̲t̲u̲r̲n̲i̲n̲g̲ ̲a̲ ̲V̲i̲e̲w̲ ̲R̲e̲f̲.̲
After reception and detection of an on-line retrieval
command (1a), the on-line catalogue is consulted
to determine the CIF-id and view-id corresponding
to the retrieval key prameters (1b). A RETRIEVE
CIF command with CIF-id and view-id as input parameter
is delivered to MMS (1c). MMS returns a view ref.
referencing the generated temporary CIF (1d) which
is handled further on by SAR to requestor after
security and accss check (1e).
b) R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲s̲
Improper completion of a retrieval procedure can
be caused by:
- Not found referenced CIF
- Retrieval intermediately impossible
Completion code is returned through step 1e.
c) C̲a̲t̲a̲l̲o̲g̲u̲e̲ ̲D̲s̲p̲l̲a̲y̲
In case that a catalogue display is required the
on-line catalogue is consulted. The entries fulfilling
the retrieval key parameters are returned through
step 1e.
2.2.1.3.2 O̲f̲f̲-̲L̲i̲n̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
According to the TOC retrieval parameter an off-line
retrieval process is initiated. This is serviced at
a lower priority level than on-line retrieva and will
result in three different actions.
a) O̲r̲d̲i̲n̲a̲r̲y̲ ̲O̲f̲f̲-̲L̲i̲n̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
Ordinary off-line retrieval is carried out by requesting
the supervisor to mount a specified volume (2a).
Determination of volume is done by consulting a
table contaiing information about time intervals
on off-line volumes. As for off-line storage a
completion code is returned (2b) telling whether
the volume is mounted or cannot intermediately
be mounted.
When mounted MMS is asked to open the off-line
volume directory and CIF area by the command GET
MMS CATALOGUE (2c). SAR consults the directory
for determination of view-ref of wanted CIF (2d).
A RETRIEVE CIF command is handed by SAR to MMS
(2e), which returns the previously mentioned view
ref. (2f) This again is passed to the calling
application via its delivery queue (2g) by SAR.
b) O̲f̲f̲-̲L̲i̲n̲e̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲s̲
If the off-line volume cannot intermediately be
mounted, the application is acknowledged by a completion
code in its dlivery queue (2h).
This completion code can as well tell that referenced
CIF not found or off-line retrieval intermediately
impossible. The need for a reduction in time interval,
because interval covers 2 volumes, is also acknowledge
back via copletion codes.
c) O̲f̲f̲-̲L̲i̲n̲e̲ ̲C̲a̲t̲a̲l̲o̲g̲u̲e̲ ̲D̲i̲s̲p̲l̲a̲y̲
As for on-line retrieval the catalogue entries
corresponding to the retrieval search keys are
returned (2g).
Figure 2.2.1.3-1
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̲
Functional responsibilities included in the storage
and retrieval package are specified in the next paragraphs.
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̲
Initialization procedure performs the initiation of
main memory collect area catalogue files, semaphores
and status information.
Main memory is initiated by loading the control area
with initial vales. The three locations shall be loaded:
PRI ̲AREA: pri ̲area start address
DTG ̲AREA: dtg ̲area start address
no ̲of-PRI ̲ENT 0
On-line catalogue files are created during initiaization.
The TOC ̲FILE ̲ON locations in information area are all
set to 0, except for TOC start time which is set upon
first storage.
Off-Line catalogue files are created and initiated
when dump is incarnated. Volume table is initialized
as an empt table with no entries.
The following semaphores are initiated:
- lock ̲cat to neutral stage
- off-line ̲disk ̲lock to neutral stage
- lock ̲table to neutral stage
- off-line ̲retrieval ̲susp to neutral stage
Status information is initiated as fllows:
- off-line ̲retrieval ̲on/off is reset to the value
on
- off-line ̲count to 0
Further the filling rate of intermediate storage is
set by the MMS command SET INTERMEDIATE STORAGE THRESHOLD.
2.2.2.1.2 C̲l̲o̲s̲e̲-̲D̲o̲w̲n̲
Close-down of SAR is performed this way. SR will operate
normally until close-down command from SSC is received.
Detailed close-down action is described in 4.2.5.1.9.
2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
Start-up command from SSC causes SAR to take the following
actions. Checkpointed ISQ is re-establishd so all pending
storage requests are queued again. Main memory control
area is initialized as described under initialization.
Semaphore and status information is set to the values
as contained in the initialization section.
2.2.2.2 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
2.2.2.2.1 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲
Storage requests for SAR are checkpointed i.e. ISQ
QELs are checkpointed at their arrival to queue and
released when storage procedure has terminated.
2.2.2.2.2 R̲e̲c̲o̲v̲e̲r̲y̲
Recovery of SAR is requested b SSC. SSC specifies which
kind of recovery to be performed. Recovery actions
performed are described in CPS/SDS/001 figure 5.10.1.2.1.3-1.
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̲
2.2.2.3.1 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
Errors detected by SAR are of the following types:
- Errors in storage keys during storage of messages
ad transactions
- Error code received during CSF section dump
- QMON delivery error
- Software errors
2.2.2.3.2 E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
The previous mentioned detected errors (refer 2.2.2.3.1)
are handled in the following way, described in the
sam order as they are detected.
- Storage request and retrieval keys are delivered
to SSC error queue.
- Error handling, caused by failure in volume name
in CSF section dump command is to complete dump
as normal with a report to supervisors report
