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
Index: ┃ 1 8 C S W ~

⟦7985b6947⟧ Bits:30005810 8" Wang WCS floppy, CR 0117A, 8" Floppy Disk

    Length: 315392 (0x4d000)
    Description: Bits:30005810 8" Wang WCS floppy, CR 0117A
    Types: 8" Floppy Disk

Namespace

name artifact - - - - - - - - - - - - - - - - - - - - - - -
1587A CPS/SDS/026 sdv BMN Table of Contents 15-01-82 11:46 3 25 15361 06-02-84 15:20 01 54 23-01-84 10:49 02-04-84 13:48 0117A 9 13 04 332 35174 0 1587A ⟦98b13d828⟧ Wang Wps File, CPS/SDS/026
1588A CPS/SDS/026 pn BMN Fra kap. 1 15-01-82 12:44 10 40 32014 02-04-84 13:47 00 15 11-01-84 08:42 02-04-84 13:48 0117A 83 27 06 788 62027 1588A ⟦2ea207fc6⟧ Wang Wps File, CPS/SDS/026
1592A CPS/SDS/026 pan BMN 4.2.1.4 18-01-82 10:53 14 26 36746 12-01-84 08:06 05 72 12-01-84 08:35 12-01-84 15:07 0117A 68 30 25 1120 60123 @ 1592A ⟦43c7d73be⟧ Wang Wps File, CPS/SDS/026
1598A CPS/SDS/026 vhn BMN 4.2.3 19-01-82 14:57 7 25 21673 09-01-84 13:24 01 25 09-01-84 13:30 12-01-84 15:08 0117A 28 13 08 304 30393 1598A ⟦0c968bd1f⟧ Wang Wps File, CPS/SDS/026
~ORPHAN01.06 ⟦bd217d074⟧ Wang Wps File, Spelunked
~ORPHAN02.05 ⟦fa886243a⟧ Wang Wps File, Spelunked
~ORPHAN07.10 ⟦10bbf7166⟧ Wang Wps File, Spelunked
1588A CPS/SDS/026 pn BMN Fra kap. 1 15-01-82 12:44 10 40 32014 11-01-84 08:40 01 40 11-01-84 08:42 12-01-84 15:06 0117A 83 27 06 852 62012 ~ORPHAN33.00 ⟦e5f28ca5e⟧ Wang Wps File, Spelunked
~ORPHAN37.05 ⟦90eb4157d⟧ Wang Wps File, Spelunked
1598A CPS/SDS/026 vhn BMN 4.2.3 19-01-82 14:57 7 25 21673 05-05-82 15:04 00 2 04-05-82 16:45 10-05-82 10:53 0117A 58 9 35 548 23221 @ ~ORPHAN60.08 ⟦604f6f5e6⟧ Wang Wps File, Spelunked

Disk picture

  Unclaimed
  Document Body
  Document Head
  Marked Free
  Content List

OctetView

0x00000…00100 (0, 0, 0)   Sector 01174130313137 ┆  A0117A                                                                                                                                                                                                                                                        ┆
0x00100…00200 (0, 0, 1)   Sector 00000000000000 ┆                                                                                                                                                                                                                                                                ┆
0x00200…00300 (0, 0, 2)   Sector ff00fcfff8ffff ┆  | x          @                                                          x                                                                                                                                                                                     ┆
0x00300…00306 (0, 0, 3)   WangDocument {d00=0x15, d01=0x87, d02=0x41, ptr=( 7,0, 0), d05=0x00}
0x00306…0030c             WangDocument {d00=0x15, d01=0x88, d02=0x41, ptr=(27,0, 8), d05=0x00}
0x0030c…00312             WangDocument {d00=0x15, d01=0x92, d02=0x41, ptr=(63,0, 0), d05=0x00}
0x00312…00318             WangDocument {d00=0x15, d01=0x98, d02=0x41, ptr=(36,0, 0), d05=0x00}
0x00318…00320             00 00 00 00 00 00 00 00   ┆        ┆
0x00320…00340             00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ┆                                ┆
         […0x5…]
