top - download
⟦ff5262f3b⟧ Wang Wps File
Length: 18753 (0x4941)
Types: Wang Wps File
Notes: CPS/SDS/001
Names: »1382A «
Derivation
└─⟦b58ce20e9⟧ Bits:30006060 8" Wang WCS floppy, CR 0092A
└─ ⟦this⟧ »1382A «
WangText
…02…CPS/SDS/001
…02…HUH/811020…02……02…
CAMPS SYSTEM DESIGN SPECIFICATION
…02…ISSUE 1.1…02…CAMPS
…06…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.17 LOG PACKAGE ............................ 664
5.17.1 General ............................. 664
5.17.1.1 Purpose and Scope ............... 664
5.17.1.2 Applicable Documents and Project
References Special for Section
5.17 ............................
664
5.17.1.3 Terms and Abbreviations Special
for Section 5.17 ................ 664
5.17.1.3.1 Terms ....................... 664
5.17.1.3.2 Abbreviations ............... 664
5.17.2 Summary of Requirements ............. 665
5.17.2.1 Package Description ............. 665
5.17.2.2 Package Functions ............... 668
5.17.2.2.1 Main Functions at Normal
Operation ...................
668
5.17.2.2.2 Functional Responsibilities . 668
5.17.2.2.2.1 Initialization, Close
Down and Restart ........
668
5.17.2.2.2.1.1 Initialize and
Restart .............
669
5.17.2.2.2.1.1.1 Start Up Types .. 669
5.17.2.2.2.1.1.2 Log Package
Initialize ......
670
5.17.2.2.2.1.2 Close Down .......... 671
5.17.2.2.2.2 Checkpointing and
Recovery ................
671
5.17.2.2.2.2.1 Checkpointing ....... 671
5.17.2.2.2.2.2 Recovery ............ 672
5.17.2.2.2.2.2.1 Warm 1 .......... 672
5.17.2.2.2.2.2.2 Warm 2 .......... 672
5.17.2.2.2.3 Error Detecting and Error
Handling ................
673
5.17.2.2.2.4 Integrity of Operation .. 674
5.17.2.2.2.5 Data Collection ......... 674
5.17.2.2.2.6 Security ................ 674
5.17.2.3 Characteristics ................. 674
5.17.2.3.1 Timing ...................... 674
5.17.2.3.1.1 Collect Run Time ........ 675
5.17.2.3.1.2 Trace Run Time .......... 675
5.17.2.3.2 Throughput .................. 675
5.17.2.3.3 Flexibility ................. 676
5.17.2.3.4 Accuracy .................... 676
5.17.3 Environment ......................... 676
5.17.3.1 Equipment ....................... 676
5.17.3.2 Software ........................ 676
5.17.3.2.1 System Software ............. 676
5.17.3.2.2 Development Support Software 677
5.17.3.3 Interfaces ...................... 677
5.17.3.3.1 External Interfaces ......... 677
5.17.3.3.2 Package Interfaces .......... 677
5.17.3.3.2.1 Application Package
Interface ...............
677
5.17.3.3.2.2 SSC Interface ........... 678
5.17.3.3.2.3 TEP Interface ........... 678
5.17.3.3.2.4 CSF Interface ........... 678
5.17.3.3.2.5 MMS Interface ........... 679
5.17.3.3.2.6 SAR Interface ........... 679
5.17.3.4 Functions Maintained by Other
Packages ........................
681
5.17 L̲O̲G̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.17.1 G̲e̲n̲e̲r̲a̲l̲
5.17.1.1 P̲u̲r̲p̲o̲s̲e̲ ̲a̲n̲d̲ ̲S̲c̲o̲p̲e̲
N/A.
5.17.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̲,̲ ̲S̲p̲e̲c̲i̲a̲l̲
̲f̲o̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲ ̲5̲.̲1̲7̲
N/A.
5.17.1.3 T̲e̲r̲m̲s̲ ̲a̲n̲d̲ ̲A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲,̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲f̲o̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲ ̲5̲.̲1̲7̲
5.17.1.3.1 T̲e̲r̲m̲s̲
Applications - packages such as TEP which contribute
with log information to the LOG package.
Diag.-id. - Diagram identification. Identify the number
of the diagram and explain the diagram page out of
the total number.
5.17.1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
N/A.
5.17.2 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
5.17.2.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The tasks of the LOG package are:
a) Collect log records from other applications.
b) Send the incoming log information to SSC for checkpointing.
c) Send the incoming log information to TEP for printout.
d) Store the log information by means of MMS and SAR
when five log records are collected or when 30
seconds have elapsed.
e) Recover the checkpointed log records after system
break down.
f) Trace log records requested by TEP using SAR to
retrieve the log CIF-ref. in question.
A chart with the LOG package and its inter-relationships
with other packages is shown on fig. 5.17.2.1-1.
Explanation to the inter-relationships chart fig. 5.17.2.1-1:
Step 1: The application transfers the log records to
LOG.
Step 2: When a specific log record is safely stored,
an acknowledge is returned.
Step 3: The incoming log records are transferred to
SSC for checkpointing.
Step 4: Log record checkpoint acknowledge returned
to LOG.
Step 5: The incoming log records are transferred to
the TEP supervisor log print queue.
Step 6: Request to MMS for creation of log CIF.
Step 7: Return of the created log CIF-ref.
Step 8: Append log record to MMS.
Step 9: Set-up time monitor in CSF.
Step 10: Receive time out from time monitor.
Step 11: Request SAR to store the log CIF.
Step 12: TEP request LOG to retrieve log records.
Step 13: LOG request SAR to find a specified log
CIF-ref.
Step 14: Return of requested log CIF-ref.
Step 15: Retrieve log records from disk.
Step 16: Return the traced log records.
Fig. 5.17.2.1-1…01…LOG Inter-Relationships.
5.17.2.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
5.17.2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲a̲t̲ ̲N̲o̲r̲m̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
The main functions at normal operation are:
a) Collection of log records from TEP and THP.
TEP and THP transfer the log records to the LOG
package via buffers and queue elements.
The log records are collected in main memory.
b) Append the collected log records.
Every 30 seconds or when 5 log records are collected,
the collected log records are appended to the log
CIF.
Every 10 minutes the present used log CIF-ref.
are stored by SAR and a new requested.
Log records are stored online for a period of at
least 24 hours and offline for at least 30 days.
c) Checkpointing of log records.
The incoming log records are checkpointed by SSC
in the standby PU.
d) Log record printout.
The incoming log records are queued in the supervisor
log print queue.
e) Trace of stored log information.
The stored log information is retrieved and traced
on supervisor request. The trace command and trace
keys are sent to LOG via the TEP package.
The requested log records are appended in a trace
CIF and the trace CIF-ref. is queued in the supervisor
print queue.
5.17.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̲
5.17.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̲
5.17.2.2.2.1.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲e̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
The initialize and restart software is placed at the
LOG package start up entry point.
5.17.2.2.2.1.1.1 S̲t̲a̲r̲t̲-̲u̲p̲ ̲T̲y̲p̲e̲s̲
D̲e̲a̲d̲ ̲1̲,̲ ̲D̲e̲a̲d̲ ̲2̲ ̲a̲n̲d̲ ̲W̲a̲r̲m̲ ̲3 - Used after ordered close
down and used as system initialize.
These start up types are all treated as Dead 1. No
recovery actions are taken and all the used data area
will be initialized.
C̲o̲l̲d̲
Cold is treated like Dead 1 apart from clearing all
online log CIFs.
W̲a̲r̲m̲ ̲1 - Used after total system error.
Warm 1 is treated like Dead 1 apart from recovering
the last used CIF-ref.
W̲a̲r̲m̲ ̲2 - Used after switch-over.
Warm 2 is treated like Warm 1 apart from recovering
of the checkpointed log records.
I̲n̲s̲e̲r̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲t̲a̲n̲d̲ ̲b̲y̲ ̲P̲U̲
When the stand-by PU is inserted, all logging activities
will be normal 30 sec. after the initialize command
from SSC is executed.
For detailed description please refer CPS/SDS/004,
section 5.17.2.2.2.1.1.1.
5.17.2.2.2.1.1.2 L̲o̲g̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲i̲t̲i̲a̲l̲i̲z̲e̲
The initialize command from SSC will cause the following
actions:
a) Identify command and call INIT routine
b) If the command is COLD, then CLEAR ̲CIF is called.
c) Send completion code to SSC.
T̲h̲e̲ ̲I̲N̲I̲T̲ ̲r̲o̲u̲t̲i̲n̲e̲:
1) Read queue element from SSC and get init. file-ID
2) Read init. file and load initialize parameters
into log data area: Record validation table,
log trace table.
3) Request 10 min. and 30 sec. time out.
4) Initialize internal log date area.
5) Initialize flags.
6) Initialize semaphores.
7) Initialize coroutines
8) Create and checkpoint log CIF
9) Return to calling routine
T̲h̲e̲ ̲C̲L̲E̲A̲R̲ ̲C̲I̲F̲ ̲r̲o̲u̲t̲i̲n̲e̲:
1) Request online CIF-ref. (SAR)
2) Clear online CIF contents (MMS)
3) Return to calling routine
5.17.2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
The close down software is resident in the COLLECT
coroutine and is called COMMAND.
When COLLECT receives a close down command from SSC,
the following actions are taken:
a) Empty incoming log queue.
b) Append the collected log records to the log CIF.
c) Update CIF-index table
d) Store log CIF
e) Send completion code to SSC.
For further description please refer to section 4.2.1.3.2.
5.17.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̲
5.17.2.2.2.2.1 C̲h̲e̲c̲k̲ ̲P̲o̲i̲n̲t̲i̲n̲g̲
The checkpointing of the incoming log records is implemented
by SSC.
Before the log package sends log records for checkpointing,
they are assigned log record serial numbers. The log
record serial number consists of a log record count
(0-4) and a checkpoint serial number.
The log record count indicates the stand-by PU buffer
address. The checkpoint serial number are used by LOG
when the checkpointed log records are recovered.
Max. five log records are checkpointed by SSC in the
standby PU. Earlier checkpointed log records will
be overwritten. The record number tells which one
to overwrite.
The present used log CIF is checkpointed on disk.
5.17.2.2.2.2.2 R̲e̲c̲o̲v̲e̲r̲y̲
The recovery routines are called when a recovery command
is received from SSC.
There are two recovery commands: Warm 1 and Warm 2.
5.17.2.2.2.2.2.1 W̲a̲r̲m̲ ̲1
A Warm 1 command will cause the following actions:
a) Identify command and call INIT routine.
b) Call REC ̲CIF routine
c) Send completion code to SSC.
T̲h̲e̲ ̲R̲E̲C̲ ̲C̲I̲F̲ ̲r̲o̲u̲t̲i̲n̲e̲
1) Recover the last used CIF-ref. from disk.
2) Return to calling routine.
5.17.2.2.2.2.2.2 W̲a̲r̲m̲ ̲2
A Warm 2 command will cause the following actions:
a) Identify command and call INIT routine.
b) Call REC ̲CIF routine
c) Call REC ̲LOG routine
d) Send completion code to SSC.
T̲h̲e̲ ̲R̲E̲C̲ ̲L̲O̲G̲ ̲r̲o̲u̲t̲i̲n̲e̲
1) Receive the five checkpointed log records from
SSC.
2) Recover the proper log records in the log collect
data area.
3) Set log record serial number.
4) Return to calling routine.
5.17.2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Errors detected by LOG are:
a) Error in the incoming log records. (length, type)
Checkable log parameters are validated for upper
and lower boundaries.
b) No buffer or CIF available from MMS.
c) No queue element available from CSF.
d) Error in trace commands and trace keys from TEP.
E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
All errors are reported to SSC.
Error a: The incoming log record is deleted and
a completion code is returned to the sender.
Error b
and c: The collect action is stopped and dummy
mode entered.
Error d: The command is deleted and a completion
code returned to TEP.
5.17.2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
To avoid errors in the log collection mechanism, all
the incoming log records are validated.
The checkable log parameters are checked for upper
and lower boundaries. The log record type and length
is also checked.
5.17.2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
The collection of log records is done by means of queue
elements and the buffer functions implemented by CSF.
The log records are transferred to the incoming log
queue by sending a queue element with a reference to
a log record buffer.
When a log record is received by LOG, an acknowledge
queue element is returned to the log record sender
when the log record is safety stored.
5.17.2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
No security action is performed by LOG.
5.17.2.3 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
5.17.2.3.1 T̲i̲m̲i̲n̲g̲
The incoming log records will be stored on disk when
30 seconds have elapsed or 5 records are collected.
Every 10 minutes, the presently used CIF will be closed
and stored. This action is only taken if the CIF contains
appended log records.
Log records are stored online for a period of at least
24 hours.
Log records are stored offline for a period of at least
30 days.
5.17.2.3.1.1 C̲o̲l̲l̲e̲c̲t̲ ̲R̲u̲n̲ ̲T̲i̲m̲e̲
The CPU time used by LOG during the log collect procedure:
a) For each log record, collected, va-
lidated, checkpointed and queued
for print out : 1
ms
b) Appending of five collected
log records : 0.2
ms
c) Storage of old log CIF and re
quest of new log CIF every 10 min. : 0.1
ms
Estimated average CPU time used by
LOG for each received log record : 1.1
ms
Estimated CPU time used by LOG in
a busy min. : 160
ms
5.17.2.3.1.2 T̲r̲a̲c̲e̲ ̲R̲u̲n̲ ̲T̲i̲m̲e̲
The average CPU time used by log,
tracing a ten busy minute log CIF
is estimated to : 100
ms
The trace procedure is executed in such a way that
no significant performance reduction occurs.
5.17.2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The amount of log records are estimated to be 145 log
records per busy minute, 7000 log records per busy
hour and 35000 per busy 24 hours.
5.17.2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The modularity of the LOG package facilitates implementation
of changes in the log record format and trace format
as well as changes in the log record collect and store
timing.
5.17.2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
Not applicable to LOG.
5.17.3 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲s̲
5.17.3.1 E̲q̲u̲i̲p̲m̲e̲n̲t
The software within the LOG package is online resident
in one processing unit.
Main memory data area consists of buffer and data area.
Main memory buffer area size will be 1000 words.
Main memory data area size will be 900 words.
5.17.3.2 S̲o̲f̲t̲w̲a̲r̲e̲
5.17.3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The system software environment to LOG are:
- CAMPS System Function
- Message Management System
5.17.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 support software is standard DAMOS and
TOS resident in a single CR 80D.
5.17.3.3 I̲n̲t̲e̲r̲f̲a̲c̲e̲
5.17.3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
There are no external interfaces to LOG.
5.17.3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
An interface overview is shown in figure 5.17.3.3.2-1.
5.17.3.3.2.1 A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The LOG package receive log records from Traffic Handling
Package and Terminal Package. This interface is referred
to as application package interface.
The application package interface is implemented by
means of queue elements and the buffer function implemented
by CSF.
The buffers are used to transport the log records from
the applications to LOG.
When a log record is safely stored an acknowledge is
returned to the sender in an answer queue.
5.17.3.3.2.2 S̲S̲C̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The interface to SSC is implemented by means of queues.
The queues are used to:
a) Transfer commands from SSC
b) Transfer log records to SSC for checkpointing
c) Receive acknowledge from SSC
d) Send completion codes to SSC
5.17.3.3.2.3 T̲E̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The interface to TEP is implemented by means of queues,
buffers, and a common buffer area. The common buffer
area may contain up to 50 log records waiting for printout.
Incoming log records are stored in a common buffer
area, queue elements with buffer pointers are sent
to the TEP printout queue.
Log trace commands are sent to LOG via a queue. The
queue elements contain pointers to buffers with trace
keys. The traced log records are stored in a CIF and
the CIF-ref. will be returned to TEP in a queue element.
5.17.3.3.2.4 C̲S̲F̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The interface to CSF is implemented by means of monitor
calls.
The monitor calls are used e.g. when requesting for
a queue element and time out.
Please refer to CPS/ICD/009.
5.17.3.3.2.5 M̲M̲S̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Each command from an application process to MMS is
implemented as a system call to MMON.
For detailed description please refer to CPS/ICD/009.
5.17.3.3.2.6 S̲A̲R̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The SAR interface is implemented with queues.
The queues are used to:
a) Request SAR for a CIF-ref. Input is a time interval
and SAR log-indicator.
b) Receive CIF-ref. from SAR.
c) Request SAR for cataloging and storage of a CIF.
Input is a CIF-ref.
Fig. 5.17.3.3.2-1…01…LOG Interfaces
Queue names used in fig. 5.17.3.3.2-1.
Q 1 IN LOG Incoming log queue
Q 2 APP ANSWQ Application answer queue
Q 3 IN COMM Incoming command queue
Q 4 COMM RESP Command response queue
Q 5 CHKP RESP Checkpoint response queue
Q 6 CTQ Checkpoint transmission
queue
Q 7 30 S TIM 30 seconds time out queue
Q 8 10MTIM 10 minutes time out queue
Q 9 RRQ Retrieval request queue
Q 10 RET RESP Retrieve response queue
Q 11 ISQ Incoming storage queue
Q 12 TRACE COMM Trace command queue
Q 13 SPQ Supervisor print queue
Q 14 SLPQ Supervisor log print queue
5.17.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̲
The functions maintained by other packages are:
- Recovery by SSC
- Error handling by SSC
- Check pointing by SSC
