⟦afaaf696e⟧

RcTekst


╱04002d4e0c0006000000000301483100000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱

════════════════════════════════════════════════════════════════════════
↓
                                  i↲
↲
↲
↲
↲
┆a1┆TABLE OF CONTENTS                                                  PAGE↲
↲
1.  INSTALLATION GUIDE .............................................  1↲
    1.1  The Installation ..........................................  1↲
    1.2  Initiate Users ............................................  3↲
↲
2.  MAINTENANCE GUIDE ..............................................  4↲
    2.1 System overview ............................................  4↲
    2.2 Configuration parameters ...................................  5↲
    2.3 Terminal handling ..........................................  5↲
    2.4 Files ......................................................  6↲
    2.5 System limits ..............................................  7↲
    2.6 System Crash ...............................................  7↲
↲
3.  APPENDIXES .....................................................  9↲
    3.1 Appendix A .................................................  9↲
    3.2 Appendix B ................................................. 10↲
    3.3 Appendix C ................................................. 11↲
↲

════════════════════════════════════════════════════════════════════════
↓
╞	╞	╞	╞	ii↲
↲

════════════════════════════════════════════════════════════════════════
↓

════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆                              ┆0b┆↲
↲
┆a1┆1. INSTALLATION GUIDE.┆e1┆↲
↲
┆a1┆1.1 The Installation.┆e1┆↲
↲
            ┆84┆You have just received RC COMPUTER's APPOINTMENT MANGEMENT ↓
┆19┆┆8c┆┄┄SYSTEM  (A.M.S) on  a 5 1/4 "  diskette.↲
↲
To install the system please follow the next steps carefully. The whole ↓
procedure should take less than five minutes.↲
(The ┆a1┆underlined┆e1┆ text are your entries on the keyboard. <cr> = carriage ↓
return . )↲
↲
1. Login as  superuser.↲
   i.e. :↲
   login: ┆a1┆root<cr>┆e1┆↲
   Password:       (The superuser password - No echo, remember <cr>)↲
   ↲
   ( You might be asked to set the date and time here.)↲
↲
   Now the promt: 1 #  will appear.↲
   (On danish terminals - ASCII will promt: 1 numbersign.)↲
↲
2. Run UNIPLEX.  ↓
   i.e. :↲
   1 # ┆a1┆/usr/uniplex/uniplex<cr>┆e1┆↲
↲
   After some seconds the UNIPLEX main menu will appear on the screen.↲
↲
3. Select the Appointment Mangement System.↲
   i.e. :↲
   type: ┆e1┆┆a1┆a┆e1┆↓
↲
4. ┆84┆If you haven't done it yet now is the time to insert the master ↓
┆19┆┆83┆┄┄diskette in the floppy drive. Remember to close the door.↲
↲
5. ┆84┆After you have typed the 'a', a messages will appear on the screen ↓
┆19┆┆83┆┄┄that tells you what to do next. That is : ↲
   type : ┆a1┆i┆e1┆↲
   to select the installation procedure.↲

════════════════════════════════════════════════════════════════════════
↓
↲
6. ┆84┆Within a couple of minutes the following text ( enclosed in ===.. ↓
┆19┆┆83┆┄┄lines )  should appear on your screen:↲
↲
============================================================================↲
↲
↲
                 Installing procedure started↲
↲
                 Please be patient for a couple of minutes.↲
↲
                 The diskette is now successfully copied!↲
↲
ALL CALENDARS EMPTY !!↲
ONLY SECRETARY KNOWN IS: initsec↲
↲
**************** Installation  procedure  finished ! ****************↲
↲
**** ATTENTION PLEASE!! ****↲
↲
When you return to UNIPLEX  you will still be in the installation↲
part of the menu system.↲
Please hit ESC to get back to the main menu↲
↲
↲
↲
↲
↲
Press any key to continue:↲
==========================================================================↲
↲
↲
    In any case don't do anything before the line:↲
    "Pre┆84┆┆84┆ss any key to continue:" appears at the bottom of the screen.↲
↲
7.  ┆84┆After pressing a key (f.ex. spacebar) you will get the installation ↓
┆19┆┆84┆┄┄screen back again - but the system is already installed - so just ↓
┆19┆┆84┆┄┄press the ┆a1┆ESC┆e1┆ key - and your are back in the UNIPLEX main menu.↲

