sge_request reflects the format of the files to define default request
profiles. If available, default request files are read and processed
during job submission before any submit options embedded in the job
script and before any options in the qsub(1) or qsh(1) command-line are
considered. Thus, the command-line and embedded script options may
overwrite the settings in the default request files (see qsub(1) or
qsh(1) for details).
There is a cluster global, a user private and a working directory local
default request definition file. The working directory local default
request file has the highest precedence and is followed by the user
private and then the cluster global default request file.
Note, that the -clear option to qsub(1) or qsh(1) can be used to dis-
card any previous settings at any time in a default request file, in
the embedded script flags or in a qsub(1) or qsh(1) command-line
The format of the default request definition files is:
o The default request files may contain an arbitrary number of lines.
Blank lines and lines with a '#' sign in the first column are
o Each line not to be skipped may contain any qsub(1) option as
described in the Univa Grid Engine Reference Manual. More than one
option per line is allowed. The batch script file and argument
options to the batch script are not considered as qsub(1) options
and thus are not allowed in a default request file.
The following is a simple example of a default request definition file:
# Default Requests File
# request group to be sun4 and a CPU-time of 5hr
# don't restart the job in case of system crashes
Having defined a default request definition file like this and submit-
ting a job as follows:
See sge_intro(1) for a full statement of rights and permissions.
UGE 8.0.0 $Date: 2004/04/19 10:52:10 $ SGE_REQUEST(5)
Man(1) output converted with