qtcsh [ tcsh options | -ABLR ]
Qtcsh is an extension to the popular csh(1) derivative tcsh. It allows
the transparent remote execution commands entered in qtcsh controlled
via Univa Grid Engine. Qtcsh can be used as interactive command inter-
preter as well as for the processing of tcsh shell scripts.
When invoked, qtcsh identifies which commands are to be run remotely
and which are not. For this purpose the files <sge_root>/<cell>/com-
mon/qtask and ~/.qtask are processed. Each line in these files defines
a command that is intended to be run remotely (see qtask(5) for a defi-
nition of the file format). The .qtask file in the user's home direc-
tory contains the user's remote task specification, while the file in
the common directory is maintained by the administrator and defines a
cluster-wide default behavior. The contents of the administrator sup-
plied qtask(5) file are completely overridden in case there is an
appropriate entry in the users qtask(5) file. This is prevented in
case an exclamation mark is prefixed to the command name in the admin-
istrators qtask file.
Qtcsh always attempts to start the designated tasks remotely via
qrsh(1). Exceptions are
o if the user enters such commands via a relative or absolute pathname
instead of the stand-alone command name (see qtask(5) for more
o if the environment variable JOB_ID is set and thus qtcsh assumes
that execution already happens remotely within a Univa Grid Engine
job and thus executes tasks locally. This avoids unwanted recursions
but can be overridden by the command-line option -R and the built-in
command qrshmode -R (see corresponding descriptions below).
o if qtcsh cannot establish a connection of Univa Grid Engine during
start-up. This allows to use qtcsh as login shell without the danger
of being blocked when no Univa Grid Engine service is available.
Qtcsh can operate in three different modes determining whether
o tasks are executed remotely.
o immediate or batch execution is requested.
o status output is verbose or only in case of any errors.
These modes either can be controlled by the command-line switches
described below during qtcsh invocation or within an executing qtcsh
via the built-in command qrshmode as described in section BUILT-IN COM-
failure of the scripts due to temporarily unavailable resources
for particular tasks.
-L Switches off default behavior of remote execution of commands.
Causes all commands to be executed locally even if they are con-
tained in one of the qtask(5) files.
-R Enforces remote execution of commands even if JOB_ID is set as
This section only describes additional shell builtin commands which are
not available in standard tcsh(1).
Without options, the current operational mode of qtcsh is dis-
played. The options have the following effect:
-A switch to verbose output mode
-N switch to non-verbose output mode
-B switch to batch execution mode
-I switch to immediate execution mode
-L always execute commands locally
-R execute configured commands remotely
SGE_ROOT Specifies the location of the Univa Grid Engine standard
SGE_CELL If set, specifies the default Univa Grid Engine cell. To
address a Univa Grid Engine cell qtcsh uses (in the
order of precedence):
The name of the cell specified in the environment
variable SGE_CELL, if it is set.
The name of the default cell, i.e. default.
If set, specifies that debug information should be writ-
ten to stderr. In addition the level of detail in which
debug information is generated is defined.
If set, specifies the tcp port on which sge_qmaster(8)
is expected to listen for communication requests. Most
installations will use a services map entry for the ser-
vice "sge_qmaster" instead to define that port.
the University of California. Therefore, the following note applies:
This product includes software developed by the University of Califor-
nia, Berkeley and its contributors.
See sge_intro(1) and the information provided in
<sge_root>/3rd_party/qtcsh for a statement of further rights and per-
UGE 8.0.0 $Date: 2004/11/12 15:40:03 $ QTCSH(1)
Man(1) output converted with