The random number routines are FORTRAN versions of combined random number
generators recommended by Pierre L'Ecuyer (Efficient and Portable Combined
Random Number Generators, Communications of the ACM, Vol. 31, No. 6 (June
1988), 742-749, 774). Three implementations are given: two for PDP-11's and
one for VAXes. For PDP-11's, use the two '*16.ftn' files for short (16-bit)
integers (especially if you don't have F77), or the two '*32.ftn' files for
long (32-bit) integers (if you have F77). For VAXes, use the two '*.for'
files. Note that the only real difference between the '*32.ftn' files and the
'*.for' files is that the latter are specifically written for VAX FORTRAN:
there is no difference in the generation formulae. Therefore, if you want a
16-bit generator for your VAX, you can use the '*16.ftn' files.
The approximate period length for each generator is noted in the 'Unifrm*.*'
files.
The 'symbols.cmd' file is a PDP-11 command file skeleton that provides a large
number of symbols for use by RSX Indirect (@). For PDP-11's, you would insert
your command file instructions between the symbol definitions section and the
subroutines section (near the end of the file). This grew from a VAX version
that provided row and column positioning escape sequences for VT1xx, VT2xx,
and VT3xx terminals, plus a few other video characteristics like bold and
reverse video. I decided to make a small file for PDP-11's, so I could have
some of the more common escape sequences, without using up too much symbol
table space or taking too much time. Well, did I get a surprise!! It turns
out that if you built the large (ICP) version of Indirect on RSX, you have
gobs of symbol table space. If you use one of the J-11 CPU's (KDJ11-xx
series), it doesn't take much time to define all those symbols either! So,
this file now has symbols for 24 rows, 80 columns, plus most of the VT2xx
escape sequences (video characteristics, selective erase, etc.). As it is
right now, the symbols take only about 1/3 of the RSX ICP symbol table, and it
takes about 2-3 seconds to run through the definitions.
The 'symbols.cmd' file originated at the Wichita Farm Credit Services as
'form_symbols.com'. I have followed their standard (which I believe is a VERY
GOOD one) for command files: "Command files shall contain NO non-printable
characters." This is quite easy for VMS DCL, but is somewhat of a pain for
RSX folks. (If you complain about VMS DCL, read 'symbols.txt' and
'symbols.cmd' and you will probably decide that things aren't really so bad
after all.)
For you VAX folks, there are two extra files: 'symbols.txt' explains how one
would convert 'symbols.cmd' to a VMS DCL command file. 'symbols.com' is all
of 'symbols.cmd'. I have not had an opportunity to test this file, but if
there are any problems, they should be minor.
James Fullerton
Institute of Logopedics
2400 Jardine Drive
Wichita, KS 67219