DataMuseum.dk

Presents historical artifacts from the history of:

CP/M

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

See our Wiki for more about CP/M

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download

⟦c683e9400⟧ TextFile

    Length: 149376 (0x24780)
    Types: TextFile
    Names: »D89«

Derivation

└─⟦5dbd6b396⟧ Bits:30005867/disk12.imd Dokumenter (RCSL m.m.)
    └─⟦this⟧ »D89« 

TextFile

p_                                                               HECZ 810324              /6
m_ 
p_    RC8000                                                                 INT
m_ 
               Utility Program INSAVE 
 
 \f

                  1_._ _ _G_E_N_E_R_A_L_ _D_E_S_C_R_I_P_T_I_O_N_ 
     
    The INSAVE program is a utility tool used for maintaining a
    safety copy of backing storage areas and entries. The safety
    copy is dumped on a number of magnetic tapes using the standard
    SAVE/LOAD format. 
     
    The program is normally used in this way. When the program is
    called first time all permanent areas and entries that fulfil
    some conditions are dumped on the magnetic tapes. Subsequent
    calls of the program will now save those areas and entries
    which have been changed since last call. The saved information
    is stored in succeeding files on the magnetic tapes. 
     
    The program uses a file descriptor to hold information about
    last successful dump. This information is: date and time, name
    of the magnetic tape, file number and mode of operation. A
    file may be continued on a number of tapes. 
     
     
2_._ _ _S_Y_N_T_A_X_ 
     
    <call> ::= INSAVE <function descriptor>.<mt-list> <parameters> 
    <function descriptor> ::= <file name> 
    <mt-list> ::= <magtape name> ! <magtape name>.<mt-list> 
    <parameters> ::= empty ! <base statement> <parameters> ! 
                     <document statement> <parameters> 
    <base statement> ::= BASE.<lower limit>.<upper limit> 
    <document statement> ::= DOCUMENT.<document-list> 
    <document-list> ::= <document name> !  
                        <document name>.<document-list> 
                
     
2_._1_ _A_n_ _E_x_a_m_p_l_e_ 
     
    A project group wants copies of their backing storage files\f

                      that are never more than one day old, and a weekly total dump
    of all their files. 
     
    Once a week they execute a job including the commands: 
      ........ 
      lastdump=set mto mt0000 0 1 
      scope project lastdump 
      insave lastdump.mt0000.mt0001.mt0002.mt0003 
      ........ 
    and once every day a job including the command: 
      ........ 
      insave lastdump.mt0000.mt0001.mt0002.mt0003 
      ........ 
     
     
3_._ _ _F_U_N_C_T_I_O_N_ 
     
    The INSAVE program is called with parameters specifying at
    least a function descriptor and a number of magnetic tapes. The
    function descriptor should point out a visible entry inside the
    project base (the max interval) of the process in which the
    program is executed. The base of the function descriptor is
    used to specify a minimal lower limit and a maximal upper limit
    of all the files that shall be saved. These limits may be
    changed with a base statement, but they can never be set to
    values outside the project base. The mode of the function
    descriptor defines the mode that is used when writing at the
    magnetic tape, the document name and file number is used to
    specify relatively the magnetic tape name and the file number
    of last successful dump. Furthermore does the time of the
    function descriptor (a shortclock) hold the time of the begin-
    ning of the last dump operation, files that have not been
    changed after this time are of course not saved. 
     
    If only files on some selected backing storage documents shall
    be dumped, the names of these documents can be defined in a
                document statement. 
     \f

    After program initiation the main catalog is scanned, and all
    entries that fulfil the demands below are dumped on the
    magnetic tape. The demands are: 
     
      a) The entry must be visible and permanent (permkey >= 2). 
          
      b) The base of the entry must be included in the interval of
         the file descriptor or in the interval specified in a
         base statement. 
          
      c) In case a document statement has defined a selection of
         backing storage documents it is checked whether the entry
         is permanented at one of these documents. 
          
      d) If the entry is an area entry the <last changed> par-
         ameter from the auxiliary catalog is looked up. If this
         value is higher than the time of the function descriptor
         the entry is dumped. If the entry describes a non-area
         file it is always dumped. 
     
    Before a file or entry is saved on the magnetic tape a message
    is printed at current output describing the record. The format
    of this message is: 
     
    <entry name> <size> <permkey>.<document name> 
          <lower limit> <upper limit> (<date> or <integer>)  
          <last changed> 
     
    The format of the different records on the magnetic tape is
    the same as used of the SAVE program when executing system
    dumps. 
     
    Dates are stored 4 segments a block (a changeable program
    option). 
     \f

                      If an entry cannot be dumped because it is reserved by another
    process, the following message is output: 
      file in use <file-name> 
    and the scan of the catalog is continued. 
     
     
                  4_._ _ _E_R_R_O_R_ _M_E_S_S_A_G_E_S_ 
     
    In case of hard errors on the magnetic tape or the backing
    storage documents, an error message will be printed on current
    output and the program will terminate with ok.no and
    warning.yes, without any updating of the function descrip-
    tor. 
     
    The following error messages exist: 
     
    ***insave call 
       The syntax of the call is erroneous. 
        
    ***insave lookup function descriptor, result <result> 
       The function descriptor cannot be found (ref. 1, p. 2.76). 
        
    ***insave invalid function descriptor 
       The function descriptor has a wrong <mode> or <contents>. 
        
    ***insave illegal bases 
       Illegal parameters values in a base-statement. 
        
    ***insave catalog error, result <result> 
       The main catalog cannot be connected, because of <result>
       (ref. 1, p. 2.52). 
        
    ***insave catalog io error, result <result> 
       An io error has occurred when scanning the main catalog.
       The error is specified in <result> (ref. 1, p. 2.18) or
       <status> (ref. 3). 
        \f

                      ***insave magtape error, result <result> 
    ***insave magtape error, status <status> 
       An error has occurred when writing at the magnetic tape.
       The cause is specified in <result> (ref. 1, p. 2.18) or
       <status> (ref. 4). 
        
    ***insave backing storage error, result <result> 
    ***insave backing storage error, status <status> 
       An error has occurred when trying to read the last listed
       file from the backing storage. The cause of the error is
       specified in <result> (ref. 1, p. 2.18) or <status> (ref.
       3). 
        
    ***insave release file, result <result> 
       The last saved file cannot be released, because of <result>
       (ref. 1, p. 2.64). 
        
    ***insave magtapes exceeded 
       The magnetic tape list is violated. 
        
    ***insave change function descriptor, result <result> 
       The function descriptor cannot be updated, because of
       <result> (ref. 1, p. 2.44). 
     
     
5_._ _ _R_E_F_E_R_E_N_C_E_S_ 
     
    1  RCSL No 31-D477: 
         RC8000 Monitor, Part 2 
     
    2  RCSL No 31-D607: 
         System 3 Utility Programs, Part 2 
     
    3  RCSL No 31-D539: 
         RC8000 Backing Store Area Process 
     
    4  RCSL No 31-D533: 
         RC8000 Magnetic Tape Process (9 track) \f

                           RCSL No 31-D540: 
         RC8000 Magnetic Tape Process (7 track) 
          
         RCSL No 31-D542: 
         RC8000 Cassette Tape Process 
          
          \f

p_                                       EL 810928               EL 811013                /3
m_ 
p_                                                RC855 
m_ 
               RC855 Bootdisk Manager 
 
 \f

                  1_._ _I_n_d_l_e_d_n_i_n_g_ 
     
"RC855 Bootdisk Manager" er et utility program som anvendes ved
håndtering af RC855 bootstrap floppy disks. En bootstrap floppy
disk indeholder 
- et "spor 0" program som loades af PROM-bootstraploaderen
  (BOOT55) ved power-up eller reset, 
- et katalog med beskrivelse af en program-menu, 
- programmerne i menuen i form af binære images. 
 
Der kan maximalt være 16 images på n bootdisk, som skal være dual
sided, double density. 
 
I katalogbeskrivelsen af hvert program-image indgår 
- programmets navn i menuen (max. 28 tegn), 
- et valgtegn, som anvendes til at vælge programmet fra menuen, 
- eventuelt autoload-attribut som indikerer at pågældende image
  skal loades automatisk uden udskrivning af menu. 
 
 
2_._ _"_S_p_o_r_ _0_"_ _p_r_o_g_r_a_m_m_e_t_s_ _f_u_n_k_t_i_o_n_ 
 
Først undersøges om der findes et image med autoload-attribut. I
så fald loades dette (hvis der er flere, loades det første).
Ellers udskrives menuen, dvs. valgtegn og navn for hvert image, og
der loades et image efter indtastning af valgtegn. 
 
 
3_._ _F_u_n_k_t_i_o_n_e_r_ _i_ _R_C_8_5_5_ _B_o_o_t_d_i_s_k_ _M_a_n_a_g_e_r_ 
 
Programmet kører på RC850 og fungerer interaktivt. Indtastede
kommandoer kan forkortes vilkårligt, kun t bogstav af kommando-
navnet er nødvendigt. 
 
Program images som skal skrives på bootdisken forudsættes overført
i tekhex format via RC850 terminalens V.24 linie, normalt ved an-
vendelse af "tekmove" utility programmet på RC8000. 
 \f

                  I det følgende beskrives de enkelte kommandoer: 
     
 
3_._1_ _I_(_n_i_t_i_a_l_i_s_e_)_ 
 
Kataloget initialiseres som værende tomt. 
 
 
3_._2_ _Z_(_e_r_o_)_ 
 
"Spor 0" programmet indlæses. 
 
 
3_._3_ _T_(_e_k_m_o_v_e_)_ _<_v_a_l_g_t_e_g_n_>_ _<_p_r_o_g_r_a_m_ _n_a_v_n_>_ 
 
Et program image indlæses og beskrives i kataloget med <valgtegn>
og <program navn>. 
 
 
3_._4_ _R_(_e_n_a_m_e_)_ _<_v_a_l_g_t_e_g_n_1_>_ _<_v_a_l_g_t_e_g_n_2_>_ _<_p_r_o_g_r_a_m_ _n_a_v_n_>_ 
 
Hvis der findes en katalogindgang identificeret med <valgtegn1>
ændres beskrivelsen til <valgtegn2> og <program navn>. 
 
 
3_._5_ _M_(_e_n_u_)_ 
 
Katalogets indhold udskrives på menu-form. 
 
 
3_._6_ _D_(_e_l_e_t_e_)_ _<_v_a_l_g_t_e_g_n_>_ 
 
Hvis der findes en katalogindgang med <valgtegn> markeres den som
slettet og kan derefter genbruges. 
 
 \f

3_._7_ _A_(_u_t_o_l_o_a_d_)_ _<_v_a_l_g_t_e_g_n_>_ 
 
Hvis der findes en katalogindgang med <valgtegn> sættes dens auto-
load-attribut. 
 
 
3_._8_ _N_(_o_r_m_a_l_)_ _<_v_a_l_g_t_e_g_n_>_ 
 
Hvis der findes en katalogindgang med <valgtegn> slettes dens
autoload-attribut. 
 
 
                  3_._9_ _S_(_i_z_e_)_ _<_v_a_l_g_t_e_g_n_>_ 
     
Størrelsen af det indikerede program image udskrives. 
 
 
3_._1_0_ _E_(_x_a_m_i_n_e_)_ _<_v_a_l_g_t_e_g_n_>_ _<_h_e_x_v_a_l_>_ 
 
Byte nummer <hexval> i det indikerede program image udskrives
hexadecimalt. 
 
 
3_._1_1_ _C_(_h_a_n_g_e_)_ _<_v_a_l_g_t_e_g_n_>_ _<_h_e_x_v_a_l_1_>_ _<_h_e_x_v_a_l_2_>_ 
 
Værdien af byte nummer <hexval1> i det indikerede program image
ændres til <hexval2>. 
 
 
3_._1_2_ _H_(_e_l_p_)_ 
 
Liste over gyldige kommandoer udskrives. 
 
 \f

p_                                       BA 800312               BA 801212                /6
m_ 
p_    RC8000                                                                 EXT
m_ 
               RC8000 BASIC SOFTWARE DOCUMENTATION LIST 
 
 \f

                  * An asterisk indicates new or changed items. 
   
  RCSL No/RC Inf. Note 
   
  S_W_8_0_0_1_ _B_A_S_I_S_ _S_Y_S_T_E_M_ _P_A_C_K_A_G_E_                     DOC. ORDER NO: SDO 002 
   
  31-D   476 Monitor Part 1 System Design 
* 31-D   606 Corrections to RCSL No 31-D476 
  31-D   477 RC8000 Monitor, Part 2 
  31-D   584 Corrections to RCSL No 31-D477 
  31-D   478 RC8000 Monitor, Part 3, Def. of External Processes 
  31-D   539 Backing Storage Area Process 
  31-D   542 Cassette Tape Process 
  31-D   528 Disc Process 
  31-D   546 Disc Process (RC36xx) 
  31-D   543 Flexible Disc Process 
  31-D   523 FPA Main Process 
  31-D   530 Interval Clock Process 
  31-D   536 Line Printer Process 
  31-D   540 Magnetic Tape Process (7 track) 
  31-D   533 Magnetic Tape Process (9 track) 
  31-D   534 Paper Tape Punch Process 
  31-D   535 Paper Tape Reader Process 
  31-D   537 Punched Card Reader Process 
  31-D   580 Terminal Process 
  31-D   544 Conversion Tables 
* 31-D   595 Operating System s, Ref. Man. 
  43-RI 1059 Terminal User>s Guide 
   
  S_W_8_0_1_0_ _S_Y_S_T_E_M_ _U_T_I_L_I_T_Y_ _P_A_C_K_A_G_E_                   DOC. ORDER NO: SDO 005
   
             Utility Package: 
   
  31-D   364 System 3 Utility Programs Part one 
  31-D   590 System 3 Utility Programs Part two 
 \f

                  RCSL No/RC Inf. Note 
   
            Maintenance Package: 
   
  31-D   471 AUTOLOAD 
  31-D   311 Base 
  31-D   376 Changekit 
  55-D    70 Checkio 
  31-D   295 Clean 
  31-D   557 Createlink, lookuplink, lookupdev 
  31-D   549 Disccopy, kiton, kitoff, kitlabel, kitname 
  31-D   280 Do 
  31-D   522 FPASTAT, DISCSTAT Utility Programs 
  31-D   382 Global 
  31-D   465 Linkcentral 
  31-D   578 Montest 
  31-D   569 Movedump 
  31-D   570 Slicelist 
   
             Backing Storage Package: 
   
                  * 31-D   602 RC8000 SQ-system 
  31-D   562 RC8000 Backing Storage Area Sorting 
* 31-D   600 RC8000 Indexed Sequential Files (ISQ) 
* 31-D   601 Extensions to the RC8000 ISQ System 
  CAP 790802 Transformation of ISQ and CF Master Files 
   
             Flexible Disc Package: 
   
  31-D   459 Flexible Disc Handling within the Algol System 
  31-D   531 Corrections/Comments to RCSL 31-D 459 
  31-D   515 Utilityprograms for Flexible Disc Handling 
  31-D   545 Corrections to RCSL 31-D 515. 
   \f

                    RCSL No/RC Inf. Note 
   
                    S_W_8_1_0_0_ _M_I_P_S_/_T_S_ _P_A_C_K_A_G_E_                             DOC. ORDER NO: SDO 031
   
  31-D   510 Modular On-line System 
  31-D   512 Swopping Online System (SOS) 
  31-D   513 Terminal Access Module (TEM) 
  31-D   571 PRIMO (2. Edition) 
  31-D   585 MIPS/TS OPERATING GUIDE 
  LKN 790410 Binding of Terminals when Running MIPS/TS 
   
  S_W_8_1_0_1_ _B_O_S_S_ _P_A_C_K_A_G_E_                                DOC. ORDER NO: SDO 017
   
  42-i  1265 BOSS 2, User>s Manual 
* JMA 800820 Corrections to BOSS 2 User>s Manual 
  31-D   498 BOSS 2, Operator>s Manual 
  SM  790328 Corrections to BOSS 2 Operator>s Manual 
  31-D   421 BOSS 2, Installation and Maintenance 
* JMA 800819 Corrections to BOSS 2 Install. and Maint. Man.  
   
  S_W_8_2_0_0_ _D_A_T_A_ _B_A_S_E_ _P_A_C_K_A_G_E_                           DOC. ORDER NO: SDO 016
   
  42-i   766 Introduction to CF-system 
  28-D     5 Connected Files System 
  31-D   583 Corrections to RCSL No 28-D 5 CF-System 
