2. Introduction to Login Files

Anyone who wants to use the LAS system must ensure that several UNIX environment variables are set. Some of these point to directories used by TAE, while others point to directories used by LAS. The easiest way to get these variables set is to place commands in the user's login file which will execute existing shell scripts/command files to define them.

2.1 UNIX Login File

On UNIX systems, the .login file should contain the following lines if a masterlog is being used.:


     if ( -r /your_path_name/las73/env/las/assign/masterlog) then            
        eval `/your_path_name/las73/env/las/assign/masterlog response comfile eval $comfile`
     else
          echo "Cannot prompt, /your_path_name/las73/env/las/assign/masterlog does not exist."
     endif
where "/your_path_name/" specifies the directory used for the installation.

The first line looks for the file /your_path_name/las73/env/las/assign/masterlog. Masterlog prompts the user for a subsystem (LAS73) and sends back the response and commands to be evaluated. The next line executes the commands placed in the shell variable comfile by masterlog. These commands execute shell scripts to define the necessary environment variables. Samples of these shell scripts are given in the following section.

A masterlog file is included within the distribution. You will need to modify this file before using it. Edit $EDCSOFT/env/las/assign/masterlog. At the location in the file which states "Site specific modifications go here", change the tae and edcsoft symbols to "/your_path_name/" as used during the installation.

2.2 Sample Shell Scripts for Defining Environment Variables

These are examples of scripts used for setting up UNIX environment variables for LAS. They are included here for illustrative purposes and are subject to change.

Example of masterlog

Example of lasinit

Example of LAS usrassign

Example of LAS pgmassign