SGE_REQUEST(5)

NAME
sge_request - Grid Engine default request definition file format

DESCRIPTION
sge_request reflects the format of the files defining default request profiles. These apply to and but for convenience, only qsub is mentioned below. 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 command-line are considered. Thus, the command-line and embedded script options may overwrite the settings in the default request files (see for details). However, where options may be repeated and accumulated, typically they are collected into a list from the various sources, which may not be what you want.

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 can be used to discard any previous settings at any time in a default request file, in the embedded script flags or in a command-line option.

The format of the default request definition files is:

•   The default request files may contain an arbitrary number of lines. Blank lines, and lines with a '#' sign in the first column, are skipped.

•   Each line not to be skipped may contain any option. More than one option per line is allowed. The batch script file and argument options to the batch script are not considered as options and thus are not allowed in a default request file.

EXAMPLES

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
-l arch=sun4,s_cpu=5:0:0

# don't restart the job in case of system crashes
-r n
=====================================================

Having defined a default request definition file like this, submitting a job as follows:

qsub test.sh

would have precisely the same effect as if the job was submitted with:

qsub -l arch=sun4,s_cpu=5:0:0 -r n test.sh

FILES
<sge_root>/<cell>/common/sge_request
	global defaults file
$HOME/.sge_request	user private defaults file
$cwd/.sge_request	cwd directory defaults file

SEE ALSO

COPYRIGHT
See for a full statement of rights and permissions.