* EAH 800314 Interpretation of the Alarm Printing from cf-system 
   
  S_W_8_2_1_0_ _M_A_G_-_T_A_P_E_ _F_I_L_E_ _M_A_N_A_G_E_M_E_N_T_ _P_A_C_K_A_G_E_            DOC. ORDER NO: SDO 012
 
     31-D   198 Magnetic Tape System MTS 2 
  31-D   228 Heapsort 
 
  S_W_8_2_1_1_ _M_U_L_T_I_ _T_E_R_M_I_N_A_L_ _H_A_N_D_L_E_R_ _P_A_C_K_A_G_E_              DOC. ORDER NO: SDO 014 
 
  31-D   470 Waitnext, User>s Reference 
 \f

                    RCSL No/RC Inf. Note 
   
  S_W_8_2_1_2_ _P_L_O_T_T_E_R_ _R_O_U_T_I_N_E_S_ _P_A_C_K_A_G_E_                    DOC. ORDER NO: SDO 030
   
  31-D   503 RC8000 Plotting System 
   
  S_W_8_2_2_0_ _M_A_T_H_E_M_A_T_I_C_A_L_-_S_T_A_T_I_S_T_I_C_A_L_ _R_O_U_T_I_N_E_S_ _P_A_C_K_A_G_E_  DOC. ORDER NO: SDO 018
 
  55-D    63 Introduction to Math.-Stat. 
  55-D    48 Adapint 
  53-M     3 Besselik 
  53-M     2 Besseljy 
  53-M     8 Beta 
  55-D    60 Decompose, Solve 
  55-D    57 Eberlein 
  31-D     3 FFT 
  31-D   129 FIT 
  55-D    58 Gamma 
  53-M     7 Householder 
  53-M     5 Invertsym 
  55-D    61 Jacobi 
  53-M    18 Minimum 
  53-M     4 Pzero 
  31-D   224 Runge Kutta 
  53-M    17 Solineq 
  53-M     6 Solvesym 
  53-M     1 Zero1 
  53-S     1 Data survey and Appendix 
  53-S     7 Recordinput and Appendix 
   
                    S_W_8_5_0_0_ _A_L_G_O_L_ _P_A_C_K_A_G_E_                               DOC. ORDER NO: SDO 003
   
* 42-i  1278 ALGOL8 User>s Guide Part 2 
  42-i  1279 ALGOL7 Reference Manual 
  42-i   781 ALGOL7 User>s Manual Part 1 
  31-D   581 ALGOL8 \f

                    RCSL No/RC Inf. Note 
   
  S_W_8_5_0_1_ _F_O_R_T_R_A_N_ _P_A_C_K_A_G_E_ _                            DOC. ORDER NO: SDO 008
   
* 42-i  1205 RC FORTRAN, User>s Manual 
   
  S_W_8_5_0_3_ _C_O_B_O_L_ _P_A_C_K_A_G_E_                               DOC. ORDER NO: SDO 039
   
  42-i  1002 COBOL Ref. Man. for RC8000 
   
  S_W_8_5_0_4_ _X_F_O_R_T_R_A_N_ _P_A_C_K_A_G_E_                            DOC. ORDER NO: SDO 043 
   
  31-D   457 XFORTRAN - A Preprocessor to RC FORTRAN 
   
  S_W_8_6_0_0_ _A_S_S_E_M_B_L_E_R_ _P_A_C_K_A_G_E_                           DOC. ORDER NO: SDO 009 
   
  42-i   785 RC Slang Assembler, Programming Guide 
  31-D   199 Run Time Organization of Algol Programs 
  31-D   210 Examples of Code Procedures 
  31-D   379 System 3 Utility Programs Part Three  
   
  S_W_8_7_0_1_ _D_I_S_C_-_D_I_S_C_ _F_i_l_e_ _R_o_u_t_e_r_ _P_a_c_k_a_g_e_               DOC. ORDER NO: SDO 046 
   
             FDLC Subpackage: 
 
* 31-D   592 FDLC-FPA Data Link Control, User>s Manual 
* 31-D   605 Corrections to RCSL No 31-D592 
* 43-GL 7810 FDLC-FPA Data Link Control, Reference Manual 
 
             DDFR Subpackage: 
 
* 31-D   579 Transfer Discfile (xdif) Utility Program and Disc to Disc 
             File Router, Reference Manual 
* 31-D   625 Remotejob Utility Program 
   \f

  S_W_8_7_0_2_ _I_B_M_ _3_2_7_0_ _T_E_R_M_I_N_A_L_ _H_A_N_D_L_E_R_                   DOC. ORDER NO: SDO 040  
  52-AA  933 Format 8000 on the Stansaab Alfaskob 3500 Data Terminal System
  52-AA  935 IBM 3270 Terminal Handler, System Messages 
  52-AA  936 IBM 3270 Terminal Handler, The Select Mechanism 
  52-AA  491 Format 8000 Algol Procedures 
* 52-AA  636 ALGOL6 CONTEXT BLOCKS \f




















         PROM Generating Program 
                                       User>s Guide
          




















                                First Edition
A/S REGNECENTRALEN of 1979, 1979                                May 1979
     Information Department RCSL 43-GL  9071\f

         Author:             H.O. Hansen 


 
 
 
 
 
 
Keywords:           DOMUS, Microprogram, PROM-burning, Guide 
                     

 
 
 
Abstract:           Thies manual describes how to use the general
                    PROM-generating program PROM (RC36-01149.01). The
                    program is used to generate PROM>s containing
                    microprograms.

 
 
          

          

 
 
 
 
 
 
 
 
 
 
 
Reservation 
 
 
 
 
 
 
Copyright   A/S Regnecentralen, 1979 
Printed by A/S Regnecentralen, Copenhagen\f

                   T_A_B_L_E_ _O_F_ _C_O_N_T_E_N_T_S_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _P_A_G_E_ 
                
               1.   INTRODUCTION ......................................... 
                
               2.   REQUIREMENTS ......................................... 
                    2.1   Core ........................................... 
                    2.2   Drivers ........................................ 
                
               3.   CALL ................................................. 
                
               4.   FUNCTIONS ............................................ 
                    4.1   BURN ........................................... 
                    4.2   BURNC .......................................... 
                    4.3   PUNCH .......................................... 
                    4.4   CHECK .......................................... 
                    4.5   LOAD ........................................... 
                    4.6   COMPA .......................................... 
                    4.7   DELET .......................................... 
                    4.8   CATLI .......................................... 
                    4.9   DUMP ........................................... 
                    4.10  RESTO .......................................... 
                    4.11  PROTE .......................................... 
                
               5.   OPERATOR MESSAGES .................................... 
                    5.1   Program Messages ............................... 
                    5.2   Errormessages .................................. 
                
               A.   EXAMPLES ............................................. 
                
               B.   REFERENCES ........................................... \f

    1_._ _ _ _ _ _ _ _ _ _ _ _ _ _I_N_T_R_O_D_U_C_T_I_O_N_. 
                
               This program "PROM" is the link between the PROM-files generated 
                   by the MIMAC-macroassembler and the burned PROM. 
 
               The program handles the PROM burner PRG701, and by selecting
               different functions in the call it>s possible to perform a lot of
               operations on the PROM-files.\f

2_._ _ _ _ _ _ _ _ _ _ _ _ _ _R_E_Q_U_I_R_E_M_E_N_T_S_. 
                
                
2_._1_ _ _ _ _ _ _ _ _ _ _ _ _C_o_r_e_. 
                
               The program PROM requires app. 15000 Bytes of core. 
                
                
2_._2_ _ _ _ _ _ _ _ _ _ _ _ _D_r_i_v_e_r_s_. 
                
               Depending on the function selected in the call, different drivers
               have to be loaded to core. 
                
               The control of an datatransfer to the PRG701 is performed via 
               second papertape punch (burning) and second papertape reader 
               (checking) drivers. 
                
                     Function              Demanded drivers 
                
                     BURN                  PTP, PTR, PTP1, PTR1 
                     PUNCH                 PTP 
                     CHECK (PROM)          PTP, PTR, PTP1, PTR1 
                     CHECK (PAPERTAPE)     PTR 
                     LOAD                  PTR 
                     COMPA                 (LOG driver) 
                     DELET                 None 
                     CATLI                 (LOG driver) 
                     DUMP                  (LOG driver) 
                     RESTO                 (LOG driver) 
                     PROTE                 None 
                
               If the operator-messages from the program with function COMPA,
               CATLI, DUMP, RESTO is wanted on an outdevice different from TTY
               the corresponding MUS-driver has to be loaded.\f

3_._ _ _ _ _ _ _ _ _ _ _ _ _ _C_A_L_L_. 
                
               The PROM Generating program is called in the following way: 
                
               PROM  PROM.>ident'U+1D FUNC.function' IN.indevice' 
                     LOG.logdevice' 
                
               where 
                
               ident'      is the PROM-file identification used when the 
                            file was created either by the MIMAC assembler 
                            or by PROM itself (function LOAD). 
                
                            It is possible to burn, punch, check, load, delete 
                            Protect up to 17 PROMs by writing more idents
                            seperated by a space in the call. 
                
                            If the selected function is either catlist, dump or
                            restore only a single ident is allowed. In this case
                            a special character, <, is legal in the ident-name.
                            This character is used to substitute any other
                            character. That means for example, catlist>ing
                            >ROM<<<> will list all PROM-files starting with the
                            letters ROM. 
                             
                            (No default - must be specified). 
                             
               function'   is the parameter to select between the different
                            functions of the program. It is allowed to write
                            one of the following eleven: 
                             
                                           BURN 
                                           BURNC 
                                           PUNCH 
                                           CHECK 
                                           LOAD 
                                           COMPA
                                           DELET 
                                           CATLI 
                                           DUMP 
                                           RESTO 
                                           PROTE \f

The functions are described in chapter 4. 
 
(Default = Burn). 
 
               indevice'   is only actual, when the function selected is CHECK
                            or LOAD. In this case the parameter indicates, if
                            the input has to be taken from either <PR1 (the
                            PRG701) or from <PTR. 
                             
                            (Default = <PR1). 
                             
               logdevice'  When the function selected is either CATLI, COMPA,
                            DUMP or RESTO this parameter defines the outputdevi-
                            ce (or file) to which the log-information  is deli-
                            vered. 
                             
                            (Default = <TTY).\f

 4_._ _ _ _ _ _ _ _ _ _ _ _ _ _F_U_N_C_T_I_O_N_S_. 
                             
4_._1_ _ _ _ _ _ _ _ _ _ _ _ _B_U_R_N_. 
                
               The function BURN is used when the program has to burn a PROM in
               the PRG701 according to a PROM-file on the disc. The
               ident-parameter in the call indicates which one(s). 
                
               The program will announce the PROM-ident and order the
               PROM-burner to be loaded. After inputting an NL to this message,
               the burning will start and it is immediately followed by a
               checkread. 
                
               If checkerrors are detected during checkread, the program will
               try to return the PROM (max. 3 times at all) before giving up. If
               the PROM still isn>t OK one or more checkerror-messages (chapter
               5.1) will now appear. 
                
               When the ident-parameter of the call contains more than one
               PROM-ident, the expiration is repeated from the "load
               burner"-message. 
                
                
    4_._2_ _ _ _ _ _ _ _ _ _ _ _ _B_U_R_N_C_. 
                
               This function (BURN Complement) is working in exactly the same
               way as function BURN with the exception that the PROM is burned
               in the opposite way described in the PROM-file. 
                
               That means that by use of BURNC it is possible to burn a PROM
               where the zeroes are burned, by use of a PROM-file, which assumes
               that the one>s are burned. 
                
                
    4_._3_ _ _ _ _ _ _ _ _ _ _ _ _P_U_N_C_H_. 
                
               The PUNCH function is used to produce PROM-papertapes from a
PROM-file. The papertapes generated will start with a "all
               holes"-byte and may e.g. be used for the RC3500 PROM-burner.\f

    4_._4_ _ _ _ _ _ _ _ _ _ _ _ _C_H_E_C_K_. 
                
               After burning a PROM, it is automatically checked, but by
               function check, it is possible to check a PROM without burning
               it, and to check a PROM-papertape, too. The check is done by
               comparison with the PROM-file pointed out by the ident-field of
               the call. 
                
               In the case that any differences between the PROM-file and the
               input (<PR1 or <PTR) should appear, a checkerrormessage is
               outputted as shown in chapter 5.1. 
                
                
    4_._5_ _ _ _ _ _ _ _ _ _ _ _ _L_O_A_D_. 
                
               The function LOAD is useful to generate PROM-files from existing
               PROM-papertapes or master-PROMs. To create the PROM-file it is
               necessary to inform the program about some of the PROM
               parameters. That is done by answering the following questions: 
                
                     ADDR. BITS: 
               Give a number between 8 and 15. 
                
                     DATA BITS: 
               Give a number equal to 1, 2, 4 or 8. 
                
                     ZERO BURN: 
               Answer NO, when the one>s have to be burned and YES, when the
               zeroes have been burned. 
                
                     PROM TYPE: 
               Answer a textstring indicating which PROM is in question, e.g.
               MMI6353. 
                    
                     TEXT: 
               Answer a textstring used as additionally information to the
               operator when burning the PROM. 
                
               After answering the last question, the PROM-data is read from
               either PTR or PRG701 (depending on the selected indevice), and a
               PROM-file is build up on the disc. \f

               Creating a number of PROM-files with identical PROM-parameters
               may be done by collecting the PROM-names in the ident-parameter.
               In this case the mentioned questions are only asked once. If the
               data is read from PTR, the different PROM-dataset have to reside
               on a single papertape. 

               "Headpunched" information on a papertape is automatically
               by-passed. 
                
                
4_._6_ _ _ _ _ _ _ _ _ _ _ _ _C_O_M_P_A_. 
                
               In situations where a PROM has to be replaced by a new modified
               one, it>s possible to examine if this new one may be produced by
               reburning of the old one. 
                
               This examination is made by the program by comparing the
               PROM-files describing the two PROMs, and that fact demands some
               conditions fulfilled: 
                     Both PROM-files has to be on the disc. 
                     The two sets of PROM-parameters have to be equal. 
                     The ident-parameter of the call has to look like: 
                            >Existing1 New1 Existing2 New2 etc." 
                
               Called like above, the program will examine the possibility to
               reburn PROM "Existing1" to PROM "New1", PROM "Existing2" to
               "New2" and so on. The result of the examination is printed on the
               selected logdevice. 
                
                
4_._7_ _ _ _ _ _ _ _ _ _ _ _ _D_E_L_E_T_. 
                    
               Removing one or more PROM-files from the disc may be done by use
               of this function. The PROM-files is deleted by this function even
               if they are protected by the function PROTECT. \f

    4_._8_ _ _ _ _ _ _ _ _ _ _ _ _C_A_T_L_I_. 
                
               By use of this function it>s possible to get a printout of the
               PROM-library (or a part of it). The PROM-ident of the call has to
               be a single PROM-name, may be with characters substituted by <>s
               (see chapter 3). 
                
               The program will produce a catalog list giving the PROM-names,
               PROM-parameters and the PROM-types. Output is delivered to the
               log-device specified in the call. 
 
 
4_._9_ _ _ _ _ _ _ _ _ _ _ _ _D_U_M_P_. 
                
               PROM-files may be saved on a magnetic tape by use of this
               function. The files to be saved are pointed out by the single
               ident-word in the ident-parameter just as for the CATLI-function.
                
               The PROM-files are always saved on station MTO in file 1, and the
               MUS magnetic tape driver has to be loaded to core from the
               discfile (MTOX) before execution. 
                
               A log of the dump expiration is printed on the selscted
               log-device. 
                    
                
    4_._1_0_ _ _ _ _ _ _ _ _ _ _ _R_E_S_T_O_. 
                
               PROM-files already saved on magtape by function DUMP may be
               restored by use of this function. 
                
               The ident-parameter is treated as for function CATLI, and the
               log-information is printed on the selected device (file). 
               Restoring PROM-files which already are on the disc, will cause
               overwriting of the old ones by the new ones fetched from mag.
               tape.
                
                
4_._1_1_ _ _ _ _ _ _ _ _ _ _ _P_R_O_T_E_. 
                
               To protect PROM-files from inexpedient deleting by for example
               function LOAD, the function PROTECT  is useful. By execution of
               PROTECT-function the attributes of the ident-PROM files in the
               call are changed to "Permanent". 
               After protecting the only way to delete/change the PROM-file is
               using the functions DELET or RESTO.\f

5_._ _ _ _ _ _ _ _ _ _ _ _ _ _O_P_E_R_A_T_O_R_ _M_E_S_S_A_G_E_S_. 
                
5_._1_ _ _ _ _ _ _ _ _ _ _ _ _P_r_o_g_r_a_m_ _M_e_s_s_a_g_e_s_. 
                
               Beside the messages (questions) in the previous chapter (4.5),
               one or more of the following ones may appear during the
               programexecution. 
                
               PROM GENERATING PROGRAM   REV. XX 
                
                     This head will appear on the console just after loading 
                     the program. 
                
               "WRITE PROTECT" OFF, INSERT PROM - TYPE: XXXX    or 
               INSERT PROM - TYPE: XXXX 
                
                     That is instructions to the operator in case he is 
                     burning or checking a PROM Type NL to proceed. 
                
               ***COMPARE OK*** 
                
                     After execution of the check function, this message will
                     appear when no errors was found in the PROM. 
                
               ***PROM TAPE ERROR 
                
                     During read of a PROM-tape from PTR a format error was
                     detected, i.e. tape is not starting with an "all holes"
                     char. 
                
               CHECKERROR IN ADDRESS: XXXXX BYTE' 
               EXPECTED: YY, READ ZZ, CONTINUE? 
                
                     During checkread of a PROM an error was detected. After
                     answering the question, the comparison will go on. If the
                     answer was "NO", no further errors will be announced, but
                     they will still be counted. 
 
                     The string BYTE' may either be empty, LSB or MSB. The
                     messages MSB and LSB are used when the check is performed
                     on an 8 bit PROM in the PRG701. 
                
               ***ERRORS IN COMPARE: XXX 
                
                     If any errors was detected in a chechreadpass, the amount
                     will be announced in this way, when the comparison is
                     finished. \f

               REBURN CONDITION FOR XXXXXX TO YYYYYY: RESULT' 
                
                     After finishing the function COMPA this message will appear
                     with RESULT' equal either the text OK or NOT OK. If the
                     result is OK then PROM XXXXXX may be reburned to PROM
                     YYYYYY. 
                
                
    5_._2_ _ _ _ _ _ _ _ _ _ _ _ _E_r_r_o_r_m_e_s_s_a_g_e_s_. 
                
               A lot of the errormessages are systemmessages and may be found in
               the manual DOMUS User>s Guide. They are all of the form: 
                
               number'***text' 
                
               Beside this, the following errormessages may appear: 
                
               ***PROM UNKNOWN, PROM: XXXX 
                
                     The PROM-ident given as firstparameter in the call is not
                     known as a PROM-file. 
                
               ***PARAMETER ERROR 
                
                     Error is one or more of the parameters in the call. 
                    