════════════════════════════════════════════════════════════════════════
↓
┆a1┆1.2 Initiate Users.┆e1┆↲
↲
The installation is now completed - but at this stage it is a good idea ↓
to convince yourself that it's really running and - last but not least - ↓
to initiate some secretaries! That is: Give the A.M.S. the ↓
initials/names of the secretaries that are going to work with the ↓
system.↲
↲
To do this select the A.M.S. from the UNIPLEX main menu.↲
i.e. : type ┆a1┆a┆e1┆ .↲
After some seconds you will get the login screen of the A.M.S. where the ↓
lines in the middle of the screen look like this:↲
↲
          Write your name or initials please:┆a1┆.┆e1┆.........↲
          =============================================↲
↲
To get into the system you have to type in the "name" : ┆a1┆initsec<cr>┆e1┆↲
Explanation: "initsec" is the only "secretary" known to the system at ↓
this stage and the ┆a1┆only┆e1┆ way to get into the system.↲
After you typed   initsec  you will get the A.M.S. main menu on the ↓
screen. Choose the ┆a1┆Initiate┆e1┆ entry . (i.e.: type ┆a1┆i┆e1┆ ) ↓
Now you get the initiate form on the screen.↲
Choose ┆a1┆$┆e1┆ to initiate a secretary. (i.e.: type ┆a1┆$┆e1┆ )↲
The cursor jumps to the $ecretary field, where you can enter the ↓
initials/name of a secretary followed by <cr>.↲
┆b0┆Att.┆f0┆: No blanks in the name - use '_' if nescesary.↲
      ( You can backspace with <--  or the DEL key )↲
↲
You automatically returned to the A.M.S main menu.↲
↲
The above step can of course be repeated.↲
To get back to UNIPLEX press the ESC key in the A.M.S. main menu↲
↲
Next time someone want to work with the A.M.S. the initiated names can ↓
be used to get into the system - instead of "initsec" .↲
↲
For further information on the A.M.S. read the :User guide to the A.M.S.  ↓

