INSTALLATION PROCEDURE FOR TABLES PROGRAMS

This distribution contains all files necessary to build the tables programs
which are described briefly in the file README.1ST and in detail in file
USERGUIDE.RNO.  It also contains, for convenience, an object module library
(FLECS.OLB) and command files to build Flecs, the Fortran preprocessor
language in which most of the tables programs are written.  This is Mark
Lewis's Flecs from account [305,202] of the Spring '79 RSX/IAS SIG tape,
slightly modified (e.g. the default file extension is changed from .FLE back
to .FLX).  If you plan to modify any of the Flecs code, you should get the
Flecs manual either from that tape or from the University of Oregon Flecs
distribution.

These programs were developed under IAS v3.1 and Fortran IV v2.5.  With the
exception of the subroutines SUBTSK, SUBRUN, SUBREC, and SUBSEN of RPTTAB,
which depend on calls to the timesharing control services macros (via Mark
Lewis's library), conversion to RSX-11M should not be difficult.  (A dummy
SUBTSK subroutine is provided to get RSX-11M users started).  Conversion to
Fortran 77 will require editing the command files for compilation (??C.CMD),
and may require editing some of the source code.

Installation command files are provided for both IAS and RSX-11M.  The RSX-11M
procedures are really IAS pre-timesharing-startup procedures.  RSX-11M users
should expect to have to do some editing of source and command files. (NOTE:
Where the RSX-11M procedure differs from the IAS procedure, the IAS procedure
is indicated by square brackets ([]), or IAS:[], while the RSX-11M procedure
is indicated by curly brackets ({}), or RSX:{}. ?? in a file name indicates
any number of letters.)

All files from the distribution tape should be copied to an empty UIC. No
UIC's are assumed in any of the command files or procedures except for the
default user account. However, the installation procedure assumes that the
user is privileged to install tasks. Also, the Fortran OTS routines are
expected to be in the system default library.

1.  Print the files README.1ST and INSTALL.DOC (this file).

2.  Edit the file USERGUIDE.RNO (the tables userguide in RUNOFF format).
    Comments (.COMMENT) throughout the file suggest alterations in the
    chapter numbering, page size, etc.  RUN it OFF:

	RNO USERGUIDE=USERGUIDE

3.  IAS:[Edit the batch file BUILD.BIS.  Replace the $JOB line with one
    containing your account name and password, and the $SET DEFAULT line with
    the appropriate one.  If you already have Flecs installed on your system
    with Mark Lewis's DCL interface (or equivalent) you may comment out the
    line
         $@FLECSBLD.

    If you have Flecs and your default Flecs file extension is .FLE,

         RENAME *.FLX;* *.FLE;*

    If you don't have batch in your system, edit the $JOB and $EOJ lines out
    of BUILD.BIS and name the output BUILD.CMD.]

    RSX:{If you have Flecs in your system, and your default Flecs file
    extension is .FLE,

         PIP *.FLE;*/RE=*.FLX;*

    Edit the files LISTAB.FLX (or .FLE) and DMPTAB.FLX. These two sources call
    GETMCR for a command line which may include a switch (e.g. LST/SEARCH
    TABPROG).  PDS puts a blank in the line before the slash, while MCR (at
    least in IAS) doesn't. Look for comments about RSX. Other files that make
    system calls are:

	INIFIL.FLX	(GETMCR)
	IOSUBS.FLX	(WTQIO)  }

4.  Issue the PDS/MCR command 

         MUNG FIXLIB

    This procedure edits all command files for taskbuilding to replace the
    name of the resident library to which the tasks are linked. (You are
    asked for the name; type it carefully, because <del> is not handled).
    If your Fortran resident library is F25RES, you can skip this step.
    If you don't have TECO, edit [FLECSBLD.CMD and ??LINK.CMD] {*.TKB}.

5.  IAS:[SUBMIT BUILD or @BUILD]
    RSX:{@BUILD.RSX  You will be asked if you want to build Flecs.}

6.  If all goes well, continue with step 7, else fix the problem and repeat 5.

7.  IAS:[Edit TEST.BIS, correcting the $JOB and $SET DEFAULT lines.  If you
    don't have batch, use the RSX procedure in step 8.  The programs cannot be
    tested without terminal I/O, which batch handles but indirect command
    files do not.]

8.  IAS:[SUBMIT TEST]
    RSX:{Print TEST.BIS and use it as a guide for testing the table programs
    manually.}

9.  If desired, [PRINT/DELETE *.FLL, *.MAP] {QUE LP0:=*.FLL/DE,*.MAP}.