***PROMPARAMETERS UNEQUAL 
                
                     To check the reburn condition of two PROM's the parameters
                     as PROM-size, datawidth, zeroburn have to be alike. If they
                     are not, this message appears before termination.\f

A_._ _ _ _ _ _ _ _ _ _ _ _ _ _C_A_L_L_ _E_X_A_M_P_L_E_S_. 
                      
               To burn the PROM: ROM436, created by the MIMAC-assembler, the
               program is called like this: 
                
               PROM >ROM436> 
                
               To check a PROM papertape (of ROM436) the program is called like
               this: 
                
               PROM >ROM436> CHECK <PTR 
                
               To create two PROM-files on the disc from the papertape
               containing data for ROA036 and ROA037 the program is called like
               this: 
                
               PROM >ROA036 ROA037> LOAD <PTR 
                
               To find out if the PROM described in PROM-file ROM100 may be
               reburned to a PROM described in ROX100 the program could be used
               in the following way: 
                
               PROM >ROM100 ROX100> COMPA LOG.<LPT\f

B_._ _ _ _ _ _ _ _ _ _ _ _ _ _R_E_F_E_R_E_N_C_E_S_. 
                
               MICROPROGRAM MACROASSEMBLER. 
               USER>S GUIDE                                       RCSL: 43-GL 8903\f

p_                                       FGS781109               FGS 800718               /4
m_ 
p_Package Description     RC8000      RC6000      RC4000                     EXT
m_ 
              Magtape File Management Package, SW8210/1/11.0 
 
 \f

     P_A_C_K_A_G_E_ _D_E_S_C_R_I_P_T_I_O_N_ 
      
     1.     Package Number : SW8210/1 
      
     2.     Package Name   : Magtape File Management Package 
      
     3.     Release        : 11.0, 1980.05.12 
      
      
     4_._ _ _ _ _ _A_b_s_t_r_a_c_t_ 
      
            The package holds mts2, a set of RC standard procedures for
            handling labelled files on magnetic tape, and heapsort, a
            program and a standard procedure, for sorting of records of
            magnetic tape files. 
            The procedures can be used in ALGOL and FORTRAN programs. 
      
      
     5_._ _ _ _ _ _P_r_e_r_e_q_u_i_s_i_t_e_s_ 
      
            RC4000/6000/8000 
            Basis System Package   (SW8001). 
            System Utility Package (SW8010). 
            ALGOL Package          (SW8500/1, release 11.0 or newer). 
            or 
            FORTRAN Package        (SW8501/1, release 13.0 or newer). 
             
             
     6_._ _ _ _ _ _D_o_c_u_m_e_n_t_a_t_i_o_n_ 
      
            The below listed manuals are collected in SDO 012. 
             
             
     6.1    RCSL No 31-D 198: Magnetic Tape System MTS2 
            The report describes the set of procedures for handling
            labelled files on magnetic tape. The handling comprises
            creation and check, positioning of tapes, use of variable
            record length. 
             
             \f

     6.2    RCSL No 31-D 228: Heapsort 
            Heapsort sorts the records of a number of files on a number of
            magnetic tapes. The files may have MTS-labels or no labels. The
            records may have fixed or variable length. 
            Heapsort is an ALGOL program, and heapsortpr is an ALGOL exter-
            nal procedure. 
             
             
     7_._ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ 
             
            The package is delivered on a 9-track magnetic tape or on a
            diskette. 
             
             
     7_._1_ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _f_r_o_m_ _M_a_g_n_e_t_i_c_ _T_a_p_e_ 
             
            File No:       Contents:                     Format: 
             
            0              label                         text 
            1              package identification        - 
            2              job to load the package       - 
            3              mts2                          binout 
            4              heapsort                      - 
             
            File No 1 is in text format and may be inspected by the utility
            program copy, e.g.: 
             
                 t = set mto mtsw8210 0 1 
                 copy list.yes t 
             \f

            File No 2 is a textfile, which contains a standard job with
            fp-commands to load the package, and it may be inspected in a
            similar manner. 
            The package is loaded by means of the job in this way: 
             
                 t = set mto mtsw8210 0 2  (or: nextfile t) 
                 loadjob = move t 
                 i loadjob 
             
             
     7_._2_ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ _f_r_o_m_ _D_i_s_k_e_t_t_e_ 
             
            The diskette containing the Magtape File Management Package is
            named SW8210 and is arranged as follows: 
             
            File No:       Contents:                     Format: 
             
            1              package identification        text, fdsave 
            2              job to load the package       text, fdsave 
            3              mts2                          binout, fdsave 
            4              heapsort                      binout, fdsave 
             
            The package identification in file No 1 can be inspected by a
            job in this way: 
             
                 fdload sw8210.1 
                 copy list.yes message.no idsw8210 
             
            The package is loaded by the job in file No 2 in this way: 
                  
                 fdload sw8210.2 
                 i jobsw8210 
             
            The requirements of the package in segments and entries are
            given in chapter 8. 
             
             \f

     8_._ _ _ _ _ _E_n_t_r_y_ _S_u_r_v_e_y_ 
             
            Installation of the package creates the following permanent
            entries: 
             
            Name:         Modekind/length:        Document Name: 
             
            heapsort      155                     drum/disc 
            heapsortpr     54                     - 
            externaladp    45                     - 
            stderroradp    13                     - 
            adpcode         2                     - 
            openadp        bs                     adpcode 
            closeadp        -                     - 
            positionadp     -                     - 
            tapeadp         -                     - 
            checkadp        -                     - 
            openandpos      -                     - 
             
            The package requires 269 segments (60 for mts2 and 209 for
            heapsort) and 11 permanent entries on drum/disc for
            installation. 
             
             
     9_._ _ _ _ _ _V_e_r_i_f_i_c_a_t_i_o_n_ 
             
            When inspected by procsurvey (heapsort by lookup or translated)
            all entries will show the date 1980.05.12. 
             
             
     1_0_._ _ _ _ _C_h_a_n_g_e_s_ 
             
            The package has not been changed since the latest release
            (10.3). 
            The actual release (11.0) is an ALGOL8 translation of the
            source. 
             
             \f

p_                                                               HECZ 810325              /9
m_ 
p_                       RC8000                                              INT
m_ 
               Utility Programmerne LIST og LAYOUT 
 
 \f

                  1_._ _ _ _ _I_N_D_L_E_D_N_I_N_G_ 
       
      Programmet afløser det hidtil anvendte LIST, og det har kode
      fælles med programmerne LAYOUT og SOAP, så disse 3 funktioner
      opnåes med 1 område og 3 entries. 
       
      Ændringerne i forhold til den tidligere version kan sammen-
      fattes til: 
       
           ny programopbygning, som letter vedligeholdelse, 
           udførelsen kræver mindre tid, og 
           der kan flettes flere sources. 
       
       
2_._ _ _ _ _F_U_N_K_T_I_O_N_ 
       
      LIST er primært beregnet til l_i_s_t_n_i_n_g_ _m_e_d_ _s_å_v_e_l_ _B_O_S_S_-_ _s_o_m_
      A_L_G_O_L_-_l_i_n_i_e_n_u_m_r_e_ _p_å_ _p_r_i_n_t_e_r_ _e_l_l_e_r_ _t_e_r_m_i_n_a_l_. 
       
      LIST kan anvendes til andre tekstfiler, som ønskes listet med
      BOSS-linienumre, og LIST kan anvendes til p_l_u_k_n_i_n_g_ _a_f_ _l_i_n_i_e_r_
      f_r_a_ _e_n_ _e_l_l_e_r_ _f_l_e_r_e_ _f_i_l_e_r_, enten til udskrift eller til sam-
      menfletning af en ny tekstfil. 
       
      Det anbefales at køre i size 20000 eller større. 
       
       
3_._ _ _ _ _E_K_S_E_M_P_L_E_R_ _P_Å_ _A_N_V_E_N_D_E_L_S_E_ 
       
      Eks. 1. 
       
      list nytext 
           Programmet LIST vil læse filen nytext og liste indholdet
           forsynet med BOSS- og ALGOL-linienumre på terminalen.
           ALGOL-linienumrene vil først optræde fra og med første
           linie, som indeholder et af ordene external eller begin.
       \f

                        Hvis man ønsker at LIST skal aflevere sin udskrift på printe-
      ren, angives dette ved at skrive conv=  eller blot c= efter-
      fulgt af programnavn og indfilnavn. 
       
      Eks. 2. 
       
      conv=list progtext 
           LIST læser fra filen progtext, genererer output med
           linienumre, og vil derefter (ligesom programmet CONVERT
           bede operativsystemet sende dette output til printeren. 
       
      Hvis udskriften ønskes leveret til andre medier, skal udfil-
      navn anføres som "venstreside" i programkaldet. 
       
      Eks. 3. 
       
      lp=list txtfile 
           LIST vil læse fra txtfile og udskrive indholdet på det
           dokument, som er beskrevet ved navnet lp. 
       
      Man kan modificere udskriften fra LIST ved efter indfilnavnet
      at anføre et eller flere optionnavne efterfulgt af værdier
      for vedkommende option. Foran optionnavn skal skilletegn være
      <sp>, og mellem optionnavn og alle tilhørende værdier, skal
      skilletegnet være . (punktum). 
       
      Udskrifter på printer og på terminal (current output) forsy-
      nes med linienumre, mens udskrifter til andre medier ikke får
      linienumre. Denne standard kan fraviges ved at anvende option
      count. 
       
      Der findes fire muligheder: 
       
      count.no,  count.boss,  count.algol  og count.yes. 
       \f

                        Eks. 4. 
       
      conv=list data count.boss 
           LIST sender til printeren indholdet af filen data forsy-
           net med BOSS-linienumre (ingen ALGOL-numre). 
       
      Option span anvendes, når man ønsker at udskrive dele af ind-
      filen bestemt ved linieintervaller (spans). 
       
      Eks. 5. 
       
           Fra en ALGOL-oversættelse af filen progtxt har man fået
           fejludskrifter for linierne 13-14, 119 og 234. Netop
           disse linier udskrives på terminalen ved anvendelse af
           programkaldet: 
            
           list progtxt span.13.14.119.119.234.234 
       
      I eks. 5 er der anvendt ALGOL-linienumre som optionværdier
      for span. Hvis man ønsker at anvende BOSS-linienumre, skal
      ordet BOSS anføres som optionsværdi før de tal, der skal op-
      fattes som BOSS-linienumre. 
       
      Option span giver yderligere mulighed for at anvende flere
      indfiler til opbygningen af den ønskede udfil. Hvis der
      blandt optionværdierne til span anføres et navn, som ikke er
      BOSS eller ALGOL, vil list fortsætte med at læse fra filen
      med dette navn eller plukke linier herfra i overensstemmelse
      med efterfølgende linienumre i "spanlisten". 
       
      Eks. 6. 
       
           newtxt=list oldtxt
           span.boss.10.120.ptxt.oldtxt.oldtxt.200.300.130.190.310 
       \f

                             I filen newtxt vil list aflevere 
            
           fra oldtxt linie 10 til 120 
           fra   ptxt hele indholdet 
           fra oldtxt linie 200 til 300 
           og         linie 130 til 190 og 
           fra        linie 310 og resten af oldtxt. 
       
      Optionværdien for max angiver den ønskede udskriftbredde (li-
      nielængde) i antal tegn. Såfremt en udskriftlinie (incl. li-
      nienumre) indeholder flere tegn end max-linielængde, deles
      denne udskriftlinie. 
       
      Standard max-værdier er: 
       
            80 tegn/linie på terminal (current output) 
           120 tegn/linie på printer og 
           meget stor ellers (ingen inddeling). 
       
      Optionsværdien for head angiver, hvorvidt der ønskes
      sideoverskrifter på udskriften (head.yes og head.no) eller
      antal linier pr. udskriftside incl. sideoverskrift (eks.:
      head.50). Et head består af indfilnavnet og dato samt
      sidenummer. Som standard giver LIST et head ved start på
      indfil for udskrift på printer og ellers ingen head. 
       
       
4_._ _ _ _ _P_R_O_G_R_A_M_K_A_L_D_ 
       
M_m_m_                 1                                           n   6 
       <udfil>=)  list<sp><indfil>  <sp><option>  .<værdi> 
P_p_p_                 0                                           1   0 

       
4_._1_ _ _ _U_d_f_i_l_ 
       
      <udfil> er navnet på en katalogindgang (filnavn) for output. 
       \f

      Er <udfil> ikke anført, benyttes current output efter at
      eventuelle fejlmeddelelser er udskrevet. 
       
      Er <udfil> c eller navn begyndende med conv, vil output blive
      converted til printer. 
       
      Er <udfil> en eksisterende katalogindgang, som beskriver et
      dokument, der må skrives på, så listes output på dokumentet,
      ellers oprettes en temporær discfil med navnet <udfil> til
      output. Hvis outputdokumentet er en discfil, forsynes kata-
      logindgangen med dato og tid efter samme konvention, som
      anvendes af BOSS. 
       
       
4_._2_ _ _ _I_n_d_f_i_l_ 
       
      <indfil> er navnet på en katalogindgang, som beskriver et
      dokument, der indeholder tekst. 
       
       
4_._3_ _ _ _O_p_t_i_o_n_._v_æ_r_d_i_ 
       
      <option>::= span  count  head  max  can  curr 
       
       
M_m_m_       
4.3.1 span.<spanværdi> 
P_p_p_                        1 
M_m_m_                                                                                    1 
      <spanværdi>::=<filnavn>bossalgol<startlinienr> .<slutlinienr> 
P_p_p_                                                                              0 
                   
      <filnavn>  
      angiver, hvorfra input skal læses.
 
      Indtil første <filnavn> er mødt, læses fra <indfil>. 
       
      boss 
      angiver, at efterfølgende linienumre skal tolkes som BOSS-
      linienumre. Indtil første boss er mødt, tolkes linienumre
      som ALGOL-linienumre. 
       \f

      algol 
      angiver, at efterfølgende linienumre skal tolkes som
      ALGOL-linienumre. 
       
M_m_m_                                     1 
      <startlinienr>. <slutlinienr> 
P_p_p_                                     0 
                  angiver det linieinterval, som skal medtages i output. Hvis
      <slutlinienr> er udeladt, medtages fra <startlinienr> til
      den inputlinie, hvor <em> læses. 
      Hvis der for en inputfil ikke er angivet linienumre,
      medtages hele filen i output. 
       
      Anvendelsen af span medfører en udskrift på current output
      om, hvilke span <udfil> består af. 
      Denne udskrift udelades dog, hvis der listes på current
      output. 
       
       
4.3.2 count.<countværdi> 
       
      <countværdi>::= nobossalgolyes 
       
      En outputlinie fra list består af et nummerfelt, som styres
      af countværdi, og herefter en tekstlinie fra input. 
       
      countværdi       nummerfelt          indhold 
         .no            0 positioner       intet 
         .boss          6 -                bosslinienr (5 pos) + <sp>
         .algol         6 -                algollinienr (5 pos) + <sp>
         .yes          11 -                boss- og algollinienr 
                                           (10 pos) + <sp> 
       
      Hvis count ikke er angivet, er default ved listning på
      current output eller printer count.yes og ellers count.no. 
       
       \f

4.3.3 head.<headværdi> 
       
      <headværdi>::= noyes<integer> 
       
      Et hoved indeholder filnavn og dato, som hentes fra indfi-
      lens katalogindgang, og dertil et sidenummer, idet hovederne
      nummereres fortløbende. 
      Et hoved indledes med følgende tegnsekvens 
           <* <ff><nl> 
      og det afsluttes med tegnsekvensen 
           <nl> *> 
       
      Karakteren <ff> er dog udeladt ved udfilens start, og hvis
      der umiddelbart før er udskrevet en <ff>. 
       
      headværdi         virkning 
      .no               der genereres ingen hoveder 
      .yes              der genereres et hoved for hver indfil-
                        start og efter hver <ff>. 
      .<integer>        der genereres yderligere hoveder hver
                        gang, der er udskrevet <integer> linier
                        siden sidst udskrevne <ff>. 
                     
      Hvis head ikke er angivet, vil der blive genereret et hoved
      for indfil-start, såfremt outputdokumentet er printer eller
      current output. Til andre outputdokumenter genereres ingen
      hoveder, når head ikke er angivet. 
       
       
              4.3.4 max.<maxværdi> 
       
      <maxværdi>::= <integer>, 20 <= <integer> < 150 
       
      Hvis en outputlinie incl. nummerfelt rummer mere end <max-
      værdi> tegn, vil linien blive delt, idet der indsættes <nl>
      og et antal <sp> svarende til nummerfeltet. 
       \f

      Liniedelingen indsættes således, at enhver outputlinie højst
      rummer <maxværdi> tegn, og at man undgår deling i text-
      strings, layoutstrings og sammenhørende bogstaver eller
      cifre. 
       
       
M_m_m_                        2 
4.3.5 can .<canværdi> 
P_p_p_                        1 
                   
      <canværdi>::= 1012 
       
                   can.10    undertrykker udskrift af blanke linier 
      can.12    -            -        -  <ff> læst fra <indfil> 
       
       
