List of submission directives

The following common directives are supported by grid-scheduler:

Directive	Description	`qsub` example
`-a [[CC]]YY]MMDDhhmm[.SS]`	Defines the date and time when a job can be executed	`-a 201131021830`
`-ar ar_id`	Assigns the job to the advanced reservation with ID `$ar_id`	`-ar 412`
`-b y[es]/n[o]`	Allows a user to indicate that the command provided to `qsub` is a binary instead of a script.	`-b y mybinary.bin`
`-cwd`	Instructs grid-scheduler to execute the job from the current working directory	`-cwd`
`-display`	Allows grid-scheduler to configure the remote X display for a graphical application.	`-display imac:3`
`-dl [[CC]]YY]MMDDhhmm[.SS]`	Available for users allowed to submit deadline jobs to indicate the final date and time the jobs can be run.	`-dl 201131021830`
`-e path`	Indicates the path to be used for standard error output streams.	`-e /users/bob/output`
`-hard`	Specifies that jobs submitted with resource requirements must fully satisfy these requirements before they can run.	`-hard`
`-hold <jobid>`	Defines that the submitted job must wait before executing until all jobs in the comma-separated `<jobid>` list have completed.	`-hold 232,234`
`-j y[yes]/n[o]`	Instructs the scheduler to merge the `stdout` and `stderr` streams from the job into a single file. By default, separate files will be created for each stream.	`-j y`
`-l resource=value`	Specifies that the job requires a particular resource to be able to run. The `qconf -sc` command shows the configured resources available for selection.	`-l exclusive=true`
`-m b/e/a/s/n`	Instructs the scheduler to send email to notify the user when the job: `b`: begins, `e`: ends, `a`: is aborted, `s`: is suspended or `n`: never email for this job	`-m beas`
`-M user[@host]`	Specifies the email address to use to notify users of job status	`-M myuser`
`-notify`	Request that the scheduler sends warning signals (`SIGUSR1` and `SIGUSR2`) to running jobs prior to sending the actual `SIGSTOP` or `SIGKILL` messages at termination time.	`-notify`
`-now y[es]/n[o]`	Signifies that interactive jobs running `qsub`, `qsh`, `qlogin` or `qrsh` should be scheduled and run immediately or not at all	`-now y`
`-N name`	Allows users to set the name to be used to identify the job. If this parameter is not specified, the job is given the same name as the jobscript	`-N BobVMDjob4`
`-o path`	Indicates the path to be used for standard output streams	`-o /users/bob/output`
`-p priority`	Allows a user to request that their jobs are run with lower than normal priority. Valid priorities are `0` (default) to `-1024` (lowest priority).	`-p 1023`
`-pe name nodes`	Requests the named parallel environment and number of nodes for the job to be run over	`-pe mpi-verbose 8`
`-q queue`	The scheduler queue to which the job should be submitted. If omitted, the scheduler automatically determines the correct queue to be used based on the job type	`-q serial.q`
`-r y[es]/n[o]`	If set to yes, this parameter causes the scheduler to automatically re-run the job if it fails during execution	`-r y`
`-soft`	Specified that jobs submitted with resource requirements can still be run even if the requestd resources are not available. If this parameter is not specified, the scheduler defaults to `hard` requirements	`-soft`
`-sync y[es]/n[o]`	Causes the `qsub` command to wait for the job to complete before exiting	`-sync y`
`-t first-last`	Submits a job task array starting at task `first` and ending with task `last`	`-t 1-1000`
`-verify`	Displays results of a dry-run submission without actually submitting the job for execution	`-verify`
`-V`	Exports all current environment variables to the job	`-V`
`-wd path`	Sets the working directory of the job	`-wd /users/bob/app2`

Grid-scheduler directives may also be specified at job submission time as parameters to the qsub command, for example:

$ qsub -j y -V -cwd ./my-serial-job.sh