OT V.1.4.1 installation instructions

Installing OT V.1.4.1

1. Change directory to where you want to install the OT system.

2. Retrieve the OT V.1.4.1 delivery package

3. Retrieve the binary distribution kit
   • Solaris 5.6 (MAR2001, CCSLite)
   • HP-UX 11.00 (MAR2001, CCSLite)
   • Solaris 5.6 (FEB2000, CCSLite: obsolete)
   • HP-UX 10.20 (FEB2000, CCSLite: obsolete)

   Note: CCS/RTAP is not supported anymore.

4. At this point you should have two gzipped tar files in your current directory. Execute:

   gunzip -c ot-1.4.1.tar.gz | tar xovf -

   This will create a directory called ot-1.4.1.

5. Execute the command sequence:

   cd ot-1.4.1
setenv OT $PWD
make

6. At this point you may remove the gzipped tar files.

7. Install all the available instrument packages: see the USG Instrument Packages Web page for more information.

8. Edit ~/.otrc to suit your preferences.
   You may want to set the variable OT_CACHE_PATH to something more specific than the default, like $HOME/eso/ot-cache.

9. Optionally you can install the Short Term Scheduler, if a full Allegro Common Lisp system is installed on your host. See below for the Installation Instruction.

Installing the Short Term Scheduler

1. Execute the command:

   cd $OT

2. If a full Allegro Common Lisp system is installed on your host, and the LISP environment variable is correctly set, retrieve the corresponding Short Term Scheduler V.1.4.1 binary distribution kit for:
   • Solaris
   • HP-UX
   Please note that the LISP environment variable must be defined at installation time for the STS to be properly installed. See below for a description of the LISP variable.

3. At this point you should have a gzipped tar file in your current directory. Execute the command sequence:

   gunzip -c STS-*-kit-V.1.4.1.tar.gz | tar xovf -


   This completes the installation of the STS.

Running OT V.1.4.1

• OT should point to the directory where you installed the system: for instance

  setenv OT $HOME/ot-1.4.1

• DSQUERY should be the name of the database server you want to connect to: for instance

  setenv DSQUERY PROBS

• PATH should contain $OT/bin; for instance:

  setenv PATH $PATH":"$OT/bin

• if you want to run the Short Term Scheduler the LISP shell variable should be correctly set as well: see below for details.

Environment variables

• VLTROOT (deafults to $P2PP)
  If the VLT software is already installed on your system, your VLTROOT shell variable is probably already set to something like /vlt/MAY97.

• DSQUERY (defaults to the current SYBASE server)
  The ObservingTool accesses the OB repository, and the DSQUERY variable indicates which server (host) holds the database itself.

• RTAPENV (deafult is installation-dependent)
  Environment variable RTAPENV should be set to the name of the active RTAP environment, either CCS or CCSlite: for instance, wip5qs.

• LISP (no default)
  The Short Term Scheduler needs a full Allegro Common Lisp installation on the same host. This environment variable should be set to the pathname of the installation directory, like /usr/local/acl4.3. If LISP is not set or it is empty, at either installation- or run-time, then the STS will not be available.

• OHS_EVENT_LOG (no default)
  VCS events sent by BOB to the OT can be saved to an ASCII file, which can later be post-processed to collect execution timing statistics. If the OHS_EVENT_LOG environment variable is set, and its value is the pathname of a writable file, all BOB events will be logged in ASCII format to that file. Otherwise no logging will take place.
  See also the VCS/OH ICD.

• OHS_CCS_SERVER_NAME (no default)
  In order to communicate with the VCS, OT configures itself as a CCS server. The default name of the server is schedule, but it is possible to call the server a different name by setting the OHS_CCS_SERVER_NAME environment variable (this is mostly done for engineering tasks).

Starting OT with:
OT: /home/ac3c/users/amchavan/work/ot
VLTROOT: /usr/server/arc/vlt/JUN96
... more lines ...

by which you can verify if the shell variables are properly set.