4.3.6 curr.<currværdi> 
       
      <currværdi>::= <integer>        0 <= <integer> < 800 
       
      Er <indfil> ikke angivet, bevirker denne option, at current
      input anvendes som indfil. 
      <integer> angiver, at den første indfillinie tildeles BOSS-
      linienummer <integer>. 
       
       
5_._ _ _ _ _F_E_J_L_M_E_D_D_E_L_E_L_S_E_R_ 
       
      ***infile/outfile conflict   <indfil> og <udfil> har samme
                                                navn 
      ***no infile                 indfil ikke angivet 
       
      ***optionlist 
      <separator> separator illegal 
      <parameter> option unknown or double 
      <parameter> value unknown \f

                        <parameter> value illegal 
      <parameter> too many values 
      <parameter> value missing 
       
      For optionlist-fejlmeddelelser tilføjes, når det har mening:
      item <integer> after optionname <option> 
       
      ***convert  lack of resources 
       
      Errors detected in <filnavn>: 
      line <bossnr> <algolnr> em read/wrong span 
       
       \f

p_                                                                 PEHO 810201            /2
m_ 
p_Package Description     RC4000      RC6000       RC8000      EXT
m_ 
               IBM 2780 Emulator Package, SW8700/1/1.0 
 
 \f

                  P_A_C_K_A_G_E_ _D_E_S_C_R_I_P_T_I_O_N_ 
 
1.    Package number:   SW8700/1 
       
2.    Package name:     IBM 2780 Emulator 
       
3.    Release:          1.0, 81.02.01 
       
       
4_._ _ _ _ _A_B_S_T_R_A_C_T_ 
       
      A new set of application programs for the Device Controller
      of an RC8000 has been developed, making it possible to use
      the RC8000 as a Remote Job Entry station for an IBM S/370
      main computer. 
       
      The communication procedure is the IBM 2780 BSC lineproto-
      col, and the transmission is handled from the RC8000 running
      under the operating systen BOSS. 
      It is then possible to transmit job- or command-files from
      backing store to the IBM, and to receive printouts (via
      spooling), using the normal BOSS commands. 
       
       
5_._ _ _ _ _P_R_E_R_E_Q_U_I_S_I_T_E_S_ 
       
      Hardware: 
      RC8000, RC8301 Front-End, with console, synchron multiplexor
      or synchron controller. 
       
      Software: 
      Basis system (SW8001) configurated for IBM 2780 emulator
      (SW8700/1). 
       
                        BOSS (SW8101) configurated for IBM 2780 emulator
      (SW8700/1). 
       
      System Utility Package (SW8010). 
       
       \f

6_._ _ _ _ _D_O_C_U_M_E_N_T_A_T_I_O_N_ 
       
      The documentation is collected in SDO 048. 
       
       
6.1   RCSL No 43-GL7841: RC8000 as IBM 2780 Terminal, User>s
      Guide 
      This manual describes the RC8000/IBM 2780 transmission
      system, the necessary commands, and a short description of
      the principle for the communication. 
       
       
6.2   RCSL No 43-GL7840: RC8000 as IBM 2780 Terminal, Reference
      Manual 
      This manual describes the RC8000/IBM 2780 communication
      system, which makes the RC8000 able to emulate an IBM 2780
      Remote Entry Terminal. 
       
       
7_._ _ _ _ _I_N_S_T_A_L_L_A_T_I_O_N_ 
       
      The package is generated and installed as a part of the
      RC8000 Basis System Package (SW8001/1). 
       
       
8_._ _ _ _ _E_N_T_R_Y_ _S_U_R_V_E_Y_ 
       
      None. 
       
       
9_._ _ _ _ _V_E_R_I_F_I_C_A_T_I_O_N_ 
       
      None. 
       
       
1_0_._ _ _ _C_H_A_N_G_E_S_ 
       
      New package. 
       \f

P_p_                      Partnr.system for RC                                        /12
m_                        HEKU/LIJ        04         81.01.15       EDB.HEKU.61 
     \f

                          A_r_b_e_j_d_s_g_r_u_p_p_e_n_s_ _f_o_r_s_l_a_g_ _t_i_l_ _e_t_ _f_r_e_m_t_i_d_i_g_t_ _p_a_r_t_n_r_._s_y_s_t_e_m_ _f_o_r_ _R_C_ 
                           
                          Projekt:             PARTNR.SYSTEM v. BM 
                          Aktivitet:           nr. 5, pkt. 3. 
                          Planlagt forløb:     nov.-dec. 1980 
                          Faktisk forløb:      nov.-jan. 1981 
                           
                          Arbejdsgruppen omkring denne aktivitet er LISC, NT, KNB, JEMI 
                          og HEKU, men KNB har ikke deltaget i møderækken og er ikke 
                          medforfatter. 
                           
                          Dette skrift er en revideret og endelig udgave af arbejdsgrup-
                          pens forslag. 
                           
                          De enkelte afsnits overskrifter er opstillet af BM i projekt-
                          beskrivelsen. Arbejdsgruppen foretrækker betegnelserne "indi-
                          vid" eller "partnr" fremfor "artikel". 
                           \f

                          1_._ _F_o_r_m_å_l_ 
                           
                          At skabe mulighed for en sammenlægning af de eksisterende
                          selvstændige nr.systemer og deres tilhørende registre.  
                          Dvs.: 
                             
                          - ntydig identifikation (adressering) af genstande, begreber m.v.
                            i såvidt muligt t nr.system. 
                             
                          - danne et solidt og varigt udgangspunkt for fleksibel
                            klassifikation og etablering af genfindingssystemer. 
                             
                          - være kort og håndterbart (og salgbart i organisationen). 
                             \f

                          2_._ _F_u_n_k_t_i_o_n_ 
                           
                          Partnr.systemet skal kunne afløse alle eksisterende nr.systemer an-
                          vendt i RC. De fleste indeholder en form for klassifikation der
                          suppleres med gruppekoder, stdtekster m.v. 
                           
                          Dette forslag indebærer n ordning i form af en adresse for alle
                          elementer i de områder der lægges ind under systemet.  
                           
                          Nr.rækkefølgen i denne adressering er tilfældig og betydningsløs. 
                           
                          Et så omfattende nr.system vil, hvis det anvendes på flere uafhæn-
                          gige registre, give store fejlmuligheder. Dette problem kan kun
                          løses ved anvendelse af n fælles database. 
                           
                          Ved tildeling af nye numre tages blot næste ledige iflg. en proto-
                          kol. I praksis vil der være behov for uddelegering af nr.tildelin-
                          gen. Dette sker ved anvendelse af et "checkhæfte" modtaget fra den
                          centrale styring. Checkhæftet omfatter et nr. interval svarende til
                          f.eks. et kvartals forbrug, evt. kan tildeling ske maskinelt.  
                           
                          Der er ønsker om tastebilag med fortrykt partnr. Dette er princi-
                          pielt OK, men det reserverede nr. interval pr. type bilag (delsy-
                          stem) bliver større og dækker en større forbrugsperiode. Koncen-
                          trationen af ibrugtagne nr. bliver måske ikke så høj som ønsket og
                          de fortrykte bilag kan bortkomme. 
                           
                          Forslaget indebærer en problemfri nr. tildeling, men stiller høje
                          krav til klassificeringsrutiner, der skal konstrueres således at de
                          "svinger" med organisationen i alle led. Desuden skal rutinerne
                          overvåges under implementering og drift for at opnå et realistisk
                          og pålideligt output. 
                           \f

                          Forslaget omfatter ikke klassifikationssystemer, men under
                          diskussionen er det blevet klart, at konvertering af delsystemer
                          først bør ske efter en revision og behovsanalyse af klassifika-
                          tionen er udført. Bl.a. skal det eksisterende nr.systems klassi-
                          fikation oftest bevares, og mange ændringsønsker og nye behov i de
                          eksisterende systemer er konstateret. 
                           \f

                          3_._ _D_e_f_i_n_i_t_i_o_n_ 
                           
                          Partnummeret er rent numerisk løbenr. suppleret med et checkciffer
                          der er placeret yderst til højre. Nummeret opdeles ved kommunika-
                          tion i grupper af 3 cifre, opdelt fra højre: F.eks. 
                                   79 003 158 
                                    1 398 279 
                                           18 
                           
                          Foranstillet nul samt mellemrum medtages ikke ved indtastning.  
                           
                          Antallet af cifre er principielt ubegrænset, men i praksis foreslås
                          8 stk., dvs. 7 betydende plus checkciffer. 
                           
                          Checkcifferberegningen foregår efter modulus 11 princippet (se
                          DS/inf.2). Herved bliver ca 10% af numrene uanvendelige, dvs. at
                          systemet rummer ca. 9 millioner numre. 
                           
                          En øjeblikkelig konvertering til dette partnr.system vil beslag-
                          lægge ca. 100.000 numre. Dvs. at et partnr. i overskuelig fremtid
                          vil have 7 cifre incl. checkciffer, og i nærmeste fremtid vil
                          størstedelen have 6 cifre. 
                           \f

                          4_._ _A_r_t_i_k_e_l_b_o_g_-_r_e_g_i_s_t_e_r_ 
                           
                          Som nævnt er et partnr. blot en adresse.  
                           
                          Ved ibrugtagning af et partnr. foretages den første, grove
                          klassifikation, jvf. fig. 1.  
                          Der skal tilrettelægges procedurer for registrering af kendetegn. 
                           
                          Et partnr.katalog kan udtages ved brug af klassifikationen og/eller
                          kendetegn som selekterings- og sorteringskriterier. 
                           
                           _ _ _ _ _ _ _ _ _ _K_L_A_S_S_I_F_I_K_A_T_I_O_N_ _ _K_E_N_D_E_T_E_G_N_(_a_t_t_r_i_b_u_t_t_e_r_)_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
                           
                                    råvare          leverandør - navn - tlf. - adr. 
                                                    priser 
                                                    rabatter 
                                                    leveringstider 
                           
                                    dok             forfatter 
                                                    antal sider  
                                                    sprog 
                           
                          Partnr.   person          ansættelsesdato 
                                                    uddannelse 
                                                    fagforening 
                                                    navn 
                                                    adresse 
                                                    by 
                                                    tlf. 
                           
                                    kunde           navn 
                                                    adr. 
                                                    anlæg 
                                                    TX-aftale 
 
                          Figur 1: Eksempel på kendetegn afh. af klassifikation. \f

                          5_._ _A_r_t_i_k_e_l_-_s_t_i_k_o_r_d_s_-_r_e_g_i_s_t_e_r_ 
                           
                          Der vil typisk ske en generel klassifikation af alle partnr. i form
                          af en gruppekode. Desuden vil en opdeling i kategorier med et sæt
                          af standardiserede kendetegn være nødvendig, f.eks: 
                               Partnr., gruppekode, modstand (dimension, værdi, effekt,
                               nøjagtighed, m.v.) 
                               Partnr., gruppekode, stålplade (dimension, kvalitet,
                               bearbejdelighed m.v.). 
                           
                          Ved fastlæggelse af standards på dette område kan PA>s varegrupper
                          og gruppekoder tages som udgangspunkt.  
                           
                          En sådan omfattende, standardiseret beskrivelse er grundlaget for
                          etablering af genfindingssystemer til brug i batch- og on-line-
                          miljø. Der er i RC79 et udtalt behov for sådanne systemer. 
                           
                          RC-salgsnr. og modulbetegnelsen ønskes bevaret og er et eksempel på
                          stikord af mindre koncentreret type. Fremover vil flere partnr.
                          have f.eks. RC8000-45S som stikord, og en udgave/status vil afgøre
                          hvilken der er den p.t. "bedste" ud fra brugerens behov. 
                           
                          Gruppen er enig om at en større detailleringsgrad i EDB-registrerin-
                          gen af de faktiske leverancer er ønskelig. En salgsordre (stam-
                          ordre) bør således indeholde "moduler" og deres FCO-status samt
                          oversigt over leverede manualer og basis-SW. Disse oplysninger
                          vedligeholdes af SYPA, INST og TS, og anvendes i tilfælde af
                          udvidelser eller ved sporing af fejl. 
                           
                          Etablering af kunde- og installationsnr. er en selvfølge; det er
                          blot partnumre.  
                           
                          Der kan ønskes en bedre registrering af dele til manualer dvs.
                           fotos, tegninger m.v. Desuden bør ringbind indgå i stk.lister. 
                           \f

                          6_._ _V_e_d_l_i_g_e_h_o_l_d_e_l_s_e_ _a_f_ _a_r_t_i_k_e_l_d_a_t_a_b_a_s_e_ 
                           
                          Organiseringen af inddata er delvis berørt i pkt. 2. 
                           
                          Systemet ligger i n fælles database, der giver frie muligheder for
                          forespørgsler. Dette kræver bl.a. høj kvalitet af data og kraftig
                          overvågning af inddata funktionerne. 
                           
                          I denne forbindelse bør noteres, at en on-line mulighed for ned-
                          brydning fra et salgsnr. til indgående råvarer i PA, som det er
                          ønsket af mange, kræver n fælles proces (f.eks. PLS). 
                           
                          Kvaliteten sikres bl.a. ved en tildeling af ansvaret for klassifi-
                          cering af bestemte felter pr. partnr. til de afdelinger der først
                          eller mest har behov for netop disse ting. Ansvaret kan evt. over-
                          drages ved statusændringer på partnr.  
                           
                          Hvor klassificering sker ud fra en standardtabel er det vigtigt, at
                          denne kan justeres hurtigt og nemt. 
                           
                          Der er behov for en central styring af  
                          - nr. protokol og kommunikation til lokale "checkhæftebestyrere"  
                          - overvågningsfunktionen: konsistenscheck 
                          - udsendelse af fejl-, rykker- og rettelseslister samt varekatalo-
                            ger og stk.lister. 
                           \f

                          7_._ _A_r_t_i_k_e_l_n_r_._s_a_m_m_e_n_h_æ_n_g_ 
                           
                          Systemet omfatter alle former for enheder og begreber, hvorfor
                          sammenhænge med et vilkårligt antal niveauer samt vilkårligt antal
                          partnr. pr. niveau skal kunne etableres.  
                           
                          Flere stk.lister pr. partnr. svarende til salgsnr.systemet er også
                          ønskeligt, men ikke ubetinget. Enten opbevares forældede og nye,
                          ikke godkendte stk.lister på papir, eller også skiftes partnr. ved
                          stk.liste ændringer. 
                           
                          Desuden skal der fra et givet partnr. til et eller flere andre
                          partnr. kunne etableres n til n relationer af typen "erstatter" og
                          "erstattes af ".  
                           
                          En stykliste skal kunne tilknyttes tekstfelter og andet, svarende
                          til f.eks. produktbeskrivelsen side 2. 
                           \f

                          8_._ _B_e_s_k_r_i_v_e_l_s_e_ _a_f_ _b_l_a_n_k_e_t_t_e_r_ 
                           
                          Gruppen har ikke detailerede forslag. 
                           
                          Ved revision skal der konstrueres nye blanketter til systemet,
                          afhængig af klassifikationen. 
                           
                          De skal være standardiserede, ligedannede, med ens termer og logisk
                          rækkefølge for tastefunktionen. 
                           
                          Der indtastes tabelværdier (koder) fremfor tekst, men i udskrifter
                          skal alt være oversat.  
                           \f

                          9_._ _O_m_n_u_m_m_e_r_e_r_i_n_g_ 
                           
                          Omnummerering kan ske maskinelt, idet et partnr. er et løbenr.  
                           
                          Ved denne lejlighed foretages en oprydning i de gamle numre, der
                          ikke skal konverteres.  
                           
                          De aktive numre skal inden omnummerering gemmes i et felt i partnr.
                          registret eller i et X-referenceregister. 
                           
                          Der er udtrykt behov for et lagerplaceringsindex til DOKU og PA.
                          Dette er uafhængigt af gl. og nyt partnr. Dokumentationen genop-
                          tryktes som hidtil, blot skal alle numre i originalen rettes (Evt.
                          skal alle originaler suppleres med en gammel udgave i arkiverne). 
                           
                          I HW-produktionen vil der komme et krav om påstempling af nyt
                          partnr.  
                           \f

                          1_0_._ _T_i_d_s_p_l_a_n_ _f_o_r_ _o_m_n_u_m_m_e_r_e_r_i_n_g_ 
                           
                          Ud fra det foreliggende materiale kan en nøjagtig tidsplan ikke
                          opstilles.  
                           
                          Gruppen skønner tidsforbruget til min. 1/2 år pr. delsystem incl.
                          revision og parallelkørsel.  
                           
                          Delsystemerne er: PA, RESA, DOKU, GLO(PB), produktionspapirer. 
                           
                          Desuden kan områderne projektstyring og tidsregistrering på længere
                          sigt også omfattes af systemet. 
                           \f