════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆2. MAINTENANCE GUIDE.┆e1┆↲
↲
┆a1┆2.1  System overview.┆e1┆↲
↲
┆a1┆Abstract:┆e1┆ ┆84┆This paper is aimed at the system manager. It describes ↓
┆19┆┆8a┆┄┄various parts of the APPOINTMENT MANGEMENT SYSTEM.↲
┆19┆┆8a┆┄┄(Hereafter: AMS)  such as files, terminals, the handling of ↓
┆19┆┆8a┆┄┄abnormal system behaviour, and configuration parameters.↲
↲
┆a1┆Static:┆e1┆ ┆84┆All programs, files etc. necessary to run the AMS are in the ↓
┆19┆┆88┆┄┄directory: ┆a1┆/usr/calsys┆e1┆.  (See App. C ). The main program is ↓
┆19┆┆88┆┄┄called: ┆a1┆appoint┆e1┆. A link to this exsists from: ┆a1┆/usr/bin/appoint┆e1┆.  ↓
┆19┆┆88┆┄┄(See: User's guide , introduction.)↲
┆a1┆Dynamic┆e1┆:┆84┆ A typical session with the AMS is described below.↲
         1. The program (code) ┆a1┆appoint┆e1┆ is loaded into memory.↲
         2. It starts executing.↲
            a. Initialisation phase.↲
               Writes: Please be patient....  on the screen.↲
               ┆84┆Read the files: appconfig.d , packtext.d , term??.cod , ↓
┆19┆┆8f┆┄┄term??.str , init.d , sub.d , day.d  and daymark.d .↲
╞	╞	 Create the files: POLFIL , DELFIL , NITFIL.↲
╞	╞	 Create semaphores.↲
╞	╞	 ( If first process running the AMS.)↲
╞	╞	 The screen login appears.↲
╞	        b. User phase.↲
╞	╞	 After filling in the initials the main menu appears.↲
╞	╞	 ┆84┆During the user phase read and write takes place on the ↓
┆19┆┆8f┆┄┄following files: resfil.d , POLFIL , DELFIL , NITFIL.  In ↓
┆19┆┆8f┆┄┄the case of a hard copy the AMS writes to a file ( either ↓
┆19┆┆8f┆┄┄respr(PID) or calpr(PID) ). This file is then printed on ↓
┆19┆┆8f┆┄┄the system printer by the shell script ┆a1┆rcprint┆e1┆.↲
            c. Logout fase.↲
╞	╞	 ┆84┆If the logout process is the only (last) running the AMS ↓
┆19┆┆8f┆┄┄it will overwrite - update - the files  init.d , sub.d , ↓
┆19┆┆8f┆┄┄day.d  and daymark.d . If not it just tells the other ↓
┆19┆┆8f┆┄┄process(es) still running that it logged out (By writing ↓
┆19┆┆8f┆┄┄a 'b' in POLFIL).↲

════════════════════════════════════════════════════════════════════════
↓
┆a1┆2.2 Configuration parameters┆e1┆↲
There are only two parameters for you to set in the file ┆a1┆appconfig.d┆e1┆ . ↓
The ┆a1┆first┆e1┆ letter in appconfig.d tells the AMS if a printer is connected ↓
- or rather - if it is allowed to use the system printer.↲
If the letter is ┆b0┆┆a1┆P┆e1┆┆f0┆  the printer is connected - anything else will ↓
┆19┆┄┆81┆┄prohibit the AMS to print anything!.↲
The ┆a1┆second┆e1┆ letter is only meaningfull if the first is ┆a1┆┆b0┆P┆f0┆┆e1┆ . If the second ↓
┆19┆┄┆81┆┄letter is ┆b0┆┆a1┆S┆e1┆┆f0┆ (For ┆b0┆┆a1┆S┆e1┆┆f0┆ilent) the reservations/updates are ┆a1┆not┆e1┆ automatically ↓
┆19┆┄┆83┆┄printed - anything different, and they are.↲
On delivery the content of appconfig.d is:↲
┆b0┆┆a1┆PT┆e1┆┆f0┆  i.e. printer connected and autoprint of reservations/updates.↲
↲
↲
┆a1┆2.3 Terminal handling.┆e1┆↲
The terminal mode when running the AMS is:↲
-echo , cbreak , nl , brkc=' B' .↲
(See: XENIX Programmer's Manual  STTY(1) ).↲
Interrupts and quits are ignored (See: SIGNAL(2) ).↲
The terminals supported have the following keys↲
(Described in /etc/termcap/)  :↲
╞	┆b0┆qr┆f0┆   (RC855  standard.)↲
╞	┆b0┆qq┆f0┆   (RC822 .)↲
╞	┆b0┆qu┆f0┆   (QVT102  QUME. )↲
(The AMS doesn't use the termcap descriptions directly - See files.)↲
↲
If the screen layout is faulty there is a disagreement between your TERM ↓
variable and the actual type of terminal.↲
(See: CSH(1) page 14       ┆a1┆setenv┆e1┆     - running CSH .↲
      SH(1)  page  2    ┆a1┆name┆e1┆ = ┆a1┆value┆e1┆  - running SHell. )↲
↲

════════════════════════════════════════════════════════════════════════
↓
┆a1┆2.4 Files┆e1┆↲
(See App. C. for overview.)↲
All files necessary to run the AMS are in the directory: ┆a1┆/usr/calsys┆e1┆.↲
The executable code for the AMS is on the file ┆a1┆appoint┆e1┆.↲
It reads (only) from the files:↲
┆a1┆appconfig.d┆e1┆╞	( Printer flags. See configuration.)↲
┆a1┆packtext.d┆e1┆    ( Various display texts a.o.)↲
┆a1┆term??.cod┆e1┆  and↲
┆a1┆term??.str┆e1┆    ┆84┆( ?? is the system variable TERM (f.ex. qr ) - which is ↓
┆19┆┆8e┆┄┄set on login in .profile (SHell) or  .cshrc (C-SHell) and ↓
┆19┆┆8e┆┄┄should describe the terminal you are working on. The ↓
┆19┆┆8e┆┄┄terminals supported are: qr , qq  , qu. The  term......  ↓
┆19┆┆8e┆┄┄files contain the form layouts, field descriptions ↓
┆19┆┆8e┆┄┄etc.)↲
All data entered into the AMS are kept in the following files (Open for ↓
read and write.)↲
┆a1┆daymark.d┆e1┆╞	( Common marked days.)↲
┆a1┆resfil.d┆e1┆╞	( Reservation data.)↲
┆a1┆init.d┆e1┆╞	( Initials/rooms/secretary  data.)↲
┆a1┆sub.d┆e1┆╞	( Subjects data.)↲
┆a1┆day.d┆e1┆╞	( Dates - reservation  data.)↲
↲
The above files, plus the file  ┆a1┆rcprint┆e1┆ (Shell  script for printing) ↓
must be present and are used during normal system use.↲
In addition there are some temporary files, namely:↲
┆a1┆POLFIL, DELFIL, NITFIL┆a1┆┆e1┆  all of which are used for multi-user ↓
communication - and as temporary files for printing:↲
┆a1┆calpr<number>┆e1┆ and ┆a1┆ respr<number>┆e1┆.↲
The remaining files are mainly concerned with initialisation of the ↓
system.↲
These are:↲
┆a1┆emptyapp┆e1┆╞	┆84┆- ┆84┆Shell script , which sets up an ┆a1┆empty┆e1┆ AMS. It uses the ↓
┆19┆┆90┆┄┄program ┆a1┆dores┆e1┆ - which creates the file ┆a1┆resfil.d┆e1┆ - ↓
┆19┆┆90┆┄┄consisting of 500 records of each 256 bytes, and the ↓
┆19┆┆90┆┄┄files ┆a1┆dumd.d┆e1┆ , ┆a1┆dumi.d┆e1┆ , ┆a1┆dums.d┆e1┆ which are the initial ↓
┆19┆┆90┆┄┄day.d , init.d  and  sub.d files respectivly.↲
Three files remain:↲
┆a1┆badlogin.n┆e1┆╞	- textfile displayed after 3 unsuccessful login trys.↲
┆a1┆fatal.n┆e1┆╞	- textfile containing fatal error messages.(See App. B).↲
┆a1┆normal┆e1┆╞	┆84┆- ┆84┆program that sets the terminal to normal mode and ↓
┆19┆┆90┆┄┄removes semaphores after system crash.↲

════════════════════════════════════════════════════════════════════════
↓
┆a1┆2.5 System limits.┆e1┆↲
The maximum number of reservations is 500 . Diagnostics:Fatal error 200.↲
Max. no. of subjects:╞	100.↲
Max. no. of initials:╞	400.↲
Max. no. of secretaries: 20.↲
Max. no. of rooms:╞	 80.↲
Trying to initiate one of the last four above limit will not produce a ↓
fatal error, but the messages :Not possible!! Table full.↲
In the current version there is no direct way to remove subjects, ↓
initials etc.↲
Subjects, initials and rooms are removed automatically ┆a1┆┆b0┆30┆e1┆┆f0┆ days after ↓
┆19┆┄┆81┆┄the last appearance in a reservation.↲
Secretaries are ┆a1┆never┆e1┆ removed - so be carefull about initiating them.↲
Reservations are automatically removed when outdated.↲
If the need should arise, subjects/initials/secretaries and rooms can ↓
be removed manualy. See App. A.  for details.↲
↲
↲
┆a1┆2.6 System Crash.↲
Hopefully there will be no need for this section - but anyhow:↲
The system can crash in three different ways.↲
1. The "normal" way for the system to crash is to detect a "fatal error" ↓
- meaning that is has gotten into a mode from which there is no safe way ↓
out. When such an error occurs the screen clears and the line :↲
┆a1┆*** FATAL ERROR ***┆e1┆↲
appears with a number and a text line (from the file fatal.n) describing ↓
the error. Now - what to do ? .↲
This depends on the error number. In any case before proceeding be sure ↓
that no one else is using the system (Use: ┆a1┆ps a┆e1┆  to check that.)↲
┆a1┆Error number is:↲
     ┆a1┆1┆e1┆.╞	┆84┆  ┆84┆The TERM variable is set to something other than qr , qq  ↓
┆19┆┆90┆┄┄or qu. Use ┆a1┆printenv┆e1┆ to get current value. Then set the ↓
┆19┆┆90┆┄┄TERM variable to the correct value (See: Terminal ↓
┆19┆┆90┆┄┄handling.).↲
10┆a1┆<┆e1┆number<100:  ┆84┆I/O error - probably a file is missing or the protection ↓
┆19┆┆90┆┄┄mode of the file in question is wrong. Check the output ↓
┆19┆┆90┆┄┄from: ┆a1┆ls -l┆e1┆  (in /usr/calsys ) against what it should be ↓
┆19┆┆90┆┄┄in App. C. (See also CHMOD(1) if necessary to change ↓
┆19┆┆90┆┄┄mode of a file.)  ↲
100┆a1┆<┆e1┆number<200: Semaphore error - try again after executing ┆a1┆normal┆e1┆.↲
200┆a1┆<┆e1┆number:     Datastructur error - Please submit error report to RC. ↓

════════════════════════════════════════════════════════════════════════
↓
In any case before trying to run the AMS again run the ┆a1┆normal┆e1┆ program! ( ↓
/usr/calsys/normal).↲
↲
2. The "abnormal" way to crash is when the text:↲
"Memory fault - core dumped."↲
suddenly appears on the screen!↲
First thing is to get the terminal back to normal mode.  Do the ↓
following :↲
Press:   (arrow down = newline).↲
Then press the following sequence (You won't see anything on the screen!!) ↓
┆a1┆/usr/calsys/normal ┆e1┆ (Att.: terminate with arrow down (newline) not with ↓
<cr>!.) You should now be able to run the AMS again. If the error ↓
continues to appear, please submit an error report to RC.↲
↲
3. The system "hangs" - that is: No matter what you do the system ↓
doesn't respond!. Login as superuser on another terminal. Type:┆a1┆ps -a┆e1┆ to ↓
find the PID of the process that hangs (running appoint) and then kill ↓
it! (See: KILL(1)).↲

════════════════════════════════════════════════════════════════════════
↓
┆a1┆Appendix  A.┆e1┆↲
┆a1┆↲
┆a1┆Manual removal of a name.┆e2┆↲
where name can be a subject , initial, room or secretary.↲
To remove a initial, room or secretary go into an editor (i.e ┆a1┆ed┆e1┆, ┆a1┆vi┆e1┆ or ↓
UNIPLEX wordprocessing) with the file ┆a1┆init.d┆e1┆ .↲
To remove a subject use the file ┆a1┆sub.d┆e1┆ instead.↲
The procedure is now as follows:↲
Say you want to get rid of the name ┆a1┆dummy┆e1┆.↲
First you find ┆a1┆dummy┆e1┆ in the file. ↲
Second you check that the ┆a1┆next┆e1┆ line starts with a zero (0) . If it does ↓
it is safe to remove the name which is done by deleting:↲
1. The line containing ┆a1┆dummy┆e1┆.↲
2. The next line starting with zero.↲
3. All lines up to and including the next line starting with a zero!↲
   ┆84┆(Possibly only one extra line, which mean that all in all only three ↓
┆19┆┆83┆┄┄lines has been deleted.)↲
Att: ┆84┆If the line immediately after the line containing ┆a1┆dummy┆e1┆ doesn't ↓
┆19┆┆85┆┄┄start with a zero (0) ┆a1┆DO NOT REMOVE┆e1┆ anything - because ┆a1┆dummy┆e1┆ is ↓
┆19┆┆85┆┄┄then part of a reservation.↲

════════════════════════════════════════════════════════════════════════
↓
 ↓
┆a1┆Appendix  B.┆e1┆↲
↲
┆a1┆Listing of fatal error's.┆e1┆↲
( /usr/calsys/fatal.n )↲
↲

════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆Appendix  C.↲
↲
┆a1┆Content of the directory: /usr/calsys  using: ls -l.↲

════════════════════════════════════════════════════════════════════════
↓
┆1a┆┆1a┆/usr/calsys┆e1┆.  (Se
DataMuseum.dk

CP/M

⟦afaaf696e⟧ RcTekst

Derivation

RcTekst

Full view
