SUBMIT(1)                  Grid Engine User Commands                 SUBMIT(1)



[1mNAME[0m
       qsub   -  submit a batch job to Grid Engine.

       qsh    -  submit an interactive X-windows session to Grid Engine.

       qlogin -  submit an interactive login session to Grid Engine.

       qrsh   -  submit an interactive rsh session to Grid Engine.

       qalter -  modify a pending batch job of Grid Engine.

       qresub -  submit a copy of an existing Grid Engine job.

[1mSYNTAX[0m
       [1mqsub [22m[ [1moptions [22m] [ [1mcommand | -- [22m[ [1mcommand_args [22m]]

       [1mqsh [22m[ [1moptions [22m] [ [1m-- xterm_args [22m]

       [1mqlogin [22m[ [1moptions [22m]

       [1mqrsh [22m[ [1moptions [22m] [ [1mcommand [22m[ [1mcommand_args [22m]]

       [1mqalter [22m[ [1moptions [22m] [1mwc_job_range_list [22m[ [1m-- [22m[ [1mcommand_args [22m]]

       [1mqalter [22m[ [1moptions [22m] [1m-u user_list | -uall [22m[ [1m-- [22m[ [1mcommand_args [22m]]

       [1mqresub [22m[ [1moptions [22m] [1mjob_id_list[0m

[1mDESCRIPTION[0m
       [4mQsub[24m  submits batch jobs to the Grid Engine queuing system. Grid Engine
       supports single- and multiple-node jobs. [1mCommand [22mcan be  a  path  to  a
       binary or a script (see [1m-b [22mbelow) which contains the commands to be run
       by the job using a shell (for example, [4msh[24m(1) or [4mcsh[24m(1)).  Arguments  to
       the  command are given as [1mcommand_args [22mto [4mqsub[24m [4m.[24m  If [1mcommand [22mis handled
       as a script then it is possible to embed flags in the script.   If  the
       first two characters of a script line either match '#$' or are equal to
       the prefix string defined with the [1m-C [22moption described below, the  line
       is parsed for embedded command flags.

       [4mQsh[24m  submits  an  interactive  X-windows  session  to  Grid  Engine. An
       [4mxterm[24m(1) is brought up from the  executing  machine  with  the  display
       directed  either  to  the X-server indicated by the DISPLAY environment
       variable or as specified with the [4m-display[24m [4mqsh[24m option. Interactive jobs
       are  not  spooled if no resource is available to execute them. They are
       either dispatched to a suitable machine for  execution  immediately  or
       the  user  submitting  the  job  is  notified  by  [4mqsh[24m that appropriate
       resources to execute the job are not available.  [1mxterm_args [22mare  passed
       to  the  [4mxterm[24m(1) executable.  Note, however, that the [4m-e[24m and [4m-ls[24m xterm
       options do not work with [4mqsh[24m [4m.[0m

       [4mQlogin[24m is similar to [4mqsh[24m in that it submits an interactive job  to  the
       queueing  system. It does not open an [4mxterm[24m(1) window on the X display,
       but uses the current terminal for user I/O. Usually, [4mqlogin[24m establishes
       a [4mtelnet[24m(1) connection with the remote host, using standard client- and
       server-side commands. These commands can be configured  with  the  [1mqlo-[0m
       [1mgin_daemon  [22m(server-side,  Grid  Engine  [4mtelnetd[24m  if not set, otherwise
       something like /usr/sbin/in.telnetd) and  [1mqlogin_command  [22m(client-side,
       Grid  Engine  [4mtelnet[24m if not set, otherwise something like /usr/bin/tel-
       net) parameters in the  global  and  local  configuration  settings  of
       [4msge_conf[24m(5).   The  client  side command is automatically parameterized
       with the remote host name and port number to which to connect,  result-
       ing in an invocation like

              /usr/bin/telnet my_exec_host 2442

       for  example.  [4mQlogin[24m is invoked exactly like [4mqsh[24m and its jobs can only
       run on INTERACTIVE queues.   [4mQlogin[24m  jobs  can  only  be  used  if  the
       [4msge_execd[24m(8) is running under the root account.

       [4mQrsh[24m  is similar to [4mqlogin[24m in that it submits an interactive job to the
       queuing system.  It uses the current terminal for user  I/O.   Usually,
       [4mqrsh[24m  establishes  a [4mrsh[24m(1) connection with the remote host. If no com-
       mand is given to  [4mqrsh[24m,  an  [4mrlogin[24m(1)  session  is  established.   The
       server-side  commands  used  can  be configured with the [1mrsh_daemon [22mand
       [1mrlogin_daemon [22mparameters in the global and local configuration settings
       of  [4msge_conf[24m(5).  An Grid Engine [4mrshd[24m or [4mrlogind[24m is used if the parame-
       ters are not set. If the parameters are set,  they  should  be  set  to
       something  like  /usr/sbin/in.rshd  or  /usr/sbin/in.rlogind.   On  the
       client-side, the [1mrsh_command [22mand [1mrlogin_command [22mparameters can  be  set
       in the global and local configuration settings of [4msge_conf[24m(5).  If they
       are not set, special Grid Engine [4mrsh[24m(1) and [4mrlogin[24m(1)  binaries  deliv-
       ered  with Grid Engine are used.  Use the cluster configuration parame-
       ters to integrate mechanisms like  [4mssh[24m  or  the  [4mrsh[24m(1)  and  [4mrlogin[24m(1)
       facilities supplied with the operating system.

       [4mQrsh[24m  jobs can only run in INTERACTIVE queues unless the option [1m-now no[0m
       is used (see below).  They can also only be run, if the [4msge_execd[24m(8) is
       running under the root account.

       [4mQrsh[24m  provides an additional useful feature for integrating with inter-
       active tools providing a specific command  shell.  If  the  environment
       variable  [1mQRSH_WRAPPER  [22mis set when [4mqrsh[24m is invoked, the command inter-
       preter pointed to by [1mQRSH_WRAPPER [22mwill be executed to run [4mqrsh[24m commands
       instead  of  the  users  login shell or any shell specified in the [4mqrsh[0m
       command-line.  The options [1m-cwd[22m,  [1m-v[22m,  [1m-V[22m,  and [1m-display [22monly apply  to
       batch jobs.

       [4mQalter[24m  can be used to change the attributes of pending jobs. For array
       jobs with a mix of running and pending tasks (see the [1m-t [22moption below),
       modification  with  [4mqalter[24m  only affects the pending tasks.  [4mQalter[24m can
       change most of the characteristics of  a  job  (see  the  corresponding
       statements  in  the  OPTIONS section below), including those which were
       defined as embedded flags in the script file (see above).  Some  submit
       options, such as the job script, cannot be changed with I. qalter.

       [4mQresub[24m  allows the user to create jobs as copies of existing pending or
       running jobs. The copied jobs will have exactly the same attributes  as
       the  ones  from  which  they were copied, except with a new job ID. The
       only modification to the copied jobs supported by [4mqresub[24m is  assignment
       of  a  hold  state with the [1m-h [22moption. This option can be used to first
       copy a job and then change its attributes via [4mqalter[24m.

       Only a manager can use [4mqresub[24m on jobs submitted by another user.  Regu-
       lar users can only use [4mqresub[24m on their own jobs.

       For  [4mqsub[24m,  [4mqsh[24m,  [4mqrsh[24m,  and  [4mqlogin[24m the administrator and the user may
       define default request files (see [4msge_request[24m(5)) which can contain any
       of the options described below.  If an option in a default request file
       is understood by [4mqsub[24m and [4mqlogin[24m but not by [4mqsh[24m the option is  silently
       ignored if [4mqsh[24m is invoked. Thus you can maintain shared default request
       files for both [4mqsub[24m and [4mqsh[24m.

       A  cluster  wide   default   request   file   may   be   placed   under
       $SGE_ROOT/$SGE_CELL/common/sge_request.   User  private default request
       files  are  processed  under  the  locations   $HOME/.sge_request   and
       $cwd/.sge_request. The working directory local default request file has
       the highest precedence, then the home directory located file  and  then
       the  cluster  global  file.   The option arguments, the embedded script
       flags and the options in the default request files are processed in the
       following order:

              left to right in the script line,
              left to right in the default request files,
              from top to bottom of the script file ([4mqsub[24m only),
              from top to bottom of default request files,
              from left to right of the command line.

       In  other  words, the command line can be used to override the embedded
       flags and the default request settings.  The embedded  flags,  however,
       will override the default settings.

       [1mNote[22m,  that  the [4m-clear[24m option can be used to discard any previous set-
       tings at any time in a default request file,  in  the  embedded  script
       flags,  or in a command-line option. It is, however, not available with
       [4mqalter[24m.

       The options described below can be requested either hard or  soft.   By
       default,  all  requests are considered hard until the [1m-soft [22moption (see
       below) is encountered. The hard/soft status remains in effect until its
       counterpart  is  encountered again.  If all the hard requests for a job
       cannot be met, the job will not be scheduled.  Jobs which cannot be run
       at the present time remain spooled.

[1mOPTIONS[0m
       [1m-@ optionfile[0m
              Forces  [4mqsub[24m,  [4mqrsh[24m, [4mqsh[24m, or [4mqlogin[24m to use the options contained
              in [1moptionfile[22m. The indicated file may contain all valid options.
              Comment lines must start with a "#" sign.

       [1m-a date_time[0m
              Available for [4mqsub[24m and [4mqalter[24m only.

              Defines  or redefines the time and date at which a job is eligi-
              ble for execution. [1mDate_time [22mconforms to [[CC]]YY]MMDDhhmm.[ss],
              where:

              CC  denotes the century in 2 digits.
              YY  denotes the year in 2 digits.
              MM  denotes the month in 2 digits.
              DD  denotes the day in 2 digits.
              hh  denotes the hour in 2 digits.
              mm  denotes the minute in 2 digits.
              ss  denotes the seconds in 2 digits (default 00).

              If any of the optional date fields is omitted, the corresponding
              value of the current date is assumed. If CC is not specified,  a
              YY of < 70 means 20YY.
              Usage  of this option may cause unexpected results if the clocks
              of the hosts in the Grid Engine pool are out of sync. Also,  the
              proper  behavior of this option very much depends on the correct
              setting of the appropriate timezone, e.g. in the TZ  environment
              variable (see [4mdate[24m(1) for details), when the Grid Engine daemons
              [4msge_qmaster[24m(8) and [4msge_execd[24m(8) are invoked.

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-ac variable[=value],...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Adds the given name/value pair(s) to the  job's  context.  [1mValue[0m
              may  be  omitted.  Grid Engine appends the given argument to the
              list of context variables for the job.  Multiple [1m-ac[22m,  [1m-dc[22m,  and
              [1m-sc [22moptions may be given.  The order is important here.

              [4mQalter[24m  allows changing this option even while the job executes.

       [1m-A account_string[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Identifies the account to which the resource consumption of  the
              job  should  be charged. The [1maccount_string [22mmay be any arbitrary
              ASCII alphanumeric string but may not contain  "\n", "\t", "\r",
              "/", ":", "@", "\", "*",  or "?".  In the absence of this param-
              eter Grid Engine will place the default account string "sge"  in
              the accounting record of the job.

              [4mQalter[24m  allows changing this option even while the job executes.

       [1m-b y[es]|n[o][0m
              Available for [4mqsub[24m, [4mqrsh[24m only. [4mQalter[24m does  not  allow  changing
              this  option.  This option cannot be embedded in the script file
              itself.

              Gives the user the possibility to  indicate  explicitly  whether
              [1mcommand  [22mshould  be treated as binary or script. If the value of
              [1m-b [22mis 'y', then [1mcommand  [22mmay be a binary or script.  The [1mcommand[0m
              might  not  be  accessible  from  the  submission host.  Nothing
              except the path of the [1mcommand [22mwill be transferred from the sub-
              mission  host  to  the  execution  host.  Path  aliasing will be
              applied to the path of [1mcommand [22mbefore [1mcommand [22mwill be  executed.

              If  the value of [1m-b [22mis 'n' then [1mcommand [22mneeds to be a script and
              it will be handled as script. The script file has to be accessi-
              ble by the submission host. It will be transferred to the execu-
              tion host.  [4mqsub[24m/[4mqrsh[24m  will  search  directive  prefixes  within
              script.

              [4mqsub[24m  will  implicitly use [1m-b n [22mwhereas [4mqrsh[24m will apply the [1m-b y[0m
              option if nothing else is specified.

       [1m-c occasion_specifier[0m
              Available for [4mqsub[24m and [4mqalter[24m only.

              Defines or redefines whether the job should be checkpointed, and
              if so, under what circumstances. The specification of the check-
              pointing occasions with this option overwrites  the  definitions
              of  the  [4mwhen[24m  parameter  in  the checkpointing environment (see
              [4mcheckpoint[24m(5)) referenced by the [4mqsub[24m  [4m-ckpt[24m  switch.   Possible
              values for [1moccasion_specifier [22mare

              n           no checkpoint is performed.
              s           checkpoint when batch server is shut down.
              m           checkpoint at minimum CPU interval.
              x           checkpoint when job gets suspended.
              <interval>  checkpoint in the specified time interval.

              The  minimum  CPU interval is defined in the queue configuration
              (see [4mqueue_conf[24m(5) for details).  <interval> has to be specified
              in  the  format  hh:mm:ss.   The  maximum  of <interval> and the
              queue's minimum CPU interval is used if <interval> is specified.
              This  is  done  to  ensure  that  a machine is not overloaded by
              checkpoints being generated too frequently.

       [1m-ckpt ckpt_name[0m
              Available for [4mqsub[24m and [4mqalter[24m only.

              Selects the checkpointing environment (see [4mcheckpoint[24m(5)) to  be
              used  for  checkpointing  the job. Also declares the job to be a
              checkpointing job.

       [1m-clear [22mAvailable for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, and [4mqlogin[24m only.

              Causes all elements of the  job  to  be  reset  to  the  initial
              default  status  prior  to  applying  any modifications (if any)
              appearing in this specific command.

       [1m-cwd   [22mAvailable for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m and [4mqalter[24m only.

              Execute the job from the current working directory.  This switch
              will  activate Grid Engine's path aliasing facility, if the cor-
              responding configuration files are present (see [4msge_aliases[24m(5)).

              In  the  case  of [4mqalter[24m, the previous definition of the current
              working directory will be overwritten if [4mqalter[24m is executed from
              a different directory than the preceding [4mqsub[24m or [4mqalter[24m.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-C prefix_string[0m
              Available for [4mqsub[24m and qrsh with script submission (-b n).

              [4mPrefix_string[24m  defines  the  prefix that declares a directive in
              the job's command. The  prefix  is  not  a  job  attribute,  but
              affects  the  behavior  of  [4mqsub[24m  and  [4mqrsh[24m. If [1mprefix [22mis a null
              string, the command will not be scanned for embedded directives.
              The  directive  prefix  consists  of two ASCII characters which,
              when appearing in the first two bytes of a script line, indicate
              that  what  follows  is  an Grid Engine command.  The default is
              "#$".
              The user should be aware  that  changing  the  first  delimiting
              character  can  produce  unforeseen  side effects. If the script
              file contains anything other than a "#" character in  the  first
              byte  position of the line, the shell processor for the job will
              reject the line and may exit the job prematurely.
              If the -C option is present in the script file, it is ignored.

       [1m-dc variable,...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Removes the given variable(s) from the job's context.   Multiple
              [1m-ac[22m, [1m-dc[22m, and [1m-sc [22moptions may be given.  The order is important.

              [4mQalter[24m allows changing this option even while the job  executes.

       [1m-display display_specifier[0m
              Available for [4mqsh[24m only.

              Directs  [4mxterm[24m(1)  to  use [1mdisplay_specifier [22min order to contact
              the X server.  The [1mdisplay_specifier [22mhas to contain the hostname
              part  of  the display name (e.g. myhost:1).  Local display names
              (e.g. :0) cannot be used in grid environments.  Values set  with
              the [1m-display [22moption overwrite settings from the submission envi-
              ronment and from [1m-v [22mcommand line options.

       [1m-dl date_time[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Specifies the deadline initiation time in  [[CC]YY]MMDDhhmm[.SS]
              format  (see  [1m-a  [22moption above). The deadline initiation time is
              the time at which a deadline job has to reach top priority to be
              able  to  complete  within a given deadline. Before the deadline
              initiation time the priority of a deadline job  will  be  raised
              steadily  until it reaches the maximum as configured by the Grid
              Engine administrator.
              This option is applicable only for users allowed to submit dead-
              line jobs.

       [1m-e [[hostname]:]path,...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Defines or redefines the path used for the standard error stream
              of the job. For [4mqsh[24m, [4mqrsh[24m and [4mqlogin[24m  only  the  standard  error
              stream  of prolog and epilog is redirected.  If the [1mpath [22mconsti-
              tutes an absolute path name, the error-path attribute of the job
              is set to [1mpath[22m, including the [1mhostname[22m. If the path name is rel-
              ative, Grid Engine expands [1mpath [22meither with the current  working
              directory  path  (if  the [1m-cwd [22mswitch (see above) is also speci-
              fied) or with the home directory path. If [1mhostname  [22mis  present,
              the  standard  error  stream will be placed in the corresponding
              location only if the job runs on the specified host. If the path
              contains a ":" without a [1mhostname[22m, a leading ":" has to be spec-
              ified.

              By default the file name for interactive jobs is [4m/dev/null[24m.  For
              batch  jobs  the default file name has the form [4mjob_name.[24me[4mjob_id[0m
              and [4mjob_name.[24me[4mjob_id[24m.[1mtask_id [22mfor array job tasks (see [1m-t  [22moption
              below).

              If  [1mpath  [22mis  a  directory, the standard error stream of the job
              will be put in this directory under the default file  name.   If
              the  pathname  contains  certain  pseudo  environment variables,
              their value will be expanded at runtime of the job and  will  be
              used to constitute the standard error stream path name. The fol-
              lowing pseudo environment variables are supported currently:

              $HOME       home directory on execution machine
              $USER       user ID of job owner
              $JOB_ID     current job ID
              $JOB_NAME   current job name (see [1m-N [22moption)
              $HOSTNAME   name of the execution host
              $TASK_ID    array job task index number

              Alternatively to $HOME the tilde sign "~" can be used as  common
              in [4mcsh[24m(1) or [4mksh[24m(1).  Note, that the "~" sign also works in com-
              bination with user names, so that "~<user>" expands to the  home
              directory  of <user>. Using another user ID than that of the job
              owner requires corresponding permissions, of course.

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-hard  [22mAvailable for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Signifies that all resource requirements following in  the  com-
              mand  line  will  be  hard requirements and must be satisfied in
              full before a job can be scheduled.
              As Grid Engine scans the command line and script file  for  Grid
              Engine  options  and  parameters  it  builds a list of resources
              required by a job. All such resource requests are considered  as
              absolutely  essential  for  the  job  to  commence. If the [1m-soft[0m
              option (see below) is encountered during the scan then all  fol-
              lowing  resources are designated as "soft requirements" for exe-
              cution, or "nice-to-have, but not essential". If the [1m-hard  [22mflag
              is  encountered  at  a  later  stage  of  the scan, all resource
              requests following it once again become "essential".  The  [1m-hard[0m
              and [1m-soft [22moptions in effect act as "toggles" during the scan.

       [1m-h | -h {u|s|o|n|U|O|S}...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m, [4mqalter[24m and [4mqresub[24m.

              List  of holds to place on a job, a task or some tasks of a job.

              `u'  denotes a user hold.
              `s'  denotes a system hold.
              `o'  denotes a operator hold.
              `n'  denotes no hold.

              As long as any hold other than `n' is assigned to  the  job  the
              job  is  not  eligible  for execution. Holds can be released via
              [4mqalter[24m and [4mqrls[24m(1).  In case of [4mqalter[24m this is supported by  the
              following additional option specifiers for the [1m-h [22mswitch:

              `U'  removes a user hold.
              `S'  removes a system hold.
              `O'  removes a operator hold.

              Grid  Engine managers can assign and remove all hold types, Grid
              Engine operators can assign and remove user and operator  holds,
              and users can only assign or remove user holds.

              In  the  case of [4mqsub[24m only user holds can be placed on a job and
              thus only the first form of the option with the [1m-h [22mswitch  alone
              is allowed.  As opposed to this, [4mqalter[24m requires the second form
              described above.

              An alternate means to assign hold is provided  by  the  [4mqhold[24m(1)
              facility.

              If  the  job is a array job (see the [1m-t [22moption below), all tasks
              specified via [1m-t [22mare affected by  the  [1m-h  [22moperation  simultane-
              ously.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-help  [22mPrints  a listing of all options.

       [1m-hold_jid wc_job_list[0m
              Available  for  [4mqsub[24m,  [4mqrsh[24m,  and [4mqalter[24m only. See [4msge_types[24m(1).
              for [1m528[0m

              [1mDefines or redefines the job dependency list  of  the  submitted[0m
              [1mjob.  A reference by job name or pattern is only accepted if the[0m
              [1mreferenced job is owned by the same user as the  referring  job.[0m
              [1mThe  submitted job is not eligible for execution unless all jobs[0m
              [1mreferenced in the comma-separated job id and/or  job  name  list[0m
              [1mhave  completed.   If any of the referenced jobs exits with exit[0m
              [1mcode 100, the submitted job will remain  ineligible  for  execu-[0m
              [1mtion.[0m

              [1mWith  the help of job names or regular pattern one can specify a[0m
              [1mjob dependency on multiple jobs satisfying the  regular  pattern[0m
              [1mor  on  all  jobs with the requested name. The name dependencies[0m
              [1mare resolved at submit time and can only be changed via  qalter.[0m
              [1mNew  jobs  or  name changes of other jobs will not be taken into[0m
              [1maccount.[0m

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-i [[hostname]:]file,...[0m
              Available for [4mqsub[24m, and [4mqalter[24m only.

              Defines or redefines the file used for the standard input stream
              of  the  job.  If the [4mfile[24m constitutes an absolute filename, the
              input-path attribute of the job is set to  [1mpath[22m,  including  the
              [1mhostname[22m. If the path name is relative, Grid Engine expands [1mpath[0m
              either with the current working  directory  path  (if  the  [1m-cwd[0m
              switch (see above) is also specified) or with the home directory
              path. If [1mhostname [22mis present, the standard input stream will  be
              placed in the corresponding location only if the job runs on the
              specified host. If the path contains a ":" without a [1mhostname[22m, a
              leading ":" has to be specified.

              By default /dev/null is the input stream for the job.

              It  is  possible  to  use certain pseudo variables, whose values
              will be expanded at runtime of the  job  and  will  be  used  to
              express  the standard input stream as described in the [4m-e[24m option
              for the standard error stream.

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-inherit[0m
              Available only for [4mqrsh[24m and [4mqmake[24m(1).

              [4mqrsh[24m allows the user to start a task  in  an  already  scheduled
              parallel  job.   The option [1m-inherit [22mtells [4mqrsh[24m to read a job id
              from the environment variable JOB_ID  and  start  the  specified
              command  as  a  task in this job. Please note that in this case,
              the hostname of the host where the command will be executed must
              precede the command to execute; the syntax changes to

              [1mqrsh  -inherit [22m[ [1mother options [22m] [1mhostname command [22m[ [1mcommand_args[0m
              ]

              Note also, that in combination with [1m-inherit[22m, most other command
              line options will be ignored.  Only the options [1m-verbose[22m, [1m-v [22mand
              [1m-V [22mwill be interpreted.  As a replacement to option [1m-cwd  [22mplease
              use [1m-v PWD[22m.

              Usually  a  task should have the same environment (including the
              current working directory) as the corresponding job, so specify-
              ing the option [1m-V [22mshould be suitable for most applications.

              [4mNote:[24m  If  in your system the qmaster tcp port is not configured
              as a service, but rather via the environment variable  SGE_QMAS-
              TER_PORT, make sure that this variable is set in the environment
              when calling [4mqrsh[24m or [4mqmake[24m with the [1m-inherit [22moption. If you call
              [4mqrsh[24m or [4mqmake[24m with the [1m-inherit [22moption from within a job script,
              export SGE_QMASTER_PORT with the  option  "-v  SGE_QMASTER_PORT"
              either as a command argument or an embedded directive.

       [1m-j y[es]|n[o][0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Specifies whether or not the standard error stream of the job is
              merged into the standard output stream.
              If both the [1m-j y [22mand the [1m-e [22moptions  are  present,  Grid  Engine
              sets but ignores the error-path attribute.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-js job_share[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Defines  or redefines the job share of the job relative to other
              jobs.  Job share is an unsigned integer value.  The default  job
              share value for jobs is 0.

              The  job  share  influences  the Share Tree Policy and the Func-
              tional Policy. It has no effect  on  the  Urgency  and  Override
              Policies  (see  [4mshare_tree[24m(5), [4msched_conf[24m(5) and the [4mGrid[24m [4mEngine[0m
              [4mInstallation[24m [4mand[24m [4mAdministration[24m [4mGuide[24m for further information on
              the resource management policies supported by Grid Engine).

              In case of the Share Tree Policy, users can distribute the tick-
              ets to which they are currently entitled among their jobs  using
              different shares assigned via [1m-js[22m. If all jobs have the same job
              share value, the tickets are distributed evenly. Otherwise, jobs
              receive tickets relative to the different job shares. Job shares
              are treated like an additional level in the share  tree  in  the
              latter case.

              In  connection  with the Functional Policy, the job share can be
              used to weight jobs within the functional job category.  Tickets
              are  distributed  relative  to any uneven job share distribution
              treated as a virtual share  distribution  level  underneath  the
              functional job category.

              If both the Share Tree and the Functional Policy are active, the
              job shares will have an effect in both policies, and the tickets
              independently  derived  in  each  of them are added to the total
              number of tickets for each job.

       [1m-l resource=value[22m,...
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Launch the job in a Grid Engine queue meeting the given resource
              request  list.   In  case  of  [4mqalter[24m the previous definition is
              replaced by the specified one.
              [4mcomplex[24m(5) describes how a list of available resources and their
              associated valid value specifiers can be obtained.
              There  may  be multiple [1m-l [22mswitches in a single command. You may
              request multiple [1m-l [22moptions to be soft or hard both in the  same
              command  line.  In  case  of  a  serial job multiple [1m-l [22mswitches
              refine the definition for the sought queue.

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-m b|e|a|s|n,...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Defines or redefines under which circumstances  mail  is  to  be
              sent to the job owner or to the users defined with the [1m-M [22moption
              described below. The option arguments have the  following  mean-
              ing:

              `b'     Mail is sent at the beginning of the job.
              `e'     Mail is sent at the end of the job.
              `a'     Mail is sent when the job is aborted or
                      rescheduled.
              `s'     Mail is sent when the job is suspended.
              `n'     No mail is sent.

              Currently no mail is sent when a job is suspended.

              [4mQalter[24m  allows  changing  the  b, e, and a option arguments even
              while the job executes. The modification of the b  option  argu-
              ment  will only be in effect after a restart or migration of the
              job, however.

       [1m-M user[@host],...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Defines or redefines the list of users to which the server  that
              executes  the  job  has  to  send mail, if the server sends mail
              about the job.  Default is the  job  owner  at  the  originating
              host.

              [4mQalter[24m  allows changing this option even while the job executes.

       [1m-masterq wc_queue_list[0m
              Available for [4mqsub[24m, [4mqrsh[24m, [4mqsh[24m, [4mqlogin[24m and [4mqalter[24m.  Only meaning-
              ful for parallel jobs, i.e. together with the -pe option.

              Defines or redefines a list of cluster queues, queue domains and
              queue instances which may be used to become the so called [4mmaster[0m
              [4mqueue[24m  of  this  parallel  job.  A  more detailed description of
              [4mwc_queue_list[24m can be found in [4msge_types[24m(1).  The [4mmaster[24m [4mqueue[24m is
              defined  as  the  queue  where  the parallel job is started. The
              other queues to which the parallel job spawns tasks  are  called
              [4mslave[24m [4mqueues[24m.  A parallel job only has one [4mmaster[24m [4mqueue[24m.

              This  parameter has all the properties of a resource request and
              will be merged with requirements  derived  from  the  [1m-l  [22moption
              described above.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-notify[0m
              Available for [4mqsub[24m, [4mqrsh[24m (with command) and [4mqalter[24m only.

              This flag, when set causes Grid Engine to send "warning" signals
              to a running job prior to sending the signals themselves.  If  a
              SIGSTOP  is pending, the job will receive a SIGUSR1 several sec-
              onds before the SIGSTOP. If a SIGKILL is pending, the  job  will
              receive  a  SIGUSR2  several  seconds  before  the SIGKILL.  The
              amount of time delay is controlled by the  [1mnotify  [22mparameter  in
              each queue configuration (see [4mqueue_conf[24m(5)).

              Note  that the Linux operating system "misused" the user signals
              SIGUSR1 and SIGUSR2 in some early Posix thread  implementations.
              You  might not want to use the [1m-notify [22moption if you are running
              multi-threaded applications in your jobs under  Linux,  particu-
              larly on 2.0 or earlier kernels.

              [4mQalter[24m  allows changing this option even while the job executes.

       [1m-now y[es]|n[o][0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqlogin[24m and [4mqrsh[24m.

              [1m-now y [22mtries to start the job immediately or  not  at  all.  The
              command  returns  0 on success, or 1 on failure (also if the job
              could not be scheduled immediately).  For array  jobs  submitted
              with  the [1m-now [22moption, if all tasks cannot be immediately sched-
              uled, no tasks are scheduled.  [1m-now y [22mis default for [4mqsh[24m, [4mqlogin[0m
              and [4mqrsh[0m
              With  the  [1m-now  n  [22moption, the job will be put into the pending
              queue if it cannot be executed immediately. [1m-now  n  [22mis  default
              for [4mqsub[24m.

       [1m-N name[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              The  name of the job. The name can be any printable set of char-
              acters except "\n", "\t", "\r", "/", ":",  "@",  "\",  "*",  and
              "?",  and  it has to start with an alphabetic character. Invalid
              job names will be denied at submit time.
              If the [1m-N [22moption is not present, Grid Engine assigns the name of
              the  job script to the job after any directory pathname has been
              removed from the script-name. If the script is read  from  stan-
              dard input, the job name defaults to STDIN.
              In  the  case of [4mqsh[24m or [4mqlogin[24m with the [1m-N [22moption is absent, the
              string `INTERACT' is assigned to the job.
              In the case of [4mqrsh[24m if the [1m-N [22moption is  absent,  the  resulting
              job  name  is determined from the qrsh command line by using the
              argument string up to the first occurrence  of  a  semicolon  or
              whitespace and removing the directory pathname.

              [4mQalter[24m  allows changing this option even while the job executes.

       [1m-noshell[0m
              Available only for [4mqrsh[24m with a command line.

              Do not start the command line given to [4mqrsh[24m in  a  user's  login
              shell, i.e.  execute it without the wrapping shell.

              This  option can be used to speed up execution as some overhead,
              like the shell startup and sourcing the shell resource files, is
              avoided.

              This  option  can only be used if no shell-specific command line
              parsing is required. If the command line contains  shell  syntax
              like  environment  variable  substitution  or  (back) quoting, a
              shell must be started.  In this case,  either  do  not  use  the
              [1m-noshell [22moption or include the shell call in the command line.

              Example:
              qrsh echo '$HOSTNAME'
              Alternative call with the -noshell option
              qrsh -noshell /bin/tcsh -f -c 'echo $HOSTNAME'

       [1m-nostdin[0m
              Available only for [4mqrsh[24m.

              Suppress  the  input stream STDIN - [4mqrsh[24m will pass the option -n
              to the [4mrsh[24m(1) command. This is especially  useful,  if  multiple
              tasks  are  executed  in  parallel using [4mqrsh[24m, e.g. in a [4mmake[24m(1)
              process - it would be undefined, which  process  would  get  the
              input.

       [1m-o [[hostname]:]path,...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              The  path  used  for  the standard output stream of the job. The
              [1mpath [22mis handled as described in the [1m-e [22moption for  the  standard
              error stream.

              By  default  the  file  name  for  standard  output has the form
              [4mjob_name.[24mo[4mjob_id[24m  and  [4mjob_name.[24mo[4mjob_id[24m.[1mtask_id  [22mfor  array  job
              tasks (see [1m-t [22moption below).

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-ot override_tickets[0m
              Available for [4mqalter[24m only.

              Changes  the  number  of override tickets for the specified job.
              Requires manager/operator privileges.

       [1m-P project_name[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Specifies the project to which this job is assigned. The  admin-
              istrator  needs to give permission to individual users to submit
              jobs to a specific project. (see [1m-aprj [22moption to [4mqconf[24m(1)).

       [1m-p priority[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Defines or redefines the priority of the job relative  to  other
              jobs.   Priority  is an integer in the range -1023 to 1024.  The
              default priority value for jobs is 0.

              Users may only decrease the priority of their jobs.  Grid Engine
              managers and administrators may also increase the priority asso-
              ciated with jobs. If a pending job has higher  priority,  it  is
              earlier  eligible for being dispatched by the Grid Engine sched-
              uler.


       [1m-pe parallel_environment n[-[m]]|[-]m,...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Parallel programming environment (PE) to instantiate. The  range
              descriptor  behind  the PE name specifies the number of parallel
              processes to be run. Grid Engine will allocate  the  appropriate
              resources  as  available.  The  [4msge_pe[24m(5)  manual  page contains
              information about the definition of PEs and about how to  obtain
              a list of currently valid PEs.
              You  can  specify  a  PE name which uses the wildcard character,
              "*".  Thus the request "pvm*" will match any  parallel  environ-
              ment  with a name starting with the string "pvm". In the case of
              multiple  parallel  environments  whose  names  match  the  name
              string,  the  parallel environment with the most available slots
              is chosen.
              The range specification is a list of range  expressions  of  the
              form  "n-m", where n and m are positive, non-zero integers.  The
              form "n" is equivalent to "n-n".  The form "-m" is equivalent to
              "1-m".   The form "n-" is equivalent to "n-infinity".  The range
              specification is processed as follows:  The  largest  number  of
              queues  requested is checked first. If enough queues meeting the
              specified attribute list are available, all  are  allocated.  If
              not, the next smaller number of queues is checked, and so forth.
              If additional [1m-l [22moptions are present, they restrict the  set  of
              eligible queues for the parallel job.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-q wc_queue_list[0m
              Available for [4mqsub[24m, [4mqrsh[24m, [4mqsh[24m, [4mqlogin[24m and [4mqalter[24m.

              Defines  or redefines a list of cluster queues, queue domains or
              queue instances which may be used to execute  this  job.  Please
              find  a  description  of  [4mwc_queue_list[24m  in  [4msge_types[24m(1).  This
              parameter has all the properties of a resource request and  will
              be merged with requirements derived from the [1m-l [22moption described
              above.

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-R y[es]|n[o][0m
              Available for [4mqsub[24m, [4mqrsh[24m, [4mqsh[24m, [4mqlogin[24m and [4mqalter[24m.

              Indicates whether a reservation for this  job  should  be  done.
              Reservation  is never done for immediate jobs, i.e. jobs submit-
              ted using the [1m-now yes [22moption.  Please note that  regardless  of
              the reservation request, job reservation might be disabled using
              max_reservation in [4msched_conf[24m(5) and might be limited only to  a
              certain number of high priority jobs.

              By default jobs are submitted with the [1m-R n [22moption.

       [1m-r y[es]|n[o][0m
              Available for [4mqsub[24m and [4mqalter[24m only.

              Identifies  the  ability  of  a  job to be rerun or not.  If the
              value of [1m-r [22mis 'yes', the job will  be  rerun  if  the  job  was
              aborted without leaving a consistent exit state.  (This is typi-
              cally the case if the node on which the job is running crashes).
              If  [1m-r  [22mis  'no',  the  job  will not be rerun under any circum-
              stances.
              Interactive jobs submitted with [4mqsh,[24m  [4mqrsh[24m  or  [4mqlogin[24m  are  not
              rerunnable.

              [4mQalter[24m  allows changing this option even while the job executes.



       [1m-sc variable[=value],...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Sets the given name/value pairs as the job's context. [1mValue  [22mmay
              be  omitted.  Grid  Engine replaces the job's previously defined
              context with the one given as the argument.  Multiple [1m-ac[22m,  [1m-dc[22m,
              and [1m-sc [22moptions may be given.  The order is important.
              Contexts  provide  a  way to dynamically attach and remove meta-
              information to and from a job. The  context  variables  are  [1mnot[0m
              passed to the job's execution context in its environment.

              [4mQalter[24m  allows changing this option even while the job executes.

       [1m-shell y[es]|n[o][0m
              Available only for [4mqsub[24m.

              [1m-shell n [22mcauses qsub to execute the command line directly, as if
              by  [4mexec[24m(2).   No  command  shell  will be executed for the job.
              This option only applies when [1m-b y [22mis also used.  Without [1m-b  y[22m,
              [1m-shell n [22mhas no effect.

              This  option can be used to speed up execution as some overhead,
              like the shell startup and sourcing the shell resource files  is
              avoided.

              This  option  can only be used if no shell-specific command line
              parsing is required. If the command line contains shell  syntax,
              like  environment  variable  substitution  or  (back) quoting, a
              shell must be started.  In this  case  either  do  not  use  the
              [1m-shell  n  [22moption  or  execute the shell as the command line and
              pass the path to the executable as a parameter.

              If a job executed with the [1m-shell n [22moption fails due to  a  user
              error,  such  as an invalid path to the executable, the job will
              enter the error state.

              [1m-shell y [22mcancels the effect of a previous [1m-shell n[22m.   Otherwise,
              it has no effect.

              See [1m-b [22mand [1m-noshell [22mfor more information.

       [1m-soft  [22mAvailable for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m only.

              Signifies  that  all resource requirements following in the com-
              mand line will be soft requirements and are to be filled  on  an
              "as available" basis.
              As  Grid  Engine scans the command line and script file for Grid
              Engine options and parameters, it builds  a  list  of  resources
              required  by  the job. All such resource requests are considered
              as absolutely essential for the job to commence.  If  the  [1m-soft[0m
              option  is  encountered  during  the  scan  then  all  following
              resources are designated as "soft requirements"  for  execution,
              or  "nice-to-have,  but  not  essential". If the [1m-hard [22mflag (see
              above) is encountered at a later stage of the scan, all resource
              requests  following  it once again become "essential". The [1m-hard[0m
              and [1m-soft [22moptions in effect act as "toggles" during the scan.

       [1m-sync y[es]|n[o][0m
              Available for [4mqsub[24m.

              [1m-sync y [22mcauses [4mqsub[24m to wait for the job to complete before exit-
              ing.   If  the job completes successfully, [4mqsub's[24m exit code will
              be that of the completed job.  If the job fails to complete suc-
              cessfully,  [4mqsub[24m  will  print out a error message indicating why
              the job failed and will have an exit code  of  1.   If  [4mqsub[24m  is
              interrupted, e.g. with CTRL-C, before the job completes, the job
              will be canceled.
              With the [1m-sync n [22moption, [4mqsub[24m will exit with an exit code  of  0
              as  soon  as  the  job  is  submitted  successfully.  [1m-sync n [22mis
              default for [4mqsub[24m.
              If [1m-sync y [22mis used in conjunction with [1m-now y[22m, [4mqsub[24m will  behave
              as though only [1m-now y [22mwere given until the job has been success-
              fully scheduled, after which time [4mqsub[24m  will  behave  as  though
              only [1m-sync y [22mwere given.
              If  [1m-sync  y [22mis used in conjunction with [1m-t n[-m[:i]][22m, [4mqsub[24m will
              wait for all the job's tasks to complete before exiting.  If all
              the  job's tasks complete successfully, [4mqsub's[24m exit code will be
              that of the first completed job tasks with a non-zero exit code,
              or  0 if all job tasks exited with an exit code of 0.  If any of
              the job's tasks fail to complete successfully, [4mqsub[24m  will  print
              out  an  error message indicating why the job task(s) failed and
              will have an exit code of 1.  If [4mqsub[24m is interrupted, e.g.  with
              CTRL-C, before the job completes, all of the job's tasks will be
              canceled.

       [1m-S [[hostname]:]pathname,...[0m
              Available for [4mqsub[24m, [4mqsh[24m and [4mqalter[24m.

              Specifies the interpreting shell for the job. Only one  [1mpathname[0m
              component  without  a  [1mhost [22mspecifier is valid and only one path
              name for a given host is allowed. Shell paths with host  assign-
              ments  define  the interpreting shell for the job if the host is
              the execution host. The shell path without host specification is
              used  if  the  execution  host  matches none of the hosts in the
              list.

              Furthermore, the pathname can be constructed with  pseudo  envi-
              ronment variables as described for the [1m-e [22moption above.

              In  the  case of [4mqsh[24m the specified shell path is used to execute
              the corresponding command interpreter in the [4mxterm[24m(1)  (via  its
              [4m-e[24m option) started on behalf of the interactive job.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-t n[-m[:s]][0m
              Available for [4mqsub[24m and [4mqalter[24m only.

              Submits  a so called [4mArray[24m [4mJob[24m, i.e. an array of identical tasks
              being differentiated only by an index number and  being  treated
              by Grid Engine almost like a series of jobs. The option argument
              to [1m-t [22mspecifies the number of array job tasks and the index num-
              ber  which  will be associated with the tasks. The index numbers
              will be exported to the job tasks via the  environment  variable
              [1mSGE_TASK_ID[22m.  The  option arguments n, m and s will be available
              through the environment variables [1mSGE_TASK_FIRST[22m,  [1mSGE_TASK_LAST[0m
              and  [1mSGE_TASK_STEPSIZE[22m.

              Following restrictions apply to the values n and m:

                     1 <= n <= MIN(2^31-1, max_aj_tasks)
                     1 <= m <= MIN(2^31-1, max_aj_tasks)
                     n <= m

              [4mmax_aj_tasks[24m  is  defined  in  the  cluster  configuration  (see
              [4msge_conf[24m(5))

              The task id range specified in the option argument may be a sin-
              gle  number,  a  simple  range of the form n-m or a range with a
              step size. Hence, the task id range specified  by  2-10:2  would
              result in the task id indexes 2, 4, 6, 8, and 10, for a total of
              5  identical  tasks,  each   with   the   environment   variable
              SGE_TASK_ID containing one of the 5 index numbers.

              All  array  job  tasks  inherit  the  same resource requests and
              attribute definitions as specified in the [4mqsub[24m or [4mqalter[24m command
              line, except for the [1m-t [22moption. The tasks are scheduled indepen-
              dently and, provided enough resources exist, concurrently,  very
              much  like  separate jobs.  However, an array job or a sub-array
              there of can be accessed as  a  single  unit  by  commands  like
              [4mqmod[24m(1) or [4mqdel[24m(1).  See the corresponding manual pages for fur-
              ther detail.

              Array jobs are commonly used to execute the same type of  opera-
              tion  on  varying input data sets correlated with the task index
              number. The number of tasks in a array job is unlimited.

              STDOUT and STDERR of array job tasks will be written  into  dif-
              ferent files with the default location

              <jobname>.['e'|'o']<job_id>'.'<task_id>

              In  order  to  change  this  default, the [1m-e [22mand [1m-o [22moptions (see
              above) can be used together with the  pseudo  environment  vari-
              ables   $HOME,   $USER,   $JOB_ID,   $JOB_NAME,  $HOSTNAME,  and
              $SGE_TASK_ID.

              Note, that you can use the output redirection to divert the out-
              put  of  all tasks into the same file, but the result of this is
              undefined.



       [1m-u username,...[0m
              Available for [4mqalter[24m only. Changes are only made on  those  jobs
              which  were  submitted  by  users specified in the list of user-
              names.  For managers it is possible to use  the  [1mqalter  -u  '*'[0m
              command to modify all jobs of all users.

              If you use the [1m-u [22mswitch it is not permitted to specify an addi-
              tional [4mwc_job_range_list[24m.

       [1m-v variable[=value],...[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m and [4mqalter[24m.

              Defines or redefines the environment variables to be exported to
              the  execution  context of the job.  If the [1m-v [22moption is present
              Grid Engine will add the environment variables defined as  argu-
              ments  to  the switch and, optionally, values of specified vari-
              ables, to the execution context of the job.

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1m-verbose[0m
              Available only for [4mqrsh[24m and [4mqmake[24m(1).

              Unlike [4mqsh[24m and [4mqlogin[24m, [4mqrsh[24m does not  output  any  informational
              messages  while  establishing  the  session,  compliant with the
              standard [4mrsh[24m(1) and [4mrlogin[24m(1) system calls.  If the option [1m-ver-[0m
              [1mbose  [22mis  set,  [4mqrsh[24m  behaves  like the [4mqsh[24m and [4mqlogin[24m commands,
              printing information  about  the  process  of  establishing  the
              [4mrsh[24m(1) or [4mrlogin[24m(1) session.

       [1m-verify[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m.

              Instead  of  submitting a job, prints detailed information about
              the would-be job as though [4mqstat[24m(1) -j were used, including  the
              effects of command-line parameters and the external environment.

       [1m-V     [22mAvailable for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m [4mwith[24m [4mcommand[24m, [4mqalter[24m and [4mqresub[24m.

              Specifies that all environment variables active within the  [4mqsub[0m
              utility be exported to the context of the job.

       [1m-w e[22m|[1mw[22m|[1mn[22m|[1mv[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m, [4mqlogin[24m and [4mqalter[24m.

              Specifies  a validation level applied to the job to be submitted
              ([4mqsub[24m, [4mqlogin[24m, and [4mqsh[24m) or the specified  queued  job  ([4mqalter[24m).
              The information displayed indicates whether the job can possibly
              be scheduled assuming  an  empty  system  with  no  other  jobs.
              Resource requests exceeding the configured maximal thresholds or
              requesting unavailable resource attributes are  possible  causes
              for jobs to fail this validation.

              The  specifiers  e,  w,  n and v define the following validation
              modes:

              `e'  error - jobs with invalid requests will be
                   rejected; the default for [4mqrsh[24m, [4mqsh[0m
                   and [4mqlogin[24m.
              `w'  warning - only a warning will be displayed
                   for invalid requests.
              `n'  none - switches off validation; the default for
                   [4mqsub[24m and [4mqalter[24m.
              `v'  verify - does not submit the job but prints an
                   extensive validation report.

              Note, that the necessary checks are  performance  consuming  and
              hence the checking is switched off by default.

              Note  also,  that the reasons for job requirements being invalid
              with respect to resource availability of queues are displayed in
              the  "[1m-w  v[22m" case using the format as described for the [4mqstat[24m(1)
              [1m-F [22moption (see description of [1mFull Format [22min section [1mOUTPUT FOR-[0m
              [1mMATS [22mof the [4mqstat[24m(1) manual page.

       [1m-wd working_dir[0m
              Available for [4mqsub[24m, [4mqsh[24m, [4mqrsh[24m and [4mqalter[24m only.

              Execute  the  job  from  the directory specified in working_dir.
              This switch will activate Grid Engine's path aliasing  facility,
              if  the  corresponding  configuration  files  are  present  (see
              [4msge_aliases[24m(5)).

              [4mQalter[24m allows changing this option even while the job  executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1mcommand[0m
              Available for [4mqsub[24m and [4mqrsh[24m only.

              The job's scriptfile or binary.  If not present or if the  oper-
              and  is  the  single-character string '-', [4mqsub[24m reads the script
              from standard input.

       [1mcommand_args[0m
              Available for [4mqsub[24m, [4mqrsh[24m and [4mqalter[24m only.

              Arguments to the job. Not valid if the script  is  entered  from
              standard input.

              [4mQalter[24m  allows changing this option even while the job executes.
              The modified parameter will only be in effect after a restart or
              migration of the job, however.

       [1mxterm_args[0m
              Available for [4mqsh[24m only.

              Arguments to the [4mxterm[24m(1) executable, as defined in the configu-
              ration.  For details, refer to [4msge_conf[24m(5)).

[1mENVIRONMENTAL VARIABLES[0m
       [1mSGE_ROOT       [22mSpecifies the location of the Grid Engine standard  con-
                      figuration files.

       [1mSGE_CELL       [22mIf  set,  specifies  the  default  Grid  Engine cell. To
                      address a Grid Engine cell [4mqsub[24m, [4mqsh[24m, [4mqlogin[24m  or  [4mqalter[0m
                      use (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. [1mdefault[22m.


       [1mSGE_DEBUG_LEVEL[0m
                      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.

       [1mSGE_QMASTER_PORT[0m
                      If set, specifies the tcp port on  which  [4msge_qmaster[24m(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.

       DISPLAY        For [4mqsh[24m jobs the DISPLAY has to be specified at job sub-
                      mission.  If the DISPLAY is not set by using  the  [1m-dis-[0m
                      [1mplay [22mor the [1m-v [22mswitch, the contents of the DISPLAY envi-
                      ronment variable are used as default.

       In addition to those environment variables specified to be exported  to
       the  job  via the [1m-v [22mor the [1m-V [22moption (see above) [4mqsub[24m, [4mqsh[24m, and [4mqlogin[0m
       add the following variables with the indicated values to  the  variable
       list:


       [1mSGE_O_HOME     [22mthe home directory of the submitting client.

       [1mSGE_O_HOST     [22mthe  name  of the host on which the submitting client is
                      running.

       [1mSGE_O_LOGNAME  [22mthe LOGNAME of the submitting client.

       [1mSGE_O_MAIL     [22mthe MAIL of the submitting  client.  This  is  the  mail
                      directory of the submitting client.

       [1mSGE_O_PATH     [22mthe executable search path of the submitting client.

       [1mSGE_O_SHELL    [22mthe SHELL of the submitting client.

       [1mSGE_O_TZ       [22mthe time zone of the submitting client.

       [1mSGE_O_WORKDIR  [22mthe  absolute  path  of the current working directory of
                      the submitting client.

       Furthermore, Grid Engine sets additional variables into the job's envi-
       ronment, as listed below.

       ARC

       SGE_ARCH       The  Grid  Engine architecture name of the node on which
                      the job is running. The name  is  compiled-in  into  the
                      [4msge_execd[24m(8) binary.

       SGE_CKPT_ENV   Specifies  the  checkpointing  environment  (as selected
                      with the [1m-ckpt [22moption) under which a  checkpointing  job
                      executes. Only set for checkpointing jobs.

       SGE_CKPT_DIR   Only  set for checkpointing jobs. Contains path [4mckpt_dir[0m
                      (see [4mcheckpoint[24m(5) ) of the checkpoint interface.

       SGE_STDERR_PATH
                      the pathname of the file to  which  the  standard  error
                      stream of the job is diverted. Commonly used for enhanc-
                      ing the output with error messages from prolog,  epilog,
                      parallel   environment   start/stop   or   checkpointing
                      scripts.

       SGE_STDOUT_PATH
                      the pathname of the file to which  the  standard  output
                      stream of the job is diverted. Commonly used for enhanc-
                      ing the output with messages from prolog, epilog, paral-
                      lel environment start/stop or checkpointing scripts.

       SGE_STDIN_PATH the  pathname  of the file from which the standard input
                      stream of the job is taken. This variable might be  used
                      in  combination with SGE_O_HOST in prolog/epilog scripts
                      to transfer the input file from the submit to the execu-
                      tion host.

       SGE_JOB_SPOOL_DIR
                      The  directory  used  by  [4msge_shepherd[24m(8)  to  store job
                      related data during job  execution.  This  directory  is
                      owned by root or by a Grid Engine administrative account
                      and commonly is not open for read  or  write  access  to
                      regular users.

       SGE_TASK_ID    The  index  number of the current array job task (see [1m-t[0m
                      option above). This is an unique number  in  each  array
                      job  and  can  be used to reference different input data
                      records, for example. This environment variable  is  set
                      to  "undefined"  for  non-array  jobs. It is possible to
                      change the predefined value of this variable with [1m-v  [22mor
                      [1m-V [22m(see options above).

       SGE_TASK_FIRST The  index  number  of  the first array job task (see [1m-t[0m
                      option above). It is possible to change  the  predefined
                      value  of  this  variable  with  [1m-v  [22mor  [1m-V [22m(see options
                      above).

       SGE_TASK_LAST  The index number of the last  array  job  task  (see  [1m-t[0m
                      option  above).  It is possible to change the predefined
                      value of this  variable  with  [1m-v  [22mor  [1m-V  [22m(see  options
                      above).

       SGE_TASK_STEPSIZE
                      The  stepsize  of  the  array  job specification (see [1m-t[0m
                      option above). It is possible to change  the  predefined
                      value  of  this  variable  with  [1m-v  [22mor  [1m-V [22m(see options
                      above).

       ENVIRONMENT    The ENVIRONMENT variable is set  to  BATCH  to  identify
                      that  the  job  is being executed under Grid Engine con-
                      trol.

       HOME           The user's home directory path from the [4mpasswd[24m(5)  file.

       HOSTNAME       The hostname of the node on which the job is running.

       JOB_ID         A  unique identifier assigned by the [4msge_qmaster[24m(8) when
                      the job was submitted. The job ID is a  decimal  integer
                      in the range 1 to 99999.

       JOB_NAME       The  job name.  For batch jobs or jobs submitted by [4mqrsh[0m
                      with a command, the job name is built as basename of the
                      [4mqsub[24m script filename resp. the [4mqrsh[24m command.  For inter-
                      active jobs it is set to  `INTERACTIVE'  for  [4mqsh[24m  jobs,
                      `QLOGIN'  for  [4mqlogin[24m  jobs  and `QRLOGIN' for [4mqrsh[24m jobs
                      without a command.

                      This default may be overwritten by the [4m-N.[24m  option.

       LOGNAME        The user's login name from the [4mpasswd[24m(5) file.

       NHOSTS         The number of hosts in use by a parallel job.

       NQUEUES        The number of queues allocated for the job (always 1 for
                      serial jobs).

       NSLOTS         The number of queue slots in use by a parallel job.

       PATH           A default shell search path of:
                      /usr/local/bin:/usr/ucb:/bin:/usr/bin

       SGE_BINARY_PATH
                      The  path  where the Grid Engine binaries are installed.
                      The value is the concatenation of the cluster configura-
                      tion   value   [1mbinary_path  [22mand  the  architecture  name
                      [1m$SGE_ARCH [22menvironment variable.

       PE             The parallel environment under which  the  job  executes
                      (for parallel jobs only).

       PE_HOSTFILE    The path of a file containing the definition of the vir-
                      tual parallel machine assigned to a parallel job by Grid
                      Engine.  See the description of the [1m$pe_hostfile [22mparame-
                      ter in [4msge_pe[24m(5) for details on the format of this file.
                      The  environment variable is only available for parallel
                      jobs.

       QUEUE          The name of the cluster queue in which the job  is  run-
                      ning.

       REQUEST        Available for batch jobs only.

                      The  request  name  of  a  job  as specified with the [1m-N[0m
                      switch (see above) or taken  as  the  name  of  the  job
                      script file.

       RESTARTED      This  variable is set to 1 if a job was restarted either
                      after a system crash or after a migration in case  of  a
                      checkpointing  job.  The variable has the value 0 other-
                      wise.

       SHELL          The user's login shell from the  [4mpasswd[24m(5)  file.  [1mNote:[0m
                      This is not necessarily the shell in use for the job.

       TMPDIR         The  absolute path to the job's temporary working direc-
                      tory.

       TMP            The same as TMPDIR; provided for compatibility with NQS.

       TZ             The  time  zone  variable  imported from [4msge_execd[24m(8) if
                      set.

       USER           The user's login name from the [4mpasswd[24m(5) file.

[1mRESTRICTIONS[0m
       There is no controlling terminal for batch jobs under Grid Engine,  and
       any  tests  or  actions  on  a controlling terminal will fail. If these
       operations are in your .login or .cshrc file, they may cause  your  job
       to abort.

       Insert the following test before any commands that are not pertinent to
       batch jobs in your .login:

              if ( $?JOB_NAME) then
                     echo "Grid Engine spooled job"
                     exit 0
              endif

       Don't forget to set your shell's search path  in  your  shell  start-up
       before this code.

[1mEXIT STATUS[0m
       The following exit values are returned:

       0    Operation was executed successfully.

       25   It was not possible to register a new job according to the config-
            ured [4mmax_u_jobs[24m or [4mmax_jobs[24m limit. Additional information  may  be
            found in [4msge_conf[24m(5)

       >0   Error occurred.

[1mEXAMPLES[0m
       The following is the simplest form of a Grid Engine script file.

       =====================================================


       #!/bin/csh
          a.out


       =====================================================

       The next example is a more complex Grid Engine script.

       =====================================================

       #!/bin/csh

       # Which account to be charged cpu time
       #$ -A santa_claus

       # date-time to run, format [[CC]yy]MMDDhhmm[.SS]
       #$ -a 12241200

       # to run I want 6 or more parallel processes
       # under the PE pvm. the processes require
       # 128M of memory
       #$ -pe pvm 6- -l mem=128

       # If I run on dec_x put stderr in /tmp/foo, if I
       # run on sun_y, put stderr in /usr/me/foo
       #$ -e dec_x:/tmp/foo,sun_y:/usr/me/foo

       # Send mail to these users
       #$ -M santa@nothpole,claus@northpole

       # Mail at beginning/end/on suspension
       #$ -m bes

       # Export these environmental variables
       #$ -v PVM_ROOT,FOOBAR=BAR

       # The job is located in the current
       # working directory.
       #$ -cwd

       a.out

       ==========================================================


[1mFILES[0m
       [4m$REQUEST.oJID[.TASKID][24m      STDOUT of job #JID
       [4m$REQUEST.eJID[.TASKID][24m      STDERR of job
       [4m$REQUEST.poJID[.TASKID][24m     STDOUT of par. env. of job
       [4m$REQUEST.peJID[.TASKID][24m     STDERR of par. env. of job
       [4m$REQUEST.hostsJID[.TASKID][24m  hosts file of par. env. of job

       [4m$cwd/.sge_aliases[24m         cwd path aliases
       [4m$cwd/.sge_request[24m         cwd default request
       [4m$HOME/.sge_aliases[24m        user path aliases
       [4m$HOME/.sge_request[24m        user default request
       [4m<sge_root>/<cell>/common/sge_aliases[0m
                                 cluster path aliases
       [4m<sge_root>/<cell>/common/sge_request[0m
                                 cluster default request
       [4m<sge_root>/<cell>/common/act_qmaster[0m
                                 Grid Engine master host file

[1mSEE ALSO[0m
       [4msge_intro[24m(1),  [4mqconf[24m(1), [4mqdel[24m(1), [4mqhold[24m(1), [4mqmod[24m(1), [4mqrls[24m(1), [4mqstat[24m(1),
       [4maccounting[24m(5), [4msge_aliases[24m(5), [4msge_conf[24m(5), [4msge_request[24m(5),  [4msge_pe[24m(5),
       [4mcomplex[24m(5).

[1mCOPYRIGHT[0m
       If  configured correspondingly, [4mqrsh[24m and [4mqlogin[24m contain portions of the
       [4mrsh[24m, [4mrshd[24m, [4mtelnet[24m and [4mtelnetd[24m code copyrighted by The  Regents  of  the
       University  of  California.  Therefore, the following note applies with
       respect to [4mqrsh[24m and [4mqlogin[24m: This product includes software developed by
       the University of California, Berkeley and its contributors.

       See   [4msge_intro[24m(1)   as   well   as   the   information   provided   in
       <sge_root>/3rd_party/qrsh and <sge_root>/3rd_party/qlogin for a  state-
       ment of further rights and permissions.



GE 6.0                   $Date: 2007/06/05 16:50:23 $                SUBMIT(1)