p_                                                               HECZ 810326              /8
m_ 
p_                       RC8000                                              INT
m_ 
               Utility Program LIB 
 
 \f

                  1_._ _ _ _ _I_N_D_L_E_D_N_I_N_G_ 
       
      Programmet kan gemme og fremfinde filer og entries og derved
      reducere behovet for permanente ressourcer. 
       
      Alle kommandoer fra CONTRACT kan benyttes på samme måde til
      LIB. På et tidspunkt skal LIB helt erstatte CONTRACT. 
       
      Filerne, der lagres i LIB-systemet, er opbevaret i en lib-
      fil, der består af 2 dele, et katalog og en data-del. Denne
      struktur er valgt for at undgå en kopiering af lib-filen ved
      hver ændring, og medfører, at specielt ON (ONT)-kommandoen er
      hurtigere end ved CONTRACT. Til gengæld fylder programmet
      noget mere, og det anbefales at køre LIB i size 30000. Kata-
      loget kan indeholde et begrænset antal filer og entries, an-
      givet ved INIT-kommandoen. Hvis der senere bliver brug for
      plads til flere, kan det kun foregå ved oprettelse af en ny,
      større lib-fil, som indholdet af den gamle lib-fil flyttes
      over på, f.eks. ved hjælp af programmet CLFLYT. 
       
      Ved ændringer til lib-filen (ON, ONT, CLEAR) ændres der af
      sikkerhedshensyn ikke på den nyeste information i katalog og
      data-del. Dette betyder, at lib-filen kræver lidt ekstra
      plads, men til gengæld er det næsten altid muligt at vende
      tilbage til den umiddelbart foregående version af lib-filen
      ved hjælp af kommandoen OLD, hvis en ændring fortrydes. 
       
      Oversigt over kommandoer: 
       
      a)   Generering af lib-filen: 
            
M_m_m_                                             1          1 
           LIB  INIT.<navn>   <antal filer>     <kit> 
P_p_p_                                             0          0 
                   
           antal filer angiver, hvor mange filer kataloget maksi-
           malt kan indeholde. \f

           Default er 45. 
           Default kit er disc. 
            
      Ved angivelse af et stort antal filer (> ca. 200) anbefales
      brug af en større size end 30000 for alle kommandoer. 
       
      b)   Indsættelse i lib-filen. 
        1) Entries og filer gemmes i lib-filen. Filen gemmes med
           det antal segmenter, der angives i tail: 
M_m_m_                                                              1         45 
           LIB  ON.<navn>  CHANGEKIT.<ACTUAL KIT>.<SAVED KIT>    <FIL> 
P_p_p_                                                              0          1 
                       <ACTUAL KIT>=<ACTUAL KIT> ELLER ALL 
            
        2) Kopiering af tekst-fil til "end of document": 
M_m_m_                                       45 
           LIB  ONT.<navn>   <fil i> 
P_p_p_                                        1 
                        
           ONT må ikke benyttes for binære filer eller for rene
           entries. 
            
           ONT kan fx bruges ved lagring af filer hentet fra et
           CONTRACT-lib, idet disse filers størrelse altid er
           opgivet til mindst 36. 
            
      c)   Udtræk fra lib-filen: 
        1) Oprettelse af filer og entries med scope LOGIN: 
M_m_m_                                                             1        45
           LIB FROM.<navn>  CHANGEKIT.<SAVED KIT>.<LOAD KIT>   <FIL>
P_p_p_                                                              0         1
                       <SAVED KIT>=<SAVED KIT> ELLER ALL 
         
        2) Oprettelse af filer og entries med scope TEMP på DISC: 
M_m_m_                                     45 
           LIB TEMP:<navn>  <fil i> 
P_p_p_                                      0 
               \f

                          3) Oprettelse af filer som entries, der peger ind på deres
           datadel i lib-filen; entries oprettes normalt: 
M_m_m_                                    45 
           LIB SET.<navn>  <fil i> 
P_p_p_                                     0 
                       SET-kommandoen skal anvendes med forsigtighed, da en
           skrivning på en fil oprettet ved hjælp af SET kan med-
           føre ødelæggelse af lib-filen, idet skrivningen foregår
           direkte i lib-filen. En skrivning af et større område,
           end der er afsat til filen, som er oprettet ved hjælp
           af SET, medfører derfor overskrivning af andre filer på
           lib-filen. SET-kommandoen kan med fordel anvendes til
           filer, der skal bruges som tekst input til SLANG, ALGOL
           eller RCMOL. 
            
        4) Oprettelse af grupper af filer og entries: 
M_m_m_                                      45 
           LIB DOC.<navn>   <fil i> 
P_p_p_                                       1 
                       Filer og entries med de angivne navne oprettes. Desuden
           oprettes alle de filer og entries, der har de angivne
           navne som dokumentnavne. 
            
      d)   Sletning af filer. 
M_m_m_                                       45 
           LIB CLEAR.<navn>   <fil i> 
P_p_p_                                        1 
                        
      e)   Oversigt over indhold i lib-fil. 
        1) Udskrift af navn og dato. 
M_m_m_                                       45 
           LIB LIST.<navn>   <fil i> 
P_p_p_                                        0 
                        
        2) Udskrift af katalog-indgange i samme format som lookup.
M_m_m_                                       45 
           LIB ALL.<navn>   <fil i> 
P_p_p_                                        0 
            \f

      f)   Retablering af information før sidste ændring (ON, ONT
           eller CLEAR) af lib-filen. 
            
           LIB OLD.<navn> 
            
           Efter en a_b_o_r_t_e_r_i_n_g_ ON/ONT er der dog r_i_s_i_k_o_ for at den
           foregående version af filer, der er genoplagt eller
           cleared i sidste gennemførte ON/ONT/CLEAR, er o_v_e_r_s_k_r_e_-
           v_e_t_. 
            
      g)   Fremtvungen reorganisering af lib-filen. 
                         Normalt UDVIDER og inskrænker (REORGANISERER) LIB selv
           lib-filen i takt med ændringer i mængden af lagrede
           data; men følgende kommandoer kan også fremtvinge en
           REORGANISERING: 
            
        1) LIB REORG.<navn> 
           Komprimerer datadelen af lib-filen og afsætter et le-
           digt område af "passende størrelse" til evt. ændringer.
            
        2) LIB CUT.<navn> 
           Som REORG, men afsætter intet ledigt område til evt.
           ændringer (den automatiske udvidelses- og indskrænk-
           ningsmekanik er dog fuldt intakt). 
            
      Angives der ingen filer som parametre til FROM, TEMP, SET,
      LIST eller ALL, udføres kommandoen for alle filer i lib-
      filen. 
       
                   Efter udførelsen af en lib-kommando angiver OK-bit'en, om
      der er sket grove fejl under udførelsen (lib-fil eksisterer
      ikke o.l.). Hvis en del af en kommando mislykkes (en fil ek-
      sisterer ikke o.l.) sættes warning-bit'en. 
       
       \f

                  2_._ _ _ _ _F_L_Y_T_N_I_N_G_ _F_R_A_ _C_O_N_T_R_A_C_T_ _T_I_L_ _L_I_B_ 
       
      Til brug ved flytning af filer fra en lib-fil til en anden
      (fx fra CONTRACT til LIB) er der et hjælpeprogram CLFLYT.
      CLFLYT leverer som output en fil, der indeholder FP-komman-
      doerne til at udføre flytningen. 
       
      Følgende job opretter en LIB lib-fil nyfil og flytter alle
      filer fra CONTRACT lib-filen gllib over på nylib. 
       
       10  mode list.yes               ; skal huskes da det benyt-
                                       ; tes af CLFLYT 
       20  o listfil 
       30  CONTRACT LIST.gllib 
       40  o  C 
       50  fpfil = CLFLYT listfil, 
       60          fra.CONTRACT.FROM.gllib, 
       70          til.LIB.ONT.nylib, 
       80          antal.5             ; antallet er afhængigt af 
                                       ; login ressourcer 
       90  LIB INIT.nylib <antal filer>; <antal filer> skal angi-
                                       ; ves så stort, at alle
                                       ; filer kan være i nylib 
                   100  i fpfil 
      110  finis 
       
      Husk at angive size 30000 og passende time. 
       
      Syntaksen for kaldet af CLFLYT er: 
M_m_m_                1 
       <udfil>    = CLFLYT <indfil>, 
P_p_p_                0 
                                fra.<lib-system>.<fra-kommando>.<fra lib-navn>,
                    til.<lib-system>.<til-kommando>.<til lib-navn>,
M_m_m_                                    1 
                     antal.<antal> 
P_p_p_                                                0 
                   \f

      Hvis <udfil> udelades, leveres output på "current output". 
       
      <indfil> er navnet på en fil med struktur som output fra
      CONTRACT- eller LIB-kommandoen LIST. Alle filer, der skal
      flyttes, skal optræde på denne liste. 
       
      <lib-system> er CONTRACT eller LIB. 
       
      <fra-kommando> er TEMP eller FROM. FROM benyttes, når der
      skal flyttes filer, hvis katalog-indgang indeholder et andet
      device-navn end "disc". Hvis TEMP benyttes ændres alle
      device-navne til "disc". FROM kræver, at nogle login res-
      sourcer er til stede (se under <antal>). 
       
      <fra lib-navn> er navnet på den lib-fil, som filerne skal
      hentes fra. 
       
      <til-kommando> er ON eller ONT. ONT benyttes kun, når der
      skal flyttes filer til LIB, fx fra CONTRACT. 
       
      <til lib-navn> er navnet på den lib-fil, som filerne skal
      flyttes til, husk at lib-filen skal være oprettet ved hjælp
      af INIT inden FP-kommandoerne på <udfil> udføres. 
       
      <antal> angiver, hvor mange filer, der flyttes ad gangen.
      Flytningen foregår gruppevis, således at de oprettede temp
      eller login-filer slettes efter flytning af hver gruppe.
      Derfor angiver <antal>, hvor mange temp eller login-ressour-
      cer, der kræves. 
      Der skal gælde, at 1 <= <antal> <= 45, og default er 45. 
       
       \f

                  3_._ _ _ _ _H_Å_R_D_ _F_E_J_L_ _S_O_M_ _A_F_B_R_Y_D_E_R_ _P_R_O_G_R_A_M_ 
       
       1:  manglende parametre 
       2:  manglende LIB 
       3:  illegal kommando, <kommando> 
       4:  filnavn eksisterer i forvejen, <LIB> 
       5:  ulovligt antal filer 
       6:  ukendt kitnavn, <kitnavn> 
       7:  lib-fil ikke oprettet, <LIB> 
       8:  ingen permanente ressourcer 
       9:  lib-fil ikke fundet, <LIB> 
      10:  fil ikke lib-fil, <LIB> 
      11:  version fra entry-tail (9) er forkert, <LIB> 
      12:  størrelse af katalog fra entry-tail (10) er forkert,
           <LIB> 
      13:  LIB kan ikke ændres, <LIB> 
      14:  filnavne, <kommando> 
      15:  katalog fuldt, intet indsat, <LIB> 
      16:  fil kan ikke oprettes, <navn> 
      17:  problemer ved overskrivning af fil, <NAVN> 
      18:  ingen login ressourcer 
      19:  ingen temp ressourcer 
      20:  udvidelse af LIB ikke mulig, <LIB> 
      21:  arbejdsområde kan ikke oprettes 
      22:  arbejdsfil kan ikke gøres permanent, intet ændret 
      23:  intet ændret, venligst clear login, <NAVN> 
      24:  sletning af gammelt LIB ikke muligt, intet ændret 
      25:  undersøg wrk-fil, LIB findes ikke, <NAVN> 
      26:  systemfejl, uoverensstemmelse i LIB, <LIB> 
       
       \f

                  4_._ _ _ _ _B_L_Ø_D_ _F_E_J_L_ _S_O_M_ _I_K_K_E_ _A_F_B_R_Y_D_E_R_ _P_R_O_G_R_A_M_ 
       
       1:  dublet i programliste fjernet,<NAVN> 
       2:  for mange parametre, ikke behandlet,<NAVN> 
       3:  illegal parameter type 
       4:  fil eksisterer ikke, <NAVN> 
       5:  illegal char or no em in file, <NAVN> 
       6:  filtype illegal ved ONT,<NAVN> 
       7:  fil findes ikke i LIB, <NAVN> 
       8:  filtype illegal ved set, <NAVN> 
       
       \f

p_                                       JMA 810420              JMA 820811               /7
m_ 
p_                      RC4000      RC8000                                   EXT
m_ 
               Corrections to RCSL No 42-i1265: BOSS2 User's Manual 
 
 \f

                  This RC Information Note contains corrections to "BOSS2, User's
Manual" (Second Edition, August 1979, RCSL No 42-i1265). 
 
With these corrections included, the manual corresponds to the
Software Package SW8101/1/18.0: BOSS Release 18.0. 
 
1_._ _(_N_E_W_)_ _P_a_g_e_ _4_8_: 
 
verify: the command name may be abbreviated to 'v' (but not 've'
        or 'ver'). 
 
2_._ _P_a_g_e_ _5_6_: 
 
The terms <jobname> and <username> are not explained. 
     <username> is the username as used at login and in the job
                specification, e.g. "jma". 
     <jobname>  is a <username> followed <userindex> as defined at
                login or in the job specification, e.g. "jma0". 
 
3_._ _(_N_E_W_)_ _P_a_g_e_ _5_6_: 
 
The syntax for the display command is: 
 
M_m_m_                                1 
P_p_p_          convert 
M_m_m_                            1 
          <jobname>  claim   
P_p_p_                            0 
display   login 
          idle 
M_m_m_          dead 
P_p_p_                                0 
 
4_._ _P_a_g_e_ _5_6_: 
 
Last 4 lines: 
Replace <username> with <jobname>. 
 \f

5_._ _P_a_g_e_ _5_7_: 
 
Just before the example, add: 
     login   means that the information displayed concerns a user
             logged in at a terminal. 
 
6_._ _(_N_E_W_)_ _P_a_g_e_ _5_7_-_5_9_: 
 
Replace the entire description of 'display convert' with: 
 
display convert 
 
This command displays information on printers and convert queues.
The output consists of a number of lines in the sequence: 
 
<routing inf> 
<printer inf> 
<paper queues> 
<remote queue> 
Format of <routing inf>: 
       one line for for each routing. 
 
Format of the following lines : 
one line for each printer active (or holding a convert), and one
line for each convert queued up. 
 
7_._ _P_a_g_e_ _6_5_: 
 
Replace the entire page with: 
 
M_m_m_                                      1                   1   1 
     transmit <mode> <name>    <doc>    <start>   <stop> 
P_p_p_                                      0                   0   0 
 
Some terminals have facilities for offline preparation and storage
of data on media such as paper tape, cassette, diskette or bubble
memory. The method to be used for the subsequent transfer of such
data to the main computer varies according to the facilities
available for this purpose in the terminal. In some cases you may
use load-specifications in a job, in other cases you may use the\f

autoline command, but a common method is just to start the
transfer and then let it proceed at maximum speed without pauses
or checks. 
 
The command transmit is designed to receive such transfers. A
loginfile with the name '<name>' is created on the backing storage
'<doc>' (default is 'disc'). If an entry of this description
already exists it will be cancelled first. Date and time is in-
serted in the file descriptor. 
 
After this the message "start transmit" is printed on the ter-
minal, to signal that BOSS is ready to receive the data. The
action then required to start the transfer varies, depending on
the type of the terminal, from the simple pushing of a button to
typing one or more local commands. 
 
If BOSS has not received the first data within a certain time,
'transmit' will terminate. This time limit is installation de-
pendant, but you may use the parameter <start> to redefine it to
'<start>' seconds. 
 
To prevent loss of data, BOSS wil use double buffering to receive
the data and the data will not be echoed, though some terminals
may echo the data locally (e.g. RC315 if mode is 'trt'). The data
will be converted according to '<mode>': 
 
tre    No conversion. The input is supposed to be ISO-text, even
       parity, but the parity bit is supposed to have been checked
       and stripped off before BOSS receives the characters (BOSS
       uses input mode = 2). 
        
trt    As 'tre', except that local echoing is enabled on RC315. 
        
trf    Input is supposed to be flexowritercode which is converted
       to ISO-code. BOSS uses input mode = 4 and checks parity.
       Characters with parity error (except 'no holes' and 'all
       holes' are replaced by 'substitute'-characters (decimal
       value 26). 
 \f

