top - download
⟦c464f386b⟧ Wang Wps File
Length: 8949 (0x22f5)
Types: Wang Wps File
Notes: FIX/1256/PSP/0056
Names: »4665A «
Derivation
└─⟦0a6a0cf2a⟧ Bits:30006130 8" Wang WCS floppy, CR 0296A
└─ ⟦this⟧ »4665A «
WangText
…09……00……00……00……00…A…0a……86…1 …02… …02… …02…
4665A…02…FIX/1256/PSP/0056
…02…JL/840229…02……02…#
FIKS LOG ̲ACTION PROCEDURE PSP
…02……02… FIKS
…0e…
FIKS LOG ̲ACTION PROCEDURE PSP
FIX/1256/PSP/0056
…0f…
J]rgen Lindballe
Ole Eskedal
AMC (6), APE, LOL, LU, REV, JL
FIKS S/W Mgr 840229
FIKS Conf.Mgr 840229
1
840229
…86…1
…02…
…02… …02…
4665A …02… FIX/1256/PSP/0056
…02… JL/840229…02……02…ii
FIKS LOG ̲ACTION PROCEDURE PSP
…02……02… FIKS
840229 All Issue 1 of Document
4665A…02…FIX/1256/PSP/0056
…02…JL/840229…02……02…iii
FIKS LOG ̲ACTION PROCEDURE PSP
…02……02… FIKS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ........................................
1
1.1 INTRODUCTION .............................
1
1.2 ABBREVIATONS .............................
1
1.3 DEFINITION OF TERMS ......................
1
2 APPLICABLE DOCUMENTS .........................
2
3 MODULE SPECIFICATION .........................
3
3.1 FUNCTIONAL CAPABILITIES ..................
3
3.2 INTERFACE DESCRIPTION ....................
3
3.3 PROCESSING ...............................
4
3.3.1 The Procedure ........................
4
3.3.2 Initialization .......................
6
3.4 DATA ORGANIZATION ........................
6
3.4.1 Data Bases ...........................
6
3.4.2 Queues ...............................
6
3.4.3 Buffers ..............................
6
3.4.4 Tables ...............................
6
3.4.5 Constants and Variables ..............
6
3.5 STORAGE ALLOCATION .......................
7
3.5.1 Memory Space Requirements ............
7
3.5.2 Disc Space Requirements ..............
7
3.6 PERFORMANCE CHARACTERISTICS ..............
7
3.7 LIMITATIONS ..............................
7
3.8 ERROR CODES ..............................
7
3.8.1 Kernel ...............................
7
3.8.2 I/O System ...........................
7
3.8.3 QACCESS ..............................
8
3.8.4 MTCB Monitor .........................
8
3.9 LISTING REFERENCES .......................
8
4 QUALITY ASSURANCE ............................
9
4.1 QUALIFICATION TESTS ......................
9
4.2 OTHER QUALITY ASSURANCE PROVISIONS .......
9
5 PREPARATION FOR DELIVERY ..................... 10
1 S̲C̲O̲P̲E̲
1.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This document specifies the L̲O̲G̲-̲A̲C̲T̲I̲O̲N̲ monitor procedure
within the FIKS application software. The design is
based on issue 5 of the Requirements Specifications.
The main tasks of the procedure are:
- to create a pseudo MTCB, and to fill it with information
from the input block
- to insert the pseudo MTCB in the LP queue of the
Log Printer
- to release the pseudo MTCB.
1.2 A̲B̲B̲R̲E̲V̲I̲A̲T̲O̲N̲S̲
LP Log Printer
MTCB Message Transition Control Block
1.3 D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲ ̲O̲F̲ ̲T̲E̲R̲M̲S̲
MESSAGE TRANSITION CONTROL BLOCK (MTCB)
A core resident representive for a message or a message
related event.
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1. REQUIREMENTS SPECIFICATION
FIX/0000/SPC/0002
Vol. I-III
2. FIKS SYSTEM DESIGN SPECIFICATION
FIX/1000/DSP/0001
3. FIKS SOFTWARE INTERFACE REFERENCE
FIX/0100/MAN/0003
4. FIKS DATA INTERFACE REFERENCE
FIX/0100/MAN/0004
5. CR80 AMOS KERNEL
CSS/302/PSP/0008
6. CR80 AMOS I/O SYSTEM
CSS/006/PSP/0006
7. CR80 FILE SYSTEM PSP
CSS/910/EWP/0001
8. SUPPORT SOFTWARE DESIGN SPECIFICATION
FIX/1103/DSP/0009
9. TEST REPORT FOR MISC. SUPPORT S/W PROCEDURES
FIX/1203/TRP/0024
3 M̲O̲D̲U̲L̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
3.1 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲C̲A̲P̲A̲B̲I̲L̲I̲T̲I̲E̲S̲
The logging facility prepares a print at the MEDE log
printer of events of different types.
3.2 I̲N̲T̲E̲R̲F̲A̲C̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
MON LOG ̲ACTION
Register use at:
CALL EXIT
R4 Ref. (Workarea) Unchanged
R7 Link Completion Code
Use of return points:
Link+0: Error
Link+1: Done
Work area of 21 words:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ̲T̲Y̲P̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ 0 unchanged
^ ̲T̲E̲R̲M̲ ̲N̲O̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ 1
^ ̲U̲S̲E̲R̲ ̲I̲D̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ 2..3
^ ^
^ ^
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ 20
3.3 P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
3.3.1 T̲h̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
Logging of events is initiated by the individual application
subsystems which via this monitor procedure LOG ̲ACTION
insert an entry in a log printer queue. The queue entry
points to a pseudo MTCB, which describes the cause
of the logging.
The log printer is localized by means of the terminal
configuration table.
The events logged are described in ref. 3, section
3.6.6.
The flow chart is shown overleaf:
1. The module is invoked by a procedure call from
an application subsystem. The call implies transfer
of a parameter block defining the logging event
and the user.
2. A pseudo MTCB is created.
3. The input parameter block is decoded and the contents
written into the pseudo MTCB.
4. The log printers logical terminal number is found
in the terminal configuration table.
5. The pseudo MTCB is inserted in the "LP" precedence
queue at the log printer.
6. The pseudo MTCB is released.
7. The module transfers control to the caller.
Figure 3.3.1-1…01…Procedure LOG ̲ACTION
3.3.2 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
During the initialization, the MON ̲INIT procedure is
called.
3.4 D̲A̲T̲A̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲
3.4.1 D̲a̲t̲a̲ ̲B̲a̲s̲e̲s̲
Not applicable.
3.4.2 Q̲u̲e̲u̲e̲s̲
The format of the pseudo MTCB inserted in the LP queue
is described in ref. 4, section 7.1, figure 7.1.2.3.
3.4.3 B̲u̲f̲f̲e̲r̲s̲
The buffer delivered by the calling process is used
for:
- input parameters
- register save area and
- working area (e.g. MTCB-block, QIOCB).
3.4.4 T̲a̲b̲l̲e̲s̲
The configuration table (see ref. 4, section 11.5)
is used to extract the logical terminal number of the
log printer.
3.4.5 C̲o̲n̲s̲t̲a̲n̲t̲s̲ ̲a̲n̲d̲ ̲V̲a̲r̲i̲a̲b̲l̲e̲s̲
Not applicable
3.5 S̲T̲O̲R̲A̲G̲E̲ ̲A̲L̲L̲O̲C̲A̲T̲I̲O̲N̲
3.5.1 M̲e̲m̲o̲r̲y̲ ̲S̲p̲a̲c̲e̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Program size = 136 words.
3.5.2 D̲i̲s̲c̲ ̲S̲p̲a̲c̲e̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
No disc space is required.
3.6 P̲E̲R̲F̲O̲R̲M̲A̲N̲C̲E̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
Not applicable
3.7 L̲I̲M̲I̲T̲A̲T̲I̲O̲N̲S̲
Not applicable.
3.8 E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲
3.8.1 K̲e̲r̲n̲e̲l̲
Copying of the Log Printer Id from the Critical Region
"Configuration Table":
CC equal to completion code.
3.8.2 I̲/̲O̲ ̲S̲y̲s̲t̲e̲m̲
Not applicable.
3.8.3 Q̲A̲C̲C̲E̲S̲S̲
Insertion of the pseudo MTCB in the LP queue:
CC equal to completion code.
3.8.4 M̲T̲C̲B̲ ̲M̲o̲n̲i̲t̲o̲r̲
- create the pseudo MTCB,
- write log information on the pseudo MTCB, and
- release the pseudo MTCB:
CC equal to completion code.
3.9 L̲I̲S̲T̲I̲N̲G̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
Source listings and linker list may be obtained from
the FIKS library (FIXLIB, ref. to SCCLDD).
4 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲
4.1 Q̲U̲A̲L̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲T̲E̲S̲T̲S̲
The test of the procedure is described in ref. 9.
4.2 O̲T̲H̲E̲R̲ ̲Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲ ̲P̲R̲O̲V̲I̲S̲I̲O̲N̲S̲
Not applicable.
5 P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲S̲ ̲F̲O̲R̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲
Preparation of the binary object code starts with an
editing of the source text.
Then the source text is merged together with the prefix
files:
GENS.D * SWELLPREFIX.D * GENERALPARAMS.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * IOSPARAMS.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * MONITORNAMES.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * KERNELPARAMS.S
and
FIX-PREFIX.D * CONFIG ̲TYPE.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * FIX-MONITORNAMES.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * QACCESS-TYPES.S
…0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f… * AL-DT-PARAMS.S
The merge file is compiled by running the SWELL compiler,
and the listing is printed.
The object code is then linked together with other
pieces of object code by the LINKER.
Finally the binary code may be installed.
Exact instructions may be obtained from the file "INFORMATION"
in the most recent ESP-directory of FIXLIB.
