top - download
⟦e7e239aa2⟧ Wang Wps File
Length: 14301 (0x37dd)
Types: Wang Wps File
Notes: CAMPS SYS. DES. SPEC.
Names: »0434A «
Derivation
└─⟦74b766e5b⟧ Bits:30006076 8" Wang WCS floppy, CR 0033A
└─ ⟦this⟧ »0434A «
WangText
…02…CPS/SDS/001
…02…RIM/810115…02……02…
CAMPS
SYSTEM
DESIGN
SPECIFICATION
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.16 LOG PACKAGE ........................
5.16.1 Summary of Requirements ..........
5.16.1.1 Package Description ..........
5.16.1.1.1 Function Summary .........
5.16.1.1.1.1 Log Collection ........
5.16.1.1.1.2 Log Printouts .........
5.16.1.1.1.3 Log Storage ...........
5.16.1.1.1.4 Retrieval of Log
Information ...........
5.16.1.1.2 Interface Summary ........
5.16.1.1.2.1 Internal Interface ....
5.16.1.1.2.2 External Interface ....
5.16.1.1.2.3 Explanation to
Interface Chart .......
5.16.1.2 Package Function .............
5.16.1.2.1 Collection of Log Records
5.16.1.2.1.1 Main Memory Log
Collection ............
5.16.1.2.2 Online Storage of Log
Records ..................
5.16.1.2.2.1 Creation of Log Item ..
5.16.1.2.2.2 Appending Log Records
to Item ...............
5.16.1.2.2.3 Storage of Log Item ...
5.16.1.2.3 Off-line Storage of Log
Item .....................
5.16.1.2.4 Print-out of Log Records
5.16.1.2.5 Retrieval of Log Records
5.16.1.2.5.1 Retrieval Procedure ...
5.16.1.2.5.2 Generating Delivery
Status Information ....
5.16.1.2.6 Timespan for Information
Needed for Transaction
Status ...................
5.16.1.2.7 Timespan in Tracing
Procedure ................
5.16.1.2.8 Timespan for Delivery
Status ...................
5.16.1.2.9 Recovery .................
5.16.1.3 Package Control ..............
5.16.1.3.1 Initialization ...........
5.16.1.3.2 Error Handling ...........
5.16.1.3.2.1 Error Detected by LOG .
5.16.1.3.2.2 Error Handled by SS&C .
5.16.1.3.2.3 Error Actions .........
5.16.1.4 Package Characteristics ......
5.16.1.4.1 Performance ..............
5.16.1.4.1.1 Throughput ............
5.16.1.4.1.2 Storage Capacity ......
5.16.1.4.1.3 Timing of LOG .........
5.16.1.5 Design and Construction ......
5.16.1.5.1 Software Construction ....
5.16.1.6 Documentation ................
5.16.1 S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
5.16.1.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
5.16.1.1.1 F̲u̲n̲c̲t̲i̲o̲n̲ ̲S̲u̲m̲m̲a̲r̲y̲
The main task of the LOG is to collect log records
via CSF log generator and store them via SFM and SAR
on disk for a possible later retrieval in conjunction
with a transaction status display, or tracing of log
information or delivery status information. Refer
to figure 5.16.1.1.1.
5.16.1.1.1.1 L̲o̲g̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
The LOG collect log information for transactions.
This include those terminated before completion.
Further log is recorded for incoming- and outgoing
messages and for channel discontinuity.
5.16.1.1.1.2 L̲o̲g̲ ̲P̲r̲i̲n̲t̲o̲u̲t̲s̲
The log records are queued for printout at the supervisor
printer each time the log is recorded.
5.16.1.1.1.3 L̲o̲g̲ ̲S̲t̲o̲r̲a̲g̲e̲
a) S̲t̲o̲r̲a̲g̲e̲ ̲O̲n̲l̲i̲n̲e̲
Log records are stored online for a period of at
least 24 hours.
b) S̲t̲o̲r̲a̲g̲e̲ ̲O̲f̲f̲l̲i̲n̲e̲
Log records are kept on the offline disk for at
least 30 days.
Figure 5.16.1.1.1…01…L̲O̲G̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
5.16.1.1.1.4 R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲L̲o̲g̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
a) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲S̲t̲a̲t̲u̲s̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲
All transactions related to the CAMPS site are
handled to the supervisor position every 24 hours
at midnight.
b) P̲e̲r̲i̲o̲d̲i̲c̲ ̲R̲e̲p̲o̲r̲t̲s̲
The delivery status information contains the information
listed in the table below.
TYPES TRANSAC- TS ITEM
REF- FROM DTG
TION TYPE ERENCE
ID
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
Incoming I TOC YES PLA/REF YES
Messages
Received C TOC YES SCD N/A
Comments
Messages for A TOC YES SCD N/A
Coordination
Outgoing L TOC YES SCD YES
Messages for
Local Dis-
tribution
Display of the information can be achieved from user
positions.
c) T̲r̲a̲c̲i̲n̲g̲ ̲(̲C̲o̲m̲p̲u̲t̲e̲r̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲)̲
The log records may be retrieved with respect to
specific retrieval keys and sent to supervisor
position.
5.16.1.1.2 I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲S̲u̲m̲m̲a̲r̲y̲
5.16.1.1.2.1 I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
C̲S̲F̲ log generator.
Event: Handling of collected log records to LOG.
T̲E̲P̲
Event: Request retrieval of log records.
Return of log records.
Log records to supervisor printer.
S̲A̲R̲
Event: Catalogue of log-id
Retrieval of log item
Retrieval of SAR catalogue information
S̲F̲M̲
Event: Storage of log item
Retrieval of log items
S̲S̲C̲
Event: Initial start of LOG
Start upon system failure
5.16.1.1.2.2 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
None.
Figure 5.16.1.1.2.1…01…I̲N̲T̲E̲R̲F̲A̲C̲E̲ ̲C̲H̲A̲R̲T̲ ̲F̲O̲R̲ ̲L̲O̲G̲ ̲
5.16.1.1.2.3 E̲x̲p̲l̲a̲n̲a̲t̲i̲o̲n̲ ̲t̲o̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲C̲h̲a̲r̲t̲
Refer to section 5.16.1.2 for detailed description.
Step 1a:
Handling of max. 5 log records, each time, from CSF
to LOG.
Step 2a:
Creation of log item.
Step 2b:
Return of ICB and item-id from MMS to LOG, when item
has been created.
Step 3a:
Appending log records to log item.
Step 3b:
Log records to TEP for print-out at supervisor log
printer.
Step 4a:
Time-out from CSF to LOG for storage of log item.
Step 4b:
Request SAR to store the log item.
Step 4c:
Acknowledgement of having catalogues the log-id.
Step 5a:
TEP request LOG to retrieve a specified log item.
Step 5b:
LOG request SAR to retrieve a log item.
Step 5c:
Return of log item to LOG.
Step 5d:
Handling of log item from LOG to TEP.
Step 5e:
Command completion code for TEP.
Step 6a:
TEP requests LOG about delivery status information.
Step 6b:
Catalogue retrieval request command.
Step 6c:
Return delivery status information to LOG.
Step 6d:
Return delivery status information to TEP.
5.16.1.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
5.16.1.2.1 C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
5.16.1.2.1.1 M̲a̲i̲n̲ ̲M̲e̲m̲o̲r̲y̲ ̲L̲o̲g̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
CSF log record generator supports collection of log
information in the following way:
The log records are collected in main memory and transferred
to the LOG when 30 seconds have elapsed or 5 records
are collected, whichever occurs first (1a). The log
records delivered to CSF are check pointed for recovery
reasons, as described in the recovery section of SSC.
5.16.1.2.2 O̲n̲l̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
The way LOG package stores the log record is based
on lumps of log records forming a log item.
5.16.1.2.2.1 C̲r̲e̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲L̲o̲g̲ ̲I̲t̲e̲m̲
The message monitor in SFM is asked to create an item
by the command:
CREATE ITEM step 2a
Input: item attributes
Output: ICB, item-id step 2b
The space allocated is that big to contain busy ten
minutes traffic of log records.
5.16.1.2.2.2 A̲p̲p̲e̲n̲d̲i̲n̲g̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲t̲o̲ ̲I̲t̲e̲m̲
Each time (1a) log records are transferred from CSF
to LOG, SFM is asked to append the log records to the
item (3a).
5.16.1.2.2.3 S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲L̲o̲g̲ ̲I̲t̲e̲m̲
When the above mentioned time interval has elapsed
CSF timer monitor signal time-out for storage of log
item (4a). This is achieved by the command (4b) for
SAR.
STORE ITEM
Input: ICB
Field list
The superfluous, not used area within the item is cut
off by MMS upon this storage.
SAR catalogue the item-id for a possible later retrieval
process. Completion of catalogue update or complete
storage process is acknowledged back (4c).
5.16.1.2.3 O̲f̲f̲l̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲L̲o̲g̲ ̲I̲t̲e̲m̲
The offline storage process of log records or log items
will be managed by SAR, the same way as SAR handles
off-line storage of ordinary items.
5.16.1.2.4 P̲r̲i̲n̲t̲-̲o̲u̲t̲ ̲o̲f̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
When the log records have been handled to LOG, it will
queue them at the supervisor's log printer. This action
is achieved through step 3b on the interface chart.
5.16.1.2.5 R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
The generation of periodic transaction status information
for the supervisor is carried out by TEP. LOG is only
used as a tool to retrieve the log records.
The supervisor's request of a tracing procedure is
generated by TEP which again use Log to retrieve the
log records.
Requesting delivery status information from a user
position i.e. TEP is carried out as described below.
5.16.1.2.5.1 R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
The log records are stored under the retrieval key
"LOG and DTG-window". Upon the production of the above
mentioned procedures, except for delivery status, TEP
issues a retrieval command with retrieval parameters
routed for LOG (5a). The action taken by LOG is to
request SAR to retrieve the log item (5b) (5c). LOG
handles the retrieved log item to TEP (5d).
5.16.1.2.5.2 G̲e̲n̲e̲r̲a̲t̲i̲n̲g̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲S̲t̲a̲t̲u̲s̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
A delivery status retrieve request command from TEP
containing TOC and terminal designator as input parameters
is handled to LOG (6a). SAR will then be asked to return,
to TEP via LOG, the system catalogue information related
to the calling terminal (6b) (6c). The catalogue contains
the necessary information for the delivery status.
5.16.1.2.6 T̲i̲m̲e̲s̲p̲a̲n̲ ̲f̲o̲r̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲N̲e̲e̲d̲e̲d̲ ̲f̲o̲r̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲
̲S̲t̲a̲t̲u̲s̲
The information needed for the periodic transaction
status is online resident. Production of transaction
status information will not require any disk mount.
5.16.1.2.7 T̲i̲m̲e̲s̲p̲a̲n̲ ̲i̲n̲ ̲T̲r̲a̲c̲i̲n̲g̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
The tracing information can be retrieved from at least
a period of 30 days. This will mean that mounting
of off-line volume may be required, but is under the
control of SAR. The retrieval parameter time interval
will be truncated to a specified maximum value, if
this value is exceeded. Further, the time interval
is reduced to the lower time interval on one volume
if the interval is covering log information resident
on two offline volumes. The TEP package is told about
the changed time interval through the command completion
report queue (5e).
5.16.1.2.8 T̲i̲m̲e̲s̲p̲a̲n̲ ̲f̲o̲r̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲S̲t̲a̲t̲u̲s̲
The delivery status information is covering a time
interval of maximum 24 hours starting at midnight.
Displayed information then covers the interval since
last request or since midnight.
5.16.1.2.9 R̲e̲c̲o̲v̲e̲r̲y̲
By failure is meant, a switch over or total system
failure.
The LOG support recovery actions for failures occuring
during the below mentioned transactions.
Failure upon transferring log records from main memory
to LOG.
Recovery action: Handling of check pointed log records
to the log package, which then determine which log
records have already been stored. The log item area
is permanent and allocated upon creation of an empty
log item. This area will be fully recovered by MMS
in SFM.
Failure upon storage of log item, when SAR and SFM
have not returned a completion code.
Recovery action: Is described in the recovery section
5.15.1.2.5.2 under the description of SAR.
Failure upon retrieving a log item.
Recovery action: SAR will receive a new command and
retrieval parameter.
5.16.1.3 P̲a̲c̲k̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
5.16.1.3.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
During initialization of system, SSC package is going
to set CSF timer monitor to a value of 10 minutes.
Upon each time-out a log item is stored (4a).
5.16.1.3.2 E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
The log package supports internal error handling as
described below. All other errors will be handled
by the SSC package.
5.16.1.3.2.1 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲e̲d̲ ̲b̲y̲ ̲L̲O̲G̲
Failure in time interval in the retrieval key parameter
is detected by LOG. Intermediate stop for retrieval
of off-line log item is as well as the above mentioned
error reported to TEP through the command completion
codes (5e).
5.16.1.3.2.2 E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲e̲d̲ ̲b̲y̲ ̲S̲S̲&̲C̲
All other errors will be reported to SSC.
5.16.1.3.2.3 E̲r̲r̲o̲r̲ ̲A̲c̲t̲i̲o̲n̲s̲
Error actions for both LOG and SSC are TBD.
5.16.1.4 P̲a̲c̲k̲a̲g̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
5.16.1.4.1 P̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲
5.16.1.4.1.1 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The amount of log records, busy minute, is estimated
to be 550 log records per minute.
Busy hour will then be estimated to 11000 log records.
Busy 24 hour will then be estimated to 55000 log records.
The storage capacity will then be based on the above
calculated busy traffic throughput.
5.16.1.4.1.2 S̲t̲o̲r̲a̲g̲e̲ ̲C̲a̲p̲a̲c̲i̲t̲y̲
The average storage space per log record is estimated
to 50 characters. The required storage space will
then, for the different storage areas be:
1) Level storage capacity
Main memory 500 charac.
2) Level storage capacity
Log item area, disk 27.500 charac.
3) Level storage capacity
online disk storage 2.75 Mbytes
4) Level storage capacity
offline disk storage 70 Mbytes
5.16.1.4.1.3 T̲i̲m̲i̲n̲g̲ ̲o̲f̲ ̲L̲O̲G̲
External timing of LOG is carried out by CSF timer
monitor each time a log item is stored (4a).
5.16.1.5 D̲e̲s̲i̲g̲n̲ ̲a̲n̲d̲ ̲C̲o̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
5.16.1.5.1 S̲o̲f̲t̲w̲a̲r̲e̲ ̲C̲o̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
Referring to section 2.5.
5.16.1.6 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Referring to section 2.6.