0x003e0…00400             00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18   ┆                                ┆
0x00400…00500 (0, 0, 4)   Sector 00000000000000 ┆                                                                                                                                                                                                                                                                ┆
0x00500…00600 (0, 0, 5)   Sector 01174130313137 ┆  A0117A                                                                                                                                                                                                                                                        ┆
0x00600…00700 (0, 0, 6)   Sector 421c402600415b ┆B @& A['      #   X%   %  PO P    ;      A     C f x f V WD  O 7 :Y(  Y+S   1588A  f    4F         < {C < { ; 8  `  i      U     bP  b  [        : 9 8     t   msi      1587A1588A              R$R%R"R#z({* ? >                                                ┆
0x00700…00800 (0, 0, 7)   Sector 00000000000000 ┆                                                                                                                                                                                                                                                                ┆
         […0x8…]
0x01000…01100 (1, 0, 0)   WangDocumentBody
         […0x5…]
0x01600…01700 (1, 0, 6)   Sector 0107f600159841 ┆  v   A========     4.3.3 Code Storage   The TMP code consists of 17 modules, each including 150 statements on average.   One swell statement is on average 4 bytes.   Required storage: 17 x 150 x 4 = 10 kbytes                                      ameters  ┆
0x01700…01800 (1, 0, 7)   Sector 00003e00159841 ┆  >   A       =========    The code resides in memory.                     4.2.3.7.2 Answer received from TMP    The following formats are used in answers from TMP:    NORMAL RESPONSE =     RECORD      SOCB : SOCB INDEX;      CC  : COMPLETION CODE;     END┆
0x01800…01900 (1, 0, 8)   WangDocumentBody
         […0xc…]
0x02500…02600 (2, 0, 5)   Sector 0206ff00159841 ┆      Andicating the amount of storage used for memory index and secondary search key are include in columns 1 and 2.   The sums in columns 1 and 2 thus indicate the total amount of disk storage and memory storage required by TMP data.     1               ┆
0x02600…02700 (2, 0, 6)   Sector 02073900159841 ┆  9   A                                                   er       BUFFER : POINTER         pointer to output buffer      END;      GET TABLE ATTRIBUTES INFO =     RECORD      SOCB : SOCB INDEX  ;      FUNCTION : TMP FUNCTION;      SUBPROCESS : SUBPROCESS ┆
0x02700…02800 (2, 0, 7)   Sector 0108ff00159841 ┆      A 1                                                                         Storage Type Disk Memory Memory Secondary   Table    Index Search Key   (kbytes) (bytes) (bytes) (kbytes)                                                                     ┆
0x02800…02900 (2, 0, 8)   WangDocumentBody
         […0x47…]
0x07000…07100 (7, 0, 0)   WangDocumentHead {hdr=WangSectHead {next=( 7,0, 1), len=0xff, h3=41158741}, f00=»1587A «, f01=»CPS/SDS/026               «, f02=»sdv                  «, f03=»BMN                  «, f04=»Table of Contents    «, f05=15-01-82 11:46, f06=»   3 «, f07=»25 «, f08=» 15361 «, f09=06-02-84 15:20, f10=»     «, f11=»01 «, f12=»    54 «, f13=23-01-84 10:49, f14=02-04-84 13:48, f15=»0117A «, f16=»  9 «, f17=»  13 «, f18=»04 «, f19=»  332 «, f20=» 35174 «, f21=»  «, f22=» 0 «, f99=330010000110062710110280aaca15050000000000000137035e00df}
0x07100…07200 (7, 0, 1)   WangDocumentBody
         […0x8…]
0x07a00…07b00 (7, 0, 10)  Sector 070bb000158741 ┆  0   A 1                                                                         CPS/SDS/026   BMN/840105   TABLE MANAGEMENT DETAILED DESIGN SPECIFICATION  ISSUE 1 CAMPS       M, > I!e=6 !Z="(=e*$<kas#r  9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x07b00…07c00 (7, 0, 11)  Sector 070cff00158741 ┆      A 1                                                                    1                                                                   TABLE OF CONTENTS     1  GENERAL ........................................... 1 001    1.1 PURPOSE AND SCOPE ...┆
0x07c00…07d00 (7, 0, 12)  Sector 070dff00158741 ┆      A............................ 1 001   1.2 APPLICABLE DOCUMENTS AND PROJECT REF. ........... 1 001    1.2.1 Applicable Documents ........................ 1 001    1.2.2 Project References .......................... 1 001    1.3 TERMS AND ABBREVIATIONS┆
0x07d00…07e00 (7, 0, 13)  Sector 070eff00158741 ┆      A ......................... 1 003    1.3.1 Terms ....................................... 1 003    1.3.2 Abbreviations ............................... 1 003   2  SUMMARY OF REQUIREMENTS ........................... 2 001    2.1 TMP DESCRIPTION ........┆
0x07e00…07f00 (7, 0, 14)  Sector 070fff00158741 ┆      A......................... 2 001   2.2 TMP FUNCTIONS ................................... 2 003    2.2.1 TMP Normal Functions ........................ 2 003     2.2.1.1 Search In Tables ........................ 2 003     2.2.1.2 Update Of Tables .....┆
0x07f00…08000 (7, 0, 15)  Sector 0700ff00158741 ┆      A................... 2 003     2.2.1.3 Reorganization Of Tables ................ 2 003     2.2.1.4 Back-up/Reload of TMP Data .............. 2 003     2.2.1.5 Global Serial Number Management ......... 2 004     2.2.1.6 System Parameter Management ...┆
0x08000…08100 (8, 0, 0)   WangDocumentBody
         […0x137…]
0x1b800…1b900 (27, 0, 8)  WangDocumentHead {hdr=WangSectHead {next=(27,0, 9), len=0xff, h3=41158841}, f00=»1588A «, f01=»CPS/SDS/026               «, f02=»pn                   «, f03=»BMN                  «, f04=»Fra kap. 1           «, f05=15-01-82 12:44, f06=»  10 «, f07=»40 «, f08=» 32014 «, f09=02-04-84 13:47, f10=»     «, f11=»00 «, f12=»    15 «, f13=11-01-84 08:42, f14=02-04-84 13:48, f15=»0117A «, f16=» 83 «, f17=»  27 «, f18=»06 «, f19=»  788 «, f20=» 62027 «, f21=»  «, f22=»   «, f99=820000000110062710110280aaca15050000000000000137031a01df}
0x1b900…1ba00 (27, 0, 9)  WangDocumentBody
         […0x6…]
0x1c000…1c100 (28, 0, 0)  Sector 1c01ff00158841 ┆      A a normal table update.    4.1.1.6 Back-up and Reload   Back-up copies a TMP file from the on-line to SYS GEN volume.   Reload copies a TMP file from SYS GEN  to the on-line volume.   After reload, the new copied file is read into memory, if it norm┆
0x1c100…1c200 (28, 0, 1)  Sector 1c02ff00158841 ┆      Aally resides here.    4.1.1.7 Reorganize   Reorganize removes unused records from a table and puts records from an overflow area in their appropriate position.  Reorganize may be stopped by a request from the Supervisor.    4.1.1.8 Functional Breakd┆
0x1c200…1c300 (28, 0, 2)  Sector 1c03ff00158841 ┆      Aown   To break this package down in subpackages, the functions described in this chapter are split into three main groups.   Each group is a subpackage containing functions with common characteristics.  The functions mapped on each subpackage is sho┆
0x1c300…1c400 (28, 0, 3)  Sector 1c044c00158841 ┆  L   Awn at fig. 4.1.1.8-1.   The three subpackages are at the second level.P process during the search.   The data structure contains the following information.   - Table ID.  - Output Address  - Output Buffer Length  - Search Mask  - Read Mask  - Number┆
0x1c400…1c500 (28, 0, 4)  Sector 1c05ff00158841 ┆      A 1                                                                   In the following all TMP modules are grouped in subpackages and listed.   Search Subpackage   - Search Communication   - Sort Key   - General Search   - Memory Table Search   - Dis┆
0x1c500…1c600 (28, 0, 5)  Sector 1c06eb00158841 ┆  k   Ak Table Search   - Special Search   Update Subpackage   - Update Communication   - Search   - Update Record   - Update Disk   - Support   - Start Up  TMP Monitor   - Process Functions   - Monitor Functions   - Main Functions     f keys is a list of ┆
0x1c600…1c700 (28, 0, 6)  Sector 1c079500158841 ┆      A 1                                                                                                         Fig. 4.1.1.7-1 Functional Breakdown  area.   The output is delivered in the same order as input Keys were sorted. Each Key has a pointer refer┆
0x1c700…1c800 (28, 0, 7)  Sector 1b08ff00158841 ┆      A 1                                                                  4.1.1.8.1 Table Search Functions   This subpackage receives search requests from a SyncEl. and generates the output which contains the wanted information.    4.1.1.8.1.1  Search Com┆
0x1c800…1c900 (28, 0, 8)  Sector 1c09ff00158841 ┆      A 1                                                                   An application process may by request specify if the first level output shall be used as input for search of a second level output.   The input parameters for a one level search an┆
0x1c900…1ca00 (28, 0, 9)  Sector 1c0aff00158841 ┆      Ad a two level search differs in the way that two different table IDs are used.   The table ID for a two level search will contain a reference to the table where the second level information is held.    4.1.1.3 Table Update   Table update will update┆
0x1ca00…1cb00 (28, 0, 10) Sector 1c0bff00158841 ┆      A one record specified by a primary key or it may update one or more fields of the same value to one new value in a table.   The single record update may remove a record, insert a record or change the data fields.   The data fields to be changed may ┆
0x1cb00…1cc00 (28, 0, 11) Sector 1c0cff00158841 ┆      Abe all, or some specified fields of same type which shall be set to the same value or it may be all fields of a special value set to another value.   The data field update may update the specified fields in all records in a table to a specified valu┆
0x1cc00…1cd00 (28, 0, 12) Sector 1c0dff00158841 ┆      Ae, or update only the specified fields having a special value to a new value.    4.1.1.4 TMP Interface Functions   The interface functions receive requests from application processes and pass them on to TMP process which performs the real processing┆
0x1cd00…1ce00 (28, 0, 13) Sector 1c0ef600158841 ┆  v   A.   The interface functions will also ensure that the application processes get the responses sent by TMP process each time a request is completed.   The interface functions will ensure that no unknown request is passed on to TMP process.  sk access┆
0x1ce00…1cf00 (28, 0, 14) Sector 1c0fff00158841 ┆      A 1                                                                  4.1.1.5 System Parameters and Global Number Series   System parameters and GSN can be read and updated.   A GSN may be read in the special way that it is increased by one just befor┆
0x1cf00…1d000 (28, 0, 15) Sector 1c00ff00158841 ┆      Ae read.  If maximum value is exceeded by the increase, the GSN value becomes one.   All accesses are performed by the application processes by using monitor procedure calls.   Parameter update and GSN indicator update are performed by TMP process as┆
0x1d000…1d100 (29, 0, 0)  Sector 1d01a000158841 ┆      A 1                                                                                                                  Fig. 4.1.1.1-4 Functional Description  position of the record (ref. figure 4.1.1.1-4).   In the following the reference table will be┆
0x1d100…1d200 (29, 0, 1)  Sector 1d02a100158841 ┆  !   A 1                                                                                                                  Fig. 4.1.1.1-5 Functional Description   reserved for TMP control data.  The second field will contain the primary key if the record h┆
0x1d200…1d300 (29, 0, 2)  Sector 1d03ff00158841 ┆      A 1                                                                  4.1.1.2 Table Search   When TMP performs a search, it gets its input from a data structure in the data area of the requesting application process.   The segments containing this str┆
0x1d300…1d400 (29, 0, 3)  Sector 1d04ff00158841 ┆      Aucture and the area where output shall be delivered are mapped into TMP process during the search.   The data structure contains the following information.   - Table ID.  - Output Address  - Output Buffer Length  - Search Mask  - Read Mask  - Number┆
0x1d400…1d500 (29, 0, 4)  Sector 1d05ff00158841 ┆      A of Keys  - List of Keys   Table ID. is a reference to the table description containing information necessary for this search.   Output address is a reference to the area where output shall be delivered.   Output buffer length tells how much the out┆
0x1d500…1d600 (29, 0, 5)  Sector 1d06ff00158841 ┆      Aput data may fill.   Search Mask specifies which fields to be searched for.   Read Mask specifies which fields shall be delivered by output.   Number of keys specifies how many input key values are specified in key list.   List of keys is a list of ┆
0x1d600…1d700 (29, 0, 6)  Sector 1d07ff00158841 ┆      Afield values used by search.   Before search TMP checks the input keys for inconsistency and perhaps sorts them via a pointer ARRAY in TMP data area.   The output is delivered in the same order as input Keys were sorted. Each Key has a pointer refer┆
0x1d700…1d800 (29, 0, 7)  Sector 1c082500158841 ┆  %   Aencing its associated output.  s makes it possible that two applications searching in same physical table may get different output because they are accessing two different Logical Tables.   The two Logical Tables may have defined that the same param┆
0x1d800…1d900 (29, 0, 8)  Sector 1d09ff00158841 ┆      Aeters should be formattet in two ways or they may have defined different subsets of the maximum available output as output from actual table.   By secondary Key Organized Tables, the TABLE DESCRIPTION defining the Inverse Table will have a reference┆
0x1d900…1da00 (29, 0, 9)  Sector 1d0aff00158841 ┆      A to associated normal Logical Table.   This means that searching in Inverse Table are consisting of two parts.   First a physical reference to Normal Table entry is found in the Inverse Table and then the output is delivered in accordance with the d┆
0x1da00…1db00 (29, 0, 10) Sector 1d0bff00158841 ┆      Aefinitions in TABLE DESCRIPTION of the Normal Table.   In special cases an connection between two different tables may be defined, so the output from the one table is automatically used as input for a search in the other table.   In this case the fi┆
0x1db00…1dc00 (29, 0, 11) Sector 1d0cff00158841 ┆      Arst level table has a reference to the second level table in its TABLE DESCRIPTION.   A search will then start searching in first level table and generate an intermediate output in TMPS own data area.   This output is then used as input for a search┆
0x1dc00…1dd00 (29, 0, 12) Sector 1d0d5c00158841 ┆  \   A generating the final output in accordance with the conventions of second level table.o identifies the record.  The primary key field in a record must be unique in one table.  The records may also be searched by a secondary key, but a secondary key ┆
0x1dd00…1de00 (29, 0, 13) Sector 1d0e9f00158841 ┆      A 1                                                                                                                 Fig. 4.1.1.1-1 Functional Description total access time is the sum of the time used by FMS and the time used by TMP.   The disk access┆
0x1de00…1df00 (29, 0, 14) Sector 1d0fa000158841 ┆      A 1                                                                                                                  Fig. 4.1.1.1-2 Functional Description ganization which means that the table is split into a number of same length blocks which are re┆
0x1df00…1e000 (29, 0, 15) Sector 1d00a000158841 ┆      A 1                                                                                                                  Fig. 4.1.1.1-3 Functional Description ncarnation called Secondary Key Organization.  This type may be used if a table is often access┆
0x1e000…1e100 (30, 0, 0)  Sector 1e01ff00158841 ┆      Aed using a unique secondary key.  The secondary keys are put in sorted order in a reference table where each secondary key has a reference to the physical position of the record (ref. figure 4.1.1.1-4).   In the following the reference table will be┆
0x1e100…1e200 (30, 0, 1)  Sector 1e02ff00158841 ┆      A called the Inverse Table.    4.1.1.1.2 Record Structure   Each record in a table consists of one or more fields.   The first field in some record types is reserved for TMP control data.  The second field will contain the primary key if the record h┆
0x1e200…1e300 (30, 0, 2)  Sector 1e03ff00158841 ┆      Aas any.   The rest of the fields may contain data of various kind.   All records known by TMP have from one to sixteen fields of various length and are defined by a record description. (Ref. figure 4.1.1.-5).    4.1.1.1.3 Field Structure   There exi┆
0x1e300…1e400 (30, 0, 3)  Sector 1e04ff00158841 ┆      Ast two field types. Simple fields and repeated fields.   The simple field consists of one information field.   The repeated field consists of a defined number of identical subfields. The first byte in a repeated field will tell how many of the subfi┆
0x1e400…1e500 (30, 0, 4)  Sector 1e053100158841 ┆  1   Aelds are used. (Ref. figure 4.1.1.1-5).    trolled by an operating system, for instance COPSY within SSC, defining the control parameters used by TMP.    3.2.2 Development Support Software   The software used for development of this package is conta┆
0x1e500…1e600 (30, 0, 5)  Sector 1e06ff00158841 ┆      A 1                                                                  4.1.1.1.4 Table Description   For each logical table one TABLE DESCRIPTION are defined.   Logical Table means a table accessed by other processes than TMP.   All Logical Tables are ┆
0x1e600…1e700 (30, 0, 6)  Sector 1e07ff00158841 ┆      Adefined in CPS/DBD reference (a).   TABLE DESCRIPTION defines all parameters nessecary by performing a search or an update access, and further it contains an part used when collecting TMP statistics.   One Physical Table may be referenced from more ┆
0x1e700…1e800 (30, 0, 7)  Sector 1d08ff00158841 ┆      Athan one TABLE DESCRIPTION. This makes it possible that two applications searching in same physical table may get different output because they are accessing two different Logical Tables.   The two Logical Tables may have defined that the same param┆
0x1e800…1e900 (30, 0, 8)  Sector 1e09ff00158841 ┆      A 1                                                                   4  TMP DESIGN    4.1 TMP OVERVIEW   Table Management Package performs search and update functions at tables, system parameters, and GSN.   The functions in TMP will be as general a┆
0x1e900…1ea00 (30, 0, 9)  Sector 1e0aff00158841 ┆      As possible so it may be possible to add further tables to the TMP data without the processing modules should be changed.    4.1.1 Functional Description   TMP functional description starts with a description of data organization and access methods u┆
0x1ea00…1eb00 (30, 0, 10) Sector 1e0bff00158841 ┆      Ased by TMP.  This is followed by a general description of the functions performed by TMP.   Finally, the functions are split into subpackages which again is split into modules.    4.1.1.1 Table Organization and Access Methods    4.1.1.1.1 Table Orga┆
0x1eb00…1ec00 (30, 0, 11) Sector 1e0cff00158841 ┆      Anization   All tables consist of a list of similar type records.  Ref. fig. 4.1.1.1-1.  A table may be organized direct or sequential.   Direct organization means that the records are identified alone by their position in the table.   Sequential org┆
0x1ec00…1ed00 (30, 0, 12) Sector 1e0dff00158841 ┆      Aanization means that the records are sorted in accordance with a primary key which also identifies the record.  The primary key field in a record must be unique in one table.  The records may also be searched by a secondary key, but a secondary key ┆
0x1ed00…1ee00 (30, 0, 13) Sector 1e0e3700158841 ┆  7   Amay identify more than one record in one table.   one key is given by one request, the mean time per key will be less than access time by one key.   The total access time is the sum of the time used by FMS and the time used by TMP.   The disk access┆
0x1ee00…1ef00 (30, 0, 14) Sector 1e0fff00158841 ┆      A 1                                                                   Refer fig. 4.1.1.1-2.  Sequential organization may be expanded to index sequential organization which means that the table is split into a number of same length blocks which are re┆
0x1ef00…1f000 (30, 0, 15) Sector 1e00ff00158841 ┆      Aferred in another sequential table containing a reference to last primary key in each block.  Ref. fig. 4.1.1.1-3.   Sequential organization has also an incarnation called Secondary Key Organization.  This type may be used if a table is often access┆
0x1f000…1f100 (31, 0, 0)  Sector 1f017400158841 ┆  t   Acreased by having the disk search coroutine in two incarnations.   The throughput will increase about 50%.    ed in a table or removed from a table.   One or more records is changed.    2.2.1.3 Reorganization Of Tables   All tables are reorganized s┆
0x1f100…1f200 (31, 0, 1)  Sector 1f02ff00158841 ┆      A 1                                                                  2.3.3 Flexibility   The number of data groups or the number of entries in one data group may increase without affecting the TMP Software.   The only difference is that more storage ┆
0x1f200…1f300 (31, 0, 2)  Sector 1f037d00158841 ┆  }   Ais needed.    2.3.4 Accuracy   Any deviation from defined parameters will result in the calling process being retired. TAILED DESIGN SPECIFICATION ISSUE 1 CAMPS       /=MM, > I!e=6 !Z="(=e*$<kas#r  9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x1f300…1f400 (31, 0, 3)  Sector 1f04ff00158841 ┆      A 1                                                                   3  ENVIRONMENT    3.1 EQUIPMENT   TMP executes in one processing unit consisting of more than one CPU.    3.2 SOFTWARE    3.2.1 System Software   TMP uses the KERNEL, FMS, and CSF ┆
0x1f400…1f500 (31, 0, 4)  Sector 1f05ff00158841 ┆      Asystem software packages.   TMP must be controlled by an operating system, for instance COPSY within SSC, defining the control parameters used by TMP.    3.2.2 Development Support Software   The software used for development of this package is conta┆
0x1f500…1f600 (31, 0, 5)  Sector 1f066000158841 ┆  `   Ained in Support Software Package.    3.3 INTERFACES    3.3.1 External Interfaces   N/A    nd TMP will then wait for further requests.    2.2.2.1.2 Close Down   TMP has no responsibility of its own by close down.    2.2.2.1.3 Restart   By restart TMP┆
0x1f600…1f700 (31, 0, 6)  Sector 1f07ff00158841 ┆      A 1                                                                  3.3.2 Package Interfaces   SSC, TEP, THP, STP, and MDP interfaces to TMP by requesting search and update functions.    3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES   TMP is supported ┆
0x1f700…1f800 (31, 0, 7)  Sector 1e084700158841 ┆  G   Aby Coroutine Monitor and System Call Monitor in the CSF package.    2.2.2.2 Check Pointing and Recovery   TMP performs no check pointing.   All data except global number series will be copied to disk each time they are updated so they will always be┆
0x1f800…1f900 (31, 0, 8)  Sector 1f09ff00158841 ┆      A recoverable.   All requests to TMP where TMP has not yet returned an answer may be lost by system failure.    2.2.2.3 Error Detection and Error Handling   If input data in a TMP request are syntactically illegal or inconsistent, the requesting proc┆
0x1f900…1fa00 (31, 0, 9)  Sector 1f0aff00158841 ┆      Aess is retired by using a Kernel call.    2.2.2.4 Integrity of Operation   When no system failure occur TMP ensures that all requests will return an answer to the calling process. TMP also ensures that no request may cause damage in the TMP process.┆
0x1fa00…1fb00 (31, 0, 10) Sector 1f0bff00158841 ┆      A   Inconsistence in TMP data caused by update may result in no more output to processes requesting search than a completion code.   Inconsistence in TMP data may only be coursed by a misused update function.   The updated part of a table is written ┆
0x1fb00…1fc00 (31, 0, 11) Sector 1f0c8e00158841 ┆      Ain a safety copy at disk before the original table is updated.    2.2.2.5 Data Collection   TMP is collecting statistics on table level.nction requests from application packages and SSC and returns answers by means of system call monitor in CSF pack┆
0x1fc00…1fd00 (31, 0, 12) Sector 1f0dff00158841 ┆      A 1                                                                      2.2.2.6 Security   TMP ensures that no subprocess reads or updates data not defined at system generation time.    2.3 CHARACTERISTICS    2.3.1 Timing   The access times specifie┆
0x1fd00…1fe00 (31, 0, 13) Sector 1f0eff00158841 ┆      Ad here are maximum time per key.   When more than one key is given by one request, the mean time per key will be less than access time by one key.   The total access time is the sum of the time used by FMS and the time used by TMP.   The disk access┆
0x1fe00…1ff00 (31, 0, 14) Sector 1f0fff00158841 ┆      Aes and access times are:                               NO OF FMS   TMP PROCES-           DISK ACCESSES   SING TIME   - Parameter read or GNS access          0       0,5 ms  - Search in memory resident tables      0        30 ms  - Update of memory t┆
0x1ff00…20000 (31, 0, 15) Sector 1f00ff00158841 ┆      Aables               4        40 ms  - Search in disk tables                 1        40 ms  - Search in disk tables via reference   2        50 ms  - Update of disk tables                 5        50 ms    2.3.2 Throughput   The throughput may be in┆
0x20000…20100 (32, 0, 0)  Sector 2001ff00158841 ┆      A   Only the record fields requested by caller are delivered.    2.2.1.2 Update Of Table   One record is inserted in a table or removed from a table.   One or more records is changed.    2.2.1.3 Reorganization Of Tables   All tables are reorganized s┆
0x20100…20200 (32, 0, 1)  Sector 2002ff00158841 ┆      Ao unused records are removed and records in overflow area are put in their appropriate place.    2.2.1.4 Back-up/Reload Of TMP Data   Tables are backed up by copying them to an offline volume, or they are reloaded by copying them back in their appro┆
0x20200…20300 (32, 0, 2)  Sector 20033000158841 ┆  0   Apriate position at the on-line volume.                                     CPS/SDS/026   BMN/840105 TABLE MANAGEMENT DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS       /=MM, > I!e=6 !Z="(=e*$<kas#r  9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x20300…20400 (32, 0, 3)  Sector 2004ff00158841 ┆      A 1                                                                  2.2.1.5 Global Serial Number Management   The GSN is maintained in a way, so that they may be read or updated by other packages.   The read may cause the GSN being read to be increa┆
0x20400…20500 (32, 0, 4)  Sector 2005ff00158841 ┆      Ased by one.    2.2.1.6 System Parameter Management   A system parameter may be read or updated.    2.2.2 Functional Responsibilities    2.2.2.1 Initialization, Close Down, and Restart    2.2.2.1.1 Initialization   In initialization TMP reloads all T┆
0x20500…20600 (32, 0, 5)  Sector 2006ff00158841 ┆      AMP data and copies the memory resident data into memory. Then coroutines are initialized and TMP will then wait for further requests.    2.2.2.1.2 Close Down   TMP has no responsibility of its own by close down.    2.2.2.1.3 Restart   By restart TMP┆
0x20600…20700 (32, 0, 6)  Sector 2007b700158841 ┆  7   A will read memory resident data into memory and initialize coroutines.   Then a consistency check of disk resistent data is made and TMP will then wait for further requests.    e Documents   - CPS/DBD/001 reference (a) see also                     s┆
0x20700…20800 (32, 0, 7)  Sector 1f08ff00158841 ┆      A 1                                                                  2.2.2.2 Check Pointing and Recovery   TMP performs no check pointing.   All data except global number series will be copied to disk each time they are updated so they will always be┆
0x20800…20900 (32, 0, 8)  Sector 2009ff00158841 ┆      A 1                                                                  1.3 TERMS AND ABBREVIATIONS    1.3.1 Terms   Subprocess   Group of modules having the same access rights.   Key   Field value used to identify a record.   Table   List of same type ┆
0x20900…20a00 (32, 0, 9)  Sector 200aff00158841 ┆      Arecords.    1.3.2 Abbreviations  1                                                                    CSF CAMPS System Functions  GSN Global Serial Number  ID Identification  MDP Message Distribution Package  FMS Storage and File Management  SSC Sys┆
0x20a00…20b00 (32, 0, 10) Sector 200b8f00158841 ┆      Atem Status and Control  SyncEl Synchronization Element  TEP Terminal Package  THP Traffic Handling Package  TMP Table Management Package > S C_*                                                                                                         ┆
0x20b00…20c00 (32, 0, 11) Sector 200cff00158841 ┆      A 1                                                                   2  SUMMARY OF REQUIREMENTS    2.1 TMP DESCRIPTION   TMP receives function requests from application packages and SSC and returns answers by means of system call monitor in CSF pack┆
0x20c00…20d00 (32, 0, 12) Sector 200d5000158841 ┆  P   Aage.   TMP reads from disk and writes to disk via FMS.   Ref. fig. 2.1-1.  ....... 4 183       4.2.3.4.2.1 Functional Specification ....... 4 183       4.2.3.4.2.2 Interface Specification ........ 4 183       4.2.3.4.2.3 Components .................┆
0x20d00…20e00 (32, 0, 13) Sector 200e9f00158841 ┆      A 1                                                                                                                  Fig. 2.1-1 Package Interrelationship ........................ 4 194       4.2.3.4.3.1 Functional Specification ....... 4 194       4.┆
0x20e00…20f00 (32, 0, 14) Sector 200fff00158841 ┆      A 1                                                                  2.2 TMP FUNCTIONS    2.2.1 TMP Normal Functions   The normal TMP functions are:   - Search In Tables  - Update Of Tables  - Reorganization Of Tables  - Back-up/Reload Of TMP Data  -┆
0x20f00…21000 (32, 0, 15) Sector 2000ff00158841 ┆      A Global Serial Number Management  - System Parameter Management    2.2.1.1 Search In Tables   One or more records from a table are identified after a key value and delivered to caller.  More than one key to the same table may be specified at a time.┆
0x21000…21100 (33, 0, 0)  WangDocumentHead {hdr=WangSectHead {next=(33,0, 1), len=0xff, h3=41158841}, f00=»1588A «, f01=»CPS/SDS/026               «, f02=»pn                   «, f03=»BMN                  «, f04=»Fra kap. 1           «, f05=15-01-82 12:44, f06=»  10 «, f07=»40 «, f08=» 32014 «, f09=11-01-84 08:40, f10=»     «, f11=»01 «, f12=»    40 «, f13=11-01-84 08:42, f14=12-01-84 15:06, f15=»0117A «, f16=» 83 «, f17=»  27 «, f18=»06 «, f19=»  852 «, f20=» 62012 «, f21=»  «, f22=»   «, f99=820000000110062710110280aaca15050000000000000137031a01df}
0x21100…21200 (33, 0, 1)  Sector 21025300158841 ┆! S   A/    !   !                                                                                                                                                                     STIK  AKTIVITET DATO TID  ANV.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.V.┆
0x21200…21300 (33, 0, 2)  Sector 2103ad00158841 ┆! -   A 1                                                                         CPS/SDS/026   BMN/840105 TABLE MANAGEMENT DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS       /=MM, > I!e=6 !Z="(=e*$<kas#r  9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x21300…21400 (33, 0, 3)  Sector 2104ff00158841 ┆!     A 1                                                                   1  GENERAL    1.1 PURPOSE AND SCOPE   The purpose of Table Management Package (TMP) is to provide search and update tools to the packages which want to access the data base contain┆
0x21400…21500 (33, 0, 4)  Sector 2105ff00158841 ┆!     Aing tables, system parameters and global number series.   Furthermore, TMP will control that no package accesses other data than it is allowed to access.   This document describes TMP down to a level where all functions performed by TMP and all comp┆
0x21500…21600 (33, 0, 5)  Sector 2106ff00158841 ┆!     Aonents to be implemented inside TMP are defined.   This description is a further detailed description of TMP functions than the one in CPS/SDS/001     In this specification is given a description of general interfaces and general data structures.   ┆
0x21600…21700 (33, 0, 6)  Sector 2107ff00158841 ┆!     AFor more detailed data and interface description refer CPS/DBD/001 and CAMPS SW Interface Control Document.    1.2 APPLICABLE DOCUMENTS AND PROJECT REFERENCES    1.2.1 Applicable Documents   - CPS/DBD/001 reference (a) see also                     s┆
0x21700…21800 (33, 0, 7)  Sector 2008e300158841 ┆  c   Aec. 4.1.6  - CPS/ICD/009 reference (b)  - CSS/006/PSP/0044 reference (c)  - CPS/210/SYS/0001 reference (d)  - CPS/ICD/002 reference (e)  - CPS/SDS/001 reference (f)  - CSS/2100/PSP/0019    1.2.2 Project References   N/A. 2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x21800…21900 (33, 0, 8)  WangDocumentBody
         […0x27…]
0x24000…24100 (36, 0, 0)  WangDocumentHead {hdr=WangSectHead {next=(36,0, 1), len=0xff, h3=41159841}, f00=»1598A «, f01=»CPS/SDS/026               «, f02=»vhn                  «, f03=»BMN                  «, f04=»4.2.3                «, f05=19-01-82 14:57, f06=»   7 «, f07=»25 «, f08=» 21673 «, f09=09-01-84 13:24, f10=»     «, f11=»01 «, f12=»    25 «, f13=09-01-84 13:30, f14=12-01-84 15:08, f15=»0117A «, f16=» 28 «, f17=»  13 «, f18=»08 «, f19=»  304 «, f20=» 30393 «, f21=»  «, f22=»   «, f99=700000000110062710110280aaca15050000000000000037035d00df}
0x24100…24200 (36, 0, 1)  WangDocumentBody
         […0x6…]
0x24800…24900 (36, 0, 8)  Sector 2409ff00159241 ┆$     Ato zero.    OPERATION ARRAY is initialized and all TMP OPERATIONS are signalled to POOL SEM.    One OPERATION is received from POOL SEM and signalled to BUFFER SEM.    Synchronization Elements are looked up and associated OBJECT DESCRIPTIONS are upd┆
0x24900…24a00 (36, 0, 9)  Sector 240aff00159241 ┆$     Aated.  Files are opened and associated FILE DESCRIPTIONS are updated.      SUBPROCESS DESCRIPTIONS are updated.    Flowgram    None.    4.2.2.5 Update Subpackage Data    4.2.2.5.1 Recovery Record   The RECOVERY RECORD describes copies of TMP data ha┆
0x24a00…24b00 (36, 0, 10) Sector 240b4b00159241 ┆$ K   Aving been updated.  The copies are located at WORKING STORAGE file.  b) Backup Start    The Backup Start is performed by the Start Up type DEAD2.    Online volume is reloaded from Of Line volume using Last Backup version of TMP data.    The memory i┆
0x24b00…24c00 (36, 0, 11) Sector 240cff00159241 ┆$     A 1                                                                   RECOVERY is always located in start of first block of WORKING STORAGE file.  Memory contains a variable used as input when writing to RECOVERY at disk.  This variable is contained ┆
0x24c00…24d00 (36, 0, 12) Sector 240dff00159241 ┆$     Ain UPDATE COREC c.f. 4.2.2.5.2.   1                                                                   TYPE   RECOVERY RECORD =     RECORD      HEAD:  RECOVERY HEAD;      ELEMENTS:    ARRAY (1..HEAD.COUNT)             OF RECOVERY ELEMENT;     END,   ┆
0x24d00…24e00 (36, 0, 13) Sector 240eff00159241 ┆$     A RECOVERY HEAD =      RECORD       COMPLETE1: BOOLEAN;      COUNT    : INTEGER;      NEXT FREE: BYTE ADDRESS;      COMPLETE2: BOOLEAN;       END;   RECOVERY ELEMENT =      RECORD;        TYPE      :         (FILE, TABLE, BLOCK)       COPY START:    ┆
0x24e00…24f00 (36, 0, 14) Sector 240fff00159241 ┆$     A     BYTE ADDRESS;       BYTE COUNT:         INTEGER;       DESTINATION:        POINTER;                "To FILE DESCRIPTION                or "TABLE DESCRIPTION        DESTINATION START:  BYTE ADDRESS;      End;   Disk Located Variable   VAR   RECO┆
0x24f00…25000 (36, 0, 15) Sector 24001d00159241 ┆$     AVERY:  RECOVERY RECORD  Call Specification   RELOAD (INPUT FILE(INITIAL,BACKUP)):ERROR OK   Fatal Errors   None    4.2.2.4.6.4 Start Up Module Data   Data References   TMP COROUTINE RECORD      c.f. 4.1.4.1.17  FILE ARRAY                c.f. 4.1.4.2┆
0x25000…25100 (37, 0, 0)  WangDocumentBody
         […0x4…]
0x25500…25600 (37, 0, 5)  Sector 2506e700159241 ┆% g   A   Flowgram    None   b) Init Memory    Narrative Description    Memory resident data is read into memory, FILE ARRAY tells which data are memory resident.    Data are read via SFM by calling READ BYTES.    Flowgram    None  IFY BYTES and WRITE BYTE┆
0x25600…25700 (37, 0, 6)  Sector 2507ff00159241 ┆%     A 1                                                                   c) Reload    Narrative Description    Initialization data file or Back-Up data file is copied to On Line volume by using the SFM commands READ BYTES and WRITE BYTES.   d) Initializ┆
0x25700…25800 (37, 0, 7)  Sector 2408ff00159241 ┆$     Ae Software    Narrative Description    Coroutine Monitor is initialized in SUPPORT Coroutine.    Remaining Coroutines are initialized.    DISABLE SEM is initialized with count set to 2.  Remaining Coroutine Semaphores are initialized with count set ┆
0x25800…25900 (37, 0, 8)  WangDocumentBody
         […0xf7…]
0x35000…35100 (53, 0, 0)  Sector 3501ff00159841 ┆5     A FUNCTION    The continuation address in SOCB is used to enter the procedure which recently processed the answer from TMP. The procedure completes its work and returns output to system Call Monitor.   d) TMP CANCEL    Cancel has no effect on TMP fun┆
0x35100…35200 (53, 0, 1)  Sector 35028100159841 ┆5     Actions.    Returns to system Call Monitor.   e) WAIT    Saves the continuation address and returns to system Call Monitor. IT EQ TRUE   ? -ELEMENT.GSN = 1    OR ELEMENT.GSN EQ 9999      INCREMENT ELEMENT.GSN    BINARY TO ASCII(ELEMENT.GSN, ELEMENT.T┆
0x35200…35300 (53, 0, 2)  Sector 3503ff00159841 ┆5     A 1                                                                  4.2.3.4.3.2 Interface   a) TMP init    Call Conventions     TMP INIT  (FUNCTION : I FUNCTION,   1)   C SOCB    : POINTER,      INR04)      (OUTR04,   2)   EXIT :      EXIT NO,      ┆
0x35300…35400 (53, 0, 3)  Sector 3504ff00159841 ┆5     ACC   :      COMPLETION CODE)     TMP INIT (R0, R1, R2, R3, R4, R5, R7, R6)    Register Conventions    refer      4.1.7.2.6.-4.   b) TMP Answer Received    Call Conventions    1) TMP ANSWER RECEIVED (ANSWER    :POINTER,       FIRST SOCB :POINTER,    ┆
0x35400…35500 (53, 0, 4)  Sector 3505ff00159841 ┆5     A   LAST SOCB  :POINTER)       (DONE COUNT:INTEGER,       DONE SOCB  :POINTER)    2) TMP ANSWER RECEIVED (R4,R6,R7,R5)    Register Conventions    refer     4.1.7.2.6--4.   c) TMP Complete Function    Call conventions    1) TMP COMPLETE FUNCTION (C SO┆
0x35500…35600 (53, 0, 5)  Sector 35069b00159841 ┆5     ACB : POINTER)       (OUTR04;       EXITNO  : INTEGER,       CC      : COMPLETION CODE)    2) TMP COMPLETE FUNCTION (R0, R1, R2, R3, R4, R6, R7, R5)  .4.2.5-1   b) Daily Global Serial Number reset    Narrative:    Checks if the GSN reference is a val┆
0x35600…35700 (53, 0, 6)  Sector 3507ff00159841 ┆5     A 1                                                                    Register Conventions    refer    4.1.7.2.6-4   d  TMP Cancel    Call Conventions    1) TMP CANCEL  (C SOCB : POINTER)    2) TMP CANCEL  (R2, R5)    Register Conventions    refer  ┆
0x35700…35800 (53, 0, 7)  Sector 2300ff00159841 ┆#     A  4.1.7.2.6-4   e) WAIT    Call Conventions    1) WAIT    2) WAIT (R5)    Register Conventions    Call Registers    R5 LINK    Return Registers    NA    4.2.3.4.3.3 Components    Internal Procedures    - TMPMON INIT  cf. 4.2.3.4.3.5.a   - TMP ANSWER┆
0x35800…35900 (53, 0, 8)  Sector 35093a00159841 ┆5 :   A   restore registers    ENTER(SCM RETURN)   stop    nary.  aces:   a) Set Global Serial Number cf. (b) 4.1.10  b) Daily Global Serial Number Reset cf. (b) 4.1.11  c) Get Global Serial Number cf. (b) 4.1.12  d) Get System Parameters cf. (b) 4.1.15   ┆
0x35900…35a00 (53, 0, 9)  Sector 350aff00159841 ┆5     A 1                                                                         GET SYSTEM PARAMETERS (PARAMETER ID: PARAMETER ID TYPE)      (OUTPUT PARAM: SYSTEM PARAMETER,       CC: COMPLETION CODE):       ERROR OK   start    CHECK PAGE ACCESS(OUTPUT P┆
0x35a00…35b00 (53, 0, 10) Sector 350bff00159841 ┆5     AARAM)    PARAMETER ID GT MAX SYSTEM PARAMETERS    LOCK(TMP HW SEM)    EQUIVALENCE(SYSTEM PARAMETER POINTER ARRAY(PARAMETER ID),      ELEMENT: SYSTEM PARAMETER SPECIFIER)    PARAMETER% = ELEMENT.PARAM    L = 1    LOOP     OUTPUT PARAM(L) = PARAMETER ┆
0x35b00…35c00 (53, 0, 11) Sector 350ce900159841 ┆5 i   A(L)     L = ELEMENT.LENGTH (( EXIT     INCREMENT (L)    END LOOP    UNLOCK(TMP HW SEM)    SOCB.STATUS = DONE    UPDATE SOCB(OK)    WAIT    restore registers    ENTER(SCM RETURN)    TMP RETIRE(TMP, PARAMETER ID ERROR)   stop    POINTER ARRAY and the ┆
0x35c00…35d00 (53, 0, 12) Sector 350dff00159841 ┆5     A 1                                                                  4.2.3.4.3 Main Module    4.2.3.4.3.1 Functional Specification   The Main Module is implemented as 4 procedures called by system Call Monitor;   TMP INIT, TMP ANSWER RECEIVED, TMP CO┆
0x35d00…35e00 (53, 0, 13) Sector 350eff00159841 ┆5     AMPLETE FUNCTION, TMP CANCEL, and 1 procedure used by actual functions WAIT.   a) TMP INIT    The Function Parameter delivered by system Call Monitor is used to select one of the external TMP monitor SCM procedures described in 4.2.3.4.1. The selecte┆
0x35e00…35f00 (53, 0, 14) Sector 350fff00159841 ┆5     Ad procedure is entered. When it reaches the point where answer from TMP shall be awaited, it places the address of the continuation point in the SOCB and returns to system Call Monitor.   b) TMP ANSWER RECEIVED    Uses the continuation address in SO┆
0x35f00…36000 (53, 0, 15) Sector 3500ff00159841 ┆5     ACB to enter the procedure which has initiated the operation represented by SOCB. When the answer has been checked, the procedure now saves in SOCB the continuation address for function completion and returns to system Call Monitor.   c) TMP COMPLETE┆
0x36000…36100 (54, 0, 0)  Sector 3601ff00159841 ┆6     A 1                                                                       GET GSN   (GSN ID: GSN ID TYPE,      INCREASE:  BOOLEAN,      (GSN VALUE:LONG      (CC: COMPLETION CODE):      ERROR OK   start    CHECK GSN(GSN ID)(ID)    LOCK(TMP HW SEM)    ┆
0x36100…36200 (54, 0, 1)  Sector 3602ff00159841 ┆6     AINCREASE EQ FALSE?    EQUIVALENCE(GSN ARRAY(ID), ELEMENT: GSN ARRAY ELEMENT)    ELEMENT.GSN EQ 999 AND    ELEMENT.THREE DIGIT EQ TRUE   ? -ELEMENT.GSN = 1    OR ELEMENT.GSN EQ 9999      INCREMENT ELEMENT.GSN    BINARY TO ASCII(ELEMENT.GSN, ELEMENT.T┆
0x36200…36300 (54, 0, 2)  Sector 3603bc00159841 ┆6 <   AHREE DIGIT)(GSN            VALUE)    UNLOCK(TMP HW SEM)    Update SOCB with: DONE and RETURN REGISTERS    UPDATE SOCB(OK)    WAIT    restore registers    ENTER(SCM RETURN)   stop    specified GSN ARRAY element is incremented according to the followi┆
0x36300…36400 (54, 0, 3)  Sector 3604ff00159841 ┆6     A 1                                                                       SET GSN   (GSN ID: GSN ID TYPE,      (GSN VALUE:GSN TEXT TYPE)      (CC: COMPLETION CODE):      ERROR OK   start    CHECK GSN ID(GSN ID)(ID)    ASCII TO BINARY(GSN VALUE)(GSN) ┆
0x36400…36500 (54, 0, 4)  Sector 3605ff00159841 ┆6     A   LOCK(TMP HW SEM)    EQUIVALENCE(GSN ARRAY(ID), ELEMENT: GSN ARRAY ELEMENT)    GSN GT 999 and    ELEMENT.THREE DIGIT EQ FALSE  ? -CC = ILLEGAL GSN FORMAT    ELEMENT.GSN = GSN    CC = OK    UNLOCK(TMP HW SEM)    SOCB.STATUS: DONE      UPDATE SOCB(C┆
0x36500…36600 (54, 0, 5)  Sector 36064300159841 ┆6 C   AC)    WAIT    restore registers    ENTER(SCM RETURN)   stop      Function completion is awaited    Waiting point is WAIT   Flowgram:   See fig. 4.2.3.4.2.5-1   b) Daily Global Serial Number reset    Narrative:    Checks if the GSN reference is a val┆
0x36600…36700 (54, 0, 6)  Sector 3607ff00159841 ┆6     A 1                                                                       DAILY GSN RESET (GSN ID: GSN ID TYPE,      (CC: COMPLETION CODE):      ERROR OK   start    CHECK GSN ID(GSN ID)(ID)    EQUIVALENCE(GSN ARRAY(ID), ELEMENT: GSN ARRAY ELEMENT)   ┆
0x36700…36800 (54, 0, 7)  Sector 3508ff00159841 ┆5     A LOCK(TMP HW SEM)    ELEMENT.DAILY RESET                 ?       CC = REJECTED   EQ FALSE    ELEMENT.THREE DIGIT EQ TRUE  ? -ELEMENT.GSN = 999    ELEMENT.GSN = 9999    UNLOCK(TMP HW SEM)    CC = OK      SOCB.STATUS = DONE    UPDATE SOCB(CC)    WAIT ┆
0x36800…36900 (54, 0, 8)  Sector 36094100159841 ┆6 A   Ared.    The input GSN ASCII value is converted to binary.  aces:   a) Set Global Serial Number cf. (b) 4.1.10  b) Daily Global Serial Number Reset cf. (b) 4.1.11  c) Get Global Serial Number cf. (b) 4.1.12  d) Get System Parameters cf. (b) 4.1.15   ┆
0x36900…36a00 (54, 0, 9)  Sector 360aff00159841 ┆6     A 1                                                                  The GSN array is locked.    Then the specified GSN array element is set to binary GSN value according to the Three DIGIT flag.     If any discrepancy exists an informative CC is ret┆
0x36a00…36b00 (54, 0, 10) Sector 360bff00159841 ┆6     Aurned.     Then the GSN array is unlocked and function completion is awaited.    Waiting point is WAIT.    Flowgram:    See fig. 4.2.3.4.2.5-3   d) Get System Parameter    Narrative:    It is checked that the specified output address is within the l┆
0x36b00…36c00 (54, 0, 11) Sector 360cff00159841 ┆6     Aogical dataspace of caller and that the parameter reference is a valid parameter reference. If these checks are not successfull the caller is retired.    then a pointer to the wanted parameter is read from the SYSTEM PARAMETER POINTER ARRAY and the ┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00159841 ┆6     Acorresponding SYSTEM PARAMETER is reserved by locking TMP HW SEM.    Then the parameter is written to the buffer specified by caller.    The TMP HW SEM is unlocked and function completion is awaited.    Waiting point in WAIT.    Flowgram:    See fig┆
0x36d00…36e00 (54, 0, 13) Sector 360e1700159841 ┆6     A. 4.2.3.4.2.5-4  s converted to a binary value.   Call conventions   ASCII TO BINARY(ASCII VALUE: LONG)        (BIN VALUE: INTEGER)     CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, BACKUP INFO)    Update INFO with:     XFER =    SIZE = S┆
0x36e00…36f00 (54, 0, 14) Sector 360fff00159841 ┆6     A 1                                                                 e) Binary to ASCII    Narrative:    The Binary value is converted to a four character ASCII value.    If THREE DIGIT is TRUE the most significant ASCII value will be a space.    The ┆
0x36f00…37000 (54, 0, 15) Sector 3600c500159841 ┆6 E   AASCII value will be filled out with preceeding zeroes .    Flowgram:    NA   f) ASCII to binary    The three or four character ASCII value is converted to a binary value.    Flowgram:    NA   cf. 4.1.4.5   TMP HW SEM cf. 4.1.4.7   GSN GROUP cf. 4.1.┆
0x37000…37100 (55, 0, 0)  Sector 3701ff00159841 ┆7     A4.6   PARAMETER SPECIFIER ARRAY cf. 4.1.4.5   PARAMETER SPECIFIER cf. 4.1.4.5   b) External Data    GSN ELEMENT.DAILY RESET   GSN ELEMENT.THREE DIGIT   GSN ELEMENT.GSN (m)   SYSTEM PARAMETER SPECIFIER.LENGTH   SYSTEM PARAMETER SPECIFIER.PARAMETER   ┆
0x37100…37200 (55, 0, 1)  Sector 3702ff00159841 ┆7     ATMP HW SEM (m)   MAX SYSTEM.PARAMETERS: INTEGER   c) Local Data    NA    4.2.3.4.2.5 Module Design   External Procedures   CHECK PAGE ACCESS 4.2.3.6.2  TMP RETIRE  4.2.3.6.3  CHECK GSN ID 4.2.3.6.1   a) Get Global Serial Number    Narrative    Check┆
0x37200…37300 (55, 0, 2)  Sector 3703ff00159841 ┆7     As if the specified GSN reference is a Valid GSN reference. If not the caller is retired.    The GSN ARRAY is reserved by Locking TMP HW SEM.    If the parameter INCREASE is TRUE the specified GSN ARRAY element is incremented according to the followi┆
0x37300…37400 (55, 0, 3)  Sector 37041000159841 ┆7     Ang rule:                                                                   SET SYSTEM PARAMETER (PARAMETER ID:PARAMETER ID TYPE,      PARAMETER:    POINTER      (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, SET SYSTEM PARA┆
0x37400…37500 (55, 0, 4)  Sector 3705ff00159841 ┆7     A 1                                                                  A three digit GSN will allways wrap around to 1 after 999 and a four digit GSN will allways wrap around to 1 after 9999.    Then the specified GSN is read and the TMP HW SEM is unlo┆
0x37500…37600 (55, 0, 5)  Sector 3706ff00159841 ┆7     Acked.    The output is converted to ASCII and SOCB is updated    Function completion is awaited    Waiting point is WAIT   Flowgram:   See fig. 4.2.3.4.2.5-1   b) Daily Global Serial Number reset    Narrative:    Checks if the GSN reference is a val┆
0x37600…37700 (55, 0, 6)  Sector 3707ff00159841 ┆7     Aid GSN reference. If not the caller is retired.    The GSN ARRAY is reserved by locking TMP HW SEM. If the DAILY RESET flag of the specified GSN is set the specified GSN is for a three digit GSN set to 999 and for a four digit GSN set to 9999.    Th┆
0x37700…37800 (55, 0, 7)  Sector 3608ff00159841 ┆6     Ae TMP HW SEM is unlocked and function completion awaited.    Waiting point is WAIT.    Flowgram:    See fig. 4.2.3.4.2.5-2   c) Set Global Serial Number    Narrative:    Checks if the GSN reference is a valid GSN reference. If not the caller is reti┆
0x37800…37900 (55, 0, 8)  Sector 3709ff00159841 ┆7     A has the following interfaces, which all are Package Interfaces:   a) Set Global Serial Number cf. (b) 4.1.10  b) Daily Global Serial Number Reset cf. (b) 4.1.11  c) Get Global Serial Number cf. (b) 4.1.12  d) Get System Parameters cf. (b) 4.1.15   ┆
0x37900…37a00 (55, 0, 9)  Sector 370aff00159841 ┆7     A 4.2.3.4.2.3 Components   refer figure 4.2.3.4.2.3-1   The components,   - SET GSN  cf. 4.2.3.4.2.5.a  - DAILY GLOBAL SERIAL NUMBER RESET cf. 4.2.3.4.2.5.b  - GET GSN  cf. 4.2.3.4.2.5.c  - GET SYSTEM PARAMETERS cf. 4.2.3.4.2.5.d   are implemented as┆
0x37a00…37b00 (55, 0, 10) Sector 370b5200159841 ┆7 R   A SCM procedures   - BINARY TO ASCII cf. 4.2.3.4.2.5.e   Internal procedure  ACKUP    (    )        (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, BACKUP INFO)    Update INFO with:     XFER =    SIZE = SIZE(BACKUP INFO)    D┆
0x37b00…37c00 (55, 0, 11) Sector 370cff00159841 ┆7     A 1                                                                 Functional Specification   A binary number is converted to three or four character ASCII number depending on the parameter THREE DIGIT.   If it is a three character ASCII number the ┆
0x37c00…37d00 (55, 0, 12) Sector 370dff00159841 ┆7     Afirst character will be a space.   Call conventions   BINARY TO ASCII(BIN VALUE: INTEGER,         THREE DIGIT: BOOLEAN)        (ASCII VALUE: LONG)   - ASCII TO BINARY cf. 4.2.3.4.2.5.f   Internal procedure   Functional Specification   A four charact┆
0x37d00…37e00 (55, 0, 13) Sector 370e8e00159841 ┆7     Aer ASCII number is converted to a binary value.   Call conventions   ASCII TO BINARY(ASCII VALUE: LONG)        (BIN VALUE: INTEGER)     CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, BACKUP INFO)    Update INFO with:     XFER =    SIZE = S┆
0x37e00…37f00 (55, 0, 14) Sector 370f8800159841 ┆7     A 1                                                                      Figure 4.2.3.4.2.3 TMP MON function module components     O TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers ┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00159841 ┆7     A 1                                                                4.2.3.4.2.4 Data Description   a) Data References    GSN ELEMENT cf. 4.1.4.6   GSN ARRAY cf. 4.1.4.6   SYSTEM PARAMETER ARRAY cf. 4.1.4.5   TMP HW SEM cf. 4.1.4.7   GSN GROUP cf. 4.1.┆
0x38000…38100 (56, 0, 0)  Sector 3801ff00159841 ┆8     A 1                                                                         SET GSN FLAGS  (GSN ID: GSN ID TYPE)       DAILY RESET: BOOLEAN,       THREE DIGIT: BOOLEAN)       (CC: COMPLETION CODE):        ERROR OK   start    CHECK GSN ID(GSN ID)(ID) ┆
0x38100…38200 (56, 0, 1)  Sector 3802ff00159841 ┆8     A   EQUIVALENCE(INFO.DATA, SET GSN FLAGS INFO)    Update INFO with:     XFER =    SIZE = SIZE(SET GSN FLAGS INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = SET GSN FLAGS    DATA.SUBPROCESS = CURRENT SUBPROCESS    DATA.GSN ID = ID    DATA.DAILY RESET = D┆
0x38200…38300 (56, 0, 2)  Sector 3803e900159841 ┆8 i   AAILY RESET    DATA.THREE DIGIT = THREE DIGIT    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSER.CC)    WAIT    restore registers    ENTER(SCM RETURN)   stop     Figure 4.2.3.4.1.5-10  )    CHECK CC(ANSWER.C┆
0x38300…38400 (56, 0, 3)  Sector 3804ff00159841 ┆8     A 1                                                                         SET SYSTEM PARAMETER (PARAMETER ID:PARAMETER ID TYPE,      PARAMETER:    POINTER      (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, SET SYSTEM PARA┆
0x38400…38500 (56, 0, 4)  Sector 3805ff00159841 ┆8     AMETER INFO)    Update INFO with:     XFER =    SIZE = SIZE(SET GSN SYSTEM PARAMETER INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = SET SYSTEM PARAMETER    DATA.SUBPROCESS = CURRENT SUBPROCESS    DATA.PARAMETER ID = PARAMETER ID    DATA.PARAMS = PARAME┆
0x38500…38600 (56, 0, 5)  Sector 3806c200159841 ┆8 B   ATER    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers    ENTER(SCM RETURN)   stop     Figure 4.2.3.4.1.5-11       WAIT    restore registers    ENTER(SCM RETURN)   stop    ┆
0x38600…38700 (56, 0, 6)  Sector 3807ff00159841 ┆8     A 1                                                                4.2.3.4.2 TMP monitor functions module    4.2.3.4.2.1 Functional Specification   The TMP monitor functions module contains the functions, the functional Description of which can be fo┆
0x38700…38800 (56, 0, 7)  Sector 3708ff00159841 ┆7     Aund as follows:   a) Set Global Serial Number cf. (b) 4.1.10  b) Daily Global Serial Number Reset cf. (b) 4.1.11  c) Get Global Serial Number cf. (b) 4.1.12  d) Get System Parameters cf. (b) 4.1.15    4.2.3.4.2.2 Interface Specification   The Module┆
0x38800…38900 (56, 0, 8)  Sector 3809ff00159841 ┆8     AIZE(ABANDON REORGANIZE INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = ABANDON REORGANIZE    DATA.SUBPROCESS = SUBPROCESS ID    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers┆
0x38900…38a00 (56, 0, 9)  Sector 380a3e00159841 ┆8 >   A    ENTER(SCM RETURN)   stop     Figure 4.2.3.4.1.5-7   OUNT = COUNT, BUFFER = BUFFER    SEND TO TMP(SEARCH SYNCEL, INFO)    EQUIVALENCE(ANSWER, GET TMP STATISTICS RESPONSE)   CHECK CC(ANSWER.CC)    Update SOCB with outputparameters    WAIT    resto┆
0x38a00…38b00 (56, 0, 10) Sector 380bff00159841 ┆8     A 1                                                                         BACKUP    (    )        (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, BACKUP INFO)    Update INFO with:     XFER =    SIZE = SIZE(BACKUP INFO)    D┆
0x38b00…38c00 (56, 0, 11) Sector 380cff00159841 ┆8     AATA.SOCB = SOCB    DATA.FUNCTION = BACKUP    DATA.SUBPROCESS = CURRENT SUBPROCESS    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers    ENTER(SCM RETURN)   stop     Figure ┆
0x38c00…38d00 (56, 0, 12) Sector 380d1600159841 ┆8     A4.2.3.4.1.5-8       SIZE = SIZE(GET TABLE ATTRIBUTES INFO)    DATA.SOCB: SOCB    DATA.FUNCTION: GET TABLE ATTRIBUTES    DATA.SUBPROCESS: CURRENT SUBPROCESS    DATA.TABLE ID: TABLE ID TYPE    DATA.PARAMS: ATTRIBUTES %    SEND TO TMP(SEARCH SYNCEL, IN┆
0x38d00…38e00 (56, 0, 13) Sector 380eff00159841 ┆8     A 1                                                                         System Start Up  (MODE: START UP TYPE)       (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, BACKUP INFO)    Update INFO with:     XFER =    SIZE = S┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00159841 ┆8     AIZE(SYSTEM START UP INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = SYSTEM START UP    DATA.SUBPROCESS = CURRENT SUBPROCESS    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers ┆
0x38f00…39000 (56, 0, 15) Sector 38003d00159841 ┆8 =   A   ENTER(SCM RETURN)   stop     Figure 4.2.3.4.1.5-9   NCTION = LOCK TABLE    DATA.SUBPROCESS ID = CURRENT SUBPROCESS    DATA.TABLE ID = TABLE ID    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    W┆
0x39000…39100 (57, 0, 0)  Sector 39015700159841 ┆9 W   AAIT    restore registers    ENTER(SCM RETURN)   stop      Figure 4.2.3.4.1.5-4   s      Narrative:    As for Get TMP statistics    Flowgram: See fig. 4.2.3.4.1.5-11   l) Send to TMP    Narrative:    Sends the specified infoblock to specified SYNCEL ┆
0x39100…39200 (57, 0, 1)  Sector 3902ff00159841 ┆9     A 1                                                                         UNLOCK TABLE  (TABLE ID: TABLE ID TYPE)       (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, UNLOCK TABLE INFO)    Update INFO with:     XFER =    S┆
0x39200…39300 (57, 0, 2)  Sector 3903ff00159841 ┆9     AIZE = SIZE(UNLOCK TABLE INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = UNLOCK TABLE    DATA.SUBPROCESS ID = CURRENT SUBPROCESS    DATA.TABLE ID = TABLE ID    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.C┆
0x39300…39400 (57, 0, 3)  Sector 39045d00159841 ┆9 ]   AC)    WAIT    restore registers    ENTER(SCM RETURN)   stop     Figure 4.2.3.4.1.5-5   AMS: TMP PARAM)      (CC:     COMPLETION CODE)               ERROR OK     start    CSF TRACE(N REQUEST, R REQUEST, 0, NIL)   CSF TRACE(N REQUEST PARAMS, P REQUEST┆
0x39400…39500 (57, 0, 4)  Sector 3905ff00159841 ┆9     A 1                                                                         REORGANIZE   (    )       (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, REORGANIZE INFO)    Update INFO with:     XFER =    SIZE = SIZE(REORGANIZE ┆
0x39500…39600 (57, 0, 5)  Sector 3906ff00159841 ┆9     AINFO)    DATA.SOCB = SOCB    DATA.FUNCTION = SOCB    DATA.SUBPROCESS = CURRENT SUBPROCESS    SENT TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers    ENTER(SCM RETURN)   stop    ┆
0x39600…39700 (57, 0, 6)  Sector 39071d00159841 ┆9     AFigure 4.2.3.4.1.5-6   (SYNCEL, INFO)   EQUIVALENCE(ANSWER, NORMAL RESPONSE)   CHECK CC(ANSWER.CC)   WAIT   restore registers   ENTER(SCM RETURN)  stop     Figure 4.2.3.4.1.5-1 REQUEST  117A  58    9 35   548  23221    @ t           *J         7 E _┆
0x39700…39800 (57, 0, 7)  Sector 3808ff00159841 ┆8     A 1                                                                         ABANDON REORGANIZE  (    )       (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, ABANDON REORGANIZE INFO)    Update INFO with:     XFER =    SIZE = S┆
0x39800…39900 (57, 0, 8)  Sector 3909ff00159841 ┆9     AOMPLETION CODE):       ERROR OK   start    EQUIVALENCE(INFO.DATA, GET TMP STATISTICS INFO)    Update INFO with:     XFER =    SIZE = SIZE(GET TMP STATISTICS INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = GET TMP STATISTICS    DATA.SUBPROCESS = CURRENT┆
0x39900…39a00 (57, 0, 9)  Sector 390aff00159841 ┆9     A SUBPROCESS    DATA.FIRST = FIRST, LAST = LAST    DATA.COUNT = COUNT, BUFFER = BUFFER    SEND TO TMP(SEARCH SYNCEL, INFO)    EQUIVALENCE(ANSWER, GET TMP STATISTICS RESPONSE)   CHECK CC(ANSWER.CC)    Update SOCB with outputparameters    WAIT    resto┆
0x39a00…39b00 (57, 0, 10) Sector 390b3200159841 ┆9 2   Are    ENTER   stop    Figure 4.2.3.4.1.5-2  :    A SYNCEL infoblock of proper type is updated and a message is sent to TMP by calling SEND TO TMP.    Upon return the completion code received is checked and function completion is awaited.    Waiting ┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00159841 ┆9     A 1                                                                         GET TABLE ATTRIBUTES (TABLE ID: TABLE ID TYPE)      (ATTRIBUTES: TABLE ATTRIBUTES):      ERROR OK   start    EQUIVALENCE(INFO.DATA, GET TABLE ATTRIBUTES INFO)    Update INFO ┆
0x39c00…39d00 (57, 0, 12) Sector 390dff00159841 ┆9     Awith:     XFER =    SIZE = SIZE(GET TABLE ATTRIBUTES INFO)    DATA.SOCB: SOCB    DATA.FUNCTION: GET TABLE ATTRIBUTES    DATA.SUBPROCESS: CURRENT SUBPROCESS    DATA.TABLE ID: TABLE ID TYPE    DATA.PARAMS: ATTRIBUTES %    SEND TO TMP(SEARCH SYNCEL, IN┆
0x39d00…39e00 (57, 0, 13) Sector 390e9d00159841 ┆9     AFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    WAIT    restore registers    ENTER(SCM RETURN)   stop     Figure 4.2.3.4.1.5-3    As for Get TMP statistics    Flowgram: See figure 4.2.3.4.1.5-7   h) Backup    Narrative:    As f┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00159841 ┆9     A 1                                                                         LOCK TABLE   (TABLE ID: TABLE ID TYPE)       (CC: COMPLETION CODE):        ERROR OK   start    EQUIVALENCE(INFO.DATA, LOCK TABLE INFO)    Update INFO with:     XFER =    SIZE┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00159841 ┆9     A = SIZE(LOCK TABLE INFO)    DATA.SOCB = SOCB    DATA.FUNCTION = LOCK TABLE    DATA.SUBPROCESS ID = CURRENT SUBPROCESS    DATA.TABLE ID = TABLE ID    SEND TO TMP(UPDATE SYNCEL, INFO)    EQUIVALENCE(ANSWER, NORMAL RESPONSE)    CHECK CC(ANSWER.CC)    W┆
0x3a000…3a100 (58, 0, 0)  Sector 3a01ff00159841 ┆:     AGet TMP statistics    Flowgram: See fig. 4.2.3.4.1.5-10   k) Set System Parameters      Narrative:    As for Get TMP statistics    Flowgram: See fig. 4.2.3.4.1.5-11   l) Send to TMP    Narrative:    Sends the specified infoblock to specified SYNCEL ┆
0x3a100…3a200 (58, 0, 1)  Sector 3a02ff00159841 ┆:     Ain TMP process by calling the Damos communication procedure SEND.    Then saves LINK in SOCB and waits for "answer received" by calling the procedure WAIT.    Upon return LINK is fetched from SOCB     Waiting point in WAIT    Flowgram:    NA   m) CH┆
0x3a200…3a300 (58, 0, 2)  Sector 3a03db00159841 ┆: [   AECK CC    Narrative:    It is checked that specified completion code is an informative one. If not the CC is fatal and the caller is Retired.    Then the SOCB, is updated by calling UPDATE SOCB    Flowgram:    NA TISTICS INFO cf. 4.2.3.7.1   GET TMP┆
0x3a300…3a400 (58, 0, 3)  Sector 3a04ff00159841 ┆:     A 1                                                                       REQUEST   (PARAMS: TMP PARAM)      (CC:     COMPLETION CODE)               ERROR OK     start    CSF TRACE(N REQUEST, R REQUEST, 0, NIL)   CSF TRACE(N REQUEST PARAMS, P REQUEST┆
0x3a400…3a500 (58, 0, 4)  Sector 3a05ff00159841 ┆:     A,      SIZE(TMP PARAM), PARAMS)   CHECK PAGE ACCESS((PARAMS), SIZE(TMP PARAM))   PARAM.FUNCTION ILLEGAL? --TMP RETIRE(TMP, ILLEGAL       FUNCTION)   EQUIVALENCE(INFO.DATA, REQUEST INFO)   Update INFO with    XFER =    SIZE = SIZE(REQUEST INFO)    DA┆
0x3a500…3a600 (58, 0, 5)  Sector 3a06ff00159841 ┆:     ATA.SOCB = SOCB    DATA.FUNCTION-PARAMS.FUNCTION SHIFT 8 ADD TMP                       REQUEST    DATA.TABLE ID = PARAMS.TABLE ID    DATA.PARAMS = PARAMS   PARAMS.FUNCTION EQ SEARCH FUNCTION?   SYNCEL = UPDATE SYNCEL                   (SYNCEL = SEARC┆
0x3a600…3a700 (58, 0, 6)  Sector 3a07c000159841 ┆: @   AH SYNCEL)   SEND TO TMP(SYNCEL, INFO)   EQUIVALENCE(ANSWER, NORMAL RESPONSE)   CHECK CC(ANSWER.CC)   WAIT   restore registers   ENTER(SCM RETURN)  stop     Figure 4.2.3.4.1.5-1 REQUEST  117A  58    9 35   548  23221    @ t           *J         7 E _┆
0x3a700…3a800 (58, 0, 7)  Sector 3908ff00159841 ┆9     A 1                                                                         GET TMP STATISTICS (FIRST: TABLE ID TYPE,       LAST: TABLE ID TYPE,       COUNT: INTEGER)      (BUFFER: POINTER,       LAST: TABLE ID TYPE,       COUNT: INTEGER,       CC: C┆
0x3a800…3a900 (58, 0, 8)  Sector 3a09ff00159841 ┆:     Aunction specified in PARAMS is a legal function. If not, the caller is retired.    Then a SYNCEL infoblock is updated according to the type REQUEST INFO and a message is sent to the TMP process by calling SEND TO TMP. If a search function is specifi┆
0x3a900…3aa00 (58, 0, 9)  Sector 3a0aff00159841 ┆:     Aed the message is sent to the SEARCH SYNCEL. If not it is sent to the UPDATE SYNCEL.    Upon return the completion code received is checked and function completion is awaited.    Waiting point in SEND TO TMP and WAIT.    Flowgram: See figure 4.2.3.4┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0bff00159841 ┆:     A.1.5-1.   b) Get-TMP-Statistics    Narrative:    A SYNCEL infoblock of proper type is updated and a message is sent to TMP by calling SEND TO TMP.    Upon return the completion code received is checked and function completion is awaited.    Waiting ┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cba00159841 ┆: :   Apoint in SEND TO TMP and WAIT.    Flowgram. See figure 4.2.3.4.1.5-2.   c) Get Table Attributes    Narrative:    As for Get TMP Statistics.    Flowgram: See figure 4.2.3.4.1.5-3.  ze cf. (b) 4.1.7   h) Backup  cf. (b) 4.1.8   i) System Start up cf. ┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0dff00159841 ┆:     A 1                                                                   d) Lock Table    Narrative:    As for Get TMP statistics.    Flowgram: See figure 4.2.3.4.1.5-4.   e) Unlock Table    Narrative:    As for Get TMP statistics    Flowgram: See figur┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00159841 ┆:     Ae 4.2.3.4.1.5-5   f) Reorganize    Narrative:    As for Get TMP statistics    Flowgram: See fig. 4.2.3.4.1.5-6   g) Abandon Reorganize    Narrative:    As for Get TMP statistics    Flowgram: See figure 4.2.3.4.1.5-7   h) Backup    Narrative:    As f┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fa700159841 ┆: '   Aor Get TMP statistics    Flowgram: See figure 4.2.3.4.1.5-8   i) System Start Up    Narrative:    As for Get TMP statistics    Flowgram: See fig. 4.2.3.4.1.5-9  on   An info block is sent to specified SYNCEL.   The procedure contains a waiting point┆
0x3af00…3b000 (58, 0, 15) Sector 3a00ff00159841 ┆:     A 1                                                                   j) SET GSN Flags    Narrative:    It is checked that specified GSN ID is valid and if not the caller is retired. The GSN ID is converted to index in GSN array.    Continues as for ┆
0x3b000…3b100 (59, 0, 0)  Sector 3b01ff00159841 ┆;     A 1                                                                   Call conventions   SEND TO TMP (SYNCEL: OBJ INDEX,         INFO:   POINTER)   CHECK CC  cf. 4.2.3.4.1.5 m   internal procedure   Call conventions   CHECK CC (CC: COMPLETION CODE)  ┆
0x3b100…3b200 (59, 0, 1)  Sector 3b026500159841 ┆; e   A 1                                                                        Figure 4.2.3.4.1.3-1 ET cf. 4.2.3.4.2.5 c  - GET SYSTEM PARAMETER cf. 4.2.3.4.2.5 d   4.2.3.2.2 Internal Procedures   - TMP INIT cf. 4.2.3.4.3.5 a  - TMP ANSWER RECEIVED cf. 4┆
0x3b200…3b300 (59, 0, 2)  Sector 3b03ff00159841 ┆;     A 1                                                                  4.2.3.4.1.4 Data Description   a) Data references    SYNC INFO cf. (a) 3.4.1.4   OBJ INDEX cf. (a) 4.2   REQUEST INFO cf. 4.2.3.7.1   GET TMP STATISTICS INFO cf. 4.2.3.7.1   GET TMP┆
0x3b300…3b400 (59, 0, 3)  Sector 3b04ff00159841 ┆;     A STATISTICS RESPONSEcf. 4.2.3.7.2   GET TABLE ATTRIBUTES INFO cf. 4.2.3.7.1   LOCK TABLE INFO cf. 4.2.3.7.1   LOCK TABLE INFO cf. 4.2.3.7.1   UNLOCK TABLE INFO cf. 4.2.3.7.1   REORGANIZE INFO cf. 4.2.3.7.1   ABANDON REORGANIZE INFO cf. 4.2.3.7.1   B┆
0x3b400…3b500 (59, 0, 4)  Sector 3b05ff00159841 ┆;     AACKUP INFO cf. 4.2.3.7.1   SYSTEM START UP INFO cf. 4.2.3.7.1   SET GSN FLAGS INFO cf. 4.2.3.7.1   SET SYSTEM PARAMETER INFO cf. 4.2.3.7.1   NORMAL RESPONSE cf. 4.2.3.7.2   SOCB ARRAY cf. (a) 4.3   b) External Data    SOCB.SS DATA (m)   c) Local Dat┆
0x3b500…3b600 (59, 0, 5)  Sector 3b06ff00159841 ┆;     Aa    INFO:  SYNC INFO;   UPDATE SYNCEL,   SEARCH SYNCEL: OBJ INDEX;      used in SEND TO TMP   N REQUEST PARAMS,   R REQUEST,   D REQUEST,   N REQUEST: INTEGER;      used in call of CSF TRACE    4.2.3.4.1.5 Module Design   External Procedures   CHEC┆
0x3b600…3b700 (59, 0, 6)  Sector 3b079100159841 ┆;     AK PAGE ACCESS    cf. 4.2.3.6.2  CSF TRACE            (b) 4.1.7.2.1.12  SEND                 (d) 4.1.6.2  TMP RETIRE          cf. 4.2.3.6.3       00      2 04 05 82 16 45 10 05 82 10 53 0117A  58    9 35   548  23221    @ t           *J         7 E _┆
0x3b700…3b800 (59, 0, 7)  Sector 3a08ff00159841 ┆:     A 1                                                                   a) Request    Narrative:    It is checked that the specified PARAMS are located in the logical dataspace of calling process. If not, the caller is retired. It is checked that the f┆
0x3b800…3b900 (59, 0, 8)  Sector 3b09ff00159841 ┆;     A functional description of which can be found as follows:   a) Request  cf. (b) 4.1.1   b) Get TMP statistics cf. (b) 4.1.2   c) Get table attributes cf. (b) 4.1.3   d) Lock table cf. (b) 4.1.4   e) Unlock table cf. (b) 4.1.5   f) Reorganize cf. (b)┆
0x3b900…3ba00 (59, 0, 9)  Sector 3b0aff00159841 ┆;     A 4.1.6   g) Abandon reorganize cf. (b) 4.1.7   h) Backup  cf. (b) 4.1.8   i) System Start up cf. (b) 4.1.9   j) Set GSN flags cf. (b) 4.1.13   k) Set system parameters cf. (b) 4.1.14    4.2.3.4.12 Interface   The module has the following package int┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0b7a00159841 ┆; z   Aerfaces:   a) Request  cf. (b) 4.1.1   b) Get TMP statistics cf. (b) 4.1.2   c) Get table attributes cf. (b) 4.1.3  NT DETAILED DESIGN SPECIFICATION  CAMPS       )M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r  9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00159841 ┆;     A 1                                                                   d) Lock table cf. (b) 4.1.4   e) Unlock table cf. (b) 4.1.5   f) Reorganize cf. (b) 4.1.6   g) Abandon reorganize cf. (b) 4.1.7   h) Backup  cf. (b) 4.1.8   i) System Start up cf. ┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00159841 ┆;     A(b) 4.1.9   j) Set GSN flags cf. (b) 4.1.13   k) Set system parameters cf. (b) 4.1.14    4.2.3.4.1.3 Components   Refer figure 4.2.3.4.1.3-1   The Components   - REQUEST  cf. 4.2.3.4.1.5 a  - GET TMP STATISTICS cf. 4.2.3.4.1.5 b  - GET TABLE ATTRIBU┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00159841 ┆;     ATES cf. 4.2.3.4.1.5 c  - LOCK TABLE cf. 4.2.3.4.1.5 d  - UNLOCK TABLE cf. 4.2.3.4.1.5 e  - REORGANIZE cf. 4.2.3.4.1.5 f  - ABANDON REORGANIZE cf. 4.2.3.4.1.5 g  - BACKUP  cf. 4.2.3.4.1.5 h  - SYSTEM START UP cf. 4.2.3.4.1.5 i  - SET GSN FLAGS cf. 4.┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00159841 ┆;     A2.3.4.1.5 j  - SET SYSTEM PARAMETER cf. 4.2.3.4.1.5 k   are SCM procedures   - SEND TO TMP cf. 4.2.3.4.1.5 l   is an internal procedure.   Functional Specification   An info block is sent to specified SYNCEL.   The procedure contains a waiting point┆
0x3bf00…3c000 (59, 0, 15) Sector 3b000900159841 ┆;     A.                                                                   4.2.3.2 Software Structure    4.2.3.2.1 SCM Procedures   - REQUEST  cf. 4.2.3.4.1.5 a  - GET TMP STATISTICS cf. 4.2.3.4.1.5 b  - GET TABLE ATTRIBUTES cf. 4.2.3.4.1.5 c  - LOCK TABLE┆
0x3c000…3c100 (60, 0, 0)  Sector 3c01ff00159841 ┆<     A cf. 4.2.3.4.1.5 d  - UNLOCK TABLE cf. 4.2.3.4.1.5 e  - REORGANIZE cf. 4.2.3.4.1.5 f  - ABANDON REORGANIZE cf. 4.2.3.4.1.5 g  - BACKUP  cf. 4.2.3.4.1.5 h  - SYSTEM START UP cf. 4.2.3.4.1.5 i  - SET GSN FLAGS cf. 4.2.3.4.1.5 j  - SET SYSTEM PARAMETER┆
0x3c100…3c200 (60, 0, 1)  Sector 3c02ff00159841 ┆<     A cf. 4.2.3.4.1.5 k  - SET GSN  cf. 4.2.3.4.2.5 a  - GET GSN  cf. 4.2.3.4.2.5 b  - DAILY GSN RESET cf. 4.2.3.4.2.5 c  - GET SYSTEM PARAMETER cf. 4.2.3.4.2.5 d   4.2.3.2.2 Internal Procedures   - TMP INIT cf. 4.2.3.4.3.5 a  - TMP ANSWER RECEIVED cf. 4┆
0x3c200…3c300 (60, 0, 2)  Sector 3c03ff00159841 ┆<     A.2.3.4.3.5 a  - TMP CANCEL cf. 4.2.3.4.3.5 a  - TMP COMPLETE cf. 4.2.3.4.3.5 a  - WAIT  cf. 4.2.3.4.3.5 a   4.2.3.3 Data Flow, Control Logic, and Waiting Points   The Control Logic is shown in figure 4.2.3.3-1.   The two waiting points for "answer r┆
0x3c300…3c400 (60, 0, 3)  Sector 3c04ff00159841 ┆<     Aeceived" and "function completion" are placed as follows:   - The procedure SEND TO TMP contains the waiting point "answer received". It shall save its return address and possible other variables in the SOCB. The procedure is called in all the SCM p┆
0x3c400…3c500 (60, 0, 4)  Sector 3c05ff00159841 ┆<     Arocedures contained in the TMP process functions module and no other procedure contains an "answer received" waiting point.   - Each of the SCM procedures contains a "function completion" waiting point. This waiting point is contained in the procedu┆
0x3c500…3c600 (60, 0, 5)  Sector 3c060f00159841 ┆<     Are WAIT. 3       4.2.3.4.2.4 Data Description ............... 4 186       4.2.3.4.2.5 Module Design .................. 4 186       4.2.3.4.3 Main Module ........................ 4 194       4.2.3.4.3.1 Functional Specification ....... 4 194       4.┆
0x3c600…3c700 (60, 0, 6)  Sector 3c076000159841 ┆< `   A 1                                                                       Figure 4.2.3.3-1      19 01 82 14 57    7 25  21673 05 05 82 15 04      00      2 04 05 82 16 45 10 05 82 10 53 0117A  58    9 35   548  23221    @ t           *J         7 E _┆
0x3c700…3c800 (60, 0, 7)  Sector 3b08ff00159841 ┆;     A 1                                                                  4.2.3.4 Module Specification    4.2.3.4.1 TMP Process Functions Module    4.2.3.4.1.1 Functional Description   The TMP process functions module contains the following functions, the┆
0x3c800…3c900 (60, 0, 8)  WangDocumentHead {hdr=WangSectHead {next=(60,0, 9), len=0xff, h3=41159841}, f00=»1598A «, f01=»CPS/SDS/026               «, f02=»vhn                  «, f03=»BMN                  «, f04=»4.2.3                «, f05=19-01-82 14:57, f06=»   7 «, f07=»25 «, f08=» 21673 «, f09=05-05-82 15:04, f10=»     «, f11=»00 «, f12=»     2 «, f13=04-05-82 16:45, f14=10-05-82 10:53, f15=»0117A «, f16=» 58 «, f17=»   9 «, f18=»35 «, f19=»  548 «, f20=» 23221 «, f21=»  «, f22=» @ «, f99=740000000110068610110280aaca1505000000000000003703bf00df}
0x3c900…3ca00 (60, 0, 9)  Sector 3c0a3a00159841 ┆< :   A     <   < < < < < ; ; ; ; ; : : : : 9 9 9 9 9 8 8 8 8 8 7 7 7 7 6 6 6 6 6 5 5 5 5 # # # # " " "                                                        DOKUMENTOVERSIGT  Dokument nr:   Dokumentnavn:   Operat]r:   Forfatter:    Kommentarer:       STA┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0ba800159841 ┆< (   A 1                                                                         CPS/SDS/026   BMN/820506   TABLE MANAGEMENT DETAILED DESIGN SPECIFICATION  CAMPS       )M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r  9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00159841 ┆<     A 1                                                                  4.2.3 TMP Monitor   TMP Monitor is a subpackage maintaining all TMP interfaces.    4.2.3.1 Functional Specification   The TMP MON functions are grouped as shown on fig. 4.2.4.1-1.  ┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00159841 ┆<     A Most functions are passed on to the TMP process except from those contained in the TMP MON function Module which requires fast access and are therefore performed by TMP MON itself and those contained in the Main Module which is the central init, an┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0ef000159841 ┆< p   Aswer received, complete and cancel points in TMP MON .   All access to TMP MON are passed through System Call Monitor and must thus follow the general System Call Monitor interface.   Refer to Module Specification 4.2.3.1 - 4.2.3.3.      '<M% !  "2<┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0f6100159841 ┆< a   A 1                                                                        Figure 4.2.3.1-1  Bl1{M40sI:^=~ J 1!"<6;!#<6 !&<6 !  "$<! <6 {M;(s!  9"c=!  "(= Z=q#p!"<6 !&<6 !  "$<!#<6 ! <6 {M)(sC  I! <6 !  "(=  <q#p!"<6 !#<6 !  "$<!&<6$`i6 {M)(sM &M7   ┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00ff00159841 ┆<     A 1                                                                  4.2.3.2 Software Structure    4.2.3.2.1 SCM Procedures   - REQUEST  cf. 4.2.3.4.1.5 a  - GET TMP STATISTICS cf. 4.2.3.4.1.5 b  - GET TABLE ATTRIBUTES cf. 4.2.3.4.1.5 c  - LOCK TABLE┆
0x3d000…3d100 (61, 0, 0)  WangDocumentBody
         […0x1f…]
0x3f000…3f100 (63, 0, 0)  WangDocumentHead {hdr=WangSectHead {next=(63,0, 1), len=0xff, h3=41159241}, f00=»1592A «, f01=»CPS/SDS/026               «, f02=»pan                  «, f03=»BMN                  «, f04=»4.2.1.4              «, f05=18-01-82 10:53, f06=»  14 «, f07=»26 «, f08=» 36746 «, f09=12-01-84 08:06, f10=»     «, f11=»05 «, f12=»    72 «, f13=12-01-84 08:35, f14=12-01-84 15:07, f15=»0117A «, f16=» 68 «, f17=»  30 «, f18=»25 «, f19=» 1120 «, f20=» 60123 «, f21=»  «, f22=» @ «, f99=640000000110062710110280aaca15050000000000000037032501df}
0x3f100…3f200 (63, 0, 1)  WangDocumentBody
         […0x6…]
0x3f800…3f900 (63, 0, 8)  Sector 00000000000000 ┆                                                                                                                                                                                                                                                                ┆
         […0xd7…]

Less…

Reduced view