tro    Input is supposed to be ISO-code, odd parity. BOSS uses
       input mode = 4 and checks parity. Characters with parity
       error (except 'no holes' and 'all holes' are replaced by
       'substitute'-characters (decimal value 26). The parity bit
       (the bit with decimal value 128) is then stripped off. 
        
trn    No conversion. BOSS uses input mode = 4, i.e. all 8 bits of
       the characters are transferred unchanged. 
        
'transmit' will terminate on any error during the transfer (except
parity errors) or when more than a certain time elapses between
the reception of data portions. This time limit is installation
dependent (a common value is 5 seconds), but you may use the
parameter <stop> to redefine it to '<stop>' seconds. 
 
The converted characters are transferred to the file. The file is
created with a length of one slice, and is extended one slice at a
time as needed. When 'transmit' terminates, the last segment will
be filled with terminators and cut to actual size. 
 
The terminators are: 
 
'tre', 'trt' and 'trf': <EM> (decimal value 25). 
tro: characters with decimal value 128. 
trn: characters with decimal value 0. 
 
Notes: 
The transfer rate possible will depend on terminal buffer size,
how much room BOSS has for its own code and the load of other
tasks (especially when the area is being extended). 2400 Baud has
been used with only occasional failures. 
 
Some terminals cannot transfer certain characters (e.g. those with
decimal values higher than 127), or stop when they meet certain
characters. In the latter case it may be possible to resume the
transfer if you use a sufficiently high value of the parameter
<stop>. 
 \f

                  8_._ _(_N_E_W_)_ _P_a_g_e_ _6_6_:_ 
 
Replace "Class 2: ..." with: 
 
Class 2: ("Half operator") enables the user to act as an operator
         on a remote side, i.e. to execute commands to control
         (remote) device on his own device host. 
  
9_._ _(_N_E_W_)_ _P_a_g_e_ _6_7_: 
 
Replace "Class 2: ..." with: 
 
Class 2: job regret store answer test snapshot repeat kill route
         cancel. 
          
1_0_._ _(_N_E_W_)_ _P_a_g_e_ _7_3_: 
          
after "trn ..." add: 
          
trz      As tru, but sprocket holes in the tape are sensed, i.e.
         blank tape will be read and stored as NULL-characters
         (binary zeroes). 
 
1_1_._ _(_N_E_W_)_ _P_a_g_e_ _7_3_: 
          
In the middle of the page, after "ptru", add: 
          
         ptrz 
         
1_2_._ _(_N_E_W_)_ _P_a_g_e_ _7_3_: 
 
Replace the section "End medium character extension" with: 
 
E_n_d_-_m_e_d_i_u_m_-_c_h_a_r_a_c_t_e_r_ _e_x_t_e_n_s_i_o_n_ 
When the last character from the tape has been read and stored,
the remaining part of the last segment of the backing storage area
will be filled with words containing an 'end-medium pattern',
according to mode: \f

p_                                       JMA 810421              CHD 820810               /7
m_ 
p_                      RC4000      RC8000                                   EXT
m_ 
               Corrections to RCSL No 31-D498 BOSS2 Operator's Manual. 
 
 \f

                  The following corrections should be included in "BOSS2 Operator's
Manual" (RCSL No 31-D498): 
 
With the following corrections included, the manual corresponds to
the software package SW8101/1/18.0: BOSS release 18.0. 
 
1_._ _P_a_g_e_ _2_-_4_: 
 
Line 4, replace 'boss fault' with '***closed by operator'. 
 
2_._ _P_a_g_e_ _3_-_4_: 
 
Insert after the statement 'Remember that ......... get command': 
 
call <device number> <device name> 
 
This command will cause BOSS to perform the monitor function 54:
'create peripheral process' with the parameters specified, i.e.
the device with logical device number <device number> is given the
name <device name>. 
 
3_._ _(_N_E_W_)_ _P_a_g_e_ _3_-_4_: 
 
Add the following, just after the insertion in 2: 
 
                                 <remote printer> 
                Cancel routing    std 
                                  all 
 
The command cancels a preveously created routing from the
printer(s) mentioned. <remote printer> must be a name of a catalog
entry (visible, but protected), describing the remote printer. 
 
"all" means: all routings are cancelled. Note, that converts
already routed are not changed. 
 \f

                  4_._ _(_N_E_W_)_ _P_a_g_e_ _3_-_5_: 
 
Remove the 6 bottom lines. 
 
5_._ _(_N_E_W_)_ _P_a_g_e_ _3_-_6_: 
 
Remove all lines from top until  
 
   "even...". 
 
Insert instead: 
 
   display convert 
 
The command displays information on printers and convert queues.
Layout of output: 
 
   <routing inf> 
   <printer inf> 
   <paper queues> 
   <remote queue> 
 
Format of <routing inf>: 
One line for each routing. 
 
              all                    std 
   routing:   std                to 
              <remote printer>       <remote printer> 
 
Format of the following links: 
one line for each printer active (or holding a convert), and one
line for each convert queued up. 
 
printer     <printer devno> 
M_m_m_paperq      <remote printer> 
                                 <paper> <user> 
P_p_p_remoteq     <device host id> 
<empty>     <empty> 
 \f

                             <file name>                waiting 
 (cont.)   jobcontrl.   <segm. left>  connecting 
           primout.                   paper out 
                                      troubles 
                                      <empty> 
 
As the queues may be manipulated during output of the lines, the
command cannot guarantee a correct "snapshot". 
 
6_._ _(_N_E_W_)_ _P_a_g_e_ _3_-_7_: 
 
Replace the line 
   kill <device number> 
with 
M_m_m_        <device number> 
   kill 
P_p_p_        <remote printer> 
 
Replace the sentence "The device must be a printer" with: 
The device must be a printer, specified either by device number
(standard printer) or the name of a catalog entry describing the
printer (remote printer). 
 
7_._ _(_N_E_W_)_ _P_a_g_e_ _3_-_9_: 
 
                  Replace 
    repeat <device number> 
      with 
M_m_m_           <device number> 
    repeat
P_p_p_           <remote printer> 
 
(and the same interpretation as above in the kill command). 
 \f

                  8_._ _ _(_N_E_W_)_ _P_a_g_e_ _3_-_1_0_: 
 
Insert at the top: 
M_m_m_         std                     std 
route    all                to 
P_p_p_         <remote printer>        <remote printer> 
 
Creates a routing, as specified.  
"std" means "on a standard printer", 
"all" means all converts,  
<remote printer> is the name of a catalog entry describing the
printer (visible and protected). 
 
The routing changes the selected printer for all future converts,
and for all converts currently queued. 
 
The routing may not take place instantly, but is postponed until
the moment that it should have been printed. 
        
The maximal number of routings is an installation parameter. 
         
It is checked, that the total list of routings does not contain
loops. 
 
9_._ _ _(_N_E_W_)_ _P_a_g_e_ _3_-_1_1_: 
 
In line 4 from bottom, replace 
   "resource free". 
with 
   "display convert, resource free". 
 
1_0_._ _(_N_E_W_)_ _P_a_g_e_ _6_-_4_: 
 
                  Replace the sentence 
   "It is thus adviceable ... 
          before closing down." 
       with 
    "Before close down of BOSS, check that no converts are queued,
           by the command display convert." 
 \f

                  1_1_._ _(_N_E_W_)_ _P_a_g_e_ _1_1_-_1_: 
 
Remove the line "boss alarm" 
        and the next. 
 
        Insert instead: 
boss not user of device 
 
The call command is given on a devce, where BOSS is not user. 
 
1_2_._ _(_N_E_W_)_ _P_a_g_e_ _1_1_-_2_: 
 
Insert, before the line 
   "coroutine area missing": 
 
A device number may be followed by an asteriks, and then the text
is added: *boss not user 
 
If more than 4 devices were requested by the job, a "+" is added
       after the device numbers. 
 
        1_3_._ _(_N_E_W_)_ _P_a_g_e_ _1_1_-_6_: 
 
Insert, before the line 
   "label name...": 
label command on <device number> 
 
A label command has been accepted. 
 
1_4_._ _(_N_E_W_)_ _P_a_g_e_ _1_1_-_7_: 
 
Insert, before the line 
   "name illegal...": 
name command on <device number> 
                   
A name command has been accepted. 
       \f

                  1_5_._ _(_N_E_W_)_ _P_a_g_e_ _1_1_-_9_: 
 
Insert, before the line 
           "printer <device number> change...": 
         
M_m_m_                                   <file name> 
---<jobname> prepare <remote name> primout     segments: <segm> 
P_p_p_                                   jobcontr 
 
The message appears on a device host console (remote console),
when output is initiated on a remote device which is not a
printer. 
 
1_6_._ _(_N_E_W_)_ _P_a_g_e_ _1_1_-_1_1_: 
 
Insert, before the line 
          "type user name...": 
 
M_m_m_                       boss not user of device 
trouble on <devno> 
P_p_p_                     device reserved by other process 
 
A job has requested a magnetic tape station, that is not
available. 
 
1_7_._ _A_p_p_e_n_d_i_x_ _1_: 
 
The references do not correspond to the present edition of "BOSS2
User's Manual". Therefore you should disregard this appendix.  
 
1_8_._ _A_p_p_e_n_d_i_x_ _2_:_ _P_a_g_e_ _A_2_-_3_: 
 
In the description of convert please add: 
 
iv) <printername> may be a filedescriptor as described in "BOSS2
User's Manual", chapter 7.  
 \f

1_9_._ _A_p_p_e_n_d_i_x_ _2_,_ _P_a_g_e_ _A_2_-_4_: 
 
In line number 4-5 'with the specified name' should be replaced by
'specified' (by local device name or by a filedescriptor). 
       \f

p_                                                               CHD 820809               /2
m_ 
p_                      RC4000      RC8000                                   EXT
m_ 
               Corrections to RCSL No 31-D673: BOSS Basic Internal Formats. 
 
 \f

                  With these corrections included, the manual corresponds to the
Software package SW8101/1/18.0: BOSS Release 18.0. 
 
1_._ _P_a_g_e_ _5_6_: 
 
Add the following testoutput types to the list: 
 
T_Y_P_E_ _ _ _ _ _ _ _ _ _ _S_O_U_R_C_E_:_ _C_O_N_T_E_N_T_S_ _D_E_S_C_R_I_P_T_I_O_N_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
 37           FAULT: Variables of Central Logic. 
 38           FAULT: Start of current page 0. 
 39           FAULT: Start of current page 1. 
 40           FAULT: Start of current page 2. 
 41           FAULT: Start of current page 3. 
 42           FAULT: Start of current page 4. 
 
The following types are used temporarily: 
 
 50           PRINTER: printertable page. 
 51           PRINTER: own printertable description. 
 52           PRINTER: convert operation. 
 53           PRINTER: Printertable page. 
 54           PRINTER: printer variable page. 
 60           BANKER:  variables from "compute as a-job". 
 61           BANKER:  variables from "compute as b-job". 
 
2_._ _P_a_g_e_ _6_7_: 
 
Add the format of types 37-42: 
 
The types 37-42 all have same format as type 22, and type 38-42
have the same length as type 22: i205hw. Type 37 have a length of
approx. 100 hw, containing the slang variables f1-f35. 
 \f

                  All types, 22 and 37-42 have the same format: 
 
 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
 TYPE  TIME  FIRST 
             ADDR   CONTENTS OF PRIMARY STORAGE 
 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _F_R_O_M_ _F_I_R_S_T_ _A_D_D_R_ _A_N_D_ _O_N_ _ _ _ _ _ _ 
 
They will all be printed by the standard testoutput program (last)
with a special format, printing one word per line. 
 
3_._ _P_a_g_e_ _6_9_: 
 
Insert, before the line "7 watchdog...": 
 
   5 metermaid (printer) 
 \f

p_                                                               TSH 830111               /2
m_ 
p_                      RC4000      RC8000                                   EXT
m_ 
               Corrections to RCSL No 31-D610: Parrent Message in RC8000. 
 
 \f

                  These corrections are only valid for monitor release 9.0. 
 
1_._ _P_a_g_e_ _3_:_ 
 
Bottom, replace last line with: 
except 'finis', 'replace' and 'newjob', see 3.2, 3.10 and 3.12. 
 
2_._ _P_a_g_e_ _5_: 
 
OPERATING SYSTEM ACTIONS, replace the action of s with: 
s: the job process will be removed. See ref. 10 2.2. 
 
3_._ _P_a_g_e_ _1_0_: 
 
PREREQUISISTES, add 
s: The replacement file must be visible from the sending process. 
 
(This correction replaces the correction in JMA820813). 
 
4_._ _P_a_g_e_ _1_1_: 
 
OPERATING SYSTEM ACTIONS, cansel "if wait = 1", in the action of
s. 
 
5_._ _P_a_g_e_ _1_2_: 
 
PREREQUISITES, add 
s: The jobfile must be visible from the catalogbase of the sending
process. 
 
6_._ _P_a_g_e_ _1_3_: 
 
s: When s receives the message, an answer with result = 1 is
returned and s starts the execution of the commands specified in
the job file. Messages from the execution (error messages or
output from 'list' or 'max' commands) will be printed on the
console of the sending process. <printerspec> is ignored. 
 \f

p_                                                               EL 810209                /4
m_ 
p_                                                RC850                      CONF
m_ 
               Anvendelse af RC850 non-volatile memory 
 
 \f

    1_._ _S_k_r_i_v_n_i_n_g_/_l_æ_s_n_i_n_g_ _a_f_ _N_V_M_-_i_n_d_h_o_l_d_ 
     
    NVM på RC850 indeholder 21 16-bit ord. Al skrivning/læsning i NVM
    foregår ved hjælp af to assembler-kodede rutiner, EWRNVM og
    ERDNVM, som henholdsvis skriver og læser et ord i NVM. Rutinerne
    findes på den diskette som indeholder RC850 test programmer,
på filen NVM (;E, og ;S) og assembleres separat. Objektfilen
linkes efter behov ind i basis-systemer og bootstrap-promsæt. 
     
Bemærk at rutinerne udvirker at interrupt-systemet disables i ca.
300 ms. 
 
    P_a_r_a_m_e_t_e_r_s_p_e_c_i_f_i_k_a_t_i_o_n_e_r_: 
     
    EWRNVM   kald:    A adresse (0-20), HL indhold 
    ERDNVM   kald:    A adresse (0-20) 
              retur:   HL indhold. 
     
     
    2_._ _I_n_f_o_r_m_a_t_i_o_n_e_r_ _i_ _N_V_M_ 
     
    NVM indeholder et antal informationer, hvoraf kun et udvalg er
    relevante for hver RC85x-applikation. Initialisering af NVM ved
    produktion er dog fælles for alle applikationer. 
     
    c_u_r_s_o_r_ _p_r_æ_s_e_n_t_a_t_i_o_n_ (cp: 2 bit, værdi 0-3) 
     
    Anvendes til at afgøre hvordan cursor skal præsenteres. Ignoreres
    af nogle applikationer. 
     
        0:   underline, ikke blink 
        1:   underline, blinkende 
        2:   block, ikke blink 
        3:   block, blinkende 
     \f

l_i_n_e_ _s_p_e_e_d_ (ls: 3 bit, værdi 0-6) 
 
Bestemmer hastighed på V.24/X.21 kommunikationslinje, asynkront
eller synkront afhængig af applikation. Slaveprinter på RC851
kører med samme hastighed. 
 
    0:    110 bps 
    1:    300 bps 
    2:    600 bps 
    3:   1200 bps 
    4:   2400 bps 
    5:   4800 bps 
    6:   9600 bps 
 
p_r_i_n_t_e_r_ _l_i_n_e_ _s_p_e_e_d_ (pls: 3 bit, værdi 0-6) 
 
Bestemmer hastighed for seriel (V.24) printer i applikationer hvor
denne kan afvige fra hastigheden på kommunikationslinjen. Kodes
som ls. 
 
s_e_c_o_n_d_a_r_y_ _a_d_d_r_e_s_s_ (sa: 3 bit, værdi 0-7) 
 
Bestemmer secondary address (poll adresse) for terminal som optræ-
der som secondary på en CIRCUIT, knyttet til VDC eller anden klyn-
ge-controller. 
 
t_e_r_m_i_n_a_l_ _n_u_m_m_e_r_ (tn: 8 bit, værdi 0-255) 
 
Terminal nummer benyttes af RC852 til at identificere terminalen i
den pågældende konfiguration, dvs. til at udpege den aktuelle ter-
minal handler på RC3502 FE. Terminal nummer initialiseres til 0
ved produktion, og en terminal med nummer 0 opfattes af FE som ik-
ke tilhørende konfigurationen. 
 \f

Format control modulet som anvendes i RC852 og RC855-biskærm og
som understøtter skærm og printer (printer kun i RC855) kompati-
belt med IBM 3270 data buffer og transaktions formater anvender
DEV-nummer (1..32) i kommunikation vedrørende henholdsvis skærm og
printer. For RC852 anvendes DEV af FE-programmellet til at identi-
ficere de enkelte skærme. 
 
For skærm-devicet gælder DEV=(tn MOD 32)+1. 
 
p_r_i_n_t_e_r_ _d_e_v_i_c_e_ _n_u_m_m_e_r_ (pdn: 5 bit, værdi 0-31) 
 
Printer device nummer bruges i RC855 biskærm til at identificere
en eventuel printer; der gælder DEV=pdn+1. 
 
h_a_r_d_ _c_o_p_y_ _p_r_i_n_t_e_r_ (hcp: 5 bit, værdi 0-31) 
 
For en skærm i en RC855 klynge, hvori der findes en eller flere
printere, angiver hcp hvilken printer der skal anvendes som hard
copy printer for den pågældende skærm; hcp=pdn for hard copy
printeren, som altså ikke behøver at sidde på samme skærm. 
 
 
3_._ _N_V_M_ _l_a_y_o_u_t_ 
 
De ovennævnte informationer anbringes i NVM som vist nedenfor 
 
    bit   MSB                                           LSB 
ord        _1_5_ _1_4_ _1_3_ _1_2_ _1_1_ _1_0_ _ _9_ _ _8_ _ _7_ _ _6_ _ _5_ _ _4_ _ _3_ _ _2_ _ _1_ _ _0_ _ 
 0         _ _ _c_p_ _ _ _ _ _p_l_s_ _ _ _ _ _ _l_s_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _t_n_ _ _ _ _ _ _ _ _ _ _ _ 
 1         _ _ _ _ _ _ _p_d_n_ _ _ _ _ _ _ _ _ _s_a_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _n_c_p_ _ _ _ _ _ _ 
 2 
..                      endnu ikke anvendt 
20         _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
 
 \f

4_._ _I_n_i_t_i_a_l_i_s_e_r_i_n_g_ _a_f_ _N_V_M_ _v_e_d_ _p_r_o_d_u_k_t_i_o_n_ 
 
Det forventes at alle RC850 skærme ved produktion testes med
RC851-programmet kørende i test-loop mode. For at sikre en
fornuftig initialisering af NVM udføres som bivirkning af test
loop kommandoen følgende assignments til NVM: tn:=0, pdn:=0,
sa:=0, hcp:=0. 
              \f

