DataMuseum.dk

Presents historical artifacts from the history of:

CR80 Wang WCS documentation floppies

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about CR80 Wang WCS documentation floppies

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦7d83a2d4c⟧ Wang Wps File

    Length: 9081 (0x2379)
    Types: Wang Wps File
    Notes: FIX/1256/PSP/0057         
    Names: »4592A «

Derivation

└─⟦0a6a0cf2a⟧ Bits:30006130 8" Wang WCS floppy, CR 0296A
    └─ ⟦this⟧ »4592A « 

WangText





…0e…   4592A/aml…02…FIX/1256/PSP/0057

…02…JL/840208…02……02…#
FIKS LOG
 JOURNAL
 PROCEDURE
 PSP
…02……02…  FIKS

…0f…












                 LOG JOURNAL PROCEDURE PSP



                 FIX/1256/PSP/0057













                 J]rgen Lindballe




                 Ole Eskedal








                 AMC (6), APE, LOL, LU, REV, JL
















                 …0e…         FIKS S/W Mgr     840208

                          FIKS Conf. Mgr   840208
          …0f…  1


          …0f…  840208…0e…
                                                 




   4592A/aml…02… FIX/1256/PSP/0057

…02… JL/840208…02…   ii
FIKS LOG JOURNAL PROCEDURE PSP
…02……02… FIKS 

















        840208                  All      Original Issue of
                                       Document



…0e…
   4592A/aml…02…FIX/1256/PSP/0057

…02…JL/840208…02…  iii
FIKS LOG JOURNAL PROCEDURE PSP
…02……02… FIKS 


…0f…



                    T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲



     1 SCOPE ........................................  1
        
       1.1 INTRODUCTION .............................  1
            
       1.2 ABBREVIATIONS ............................  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 ...............................  5
            
         3.3.1 The Procedure ........................  5
                
         3.3.2 Initialization .......................  7
                

       3.4 DATA ORGANIZATION ........................  8
            
         3.4.1 The Data Bases .......................  8
                
         3.4.2 The Queues ...........................  8
                
         3.4.3 Buffers ..............................  8
                
         3.4.4 Tables ...............................  8
                
         3.4.5 Constants and Variables ..............  8
                

       3.5 STORAGE ALLOCATION .......................  9
            
         3.5.1 Memory Space Requirements ............  9
                
         3.5.2 Disc Space Requirements ..............  9
                

       3.6 PERFORMANCE CHARACTERISTICS ..............  9
            
       3.7 LIMITATIONS ..............................  9
            
       3.8 ERROR CODES .............................. 10
            
         3.8.1 Kernel ............................... 10
                
         3.8.2 I/O-System ........................... 10
                
         3.8.3 QACCESS .............................. 10
                
         3.8.4 MTCB Monitor ......................... 10
                

       3.9 LISTING REFERENCES ....................... 10
            

     4 QUALITY ASSURANCE ............................ 11
        
       4.1 QUALIFICATION TESTS ...................... 11
            
       4.2 OTHER QUALITY ASSURANCE PROVISIONS ....... 11
            
     5 PREPARATIONS FOR DELIVERY .................... 11
        


                         1  S̲C̲O̲P̲E̲



1.1      I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲

         This document specifies the LOG JOURNAL monitor procedure
         within the FIKS application software.  The design is
         based on issue 5 of the Requirements Specifications.

         The main task of the LOG JOURNAL is:

         -   to create a pseudo MTCB with the proper data as
             obtained from the input and to enqueue this into
             the JOURNAL PROCESS input queue.



1.2      A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲

         LJP-Q   Journal Process Queue
         MTCB    Message Transition Control Block



