Installation of SIR 2000 under Open VMS (Alpha)

*** Part A - System - should be performed by the superuser

1) Create a home directory for SIR 2000. These instructions assume
that you choose to use $DKA100:[SIR2000] as the SIR home directory.
Make it your default directory.

2) Copy two files - unzip.exe and sir2000.zip from the distribution
CD into this directory. Execute the following commands to unzip the
archive file:

    unzip == $DKA100:[SIR2000]unzip.exe
    unzip sir2000.zip

Now you can delete these two files as you don't need them anymore.

3) Create the symbol names for SIR home directory and executables
as described in the End User's part of this document.

3) Normally SIR home directory can be declared read-only for everyone.
If only a small group of power users use SIR on your system, you might
wish to modify the owner/group and access rights status of the files and
subdirectories installed. It would allow power users to add custom help
pages, images and toolbar button bitmaps into the relevant subdirectories
of the SIR home directory, replace keymap files and even modify the code
in the core libraries of SIR stored in the SIR system procedure file.

4) Run the sir executable file. Your will be prompted to type in your
licence information and SIR will create the licence file sir.lcn in SIR
home directory. It is a text file and can be edited manually if you don't
have the X-Window environment and have installed SIR only for its server
functionality. In that case, you need to create the file manually. Write
your user id on the first line, your licence code on the second and the
licence holder name on the third.

5) You may need to replace two keymap files (*.kmp) if you have problems
with working in SIR execution window. Delete these files and start SIR.
Define the key mapping and save it. Note that the file will be saved in
your CURRENT working directory. You may need to copy it into SIR home
directory. Repeat the same for SIRFORMS. When users run SIR, it searches
for keymap files in the current working directory and if a local copy is
not found, uses the file from SIR home directory. If different users use
different X-Window environments (some work on the Alpha machine itself,
others access it using the X-Window emulators installed on their PCs),
the remote users will have to keep their own keymap files in a directory
which is their current directory when they run SIR.

6) Check that the fonts used by SIR (defined in sir.ini in user's home
directory) are present on your system. The sample version of sir.ini is
in the test subdirectory of the SIR home directory. It is here only for
your reference and never used by SIR. Each user needs to copy it into
his/her home directory, otherwise SIR will not be able to find it. Edit
the master copy if the fonts have to be changed and tell the users to
take it. You might need to create a special version of this file for
the users running SIR from remote PCs under X-Window emulators.

7) Write brief instructions for your users, so they know the name of the
SIR home directory for this version of SIR and can perform the end-user
part of installation for their specific environments.

*** Part B - User - performed by each SIR user

Edit your login script (or just modify the current shell environment
for a quick test) to include the following:

1) Define SIRDIR environment variable pointing to SIR home directory
2) Define the names to start the SIR components

The person who has installed the Beta on the system can provide you
with instructions on how to do it in your specific environment. In the
simplest case you could place something like that into your login
script:

$ define /system /executive /nolog SIRDIR DKA100:[SIR2000]
$
$ SIR       :== $DKA100:[SIR2000]sir.exe
$ SIRBATCH  :== $DKA100:[SIR2000]sirbatch.exe
$ SIRSQL    :== $DKA100:[SIR2000]sirsql.exe
$ SIRSQLB   :== $DKA100:[SIR2000]sirsqlb.exe
$ SIRSQLS   :== $DKA100:[SIR2000]sirsqls.exe
$ SIRFORMS  :== $DKA100:[SIR2000]sirforms.exe
$ SIRMASTER :== $DKA100:[SIR2000]sirmaster.exe
$ SIRRMT    :== $DKA100:[SIR2000]sirrmt.exe

3) You might want to copy the sample of SIR configuration file (sir.ini)
from the test subdirectory of SIR home directory into your own personal
home directory. This step is optional, SIR has reasonable defaults for
its settings and will create/modify the configuration file itself. The
reason why we do recommend to copy the file into your home directory is
to have it nicely laid out with all the settings. Some of the setting
are not accessible interactively and you have to edit the file manually
if you want to change them. It will be much easier to do if you have a
complete and well organized set of setting in your sir.ini file. Never
edit the file while any SIR component is running - SIR overwrites the
complete file on exit and all your changes will be lost. It also applies
when two or more of SIR products run simultaneously - the program which
terminates last will save its copy of the file. Note that the default
fonts used by SIR may be absent in your X-Window installation. In that
case, you MUST have the sir.ini file with correct font names in your home
directory.