p_                                      BKS 810128               BKS 811019               /3
m_ 
p_Package Description     RC8000                                             INT
m_ 
             BASIC/COMAL Package, SW8502/1/2.3 
 
 \f

     P_A_C_K_A_G_E_ _D_E_S_C_R_I_P_T_I_O_N_ 
      
     1.     Package Number : SW8502/1 
      
     2.     Package Name   : BASIC/COMAL 
      
     3.     Release        : 2.3, 801121 
      
      
     4_._ _ _ _ _ _A_b_s_t_r_a_c_t_ 
      
            The package holds an interpreter for the programming language
            RC BASIC/COMAL. 
             
      
     5_._ _ _ _ _ _P_r_e_r_e_q_u_i_s_i_t_e_s_ 
      
            RC8000 Basis System Package (SW8001) 
            System Utility Package (SW8010). 
            MIPS/TS Package        (SW8100). 
            Assembler Package      (SW8600). 
            Algol Package          (SW8500). 
             
             
     6_._ _ _ _ _ _D_o_c_u_m_e_n_t_a_t_i_o_n_ 
             
            The documentation is collected in SDO049. 
       
     6.1    RCSL 42-i1203 RC BASIC/COMAL, Programming Guide. 
             
            This guide describes the RC BASIC language implemented for
            RC8000. 
             
             
     7_._ _ _ _ _ _I_n_s_t_a_l_l_a_t_i_o_n_ 
             
            The package is delivered on a 9-track magnetic tape. 
             \f

            The requirements of the package in segments and entries are
            given in chapter 8. 
             
            The tape is arranged as follows: 
             
            File no:     Contents:           Format: 
            0            label 
            1            jobs to maintain    text 
                         the package 
            2-14         BASIC/COMAL text    text 
                         files 
            15           Programs to run     save 
                         the package 
             
            File no 1 contains jobfiles to load, save, compile and list the
            BASIC/COMAL system.  
             
            BASIC/COMAL is loaded and compiled by means of the fp-commands:
             
M_m_m_                                         mto 
                        comalhelp = set       mtcomal  0  1 
P_p_p_                                         nrz 
                        i comalhelp 
                        i comalload 
                        i comalgo 
             
             
     8_._ _ _ _ _ _E_n_t_r_y_ _S_u_r_v_e_y_ 
             
            Name                  Modekind/Length      Type 
             
            comalhelp                     7            text 
            tcomal                      426            text 
            tcomalmove                   18            text 
            tspoolfull                    5            text 
            ttestbit                      3            text 
            twritedate                   16            text 
            tdecomposef                  19            text \f

            Name                  Modekind/Length      Type 
             
            tisotable                     4            text 
            tchangeerr                    8            text 
            comalsyntax                  30            text 
            nametable                     2            text 
            tgenscan                      6            text 
            tgensyntax                   19            text 
            basicerror                   14            bs-area 
            xcomal                      483            algol-program 
            basicmove                     1            ext.procedure, slang
            spoolfull                     1            ext.procedure, slang
            testbit                       3            ext.procedure, algol
            writedate                     1            ext.procedure, slang
            decomposef                    2            ext.procedure, slang
            solvef                       bs            ext.procedure, slang
            isotable                      1            ext.procedure, slang
            changeerror                  43            algol program 
            genscan                      38            algol program 
            gensyntax                    46            algol program 
            scantable                     4            bs-area 
            syntaxtable                   6            bs-area 
            fastmove                     39            utility program 
            catupdate                   111            utility program 
            usercat                     100            bs-area 
            usertext                      1            text 
             
             
     9_._ _ _ _ _ _V_e_r_i_f_i_c_a_t_i_o_n_ 
             
            During compiling and start of BASIC/COMAL the message 
             
                version 2.3 d.801121.1345 
             
            will appear. 
             
     1_0_._ _ _ _ _C_h_a_n_g_e_s_ 
             
            The package has not been changed since the latest release. 
             \f

p_                                                               EL 810217                /2
m_ 
p_                                   RC700        RC850
m_ 
               Interrupt vektorer på RC700 og RC850. 
 
 \f

    1_._ _G_e_n_e_r_e_l_t_ 
     
    En PASCAL80-channel er på PI-1 maskinen en distinkt interrupt
    vektor værdi. 
     
    På hver version af PI-1 maskinen kender basis-programmellet et sæt
interrupt vektor værdier som svarer til de tilstedeværende devices
som kan give interrupts. 
     
For hver version af PI-1 maskinen (dvs. af basis-programmellet)
fastlægges ved assembleringen 
 
    - en adresse hvor allokering af basis variable starter
      ("FIRSTRAM"). Z80 I-registret, som HW fortolker som en pegepind
      til en tabel af entry points for interrupt service rutiner,
      initialiseres til FIRSTRAM/256.  
       
    - største og mindste interrupt vektor værdi, dvs. afgrænsningen af
      den tabel I-registret peger på. 
       
    - hvilke interrupt-prologer som findes. Tilstedeværelsen af
      interrupt-prolog i gør det muligt at udføre CHANNEL-statement og
      WaitI på vektor i uden bruger-defineret (assemblerkodet)
      interrupt service rutine. 
       
             Som hovedregel foregår den initialisering af devices, som
bestemmer hvilke(n) interrupt vektor værdi(er) hvert device
genererer, i basisprogrammellet ved opstart. 
     \f

    2_._ _I_n_t_e_r_r_u_p_t_e_n_d_e_ _d_e_v_i_c_e_s_ 
     
    - SIO/lp   (lp står line & printer) findes på RC700 og alle RC850
               modeller. 
    - PIO      findes på RC700 
    - SIO/kc   (kc står for keyboard & CIRCUIT) findes på alle RC850
           modeller. 
- CTC      findes på RC700 og alle RC850 modeller. 
    - CTC35    findes på RC850 med 3500 i/o interface. 
            
             3_._ _T_i_l_d_e_l_i_n_g_ _a_f_ _i_n_t_e_r_r_u_p_t_ _v_e_k_t_o_r_ _v_æ_r_d_i_e_r_ 
 
    (hexadecimale værdier) 
    0, 2, 4, 6:        CTC, henholdsvis kanal 0, 1, 2 og 3 (0 og 2
                       benyttes ikke på RC850) 
    8, A:              PIO (kun RC700) 
    C:                 ghost (kun RC850) 
    10, 12, 14, 16:    SIO/lp Kanal B 
    18, 1A, 1C, 1E:    SIO/lp Kanal A 
    20, 22, 24, 26:    SIO/kc Kanal B (kun RC850) 
    28, 2A, 2C, 2E:    SIO/kc Kanal A (kun RC850) 
    30, 32, 34, 36:    CTC35, henholdsvis kanal 0, 1, 2 og 3 (kun
                       RC850 med 3500 i/o interface) 
                        

             4_._ _I_n_t_e_r_r_u_p_t_ _v_e_k_t_o_r_ _i_n_t_e_r_v_a_l_l_e_r_ _f_o_r_ _f_o_r_s_k_e_l_l_i_g_e_ _v_e_r_s_i_o_n_e_r_ 
                        
    I parentes nævnes de værdier som er til rådighed for SW
    interrupts: 
RC700:               0-1E (C, E) 
RC850 generelt:      4-2E (8, A, E) 
RC850 med 3500 i/o:  4-36 (8, A, E) 
 \f

p_                                                               EL 810226                /1
m_ 
p_                                   RC700        RC850
m_ 
               Memory Requirements for RC700/RC850 programs. 
 
 \f

    The following table lists the memory requirements of a number of
    Z80 assembler coded programs for RC700 and RC850.  
     
    The requirements are given as numbers of bytes (decimal). Notice
    that all this information is subject to minor changes. 
     
                                      code   data 
PI-1 basic software (RC850 version)   2453    331 
RC850 display driver                   832    155 
    Refresh RAM original (RC850)                 4096 
RC850 keyboard driver                  741    190 
NVM routines (RC850)                   258      4 
V.24 asynch. line driver              1495    220 
    V.24 printer driver                    734     99 
    PI-1 interpreter                      3584 
    RC850 selftest program                 309 
    RC850 CIRCUIT driver                  1313    147 
     \f

p_                                                               EL 810304                /2
m_ 
p_                                   RC700        RC850
m_ 
               Exception codes. 
 
 \f

              The exception codes which are generated by PI-1 basic software or
by the PI-1 interpreter are listed below. The codes between 0 and
2F are the same as those generated by the RC3502. 
 
 
 
C_o_d_e_ _(_h_e_x_a_d_e_c_i_m_a_l_)_ _ _ _M_e_a_n_i_n_g_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1                    signal: reference = NIL 
5                    nil message pointer
B                    arithmetic exception 
C                    index exception 
10                   stack overflow 
11                   range exception 
13                   push: first param = NIL 
14                   push: first param not empty 
17                   pop:  first param <' NIL 
18                   pop:  second param = NIL 
1D                   lock: size error 
1F                   pool: no memory 
22                   start: shadow = NIL 
24                   illegal switch in case construction 
25                   upper limit in call of succ 
26                   lower limit in call of pred 
30                   wait: reference <' NIL 
31                   alloc: reference <' NIL 
32                   reservech: reference <' NIL 
33                   release: reference = NIL 
34                   semaphore underflow (more than 128 waiting  
                     incarnations) 
35                   semaphore overflow (more than 127 queued 
                     messages) 
36                   channel-statement: reference = NIL or message
                     not channel message 
 \f

C_o_d_e_ _(_h_e_x_a_d_e_c_i_m_a_l_)_ _ _ _M_e_a_n_i_n_g_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
37                   link: process already linked to name 
38                   create: shadow = NIL 
39                   create: no process linked to name 
3A                   set exception: adjust 
3B                   reference not NIL at end of lock-statement 
 
 
Exception codes 3C-7F are reserved for basic system extensions, in
particular DISTMON. \f

p_                                       BA 830606               BA 840104                /8
m_ 
                         RC8000      EXT
   
m_m_              RC8000 Basic Software Documentation List for Current Class A, B 
p_p_              and C Packages 
 
  RCSL No/RC Inf. Note 
      \f

                  * An asterisk indicates new or changed items. 
       
A S_W_8_0_0_1_/_1_ _B_A_S_I_S_ _S_Y_S_T_E_M_ _P_A_C_K_A_G_E_,_ _V_E_R_S_I_O_N_ _1_           DOC. ORDER NO: SDO 002 
* 31-D   686 Monitor Part 1 System Design 
  31-D   679 RC8000 Monitor, Part 2 
  31-D   478 RC8000 Monitor, Part 3, Def. of External Processes 
  31-D   539 Backing Storage Area Process 
  31-D   542 Cassette Tape Process 
  31-D   528 Disc Process 
  31-D   546 Disc Process (RC36xx) 
  31-D   543 Flexible Disc Process 
  31-D   523 FPA Main Process 
  31-D   530 Interval Clock Process 
  31-D   536 Line Printer Process 
  31-D   540 Magnetic Tape Process (7 track) 
  31-D   533 Magnetic Tape Process (9 track) 
  31-D   534 Paper Tape Punch Process 
  31-D   535 Paper Tape Reader Process 
  31-D   537 Punched Card Reader Process 
  31-D   580 Terminal Process 
  31-D   544 Conversion Tables 
  31-D   624 Errorlog Process 
  31-D   555 RC8000 Host Process 
  31-D   643 Operating System s, Basis System Version 1, Ref. Man. 
  43-RI 1059 RC-NET RC3600 Device Controller/Terminal, Op. Guide/User's G. 
  HSI 810618 Autoload of Monitor Release 7.0 
  HSI 820315 Changes in Monitor Release 8.0 
  HØ  830215 DC1/DC3 Protocol on Asynchronous Terminals 
   \f

A S_W_8_0_0_1_/_2_ _B_A_S_I_S_ _S_Y_S_T_E_M_ _P_A_C_K_A_G_E_,_ _V_E_R_S_I_O_N_ _2_           DOC. ORDER NO: SDO 104 
* 31-D   686 Monitor Part 1 System Design 
  31-D   697 RC8000 Monitor, Part 2, Reference Manual 
* TSH 830824 Corrections to RCSL No 31-D697: RC8000 Monitor, Part 2,
             Reference Manual 
  31-D   478 RC8000 Monitor, Part 3, Def. of External Processes 
  31-D   539 Backing Storage Area Process 
  31-D   542 Cassette Tape Process 
  31-D   528 Disc Process 
  31-D   546 Disc Process (RC36xx) 
  31-D   543 Flexible Disc Process 
  31-D   523 FPA Main Process 
  31-D   530 Interval Clock Process 
  31-D   536 Line Printer Process 
* LBJ 830711 RC8000 Lineprinter Process, SW8001/2 
  31-D   540 Magnetic Tape Process (7 track) 
  31-D   533 Magnetic Tape Process (9 track) 
  31-D   534 Paper Tape Punch Process 
  31-D   535 Paper Tape Reader Process 
  31-D   537 Punched Card Reader Process 
* LBJ 830712 RC8000 Terminal Process, SW8001/2 
  31-D   544 Conversion Tables 
  31-D   690 Operating System s, Basis System Version 2, Ref. Man. 
  43-RI 1059 RC-NET RC3600 Device Controller/Terminal, Op. Guide/User's G. 
  31-D   624 Errorlog Process 
  31-D   555 RC8000 Host Process 
  HSI 810618 Autoload of Monitor Release 7.0 
  HØ  830215 DC1/DC3 Protocol on Asynchronous Terminals 
   
A S_W_8_0_1_0_/_1_ _S_Y_S_T_E_M_ _U_T_I_L_I_T_Y_ _P_A_C_K_A_G_E_                    DOC. ORDER NO: SDO 005 
  U_t_i_l_i_t_y_ _S_u_b_p_a_c_k_a_g_e_: 
  31-D   676 System 3 Utility Programs Part one 
* 31-D   607 System 3 Utility Programs Part two 
   \f

  M_a_i_n_t_e_n_a_n_c_e_ _S_u_b_p_a_c_k_a_g_e_: 
  31-D   471 AUTOLOAD 
  31-D   657 Base 
  31-D   376 Changekit 
  55-D    70 Checkio 
  31-D   295 Clean 
  31-D   557 Createlink, lookuplink, lookupdev 
  31-D   549 Disccopy, kiton, kitoff, kitlabel, kitname 
  FGS 821001 Disccopy Release 12.1 for Use with Monitor Release 8.0 
  31-D   280 Do 
  31-D   660 Fpastat 
  31-D   659 FPASTAT, DISCSTAT Utility Programs 
  31-D   382 Global 
  31-D   658 Initamx 
  31-D   465 Linkcentral 
  31-D   578 Montest 
  31-D   661 Movedump 
  31-D   570 Slicelist 
* 31-D   707 Basemove 
   
      A S_W_8_1_0_0_/_1_ _M_I_P_S_/_T_S_ _P_A_C_K_A_G_E_                          DOC. ORDER NO: SDO 031  
  31-D   662 Swopping Online System (SOS) 
  FB  820302 Supplement to 31-D662, Swopping Online System (SOS) 
  31-D   689 Terminal Access Module (TEM) 
  31-D   688 PRIMO  
  31-D   585 MIPS/TS OPERATING GUIDE 
  LKN 790410 Binding of Terminals when Running MIPS/TS 
   \f

A S_W_8_1_0_1_/_1_ _B_O_S_S_ _P_A_C_K_A_G_E_                              DOC. ORDER NO: SDO 017 
  42-i  1265 BOSS 2, User's Manual 
      JMA 830214 Corrections to RCSL 42-i1265: BOSS 2 User's Manual 
  31-D   680 BOSS, Operating Guide 
* JMA 830216 Correction to RCSL No 31-D680: BOSS, Operating Guide 
  31-D   610 Parent Messages in RC8000 
  TSH 830216 Corrections to RCSL 31-D610: Parent Messages in RC8000 
  31-D   628 BOSS 2, Installation and Maintenance 
  JMA 830213 Corrections to RCSL 31-D628: BOSS 2, Installation and
             Maintenance 
  31-D   673 BOSS, Basic Internal Formats 
  JMA 830215 Corrections to RCSL 31-D673: BOSS, Basic Internal Formats 
 
C S_W_8_1_0_2_/_1_ _D_A_O_S_ _S_Y_S_T_E_M_ _P_A_C_K_A_G_E_                       DOC. ORDER NO: SDO 093 
* 52-AA 1193 Directory Assistance Operating System DAOS 
 
A S_W_8_2_0_0_/_1_ _D_A_T_A_ _B_A_S_E_ _P_A_C_K_A_G_E_                         DOC. ORDER NO: SDO 016 
  42-i   766 Introduction to CF-system 
  28-D     5 Connected Files System 
  31-D   583 Corrections to RCSL No 28-D 5 CF-System 
  EAH 800314 Interpretation of the Alarm Printing from cf-system 
   
A S_W_8_2_0_1_/_1_ _B_A_C_K_I_N_G_ _S_T_O_R_A_G_E_ _P_A_C_K_A_G_E_                   DOC. ORDER NO: SDO 055 
      31-D   602 RC8000 SQ-system 
  31-D   562 RC8000 Backing Storage Area Sorting 
  31-D   600 RC8000 Indexed Sequential Files (ISQ) 
  31-D   634 Corrections to 31-D600 
  31-D   601 Extensions to the RC8000 ISQ System 
  31-D   635 Corrections to 31-D601 
  CAP 790802 Transformation of ISQ and CF Master Files 
  EAH 810401 Handling of ISQ-files in a Coroutine System 
      FB  820708 Procedure Removeupdi 
  FB  821018 ISQ Procedures and Zone State 
 \f

B S_W_8_2_1_0_/_1_ _M_A_G_-_T_A_P_E_ _F_I_L_E_ _M_A_N_A_G_E_M_E_N_T_ _P_A_C_K_A_G_E_          DOC. ORDER NO: SDO 012 
  31-D   198 Magnetic Tape System MTS 2 
  31-D   228 Heapsort 
   
