Sun Shared Visualization 1.1 Software Client Administration Guide

This appendix provides basic information about the Sun Grid Engine commands and options. More thorough information is available in the Sun Grid Engine documentation. See Related Documentation.

Topics in this section include:

• Accessing the Sun Grid Engine Environment
• Setting Up the Sun Grid Engine Environment Variables
• Basic Sun Grid Engine Commands
• qsub and qrsh Commands
• Example Sun Grid Engine Job Script

---

Accessing the Sun Grid Engine Environment

To access Sun Grid Engine, the client host NFS mounts the Sun Grid Engine installation. Your client host should mount Sun Grid Engine so that you can use the same $SGE_ROOT as the NFS server does. (The default is /gridware/sge.)

1. Test the accessibility of the $SGE_ROOT directory from your client host:

# ls /net/nfsserverhostname/gridware

where /gridware is the base directory of your $SGE_ROOT.

2. From your client host, access the NFS server’s $SGE_ROOT as the client’s own $SGE_ROOT using /etc/vfstab, /etc/fstab, or automount.

• For Solaris automounting:

a. Add the following line to the /etc/auto_direct file:

/gridware  -rw,suid,bg,hard,noquota,intr nfsserverhostname:/gridware

where /gridware is the base directory of your $SGE_ROOT.

b. Restart the automounter:

• For the Solaris 10 (or later) OS


# svcadm -v restart autofs


• For earlier Solaris releases:


# /etc/init.d/autofs stop ; /etc/init.d/autofs start

• For Linux mounting:

a. Add the following line to the /etc/fstab file:,

nfsserverhostname:/gridware    /gridware  nfs        auto,suid,bg,intr          0 0

b. Type these two commands:

# mkdir /gridware
# mount /gridware

where /gridware is the base directory of your $SGE_ROOT.

3. If your grid installation requires it, copy the server’s sge_qmaster line from the server’s /etc/services file into your client’s.

This step is not needed if the SGE settings files set the SGE_QMASTER_PORT environment variable. See Setting Up the Sun Grid Engine Environment Variables.

---

Setting Up the Sun Grid Engine Environment Variables

  Set up the Sun Grid Engine environment variables:

• tcsh and csh users set up environment variables using:


submit_host% source /gridware/sge/default/common/settings.csh

Substitute /gridware/sge with your value for $SGE_ROOT.

• sh, bash, and ksh users use:


$ . /gridware/sge/default/common/settings.sh

Substitute /gridware/sge with your value for $SGE_ROOT.

You might want to insert a command like these in your login configuration file, probably subject to a test that the settings file exists (is readable).

---

Basic Sun Grid Engine Commands

TABLE C-1 provides a brief description of the basic Sun Grid Engine commands.

If SGE commands such as qstat are still not found after setting up the environment, have your system administrator verify that the NFS server contains binaries for your client’s architecture (operating system and processor, as output by SGE’s arch command at $SGE_ROOT/util/arch). For example, if arch prints sol-amd64, then $SGE_ROOT/bin should contain a subdirectory named sol-amd64.

qsub job output is redirected to a file (and qrsh output is not). By default, this file is $HOME/JobName.oJobId. Any error output is likewise saved in the error file, which defaults to $HOME/JobName.eJobId. Other differences between qsub and qrsh are presented in TABLE C-3. Both qsub and qrsh require an absolute (starting with /) or relative path to the program or script to be submitted. $PATH will not be searched to locate qsub or qrsh.

---

qsub and qrsh Commands

The qsub command starts batch jobs at a later time. The qrsh command runs jobs interactively.

Some Common qsub and qrsh Options

TABLE C-2 provides command options common to both qsub and qrsh.

Different Default Behavior of qsub and qrsh

Though the qsub and qrsh commands start jobs, their respective default behavior is different. TABLE C-3 presents the differences in qsub’s and qrsh’s defaults for certain options.

---

Example Sun Grid Engine Job Script

The following example job script starts /opt/VirtualGL/bin/glxspheres on a Solaris or Linux graphics server. This script is a simplified version of $SGE_ROOT/graphics/RUN.glxspheres. Italicized text in this listing provides commentary, but is not part of the job script itself.

#
# The name of my job:
#$ -N glxspheres
#
# The interpreter SGE must use:

#
# Join stdout and stderr:
#$ -j y
#
# This job needs a graphics device:

#
# Specify that these environment variables are to be sent to SGE with the job:
#$ -v DISPLAY
#$ -v VGL_CLIENT
#$ -v VGL_GAMMA
#$ -v VGL_GLLIB
#$ -v VGL_SPOIL
#$ -v VGL_X11LIB
#$ -v SSH_CLIENT
# If these variables are not set before qsub/qrsh is invoked,
# then the job will find these variables set, but with a null string value ("").
#
# Script can run on what systems?
# Solaris (SPARC or x86, 32-bit or 64-bit) and Linux systems (32- or 64-bit),
# provided glxspheres is installed on the target system in one of the paths below.
#$ -l arch=sol-sparc|sol-sparc64|sol-x86|sol-amd64|lx24-x86|lx24-amd64
 
# If VGL_DISPLAY is set by SGE, then run program with vglrun. Otherwise don't.

    if [ ! -x $VGLRUN ]; then
	echo 1>&2 "vglrun not found on host ${HOSTNAME:=‘hostname‘}"
	exit 1
    fi
else
    VGLRUN=""
fi
 
if  [ -x /opt/VirtualGL/bin/glxspheres ]; then
    path=/opt/VirtualGL/bin/glxspheres
else
    echo 1>&2 "glxspheres not found on host ${HOSTNAME}"
    exit 2
fi
    
# Sun Grid Engine job starts vglrun which starts glxspheres
# with any arguments passed to this script.  If VGL_DISPLAY is not set,
# $VGLRUN will be the empty string, and vglrun won't be invoked.
$VGLRUN "$path" "$@"

Sun Shared Visualization 1.1 Software Client Administration Guide

820-3257-12

Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.