1.3      D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲ ̲O̲F̲ ̲T̲E̲R̲M̲S̲

         M̲E̲S̲S̲A̲G̲E̲ ̲T̲R̲A̲N̲S̲I̲T̲I̲O̲N̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲B̲L̲O̲C̲K̲ ̲(̲M̲T̲C̲B̲)̲

         A core resident representative for a message or an
         event related to a message.





                 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, Issue 5, 800310

         2.  FIKS SYSTEM DESIGN SPECIFICATION
             FIX/1000/DSP/0001
             Issue 5, 800507

         3.  FIKS SOFTWARE INTERFACE REFERENCE
             FIX/0100/MAN/0003
             Issue 2, 800530

         4.  FIKS DATA INTERFACE REFERENCE
             FIX/0100/MAN/0004
             Issue 2, 800530

         5.  CR80 AMOS KERNEL
             CSS/302/PSP/0008
             Issue 2, 810303

         6.  CR80 AMOS I/O SYSTEM
             CSS/006/PSP/0006
             Issue 3, 810401

         7.  CR80 FILE SYSTEM PSP
             CSS/910/EWP/0001
             Issue 2, 790226

         8.  SUPPORT SOFTWARE DESIGN SPECIFICATION
             FIX/1103/DSP/0009
             Issue 1, 800430

         9.  TEST REPORT FOR MISC. SUPPORT S/W PROCEDURES
             FIX/1203/TRP/0029
             Issue 1



                 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 procedure LOG ̲JOURNAL prepares and enqueues a pseudo
         MTCB for the JOURNAL process.



3.2      I̲N̲T̲E̲R̲F̲A̲C̲E̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲

         MON LOG ̲JOURNAL
         REGISTER USE AT

         CALL                          EXIT
         R4 Ref.(Work)                 Unchanged
         R7 Link                       Completion code

         Work area of 21 words:

         WORK

                       ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
                     ^ ̲T̲Y̲P̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^   0
                     ^ ̲T̲E̲R̲M̲.̲ ̲N̲O̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲   1
                     ^ REF(MSG ̲ID)              ^   2
                     ^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^
                     ^                          ^
                     ^                          ^
                     ^                          ^
                     ^                          ^
                     ^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^  20

         EXIT
         Destroyed



         TYPE may be:

             1.  Message release

             2.  Message delivered to terminal queue

             3.  Message delivered to the DT queue of the supervisor
                 terminal

             4.  Retrieve request for display

             5.  Retrieve request for print out

             6.  Retrieve request for distribution

             7.  Distribution of retrieved message

             8.  Retrieve request for re-addressing

             9.  SH-message delivered to terminal queue

            10.  Message print out started

         TERM ̲NO is the logical terminal number.

         MSG ̲ID is the message identification

             3 character terminal - ID +
             3 digit sequence number



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̲

         The flow-chart of the monitor procedure LOG-JOURNAL
         is shown overleaf.

         A pseudo MTCB is created, and after having filled the
         work area with the input data, the MTCB is filled.

         The layout of the pseudo MTCB may be found in ref.
         4, ch. 7.1.2.3.

         The pseudo MTCB is enqueued the JOURNAL PROCESS input
         queue: LJP-Q.

         Finally the MTCB is released.




















































         Figure 3.3.1-1…01…The Log ̲Journal Procedure



3.3.2    I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲

         During the initialization MON-INIT is called.





3.4      D̲A̲T̲A̲ ̲O̲R̲G̲A̲N̲I̲Z̲A̲T̲I̲O̲N̲



3.4.1    T̲h̲e̲ ̲D̲a̲t̲a̲ ̲B̲a̲s̲e̲s̲

         Not applicable.



3.4.2    T̲h̲e̲ ̲Q̲u̲e̲u̲e̲s̲

         Output queue is LJP-Q which is input queue for the
         JOURNAL PROCESS.

         It consists of a single subqueue.



3.4.3    B̲u̲f̲f̲e̲r̲s̲

         A working area of 21 words is delivered by the calling
         process.

         It is used for:

         -   Input parameters
         -   Working area
         -   Storage of the registers R0-R7



3.4.4    T̲a̲b̲l̲e̲s̲

         Not applicable.



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:    123 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̲

         Not applicable.



3.8.2    I̲/̲O̲-̲S̲y̲s̲t̲e̲m̲

         Not applicable.



3.8.3    Q̲A̲C̲C̲E̲S̲S̲

         If CC () 0 after having called:

         -   INSERT

         the pseudo MTCB is released.



3.8.4    M̲T̲C̲B̲ ̲M̲o̲n̲i̲t̲o̲r̲

         If CC () 0 after having called:

         -   WRITE

         the pseudo MTCB is released



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

         and

         FIX-PREFIX.D * 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.