A S_W_8_2_1_1_/_1_ _F_L_E_X_I_B_L_E_ _D_I_S_C_ _P_A_C_K_A_G_E_                     DOC. ORDER NO: SDO 057 
      31-D   459 Flexible Disc Handling within the Algol System 
  31-D   531 Corrections/Comments to RCSL 31-D 459 
  31-D   596 Utility Programs for Flexible Disc Handling  
   
    B S_W_8_2_1_2_/_1_ _P_L_O_T_T_E_R_ _R_O_U_T_I_N_E_S_ _P_A_C_K_A_G_E_                  DOC. ORDER NO: SDO 030 
  31-D   503 RC8000 Plotting System 
   
                  C S_W_8_2_2_0_/_1_ _M_A_T_H_E_M_A_T_I_C_A_L_-_S_T_A_T_I_S_T_I_C_A_L_ _R_O_U_T_I_N_E_S_ _P_A_C_K_A_G_E_ DOC. ORDER NO: SDO 018 
     55-D    63 Introduction to Math.-Stat. 
  55-D    48 Adapint 
  53-M     3 Besselik 
  53-M     2 Besseljy 
  53-M     8 Beta 
  55-D    60 Decompose, Solve 
  55-D    57 Eberlein 
  31-D     3 FFT 
  31-D   129 FIT 
  55-D    58 Gamma 
  53-M     7 Householder 
  53-M     5 Invertsym 
  55-D    61 Jacobi 
  53-M    18 Minimum 
  53-M     4 Pzero 
  31-D   224 Runge Kutta 
  53-M    17 Solineq 
  53-M     6 Solvesym 
  53-M     1 Zero1 
  53-S     1 Data survey and Appendix 
  53-S     7 Recordinput and Appendix 
   \f

                  B S_W_8_2_2_1_/_1_ _A_L_G_O_L_ _T_E_X_T_ _P_R_O_C_E_D_U_R_E_S_ _P_A_C_K_A_G_E_             DOC. ORDER NO: SDO 059 
  31-D   647 ALGOL Text Procedures, User's Guide 
   
                  C S_W_8_2_3_0_/_1_ _R_O_F_F_ _P_A_C_K_A_G_E_                              DOC. ORDER NO: SDO 081 
  52-AA 1120 ROFF - Tekstbehandling på RC8000 (Danish Language) 
  52-AA 1166 Bigtext on the Qume Printer 
 
B S_W_8_2_3_2_/_1_ _T_T_Y_ _E_M_U_L_A_T_O_R_ _P_A_C_K_A_G_E_                      DOC. ORDER NO: SDO 056 
  31-D   667 Betjening af terminaler tilsluttet RC8000 via TTY Emulator,
             brugervejledning (Danish Language) 
  31-D   683 RC8000 TTY Emulator til IBM 3270 kompatible skærme, instal-
             lations- og betjeningsvejledning (Danish Language) 
   
B S_W_8_2_4_0_/_1_ _A_L_G_O_L_ _C_O_R_O_U_T_I_N_E_ _S_Y_S_T_E_M_ _P_A_C_K_A_G_E_            DOC. ORDER NO: SDO 061 
  31-D   674 ALGOL Coroutine System, User's Guide 
  31-D   666 ALGOL Coroutine System, Testudskrivning, Brugervejledning
             (Danish Language) 
   
A S_W_8_5_0_0_/_1_ _A_L_G_O_L_ _P_A_C_K_A_G_E_                             DOC. ORDER NO: SDO 003 
  42-i  1278 ALGOL8 User's Guide Part 2 
  42-i  1279 ALGOL7 Reference Manual 
  42-i   781 ALGOL7 User's Manual Part 1 
  31-D   581 ALGOL8 
  FGS 821011 ALGOL Programs Communicating with Disc Proc. and Mon. Rel. 8.0 
   
                  A S_W_8_5_0_1_/_1_ _F_O_R_T_R_A_N_ _P_A_C_K_A_G_E_                           DOC. ORDER NO: SDO 008 
  42-i  1205 RC FORTRAN, User's Manual 
   
                  A S_W_8_5_0_1_/_2_ _F_O_R_T_R_A_N_ _P_A_C_K_A_G_E_                           DOC. ORDER NO: SDO 129 
* 42-i  1205 RC FORTRAN, User's Manual 
   
C S_W_8_5_0_3_/_1_ _C_O_B_O_L_ _P_A_C_K_A_G_E_                             DOC. ORDER NO: SDO 039 
  42-i  1002 COBOL Ref. Man. for RC8000 
   
                  C S_W_8_5_0_4_/_1_ _X_F_O_R_T_R_A_N_ _P_A_C_K_A_G_E_                          DOC. ORDER NO: SDO 043 
  31-D   457 XFORTRAN - A Preprocessor to RC FORTRAN 
   \f

                  B S_W_8_5_0_5_/_1_ _P_A_S_C_A_L_                                    DOC. ORDER NO: SDO 062 
  42-i  1786 RC8000 PASCAL, User's Guide 
       
A S_W_8_6_0_0_/_1_ _A_S_S_E_M_B_L_E_R_ _P_A_C_K_A_G_E_                         DOC. ORDER NO: SDO 009 
  42-i   785 RC Slang Assembler, Programming Guide 
  31-D   199 Run Time Organization of Algol Programs 
  31-D   210 Examples of Code Procedures 
  31-D   379 System 3 Utility Programs Part Three  
   
                  B S_W_8_7_0_0_/_1_ _I_B_M_ _2_7_8_0_ _E_M_U_L_A_T_O_R_ _P_A_C_K_A_G_E_                 DOC. ORDER NO: SDO 048 
  43-GL11805 RC8000 as IBM 2780 Terminal, User's Guide 
  43-GL11806 RC8000 as IBM 2780 Terminal, Reference Manual 
* BIJ 831007 Corrections to RCSL No 43-GL11806: RC8000 as IBM 2780 Terminal,
             Reference Manual 
   
B S_W_8_7_0_1_/_1_ _D_I_S_C_-_D_I_S_C_ _F_I_L_E_ _R_O_U_T_E_R_ _P_A_C_K_A_G_E_             DOC. ORDER NO: SDO 046 
  F_D_L_C_ _S_u_b_p_a_c_k_a_g_e_: 
  KC 821201 Disc-disc File Router Package 
  31-D   592 FDLC-FPA Data Link Control, User's Manual 
  31-D   605 Corrections to RCSL No 31-D592 
  43-GL 7810 FDLC-FPA Data Link Control, Reference Manual 
  D_D_F_R_ _S_u_b_p_a_c_k_a_g_e_: 
  31-D   579 Transfer Discfile (xdif) Utility Program and Disc to Disc 
             File Router, Reference Manual 
  31-D   625 Remotejob Utility Program 
   
   B S_W_8_7_0_2_/_1_ _I_B_M_ _3_2_7_0_ _T_E_R_M_I_N_A_L_ _H_A_N_D_L_E_R_ _P_A_C_K_A_G_E_ _V_E_R_S_._ _1_ DOC. ORDER NO: SDO 040 
  52-AA  933 Format 8000 on the Stansaab Alfaskob 3500 Data Terminal System 
  52-AA 1037 IBM 3270 Terminal Handler 
  52-AA  935 IBM 3270 Terminal Handler, System Messages 
  52-AA  936 IBM 3270 Terminal Handler, The Select Mechanism 
   
A S_W_8_7_0_2_/_2_ _I_B_M_ _3_2_7_0_ _T_E_R_M_I_N_A_L_ _H_A_N_D_L_E_R_ _P_A_C_K_A_G_E_ _V_E_R_S_._ _2_ DOC. ORDER NO: SDO 084 
  31-D   692 IBM 3270 Terminal Handler, General Description 
  31-D   693 IBM 3270 Terminal Handler, User's Guide 
  31-D   694 IBM 3270 Terminal Handler, System Messages 
  31-D   695 IBM 3270 Terminal Handler, Reference Manual 
   \f

A S_W_8_7_1_0_/_1_ _R_C_N_E_T_ _D_e_v_i_c_e_ _C_o_n_t_r_o_l_l_e_r_                   DOC. ORDER NO: SDO 120 
* 31-D   714 RC8000 on RCNET: A General Description 
 
A S_W_8_7_1_1_/_1_ _R_C_8_0_0_0_ _S_H_I_P_P_I_N_G_                           DOC. ORDER NO: SDO 108 
* 31-D   701 RC8000 Shipping, General Information 
* 31-D   702 RC8000 Shipping, User's Guide 
* 31-D   703 RC8000 Shipping, Operating Guide/Installation Guide 
* 31-D   704 RC8000 Host Service, Reference Manual 
   
A S_W_8_7_1_2_/_1_ _R_C_N_E_T_ _T_r_a_n_s_i_t_ _N_o_d_e_                        DOC. ORDER NO: SDO 121 
* 31-D   714 RC8000 on RCNET: A General Description 
 
A S_W_8_7_1_3_/_1_ _A_C_P_8_0_0_0_                                   DOC. ORDER NO: SDO 118 
* 31-D   715 Asynkron Kommunikations Pakke (ACP8000), Generel Beskrivelse
             (Danish language) 
* 31-D   712 Asynchronous Communication Package (ACP8000), Installation
             Guide/Operating Guide 
* 31-D   713 Asynkron Kommunikations Pakke (ACP8000), Brugervejledning
             (Danish language) 
 
A S_W_8_7_2_0_/_1_ _R_C_8_5_5_ _D_A_T_E_X_ _I_B_M_ _3_2_7_0_ _B_S_C_ _P_A_C_K_A_G_E_          DOC. ORDER NO: SDO 100 
  31-D   699 IBM 3270 Terminal Handler (X.21), General Description 
  31-D   693 IBM 3270 Terminal Handler, User's Guide 
  31-D   694 IBM 3270 Terminal Handler, System Messages 
  31-D   695 IBM 3270 Terminal Handler, Reference Manual 
   
B S_W_8_7_3_0_/_1_ _R_O_C_S_                                      DOC. ORDER NO: SDO 124 
* 43-GL10936 ROCS/3270 Operator's Reference Manual 
* BES 831107 Systemvalg fra skærm i ROCS-systemet (Danish language) 
 \f

p_                                                               POLM810803               /1
m_ 
p_                     RC8000      INT
m_ 
               Documentation List for the IBM 3270 Terminal Handler, Package SW8702/3.1
 
 \f

                    External Documentation: 
      1) Format 8000 on the Stansaab Alfaskop 3500 Data Terminal System
         General Description, Revision 2, 
         RCSL No 52-AA933 (substitutes RCSL No 52-AA866) 
          
      2) IBM 3270 Terminal Handler, Definition of the ISO<->EBCDIC
         Conversion Table 
         RCSL No 52-AA1037 
          
      3) IBM 3270 Terminal Handler, System Messages, Revision 2,  
         RCSL No 52-AA935 (substitutes RCSL No 52-AA904) 
          
      4) IBM 3270 Terminal Handler, The Select Mechanism, User's Manual,
         RCSL No 52-AA936 
   
  Internal Documentation: 
      5) FORMAT 8000 Control Unit Simulator, Reference Manual, 
         Revision 2.0, 
         RCSL No 52-AA934 (substitutes RCSL No 52-AA879) 
          
      6) Focus, IBM 3270 Terminal Handler, System Generation, 
         Revision 3, 
         RCSL No 52-AA1042 (substitutes RCSL No 52-AA932) 
          
      7) IBM 3270 Terminal Handler, System Generation for the M3270,
         Master Module, 
         RCSL No 52-AA913 
          
      8) STANSAAB ALFASKOP 3500 Data Terminal System, 
         Indbyggede servicefunktioner i remoteskærme, 
         790418/LG (ikke RCSL-registreret) 
          
      9) IBM 3270 Information Display System, Component Description, 
         IBM GA 27-2749 (ikke RCSL-registreret) 
          
     10) IBM 3270 Terminal Handler, Generation of the ISO<->EBCDIC
         Conversion Table 
         RCSL No 52-AA1041 
          \f

p_                                                               EL 810928                /3
m_ 
p_                                                RC855
m_ 
               RC855 Bootdisk Manager 
 
 \f

                  1_._ _I_n_d_l_e_d_n_i_n_g_ 
     
"RC855 Bootdisk Manager" er et utility program som anvendes ved
håndtering af RC855 bootstrap floppy disks. En bootstrap floppy
disk indeholder 
- et "spor 0" program som loades af PROM-bootstraploaderen
  (BOOT55) ved power-up eller reset, 
- et katalog med beskrivelse af en program-menu, 
- programmerne i menuen i form af binære images. 
 
Der kan maximalt være 16 images på n bootdisk, som skal være dual
sided, double density. 
 
I katalogbeskrivelsen af hvert program-image indgår 
- programmets navn i menuen (max. 28 tegn), 
- et valgtegn, som anvendes til at vælge programmet fra menuen, 
- eventuelt autoload-attribut som indikerer at pågældende image
  skal loades automatisk uden udskrivning af menu. 
 
 
2_._ _"_S_p_o_r_ _0_"_ _p_r_o_g_r_a_m_m_e_t_s_ _f_u_n_k_t_i_o_n_ 
 
Først undersøges om der findes et image med autoload-attribut. I
så fald loades dette (hvis der er flere, loades det første).
Ellers udskrives menuen, dvs. valgtegn og navn for hvert image, og
der loades et image efter indtastning af valgtegn. 
 
 
3_._ _F_u_n_k_t_i_o_n_e_r_ _i_ _R_C_8_5_5_ _B_o_o_t_d_i_s_k_ _M_a_n_a_g_e_r_ 
 
Programmet kører på RC850 og fungerer interaktivt. Indtastede
kommandoer kan forkortes vilkårligt, kun t bogstav af kommando-
navnet er nødvendigt. 
 
Program images som skal skrives på bootdisken forudsættes overført
i tekhex format via RC850 terminalens V.24 linje, normalt ved an-
vendelse af "tekmove" utility programmet på RC8000. 
 \f

                  I det følgende beskrives de enkelte kommandoer: 
     
 
3_._1_ _I_(_n_i_t_i_a_l_i_s_e_)_ 
 
Kataloget initialiseres som værende tomt og "spor 0" programmet
indlæses. 
 
 
3_._2_ _T_(_e_k_m_o_v_e_)_ _<_v_a_l_g_t_e_g_n_>_ _<_p_r_o_g_r_a_m_ _n_a_v_n_>_ 
 
Et program image indlæses og beskrives i kataloget med <valgtegn>
og <program navn>. 
 
 
3_._3_ _M_(_e_n_u_)_ 
 
Katalogets indhold udskrives på menu-form. 
 
 
3_._4_ _D_(_e_l_e_t_e_)_ _<_v_a_l_g_t_e_g_n_>_ 
 
Hvis der findes en katalogindgang med <valgtegn> markeres den som
slettet og kan derefter genbruges. 
 
 
3_._5_ _A_(_u_t_o_l_o_a_d_)_ _<_v_a_l_g_t_e_g_n_>_ 
 
Hvis der findes en katalogindgang med <valgtegn> sættes dens auto-
load-attribut. 
 
 
3_._6_ _N_(_o_r_m_a_l_)_ _<_v_a_l_g_t_e_g_n_>_ 
 
Hvis der findes en katalogindgang med <valgtegn> slettes dens
autoload-attribut. 
 
 \f

                  3_._7_ _S_(_i_z_e_)_ _<_v_a_l_g_t_e_g_n_>_ 
     
Størrelsen af det indikerede program image udskrives. 
 
 
3_._8_ _E_(_x_a_m_i_n_e_)_ _<_v_a_l_g_t_e_g_n_>_ _<_h_e_x_v_a_l_>_ 
 
Byte nummer <hexval> i det indikerede program image udskrives
hexadecimalt. 
 
 
3_._9_ _C_(_h_a_n_g_e_)_ _<_v_a_l_g_t_e_g_n_>_ _<_h_e_x_v_a_l_1_>_ _<_h_e_x_v_a_l_2_>_ 
 
Værdien af byte nummer <hexval1> i det indikerede program image
ændres til <hexval2>. 
 
 
3_._1_0_ _H_(_e_l_p_)_ 
 
Liste over gyldige kommandoer udskrives. 
 
 \f

                  This RC Information Note contains corrections to "BOSS2, User's
Manual" (Second Edition, August 1979, RCSL No 42-i1265). 
 
With these corrections included, the manual corresponds to the
Software Package SW8101/1/18.0: BOSS Release 18.0. 
 
1_._ _(_N_E_W_)_ _P_a_g_e_ _4_8_: 
 
verify: the command name may be abbreviated to 'v' (but not 've'
        or 'ver'). 
 
2_._ _P_a_g_e_ _5_6_: 
 
The terms <jobname> and <username> are not explained. 
     <username> is the username as used at login and in the job
                specification, e.g. "jma". 
     <jobname>  is a <username> followed <userindex> as defined at
                login or in the job specification, e.g. "jma0". 
 
3_._ _(_N_E_W_)_ _P_a_g_e_ _5_6_: 
 
The syntax for the display command is: 
 
M_m_m_                                1 
P_p_p_          convert 
M_m_m_                            1 
          <jobname>  claim   
P_p_p_                            0 
display   login 
          idle 
M_m_m_          dead 
P_p_p_                                0 
 
4_._ _P_a_g_e_ _5_6_: 
 
Last 4 lines: 
Replace <username> with <jobname>. 
 \f

«eof»