QCONF(1)                   Grid Engine User Commands                  QCONF(1)



[1mNAME[0m
       qconf - Grid Engine Queue Configuration

[1mSYNTAX[0m
       [1mqconf options[0m

[1mDESCRIPTION[0m
       [4mQconf[24m  allows  the  system administrator to add, delete, and modify the
       current Grid Engine configuration,  including  queue  management,  host
       management,  complex management and user management.  [4mQconf[24m also allows
       you to examine the current queue configuration for existing queues.

       [4mQconf[24m allows the use of the backslash, '\', character at the end  of  a
       line  to  indicate  that the next line is a continuation of the current
       line.  When displaying settings, such as the output of one of  the  -s*
       options,  [4mqconf[24m will break up long lines (lines greater than 80 charac-
       ters) into smaller lines using backslash line continuation where possi-
       ble.   Lines will only be broken up at commas or whitespace.  This fea-
       ture can be disabled by setting the SGE_SINGLE_LINE  environment  vari-
       able.

[1mOPTIONS[0m
       Unless  denoted  otherwise, the following options and the corresponding
       operations are available to all users with a valid account.


       [1m-Aattr obj_spec fname obj_instance,...[0m
                                     [4m<add[24m [4mto[24m [4mobject[24m [4mattributes>[0m
              Similar to [1m-aattr [22m(see below) but takes specifications  for  the
              object  attributes  to  be  enhanced  from  file named [1mfname[22m. As
              opposed to [1m-aattr[22m, multiple attributes can  be  enhanced.  Their
              specification  has  to  be  enlisted in [1mfname [22mfollowing the file
              format of the corresponding object (see  [4mqueue_conf[24m(5)  for  the
              queue, for example).
              Requires root/manager privileges.

       [1m-Acal fname                   [4m[22m<add[24m [4mcalendar>[0m
              Adds  a  new calendar definition to the Grid Engine environment.
              Calendars are used in Grid Engine for defining availability  and
              unavailability  schedules  of  queues.  The format of a calendar
              definition is described in [4mcalendar_conf[24m(5).

              The calendar definition is taken from the file  [1mfname[22m.  Requires
              root/ manager privileges.

       [1m-Ackpt fname                  [4m[22m<add[24m [4mckpt.[24m [4menvironment>[0m
              Add  the  checkpointing  environment  as  defined  in [1mfname [22m(see
              [4mcheckpoint[24m(5)) to the list of supported  checkpointing  environ-
              ments.  Requires root or manager privileges.

       [1m-Aconf file_list              [4m[22m<add[24m [4mconfigurations>[0m
              Add  the  configurations (see [4mge_conf[24m(5)) specified in the files
              enlisted in the comma separated [1mfile_list[22m. The configuration  is
              added for the host that is identical to the file name.
              Requires root or manager privileges.

       [1m-Ae fname                     [4m[22m<add[24m [4mexecution[24m [4mhost>[0m
              Add the execution host defined in [1mfname [22mto the Grid Engine clus-
              ter. The format of the execution host specification is described
              in [4mhost_conf[24m(5).  Requires root or manager privileges.

       [1m-Ahgrp file                   [4m[22m<add[24m [4mhost[24m [4mgroup[24m [4mconfig>[0m
              Add the host group configuration defined in [1mfile[22m.  The file for-
              mat of [1mfile [22mmust comply to the format specified in [4mhostgroup[24m(5).
              Requires root or manager privileges.

       [1m-Arqs fname [4m[22m<add[24m [4mRQS[24m [4mconfiguration>[0m
              Add the resource quota set (RQS) defined in the file named [1mfname[0m
              to the Grid Engine cluster. Requires root or manager privileges.

       [1m-Ap fname                     [4m[22m<add[24m [4mPE[24m [4mconfiguration>[0m
              Add  the  parallel environment (PE) defined in [1mfname [22mto the Grid
              Engine cluster. Requires root or manager privileges.

       [1m-Aprj fname                   [4m[22m<add[24m [4mnew[24m [4mproject>[0m
              Adds the project description defined in [1mfname  [22mto  the  list  of
              registered  projects (see [4mproject[24m(5)).  Requires root or manager
              privileges.

       [1m-Aq fname                     [4m[22m<add[24m [4mnew[24m [4mqueue>[0m
              Add the queue defined in  [1mfname  [22mto  the  Grid  Engine  cluster.
              Requires root or manager privileges.

       [1m-Au fname                     [4m[22m<add[24m [4man[24m [4mACL>[0m
              Add  the user access list (ACL) defined in [1mfname [22mto Grid Engine.
              User lists are used for  queue  usage  authentication.  Requires
              root/manager/operator privileges.

       [1m-Dattr obj_spec fname obj_instance,...[0m
                                     [4m<del.[24m [4mfrom[24m [4mobject[24m [4mattribs>[0m
              Similar  to  [1m-dattr  [22m(see  below) but the definition of the list
              attributes from which entries are to be deleted is contained  in
              the  file named [1mfname[22m. As opposed to [1m-dattr[22m, multiple attributes
              can be modified. Their specification has to be enlisted in [1mfname[0m
              following  the  file  format  of  the  corresponding object (see
              [4mqueue_conf[24m(5) for the queue, for example).
              Requires root/manager privileges.

       [1m-Mattr obj_spec fname obj_instance,...[0m
                                     [4m<mod.[24m [4mobject[24m [4mattributes>[0m
              Similar to [1m-mattr [22m(see below) but takes specifications  for  the
              object  attributes  to  be  modified  from  file named [1mfname[22m. As
              opposed to [1m-mattr[22m, multiple attributes can  be  modified.  Their
              specification  has  to  be  enlisted in [1mfname [22mfollowing the file
              format of the corresponding object (see  [4mqueue_conf[24m(5)  for  the
              queue, for example).
              Requires root/manager privileges.

       [1m-Mc fname                     [4m[22m<modify[24m [4mcomplex>[0m
              Overwrites  the  complex configuration by the contents of [1mfname[22m.
              The argument file must comply to the format  specified  in  [4mcom-[0m
              [4mplex[24m(5).  Requires root or manager privilege.

       [1m-Mcal fname                   [4m[22m<modify[24m [4mcalendar>[0m
              Overwrites  the  calendar  definition as specified in [1mfname[22m. The
              argument file must comply to  the  format  described  in  [4mcalen-[0m
              [4mdar_conf[24m(5).  Requires root or manager privilege.

       [1m-Mckpt fname                  [4m[22m<modify[24m [4mckpt.[24m [4menvironment>[0m
              Overwrite an existing checkpointing environment with the defini-
              tions in [1mfname [22m(see [4mcheckpoint[24m(5)).  The name attribute in [1mfname[0m
              has  to  match  an  existing checkpointing environment. Requires
              root or manager privileges.

       [1m-Mconf file_list              [4m[22m<modify[24m [4mconfigurations>[0m
              Modify the configurations  (see  [4mge_conf[24m(5))  specified  in  the
              files  enlisted in the comma separated [1mfile_list[22m. The configura-
              tion is modified for the host that  is  identical  to  the  file
              name.
              Requires root or manager privileges.

       [1m-Me fname                     [4m[22m<modify[24m [4mexecution[24m [4mhost>[0m
              Overwrites  the  execution  host configuration for the specified
              host with the contents of [1mfname[22m, which must comply to the format
              defines in [4mhost_conf[24m(5).  Requires root or manager privilege.

       [1m-Mhgrp file                   [4m[22m<modify[24m [4mhost[24m [4mgroup[24m [4mconfig.>[0m
              Allows  changing  of host group configuration with a single com-
              mand.  All host group configuration entries  contained  in  [1mfile[0m
              will  be  applied.  Configuration  entries not contained in [1mfile[0m
              will be deleted. The file format of [1mfile [22mmust comply to the for-
              mat specified in [4mhostgroup[24m(5).

       [1m-Mrqs fname [mrqs_name]       [4m[22m<modify[24m [4mRQS[24m [4mconfiguration>[0m
              Same  as  [1m-mrqs [22m(see below) but instead of invoking an editor to
              modify the RQS configuration, the file [1mfname  [22mis  considered  to
              contain  a  changed  configuration.  The name of the rule set in
              [1mfname [22mmust be the same as rqs_name. If rqs_name is not set,  all
              rule  sets  are  overwritten  by the rule sets in [1mfname [22mRefer to
              [4mge_resource_quota[24m(5) for details on the RQS  configuration  for-
              mat.  Requires root or manager privilege.

       [1m-Mp fname                     [4m[22m<modify[24m [4mPE[24m [4mconfiguration>[0m
              Same  as  [1m-mp  [22m(see  below) but instead of invoking an editor to
              modify the PE configuration the file [1mfname [22mis considered to con-
              tain  a changed configuration.  Refer to [4mge_pe[24m(5) for details on
              the PE configuration format.  Requires root  or  manager  privi-
              lege.

       [1m-Mprj fname                   [4m[22m<modify[24m [4mproject[24m [4mconfig.>[0m
              Same  as  [1m-mprj [22m(see below) but instead of invoking an editor to
              modify the project configuration the file [1mfname [22mis considered to
              contain  a  changed  configuration.   Refer  to  [4mproject[24m(5)  for
              details on the project configuration format.  Requires  root  or
              manager privilege.

       [1m-Mq fname                     [4m[22m<modify[24m [4mqueue[24m [4mconfiguration>[0m
              Same  as  [1m-mq  [22m(see  below) but instead of invoking an editor to
              modify the queue configuration the file [1mfname [22mis  considered  to
              contain  a  changed  configuration.   Refer to [4mqueue_conf[24m(5) for
              details on the queue configuration  format.   Requires  root  or
              manager privilege.

       [1m-Msconf   fname                 [4m[22m<modify[24m  [4mscheduler[24m  [4mconfiguration[24m  [4mfrom[0m
       [4mfile>[0m
              The current scheduler configuration (see [4msched_conf[24m(5)) is over-
              ridden with the configuration specified in the  file.   Requires
              root or manager privilege.

       [1m-Mstree fname                 [4m[22m<modify[24m [4mshare[24m [4mtree>[0m
              Modifies  the  definition of the share tree (see [4mshare_tree[24m(5)).
              The modified sharetree is read from file fname.   Requires  root
              or manager privileges.

       [1m-Mu fname                     [4m[22m<modify[24m [4mACL>[0m
              Takes  the  user access list (ACL) defined in [1mfname [22mto overwrite
              any existing ACL with the  same  name.  See  [4maccess_list[24m(5)  for
              information  on  the  ACL configuration format. Requires root or
              manager privilege.

       [1m-Muser fname                  [4m[22m<modify[24m [4muser>[0m
              Modify the user defined in [1mfname [22min the Grid Engine cluster. The
              format  of  the  user  specification  is  described  in [4muser[24m(5).
              Requires root or manager privileges.

       [1m-Rattr obj_spec fname obj_instance,...[0m
                                     [4m<replace[24m [4mobject[24m [4mattribs>[0m
              Similar to [1m-rattr [22m(see below) but the  definition  of  the  list
              attributes  whose  content  is to be replace is contained in the
              file named [1mfname[22m. As opposed to [1m-rattr[22m, multiple attributes  can
              be  modified.  Their  specification  has to be enlisted in [1mfname[0m
              following the file  format  of  the  corresponding  object  (see
              [4mqueue_conf[24m(5) for the queue, for example).
              Requires root/manager privileges.

       [1m-aattr obj_spec attr_name val obj_instance,...[0m
                 [4m<add[24m [4mto[24m [4mobject[24m [4mattributes>[0m
              Allows  adding  specifications  to  a  single configuration list
              attribute in multiple instances of an object with a single  com-
              mand.  Currently  supported objects are the queue, the host, the
              host group, the parallel environment, the  resource  quota  sets
              and the checkpointing interface configuration being specified as
              [4mqueue[24m , [4mexechost[24m , [4mhostgroup[24m , [4mpe[24m , [4mrqs[24m  or  [4mckpt[24m  in  [1mobj_spec[22m.
              For  the  obj_spec [4mqueue[24m the obj_instance can be a cluster queue
              name, a queue domain name or a queue instance  name.  Find  more
              information  concerning  different  queue names in [4msge_types[24m(1).
              Depending on the type of the obj_instance this adds to the clus-
              ter queues attribute sublist the cluster queues implicit default
              configuration value or the queue domain configuration  value  or
              queue  instance  configuration  value.  The queue [1mload_thesholds[0m
              parameter is an example of a list  attribute.  With  the  [1m-aattr[0m
              option,  entries  can  be added to such lists, while they can be
              deleted with [1m-dattr[22m, modified with  [1m-mattr[22m,  and  replaced  with
              [1m-rattr[22m.
              For the obj_spec [4mrqs[24m the obj_instance is a unique identifier for
              a specific rule. The identifier consists of a rule-set name  and
              either  the  number  of the rule in the list, or the name of the
              rule, separated by a /
              The name of the configuration attribute to be enhanced is speci-
              fied  with  [1mattr_name  [22mfollowed by [1mval [22mas a [4mname=value[24m pair. The
              comma separated list of object  instances  (e.g.,  the  list  of
              queues) to which the changes have to be applied are specified at
              the end of the command.
              The following restriction applies: For the [4mexechost[24m  object  the
              [1mload_values [22mattribute cannot be modified (see [4mhost_conf[24m(5)).
              Requires root or manager privileges.

       [1m-acal calendar_name           [4m[22m<add[24m [4mcalendar>[0m
              Adds  a  new calendar definition to the Grid Engine environment.
              Calendars are used in Grid Engine for defining availability  and
              unavailability  schedules  of  queues.  The format of a calendar
              definition is described in [4mcalendar_conf[24m(5).

              With the calendar name given in the option argument  [4mqconf[24m  will
              open  a temporary file and start up the text editor indicated by
              the environment variable EDITOR (default editor is [4mvi[24m(1) if EDI-
              TOR  is  not  set).  After  entering the calendar definition and
              closing the editor the new calendar is  checked  and  registered
              with [4mge_qmaster[24m(8).  Requires root/manager privileges.

       [1m-ackpt ckpt_name              [4m[22m<add[24m [4mckpt.[24m [4menvironment>[0m
              Adds a checkpointing environment under the name [1mckpt_name [22mto the
              list of checkpointing environments maintained by Grid Engine and
              to be usable to submit checkpointing jobs (see [4mcheckpoint[24m(5) for
              details on the format of  a  checkpointing  environment  defini-
              tion).  [4mQconf[24m retrieves a default checkpointing environment con-
              figuration and executes [4mvi[24m(1) (or $EDITOR if the EDITOR environ-
              ment  variable is set) to allow you to customize the checkpoint-
              ing environment configuration. Upon exit from  the  editor,  the
              checkpointing  environment  is  registered  with  [4mge_qmaster[24m(8).
              Requires root/manager privileges.

       [1m-aconf host,...               [4m[22m<add[24m [4mconfiguration>[0m
              Successively adds configurations (see [4mge_conf[24m(5)) For the  hosts
              in  the  comma  separated  [4mfile_list[24m.   For each host, an editor
              ($EDITOR indicated or [4mvi[24m(1)) is invoked  and  the  configuration
              for  the  host  can  be entered. The configuration is registered
              with [4mge_qmaster[24m(8) after saving the file and quitting  the  edi-
              tor.
              Requires root or manager privileges.

       [1m-ae [host_template]           [4m[22m<add[24m [4mexecution[24m [4mhost>[0m
              Adds  a  host  to  the list of Grid Engine execution hosts. If a
              queue is configured on a host this host is  automatically  added
              to  the Grid Engine execution host list.  Adding execution hosts
              explicitly offers the advantage to be able to specify parameters
              like  load  scale  values with the registration of the execution
              host. However, these parameters  can  be  modified  (from  their
              defaults)  at any later time via the [1m-me [22moption described below.
              If the [1mhost_template [22margument is present,  [4mqconf[24m  retrieves  the
              configuration of the specified execution host from [4mge_qmaster[24m(8)
              or a generic template otherwise.  The template is then stored in
              a  file  and  [4mqconf[24m  executes  [4mvi[24m(1) (or the editor indicated by
              $EDITOR if the EDITOR environment variable is set) to change the
              entries  in the file.  The format of the execution host specifi-
              cation is described in [4mhost_conf[24m(5).  When the changes are saved
              in  the  editor and the editor is quit the new execution host is
              registered with  [4mge_qmaster[24m(8).   Requires  root/manager  privi-
              leges.

       [1m-ah hostname,...              [4m[22m<add[24m [4madministrative[24m [4mhost>[0m
              Adds hosts [1mhostname [22mto the Grid Engine trusted host list (a host
              must be in this list to execute administrative Grid Engine  com-
              mands,  the  sole exception to this being the execution of [4mqconf[0m
              on the [4mge_qmaster[24m(8) node). The default Grid Engine installation
              procedures  usually  add all designated execution hosts (see the
              [1m-ae [22moption above) to the Grid Engine trusted host list automati-
              cally.  Requires root or manager privileges.

       [1m-ahgrp group                  [4m[22m<add[24m [4mhost[24m [4mgroup[24m [4mconfig.>[0m
              Adds  a  new  host group with the name specified in [1mgroup.  [22mThis
              command invokes an editor (either [4mvi[24m(1) or the editor  indicated
              by  the  EDITOR environment variable).  The new host group entry
              is registered after changing the entry and exiting  the  editor.
              Requires root or manager privileges.

       [1m-arqs [rqs_name]              [4m[22m<add[24m [4mnew[24m [4mRQS>[0m
              Adds  one or more [4mResource[24m [4mQuota[24m [4mSet[24m (RQS) description under the
              names [1mrqs_name [22mto the list of RQSs  maintained  by  Grid  Engine
              (see  [4mge_resource_quota[24m(5)  for  details  on the format of a RQS
              definition).  [4mQconf[24m retrieves a default  RQS  configuration  and
              executes [4mvi[24m(1) (or $EDITOR if the EDITOR environment variable is
              set) to allow you to customize the RQS configuration. Upon  exit
              from  the  editor,  the  RQS  is  registered with [4mge_qmaster[24m(8).
              Requires root or manager privileges.

       [1m-am user,...                  [4m[22m<add[24m [4mmanagers>[0m
              Adds the indicated  users  to  the  Grid  Engine  manager  list.
              Requires root or manager privileges.

       [1m-ao user,...                  [4m[22m<add[24m [4moperators>[0m
              Adds  the  indicated  users  to  the  Grid Engine operator list.
              Requires root or manager privileges.

       [1m-ap pe_name                   [4m[22m<add[24m [4mnew[24m [4mPE>[0m
              Adds a [4mParallel[24m [4mEnvironment[24m  (PE)  description  under  the  name
              [1mpe_name  [22mto  the list of PEs maintained by Grid Engine and to be
              usable to submit parallel jobs (see [4mge_pe[24m(5) for details on  the
              format  of  a PE definition).  [4mQconf[24m retrieves a default PE con-
              figuration and executes [4mvi[24m(1) (or $EDITOR if the EDITOR environ-
              ment  variable is set) to allow you to customize the PE configu-
              ration. Upon exit from the editor, the  PE  is  registered  with
              [4mge_qmaster[24m(8).  Requires root/manager privileges.

       [1m-at thread_name [4m[22m<activates[24m [4mthread[24m [4min[24m [4mmaster>[0m
              Activates   an   additional   thread   in  the  master  process.
              [1mthread_name [22mmight be either "scheduler"  or  "jvm".  The  corre-
              sponding  thread is only started when it is not already running.
              There might be only one scheduler and only one jvm thread in the
              master process at the same time.

       [1m-aprj                         [4m[22m<add[24m [4mnew[24m [4mproject>[0m
              Adds  a  project  description to the list of registered projects
              (see [4mproject[24m(5)).  [4mQconf[24m retrieves a template project configura-
              tion  and  executes  [4mvi[24m(1) (or $EDITOR if the EDITOR environment
              variable is set) to allow you to customize the new project. Upon
              exit  from  the editor, the template is registered with [4mge_qmas-[0m
              [4mter[24m(8).  Requires root or manager privileges.

       [1m-aq [queue_name]              [4m[22m<add[24m [4mnew[24m [4mqueue>[0m
              [4mQconf[24m   retrieves   the   default   queue   configuration   (see
              [4mqueue_conf[24m(5))  and  executes  [4mvi[24m(1)  (or  $EDITOR if the EDITOR
              environment variable is set) to allow you to customize the queue
              configuration.  Upon  exit  from the editor, the queue is regis-
              tered with [4mge_qmaster[24m(8).  A minimal configuration requires only
              that the queue name and queue hostlist be set.  Requires root or
              manager privileges.

       [1m-as hostname,...              [4m[22m<add[24m [4msubmit[24m [4mhosts>[0m
              Add hosts [1mhostname [22mto the list of hosts allowed to  submit  Grid
              Engine  jobs  and control their behavior only.  Requires root or
              manager privileges.

       [1m-astnode node_path=shares,... [4m[22m<add[24m [4mshare[24m [4mtree[24m [4mnode>[0m
              Adds the specified share tree node(s) to  the  share  tree  (see
              [4mshare_tree[24m(5)).    The   [1mnode_path   [22mis   a   hierarchical  path
              ([1m[/]node_name[[/.]node_name...][22m)  specifying the location of the
              new  node  in the share tree.  The base name of the node_path is
              the name of the new node.  The node is initialized to the number
              of specified shares.  Requires root or manager privileges.

       [1m-astree                       [4m[22m<add[24m [4mshare[24m [4mtree>[0m
              Adds  the  definition  of  a  share  tree  to  the  system  (see
              [4mshare_tree[24m(5)).  A template share tree is retrieved and an  edi-
              tor (either [4mvi[24m(1) or the editor indicated by $EDITOR) is invoked
              for modifying the share tree definition. Upon exiting  the  edi-
              tor,   the  modified  data  is  registered  with  [4mge_qmaster[24m(8).
              Requires root or manager privileges.

       [1m-Astree fname                 [4m[22m<add[24m [4mshare[24m [4mtree>[0m
              Adds  the  definition  of  a  share  tree  to  the  system  (see
              [4mshare_tree[24m(5))  from  the  file fname.  Requires root or manager
              privileges.

       [1m-au user,... acl_name,...     [4m[22m<add[24m [4musers[24m [4mto[24m [4mACLs>[0m
              Adds users to Grid Engine user access lists (ACLs).  User  lists
              are  used  for  queue  usage  authentication. Requires root/man-
              ager/operator privileges.

       [1m-Auser fname                  [4m[22m<add[24m [4muser>[0m
              Add the user defined in [1mfname [22mto the Grid  Engine  cluster.  The
              format  of  the  user  specification  is  described  in [4muser[24m(5).
              Requires root or manager privileges.

       [1m-auser                        [4m[22m<add[24m [4muser>[0m
              Adds a user to the list of registered users (see [4muser[24m(5)).  This
              command  invokes an editor (either [4mvi[24m(1) or the editor indicated
              by the EDITOR environment variable) for a template user. The new
              user is registered after changing the entry and exiting the edi-
              tor. Requires root or manager privileges.

       [1m-clearusage                   [4m[22m<clear[24m [4msharetree[24m [4musage>[0m
              Clears all user and project usage from the sharetree.  All usage
              will be initialized back to zero.

       [1m-cq wc_queue_list             [4m[22m<clean[24m [4mqueue>[0m
              Cleans  queue  from  jobs which haven't been reaped. Primarily a
              development  tool.  Requires  root/manager/operator  privileges.
              Find a description of wc_queue_list in [4msge_types[24m(1).

       [1m-dattr obj_spec attr_name val obj_instance,...[0m
                                     [4m<delete[24m [4min[24m [4mobject[24m [4mattribs>[0m
              Allows  deleting  specifications  in a single configuration list
              attribute in multiple instances of an object with a single  com-
              mand.    Find   more   information   concerning   obj_spec   and
              obj_instance in the description of [1m-aattr[0m

       [1m-dcal calendar_name,...       [4m[22m<delete[24m [4mcalendar>[0m
              Deletes the specified  calendar  definition  from  Grid  Engine.
              Requires root/manager privileges.

       [1m-dckpt ckpt_name              [4m[22m<delete[24m [4mckpt.[24m [4menvironment>[0m
              Deletes   the   specified  checkpointing  environment.  Requires
              root/manager privileges.

       [1m-dconf host,...               [4m[22m<delete[24m [4mlocal[24m [4mconfiguration>[0m
              The local configuration entries  for  the  specified  hosts  are
              deleted  from  the configuration list.  Requires root or manager
              privilege.

       [1m-de host_name,...             [4m[22m<delete[24m [4mexecution[24m [4mhost>[0m
              Deletes  hosts  from  the  Grid  Engine  execution  host   list.
              Requires root or manager privileges.

       [1m-dh host_name,...             [4m[22m<delete[24m [4madministrative[24m [4mhost>[0m
              Deletes  hosts from the Grid Engine trusted host list.  The host
              on which [4mge_qmaster[24m(8) is currently running  cannot  be  removed
              from the list of administrative hosts.  Requires root or manager
              privileges.

       [1m-drqs rqs_name_list           [4m[22m<delete[24m [4mRQS>[0m
              Deletes the specified resource quota sets (RQS).  Requires  root
              or manager privileges.

       [1m-dm user[,user,...]           [4m[22m<delete[24m [4mmanagers>[0m
              Deletes  managers  from the manager list.  Requires root or man-
              ager privileges.

       [1m-do user[,user,...]           [4m[22m<delete[24m [4moperators>[0m
              Deletes operators from the operator list.  Requires root or man-
              ager privileges.

       [1m-dp pe_name                   [4m[22m<delete[24m [4mparallel[24m [4menvironment>[0m
              Deletes  the specified parallel environment (PE).  Requires root
              or manager privileges.

       [1m-dprj project,...             [4m[22m<delete[24m [4mprojects>[0m
              Deletes the specified project(s). Requires  root/manager  privi-
              leges.

       [1m-dq queue_name,...            [4m[22m<delete[24m [4mqueue>[0m
              Removes  the specified queue(s).  Active jobs will be allowed to
              run to completion.  Requires root or manager privileges.

       [1m-ds host_name,...             [4m[22m<delete[24m [4msubmit[24m [4mhost>[0m
              Deletes hosts from the Grid Engine submit host  list.   Requires
              root or manager privileges.

       [1m-dstnode node_path,...        [4m[22m<delete[24m [4mshare[24m [4mtree[24m [4mnode>[0m
              Deletes  the  specified  share tree node(s).  The [1mnode_path [22mis a
              hierarchical path  ([1m[/]node_name[[/.]node_name...][22m)   specifying
              the  location  of  the  node  to  be  deleted in the share tree.
              Requires root or manager privileges.

       [1m-dstree                       [4m[22m<delete[24m [4mshare[24m [4mtree>[0m
              Deletes the current share tree. Requires root or manager  privi-
              leges.

       [1m-du user,... acl_name,...     [4m[22m<delete[24m [4musers[24m [4mfrom[24m [4mACL>[0m
              Deletes  one  or  more  users  from one or more Grid Engine user
              access lists (ACLs). Requires root/manager/operator  privileges.

       [1m-dul acl_name,...             [4m[22m<delete[24m [4muser[24m [4mlists>[0m
              Deletes  one  or  more  user  lists  from  the system.  Requires
              root/manager/operator privileges.

       [1m-duser user,...               [4m[22m<delete[24m [4musers>[24m"
              Deletes the specified user(s) from the list of registered users.
              Requires root or manager privileges.

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

       [1m-k{m|s|e[j] {host,...|all}}   [4m[22m<shutdown[24m [4mGrid[24m [4mEngine>[0m
              [1mNote:  [22mThe  [1m-ks  [22mswitch  is deprecated, may be removed in future
              release.  Please use the [1m-kt [22mswitch instead.
              Used to shutdown Grid Engine components (daemons).  In the  form
              [1m-km  [4m[22mge_qmaster[24m(8)  is forced to terminate in a controlled fash-
              ion. In the same way the [1m-ks [22mswitch causes  termination  of  the
              scheduler  thread.   Shutdown  of  running [4mge_execd[24m(8) processes
              currently registered is initiated by the [1m-ke [22moption. If [1m-kej  [22mis
              specified  instead,  all jobs running on the execution hosts are
              aborted prior to termination of the  corresponding  [4mge_execd[24m(8).
              The  comma  separated host list specifies the execution hosts to
              be addressed by the [1m-ke [22mand [1m-kej [22moption. If the keyword  [1mall  [22mis
              specified  instead  of a host list, all running [4mge_execd[24m(8) pro-
              cesses are shutdown. Job abortion, initiated by the [1m-kej  [22moption
              will  result  in [1mdr [22mstate for all running jobs until [4mge_execd[24m(8)
              is running again.
              Requires root or manager privileges.

       [1m-kt thread_name   [4m[22m<terminate[24m [4mmaster[24m [4mthread>[24m"
              Terminates a thread in the master process. Currently it is  only
              supported  to shutdown the "scheduler" and the "jvm" thread. The
              command will only be successful if the corresponding  thread  is
              running.

       [1m-kec {id,...|all}             [4m[22m<kill[24m [4mevent[24m [4mclient>[0m
              Used to shutdown event clients registered at [4mge_qmaster[24m(8).  The
              comma separated event client list specifies the event clients to
              be  addressed  by the [1m-kec [22moption.  If the keyword [1mall [22mis speci-
              fied instead of an event client list, all running event  clients
              except special clients like the scheduler thread are terminated.
              Requires root or manager privilege.

       [1m-mattr obj_spec attr_name val obj_instance,...[0m
                                     [4m<modify[24m [4mobject[24m [4mattributes>[0m
              Allows changing a single  configuration  attribute  in  multiple
              instances  of an object with a single command.  Find more infor-
              mation concerning obj_spec and obj_instance in  the  description
              of [1m-aattr[0m

       [1m-mc                           [4m[22m<modify[24m [4mcomplex>[0m
              The complex configuration (see [4mcomplex[24m(5)) is retrieved, an edi-
              tor is executed (either [4mvi[24m(1) or the editor indicated  by  $EDI-
              TOR)  and  the  changed complex configuration is registered with
              [4mge_qmaster[24m(8) upon exit of the editor.  Requires root or manager
              privilege.

       [1m-mcal calendar_name           [4m[22m<modify[24m [4mcalendar>[0m
              The  specified  calendar  definition  (see  [4mcalendar_conf[24m(5)) is
              retrieved, an editor is executed (either  [4mvi[24m(1)  or  the  editor
              indicated  by  $EDITOR)  and  the changed calendar definition is
              registered with [4mge_qmaster[24m(8) upon exit of the editor.  Requires
              root or manager privilege.

       [1m-mckpt ckpt_name              [4m[22m<modify[24m [4mckpt.[24m [4menvironment>[0m
              Retrieves  the  current  configuration  for the specified check-
              pointing environment, executes an editor (either  [4mvi[24m(1)  or  the
              editor  indicated by the EDITOR environment variable) and regis-
              ters the new configuration with  the  [4mge_qmaster[24m(8).   Refer  to
              [4mcheckpoint[24m(5)  for details on the checkpointing environment con-
              figuration format.  Requires root or manager privilege.

       [1m-mconf [host,...|global]      [4m[22m<modify[24m [4mconfiguration>[0m
              The configuration for the specified host is retrieved, an editor
              is  executed  (either  [4mvi[24m(1) or the editor indicated by $EDITOR)
              and the changed configuration is registered  with  [4mge_qmaster[24m(8)
              upon exit of the editor.  If the optional host argument is omit-
              ted or if the special host name [1mglobal is specified, the  global[0m
              [1mconfiguration  is modified.  The  format of the configuration is[0m
              [1mdescribed in [4m[22mge_conf[24m(5).
              Requires root or manager privilege.

       [1m-me hostname                  [4m[22m<modify[24m [4mexecution[24m [4mhost>[0m
              Retrieves the current configuration for the specified  execution
              host,  executes  an editor (either [4mvi[24m(1) or the editor indicated
              by the EDITOR environment variable) and  registers  the  changed
              configuration with [4mge_qmaster[24m(8) upon exit from the editor.  The
              format of the  execution  host  configuration  is  described  in
              [4mhost_conf[24m(5).  Requires root or manager privilege.

       [1m-mhgrp group [4m[22m<modify[24m [4mhost[24m [4mgroup[24m [4mconfiguration>[0m
              The host group entries for the host group specified in [1mgroup [22mare
              retrieved and an editor (either [4mvi[24m(1) or the editor indicated by
              the  EDITOR  environment  variable) is invoked for modifying the
              host group configuration. By closing the  editor,  the  modified
              data  is registered.  The format of the host group configuration
              is described in [4mhostgroup[24m(5).  Requires root or  manager  privi-
              leges.

       [1m-mrqs [rqs_name]              [4m[22m<modify[24m [4mRQS[24m [4mconfiguration>[0m
              Retrieves  the  resource quota set (RQS)configuration defined in
              rqs_name, or if rqs_name is not given,  retrieves  all  resource
              quota sets, executes an editor (either [4mvi[24m(1) or the editor indi-
              cated by the EDITOR environment variable) and registers the  new
              configuration     with     the    [4mge_qmaster[24m(8).     Refer    to
              [4mge_resource_quota[24m(5) for details on the RQS  configuration  for-
              mat.  Requires root or manager privilege.

       [1m-mp pe_name                   [4m[22m<modify[24m [4mPE[24m [4mconfiguration>[0m
              Retrieves  the  current configuration for the specified [4mparallel[0m
              [4menvironment[24m (PE), executes an editor (either [4mvi[24m(1) or the editor
              indicated  by the EDITOR environment variable) and registers the
              new configuration with the [4mge_qmaster[24m(8).  Refer to [4mge_pe[24m(5) for
              details  on  the PE configuration format.  Requires root or man-
              ager privilege.

       [1m-mprj project                 [4m[22m<modify[24m [4mproject>[0m
              Data for the specific project is retrieved (see [4mproject[24m(5))  and
              an  editor  (either [4mvi[24m(1) or the editor indicated by $EDITOR) is
              invoked for modifying the project definition. Upon  exiting  the
              editor,  the modified data is registered.  Requires root or man-
              ager privileges.

       [1m-mq queuename                 [4m[22m<modify[24m [4mqueue[24m [4mconfiguration>[0m
              Retrieves the current configuration  for  the  specified  queue,
              executes  an editor (either [4mvi[24m(1) or the editor indicated by the
              EDITOR environment variable) and registers the new configuration
              with  the  [4mge_qmaster[24m(8).  Refer to [4mqueue_conf[24m(5) for details on
              the queue configuration format.  Requires root or manager privi-
              lege.

       [1m-msconf                       [4m[22m<modify[24m [4mscheduler[24m [4mconfiguration>[0m
              The  current  scheduler  configuration  (see  [4msched_conf[24m(5))  is
              retrieved, an editor is executed (either  [4mvi[24m(1)  or  the  editor
              indicated  by  $EDITOR)  and the changed configuration is regis-
              tered with [4mge_qmaster[24m(8) upon exit of the editor.  Requires root
              or manager privilege.

       [1m-mstnode node_path=shares,... [4m[22m<modify[24m [4mshare[24m [4mtree[24m [4mnode>[0m
              Modifies the specified share tree node(s) in the share tree (see
              [4mshare_tree[24m(5)).   The   [1mnode_path   [22mis   a   hierarchical   path
              ([1m[/]node_name[[/.]node_name...][22m)   specifying the location of an
              existing node in the share tree.  The node is set to the  number
              of specified [1mshares[22m.  Requires root or manager privileges.

       [1m-mstree                       [4m[22m<modify[24m [4mshare[24m [4mtree>[0m
              Modifies  the  definition of the share tree (see [4mshare_tree[24m(5)).
              The present share tree is retrieved and an editor (either  [4mvi[24m(1)
              or the editor indicated by $EDITOR) is invoked for modifying the
              share tree definition. Upon exiting  the  editor,  the  modified
              data is registered with [4mge_qmaster[24m(8).  Requires root or manager
              privileges.

       [1m-mu acl_name                  [4m[22m<modify[24m [4muser[24m [4maccess[24m [4mlists>[0m
              Retrieves the  current  configuration  for  the  specified  user
              access  list,  executes  an  editor  (either [4mvi[24m(1) or the editor
              indicated by the EDITOR environment variable) and registers  the
              new configuration with the [4mge_qmaster[24m(8).  Requires root or man-
              ager privilege.

       [1m-muser user                   [4m[22m<modify[24m [4muser>[0m
              Data for the specific user is retrieved  (see  [4muser[24m(5))  and  an
              editor (either [4mvi[24m(1) or the editor indicated by the EDITOR envi-
              ronment variable) is invoked for modifying the user  definition.
              Upon  exiting  the  editor,  the  modified  data  is registered.
              Requires root or manager privileges.

       [1m-purge queue attr_nm,... obj_spec[0m
                 [4m<purge[24m [4mdivergent[24m [4mattribute[24m [4msettings>[0m
              Delete the values of the attributes defined in [1mattr_nm [22mfrom  the
              object  defined in [1mobj_spec[22m. Obj_spec can be "queue_instance" or
              "queue_domain".  The names of the attributes  are  described  in
              [4mqueue_conf[24m(1).
              This  operation only works on a single queue instance or domain.
              It cannot be used on a cluster queue.  In  the  case  where  the
              [1mobj_spec  [22mis "queue@@hostgroup", the attribute values defined in
              [1mattr_nm [22mwhich are set for the indicated hostgroup  are  deleted,
              but  not  those  which  are  set for the hosts contained by that
              hostgroup.  If the [1mattr_nm [22mis '*', all attribute values set  for
              the given queue instance or domain are deleted.
              The  main  difference  between  -dattr and -purge is that -dattr
              removes a value from a single  list  attribute,  whereas  -purge
              removes one or more overriding attribute settings from a cluster
              queue configuration.   With  -purge,  the  entire  attribute  is
              deleted for the given queue instance or queue domain.

       [1m-rattr obj_spec attr_name val obj_instance,...[0m
                                     [4m<replace[24m [4mobject[24m [4mattributes>[0m
              Allows replacing a single configuration list attribute in multi-
              ple instances of an object with a  single  command.   Find  more
              information concerning obj_spec and obj_instance in the descrip-
              tion of [1m-aattr .[0m
              Requires root or manager privilege.

       [1m-rsstnode node_path,...       [4m[22m<show[24m [4mshare[24m [4mtree[24m [4mnode>[0m
              Recursively shows the name and shares  of  the  specified  share
              tree  node(s)  and the names and shares of its child nodes. (see
              [4mshare_tree[24m(5)).   The   [1mnode_path   [22mis   a   hierarchical   path
              ([1m[/]node_name[[/.]node_name...][22m)   specifying  the location of a
              node in the share tree.

       [1m-sc                           [4m[22m<show[24m [4mcomplexes>[0m
              Display the complex configuration.

       [1m-scal calendar_name           [4m[22m<show[24m [4mcalendar>[0m
              Display the configuration of the specified calendar.

       [1m-scall                        [4m[22m<show[24m [4mcalendar[24m [4mlist>[0m
              Show a list of all calendars currently defined.

       [1m-sckpt ckpt_name              [4m[22m<show[24m [4mckpt.[24m [4menvironment>[0m
              Display the configuration of the specified  checkpointing  envi-
              ronment.

       [1m-sckptl                       [4m[22m<show[24m [4mckpt.[24m [4menvironment[24m [4mlist>[0m
              Show  a list of the names of all checkpointing environments cur-
              rently configured.

       [1m-sconf [host,...|global]      [4m[22m<show[24m [4mconfiguration>[0m
              Print the global or local (host specific) configuration.  If the
              optional  comma  separated  host list argument is omitted or the
              special string [1mglobal [22mis given, the global configuration is dis-
              played.   The  configuration  in effect on a certain host is the
              merger of the global configuration and the host  specific  local
              configuration.  The  format of the configuration is described in
              [4mge_conf[24m(5).

       [1m-sconfl                       [4m[22m<show[24m [4mconfiguration[24m [4mlist>[0m
              Display a list of hosts for which configurations are  available.
              The special host name [1mglobal refers to the global configuration.[0m

       [1m-sds                          [4m[22m<show[24m [4mdetached[24m [4msettings>[0m
              Displays detached settings in the cluster configuration.

       [1m-se hostname                  [4m[22m<show[24m [4mexecution[24m [4mhost>[0m
              Displays the definition of the specified execution host.

       [1m-sel                          [4m[22m<show[24m [4mexecution[24m [4mhosts>[0m
              Displays the Grid Engine execution host list.

       [1m-secl                         [4m[22m<show[24m [4mevent[24m [4mclients>[0m
              Displays the Grid Engine event client list.

       [1m-sep                          [4m[22m<show[24m [4mlicensed[24m [4mprocessors>[0m
              [1mNote: [22mDeprecated, may be removed in future release.
              Displays a list of number of processors which are  licensed  per
              execution host and in total.

       [1m-sh                           [4m[22m<show[24m [4madministrative[24m [4mhosts>[0m
              Displays the Grid Engine administrative host list.

       [1m-shgrp group                  [4m[22m<show[24m [4mhost[24m [4mgroup[24m [4mconfig.>[0m
              Displays  the  host  group  entries  for  the group specified in
              [1mgroup.[0m

       [1m-shgrpl                       [4m[22m<show[24m [4mhost[24m [4mgroup[24m [4mlists>[0m
              Displays a name list of all currently defined host groups  which
              have a valid host group configuration.

       [1m-shgrp_tree group     [4m[22m<show[24m [4mhost[24m [4mgroup[24m [4mtree>[0m
              Shows a tree like structure of host group.

       [1m-shgrp_resolved group       [4m[22m<show[24m [4mhost[24m [4mgroup[24m [4mhosts>[0m
              Shows  a  list  of all hosts which are part of the definition of
              host group. If the  host  group  definition  contains  sub  host
              groups than also these groups are resolved and the hostnames are
              printed.

       [1m-srqs [rqs_name_list]         [4m[22m<show[24m [4mRQS[24m [4mconfiguration>[0m
              Show the definition of the [4mresource[24m [4mquota[24m [4msets[24m  (RQS)  specified
              by the argument.

       [1m-srqsl                        [4m[22m<show[24m [4mRQS-list>[0m
              Show  a  list  of  all  currently  defined  [4mresource[24m [4mquota[24m [4msets[24ms
              (RQSs).

       [1m-sm                           [4m[22m<show[24m [4mmanagers>[0m
              Displays the managers list.

       [1m-so                           [4m[22m<show[24m [4moperators>[0m
              Displays the operator list.

       [1m-sobjl obj_spec attr_name val [4m[22m<show[24m [4mobject[24m [4mlist>[0m
              Shows a list of all configuration objects for which val  matches
              at  least  one  configuration value of the attributes whose name
              matches with attr_name.

              Obj_spec can be "queue" or "queue_domain" or "queue_instance" or
              "exechost".   Note:  When  "queue_domain" or "queue_instance" is
              specified as obj_spec matching is only done with  the  attribute
              overridings  concerning the host group or the execution host. In
              this case queue domain names resp. queue instances are returned.

              Attr_name can be any of the configuration file keywords enlisted
              in [4mqueue_conf[24m(5) or [4mhost_conf[24m(5).  Also wildcards can be used to
              match multiple attributes.

              Val can be an arbitrary string or a wildcard expression.

       [1m-sp pe_name                   [4m[22m<show[24m [4mPE[24m [4mconfiguration>[0m
              Show  the  definition of the [4mparallel[24m [4menvironment[24m (PE) specified
              by the argument.

       [1m-spl                          [4m[22m<show[24m [4mPE-list>[0m
              Show a list  of  all  currently  defined  [4mparallel[24m  [4menvironment[24ms
              (PEs).

       [1m-sprj project                 [4m[22m<show[24m [4mproject>[0m
              Shows  the definition of the specified project (see [4mproject[24m(5)).

       [1m-sprjl                        [4m[22m<show[24m [4mproject[24m [4mlist>[0m
              Shows the list of all currently defined projects.

       [1m-sq wc_queue_list             [22m<show queues>
              Displays one or multiple cluster queues or  queue  instances.  A
              description of wc_queue_list can be found in [4msge_types[24m(1).

       [1m-sql                          [4m[22m<show[24m [4mqueue[24m [4mlist>[0m
              Show a list of all currently defined cluster queues.

       [1m-ss                           [4m[22m<show[24m [4msubmit[24m [4mhosts>[0m
              Displays the Grid Engine submit host list.

       [1m-ssconf                       [4m[22m<show[24m [4mscheduler[24m [4mconfiguration>[0m
              Displays  the  current  scheduler  configuration  in  the format
              explained in [4msched_conf[24m(5).

       [1m-sstnode node_path,...        [4m[22m<show[24m [4mshare[24m [4mtree[24m [4mnode>[0m
              Shows the name and shares of the specified  share  tree  node(s)
              (see  [4mshare_tree[24m(5)).   The  [1mnode_path  [22mis  a  hierarchical path
              ([1m[/]node_name[[/.]node_name...][22m)  specifying the location  of  a
              node in the share tree.

       [1m-sstree                       [4m[22m<show[24m [4mshare[24m [4mtree>[0m
              Shows the definition of the share tree (see [4mshare_tree[24m(5)).

       [1m-sst                          [4m[22m<show[24m [4mformated[24m [4mshare[24m [4mtree>[0m
              Shows  the  definition  of  the  share  tree in a tree view (see
              [4mshare_tree[24m(5)).

       [1m-sss                          [4m[22m<show[24m [4mscheduler[24m [4mstatus>[0m
              Currently displays the host on which the Grid  Engine  scheduler
              is active or an error message if no scheduler is running.

       [1m-su acl_name                  [4m[22m<show[24m [4muser[24m [4mACL>[0m
              Displays a Grid Engine user access list (ACL).

       [1m-sul                          [4m[22m<show[24m [4muser[24m [4mlists>[0m
              Displays  a  list  of names of all currently defined Grid Engine
              user access lists (ACLs).

       [1m-suser user,...               [4m[22m<show[24m [4muser>[0m
              Shows the definition of the specified user(s) (see [4muser[24m(5)).

       [1m-suserl                       [4m[22m<show[24m [4musers>[0m
              Shows the list of all currently defined users.

       [1m-tsm                          [4m[22m<trigger[24m [4mscheduler[24m [4mmonitoring>[0m
              The Grid Engine scheduler is forced  by  this  option  to  print
              trace   messages   of  its  next  scheduling  run  to  the  file
              [4m<ge_root>/<cell>/common/schedd_runlog[24m.   The  messages  indicate
              the  reasons for jobs and queues not being selected in that run.
              Requires root or manager privileges.

              Note, that the reasons for job requirements being  invalid  with
              respect  to  resource availability of queues are displayed using
              the format as described for the [4mqstat[24m(1) [1m-F [22moption (see descrip-
              tion  of  [1mFull  Format [22min section [1mOUTPUT FORMATS [22mof the [4mqstat[24m(1)
              manual page.

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

       [1mGE_CELL        [22mIf  set,  specifies  the  default  Grid  Engine cell. To
                      address a Grid Engine cell [4mqconf[24m uses (in the  order  of
                      precedence):

                             The name of the cell specified in the environment
                             variable GE_CELL, if it is set.

                             The name of the default cell, i.e. [1mdefault[22m.


       [1mGE_DEBUG_LEVEL [22mIf 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.

       [1mGE_QMASTER_PORT[0m
                      If set, specifies the tcp port on which [4mge_qmaster[24m(8) is
                      expected  to  listen  for  communication requests.  Most
                      installations will use a services map entry  instead  to
                      define that port.

       [1mGE_EXECD_PORT  [22mIf  set,  specifies the tcp port on which [4mge_execd[24m(8) is
                      expected to listen  for  communication  requests.   Most
                      installations  will  use a services map entry instead to
                      define that port.

       [1mSGE_SINGLE_LINE[0m
                      If set, indicates that long lines should not  be  broken
                      up  using  backslashes.   This  setting  is  useful  for
                      scripts which expect one entry per line.

[1mRESTRICTIONS[0m
       Modifications to a queue configuration do not affect an  active  queue,
       taking effect on next invocation of the queue (i.e., the next job).

[1mFILES[0m
       [4m<ge_root>/<cell>/common/act_qmaster[0m
                      Grid Engine master host file

[1mSEE ALSO[0m
       [4mge_intro[24m(1),    [4mqstat[24m(1),    [4mcheckpoint[24m(5),   [4mcomplex[24m(5),   [4mge_conf[24m(5),
       [4mhost_conf[24m(5),  [4mge_pe[24m(5),  [4mqueue_conf[24m(5),  [4mge_execd[24m(8),   [4mge_qmaster[24m(8),
       [4mge_resource_quota[24m(5)

[1mCOPYRIGHT[0m
       See [4mge_intro[24m(1) for a full statement of rights and permissions.



GE 6.2u2                 $Date: 2008/12/23 16:56:44 $                 QCONF(1)
