Account Set Up Procedures
Last Revision: April 5, 2016 by Tony Roman
Abstract
This document is intended to help a Program Coordinator get the computer accounts, database permissions,
and set up files necessary for processing HST observing programs.
The SOGS Firewall
All of the observatory planning and scheduling machines are considered part of a subnet called SOGS. SOGS
stands for Science Operations Ground System. You will notice, for example, that your workstation has a
name like: elrond.sogs.stsci.edu. The sogs after the machine name means that your machine is on the SOGS
subnet. Because they contain information that will be uplinked to HST and JWST, all SOGS systems lie
behind an extra internet firewall. This is a second layer of protection in addition to the general STScI
firewall. For information about what can go in and out of the SOGS firewall, see:
Meet the computer and software people
If you are just getting started, you can ask those around you for help. When you need more help, this is
who to contact. Try to be prepared with as much relevant information as possible. For instance, write down
what you did leading up to the problem or various things you tried. It might help to print the screen to
capture your last few commands.
From Information Technology Services (IT)
Send e-mail to support@stsci.edu or call the computer support
help desk (x4400, room 330).
From Astronomical Planning & Support Branch (APSB)
For Assist Database questions, see
Maria Bertch.
For Transformation questions, see
Reiko Rager.
For Spike questions, see
Bob Boyer.
For APT questions, see
Rob Hawkins.
Obtain computer accounts
You will need an account on the SOGS network.
In order to obtain the accounts, fill out a computer account request form. (If you are new to the
Institute the account form may have already been completed for you - ask before you fill out a new
form.) They are available outside of room 330. On the form, request a SOGS account; and be sure to
indicate that your default group should be spb for HST and ops for JWST. These groups are
more like properties of the account which gives you certain privileges. If you already have an account
on another STScI computer, request the same account names for your new accounts.
Obtain database privileges
You will need access to the Proposal Library (PLib), and the Assist, PMDB, GSS, and PPSDB databases. PLib
is a configured storage and retrieval system for the observing program files. The Assist and PMDB
databases are large relational databases that live on a server computer named HAL9000. These databases are
used for HST. GSS and PPSDB are databases that are used for JWST. Once you have received your account, you
can request PLib privileges by sending mail to
Tony Roman. For Assist and PMDB access, send mail to
dba@stsci.edu. Request these permissions:
- Read and write access to the Assist databse on HAL9000
- Read and write access to the 'spss' database on HAL9000
For GSS and PPSDDB access, send mail to
Tony Roman. Request these permissions:
- Read-only to the 'gss' databse on GORT
- Read and write access to the 'pps' database on GORT
(Again, if you are new to the Institute these database permissions may have already been established for
you - ask before you send a new request).
Set up your account
Once you are notified of your new account and password, logon to a Mac workstation.
Change your password
Change your password by using the Accounts panel in the Mac System Preferences. You will be prompted for
your old and new passwords. The new password will be automatically communicated to all SOGS
workstations.
Set up ssh
ssh (secure shell) is a unix command that allows secure remote login into another machine. A number of
HST and JWST planning and scheduling tools depend on ssh. To configure your account for the proper use
of ssh, login into a SOGS Mac and type the command:
/data/multi-mission/infrastructure/ssh/scripts/setup_single_ssh_dir
Copy some set up files
When running the account-setup command mentioned below, you might see an
error message indicating a conflict between a file in /User or /home and a file of the same name in
/user. To resolve this conflict, it is fine to delete the former file in favor of the one in /user. If
you have any questions about account-setup, please contact
Tony Roman.
-
Linux - Login to a SOGS Linux machine (e.g. coyote) and run the command:
/data/multi-mission/tools/implementation/account-setup
- OS X - Login to a SOGS OS X machine (e.g. your desktop workstation) and run the command:
/data/multi-mission/tools/implementation/account-setup
- Solaris - Login to a SOGS Solaris machine (e.g. bugs) run the command:
/data/multi-mission/tools/implementation/account-setup
Once you have copied these files, log out and log back in.
Very briefly, this is the purpose these and other "hidden" setup files:
-
.alias: - This file is also sourced directly by the .cshrc. It contains both aliases
(shortcut commands that you define) as well as shell settings. Aliases and shell settings that all
PCs need are grouped in a file called ops-alias.
-
.clinit.cl: - This file is executed whenever you run a LISP program (e.g. Trans, CASM,
Spike, or POPS). Again, a common setup file is loaded, but your own preferences can be added.
-
.cshrc: - The cshell run commands file is executed at login (or whenever you bring up a new
shell window) if your default shell is the cshell or tcshell. The file should not be modified. It
contains calls to other files which you can change to modify your environment.
-
.emacs: - This file is executed whenever you start up the emacs editor. It can contain
preferences you have for running emacs, but it also loads a generic preference file that is
maintained for us.
-
.envrc: - This file is sourced indirectly by the .cshrc through the checkenv routine. It
contains "packages" of environment variables, paths, etc. needed to run applications. The standard
packages that you will need as a PC have been further packaged into something called OPS.
-
.setenv: - This file is sourced directly by the .cshrc. This is where you set environment
variables such as your default printer and editor. Environment variables that all PCs need are
grouped in a file called ops-env.
The following information will help you start using and customizing your set up files:
Play around a little to get the hang of opening (double click!) and closing icons, moving icons and
windows around, and resizing windows. If you need additional terminal screens you can select them from
the dock. The graphical desktop mailtool is available from the dock. Bring up an emacs editor and
web browser.
To set your default printer, set the LPDEST and PRINTER environment variables in your .setenv file. To
see a list of available printers, see the
printer web page
.
You also may want to change your terminal prompt, and there are some environment variables that
provide shortcuts for doing this:
- MACHINE_NAME_PROMPT - Set the prompt to the machine name.
- INCLUDE_USER_IN_PROMPT - Include the user's username in the prompt.
- INCLUDE_MISSION_IN_PROMPT - Include the mission name in the prompt.
- LOWERCASE_PROMPT - Set the prompt to all lowercase.
- UPPERCASE_PROMPT - Set the prompt to all uppercase.
Any combination of these environment variables can be set in your .setenv file; and in these cases, it
is sufficient to simply define the variable without giving it a value. For example, putting these
lines in your .setenv:
setenv MACHINE_NAME_PROMPT
setenv INCLUDE_USER_IN_PROMPT
setenv LOWERCASE_PROMPT
would result in a prompt like:
elrond aroman>
With the right unix syntax, further customization of your prompt can be done in your .alias file.
You can further customize the desktop environment by doing things like adding new menu items in the
Terminal application and changing the behavior of the windows. This is documented in the on line
desktop help, but you can also ask someone for help doing this.
Check to see if you have the tcshell
When your account was set up, you should have been given a default shell of the tcshell. The tcshell
(tab c shell) is built on top of the cshell and has some nice features. (For instance you can use the
up arrow at the command line to retrieve recent commands, and use the tab key to complete file names
and command names.) To confirm this, type:
printenv SHELL
Set PC Tool Box Preferences
You can create and modify your PC Tool Box preferences by using the tool box itself. So bring up the
tool box by typing:
tools
at the prompt. There is a preferences button on the top row.
(Don't forget to use the command: mkdir
to make the working directory you just gave
yourself.)
Get your name added to the PCs lists
Database List of PCs
Some of the software here allows you to select your name from a list (instead of making you type your
name). Send e-mail to Tony Roman and request to be added to the
list of PCs in the database. NOTE: Persons cross-training as PCs should omit this step.
Get your phone added to the voice mail distribution list
When there are problems with e-mail and/or the computers themselves, updates are distributed by voice
mail. To get your phone added to the voice mail distribution list, send e-mail to
Tony Roman.
Put yourself on the software distribution lists
Email distribution lists are available for the major software systems, databases, and database servers.
Being on these lists will allow you to stay informed about problems or discussions about the software:
Unfortunately, STScI has two different systems (MajorDomo and Exchange) for email list management; so
the procedure to join a list depends on the system under which it is managed.
Subscribe to the following MajorDomo lists, by visiting the
MajorDomo Page:
Subscribe to the following are Exchange groups:
- assist-users
- JWST-PIT
- hal9000_dist
- oed_opb
- opm
- pc
- ppsdb-ops-users
- sogs-systems-status
- spike-users
- target_of_opportunity
- trans-users
- zeppo_dist
To subscribe to an Exchange group:
- go to Outlook Web Application
- sign in using your STScI AD password
- select Options->See All Options... in the upper right
- select Groups from the menu at the left
- under Public Groups I Belong To, select Join...
Test Your Account
To determine if your SOGS account is properly configured, type: check-account
at the command line prompt. Run this command separately in the HST and JWST
environments.