QMON(1)                    Grid Engine User Commands                   QMON(1)



[1mNAME[0m
       qmon - X-Windows OSF/Motif graphical user's interface for Grid Engine

[1mSYNTAX[0m
       [1mqmon [22m[options]

[1mDESCRIPTION[0m
       [4mQmon[24m allows administrators and users to manipulate the Grid Engine sys-
       tem from an X-Window  environment.   [4mQmon[24m  provides  various  dialogues
       linked  together  in  multiple  ways.  For each task the user wishes to
       accomplish via [4mqmon[24m a corresponding dialogue  is  provided.  There  are
       multiple ways to address the proper dialogue for a certain task:


       +o  The  [4mqmon[24m  main window that comes up first on start-up contains icon
          buttons for all major administrative and user tasks. A functionality
          tooltip is displayed when pointing at the different icons.

       +o  A  [1mTask  [22mpulldown  menu  button appears in the [4mqmon[24m main window menu
          bar. Clicking on it opens a list of available tasks.  Selecting  one
          of them opens the corresponding dialogue.

       +o  The  [1mTask [22mpulldown menu also contains the key accelerators which can
          be used to invoke the task dialogues directly from the  main  window
          by pressing a certain button sequence on the keyboard.

       +o  While  navigating  through  a certain dialogue and its dialogue sub-
          hierarchy, links to other  dialogues  occur  whenever  a  connection
          between both dialogues is obvious. Pushing the buttons that identify
          the links opens up the other dialogues.

[1mOPTIONS[0m
       The supported options are the standard X Toolkit options  as  described
       in [4mX[24m(1) section [1mOptions[22m. Furthermore, [4mqmon[24m supports:

       [1m-cmap  [22mInstalls a private color map for [4mqmon.[24m  This is sometimes useful
              if other applications have already allocated lots of colors  and
              if  [4mqmon,[24m  therefore, prints corresponding error messages. [1mNote[22m,
              however, that using a private color map will result in color map
              switches whenever you enter or leave [4mqmon[24m windows.

       [1m-fontFamily {big|medium|small}[0m
              Notifies [4mqmon[24m to use different sized font families for different
              resolution sizes.

       [1m-help  [22mDisplays usage information.

       [1m-nologo[0m
              Startup without logo.

[1mDIALOGUES[0m
   [1mJob Control[0m
       The [1mJob Control [22mdialogue provides a folder of tabulated  lists  of  the
       still  pending  jobs,  already running jobs and recently finished jobs.
       The dialogue allows for detailed information on the jobs as well as for
       the  deletion  and  suspension of jobs being selected.  In addition the
       job control dialogue offers links to the [1mSubmit [22mdialogue  in  order  to
       submit  new  jobs  or to change attributes of pending jobs ([1mQalter [22mbut-
       ton). The shown displayed fields in the tabular display  and  the  jobs
       displayed can be customized by pressing the [1mCustomize [22mbutton. This cus-
       tomization can be saved to the [4m~/.qmon_preferences[24m file and is used  on
       following  startups  for  the  initial configuration of the [1mJob Control[0m
       dialogue.


   [1mQueue Control[0m
       The [1mQueue Control [22mdialogue with its sub-dialogue hierarchy enables  the
       user  to  control  the  status of the Grid Engine queues being actually
       configured in the system and allows the administrator to add new queues
       or  to  modify  or delete already existing ones. The [1mQueue Control [22mdia-
       logue shows a tabbed view of  Cluster  Queues  or  their  corresponding
       Queue Instances in a tabular way.

       By  pushing the [1mAdd[22m, [1mClone [22mor [1mModify [22mbutton, a sub-dialogue for config-
       uring Grid Engine queues is opened.  A queue needs to  be  selected  to
       use  the  clone  and  modify  operation. The configuration sub-dialogue
       allows for definition of the queue and its attributes.  The  configura-
       tion  sub-dialogue  contains  in the upper section the queue name and a
       list of hosts or hostgroups for which this queue contains the  configu-
       ration.   The  lower  section contains a list of hosts or hostgroups at
       the left, where the default attributes are shown when the "@/" entry is
       highlighted.   These default attributes can be overruled on a hostgroup
       or host basis by enabling attributes and changing  their  values  after
       this  hostgroup  or  host  entry  has been added in the "Attributes for
       Host/Hostgroup"  listbox.   The  queue  configuration  parameters  (see
       [4mqueue_conf[24m(5)) are subdivided in different categories ([1mGeneral Configu-[0m
       [1mration[22m, [1mExecution Methods[22m, [1mCheckpointing[22m, [1mLoad/Suspend Thresholds[22m, [1mLim-[0m
       [1mits[22m,  [1mComplexes[22m,  [1mUser Access[22m, [1mProject Access, Subordinate Queues, Own-[0m
       [1mers) which are selectable by the tab widget area presented in the lower[0m
       [1mregion  of the queue configuration sub-dialogue.  The administrator may[0m
       [1mselect previously configured  settings  from  already  existing  queues[0m
       [1m(Clone  button).  By  pushing the Ok button, the definitions are regis-[0m
       [1mtered with [4m[22mge_qmaster[24m(8).  The [1mQueue Control [22mdialogue can be customized
       in a similar way as the [1mJob Control [22mdialogue. The settings applied here
       are also saved in [4m~/.qmon_preferences[24m.

   [1mSubmit[0m
       The [1mJob Submission [22mdialogue serves for submitting batch and interactive
       jobs  and is also invoked when changing attributes of pending jobs from
       the [1mJob Control [22mdialogue explained above  ([1mQalter  [22mbutton).  To  toggle
       between  batch  and  interactive  jobs please use the [1mBatch/Interactive[0m
       button at the top of the button column on the right  side  of  the  [1mJob[0m
       [1mSubmission [22mscreen.

       The  dialogue  consists of a folder containing two job preparation dia-
       logue pages. The most frequently used parameters in the course of a job
       submission  are  offered  on  the  [1mGeneral [22mpage. A job script has to be
       defined, all other fields are optional. If the job demands for specifi-
       cation of advanced requirements, the [1mAdvanced [22mtab can be used to switch
       to an enhanced parameter display.

       If resource  requirements  are  mandatory  for  the  job,  the  [1mRequest[0m
       [1mResources  [22micon button has to be used to pop up the [1mRequested Resources[0m
       sub-dialogue.  This sub-dialogue allows for selection of  the  required
       resources of the job and for definition of the quantities in which this
       resources are to be provided. The [1mAvailable Resources  [22mare  constituted
       by  those complex attributes being declared [4mrequestable[24m (see [4mcomplex[24m(5)
       for details). Resource requirements can be made [1mHard[22m, i.e. they must be
       met  before  a  job  can  be started in a queue, or [1mSoft[22m, i.e. they are
       granted on an as available basis.

       Closing the [1mRequested Resources [22msub-dialogue with the done button books
       the specified requirement for the job. Pushing the [1mSubmit [22mbutton on the
       top level [1mSubmit [22mdialogue submits the job.

   [1mComplex Config[0m
       The  [1mComplex  Config  [22mallows  the  administrator  to  add  new  complex
       attributes  or to modify or delete existing ones (see [4mcomplex[24m(5)).  The
       complex configuration dialogue provides a tabulated list of the complex
       attribute  entries  and  an  input region for the declaration of new or
       modified entries. The [1mAdd [22mbutton updates the tabulated list with a  new
       attribute.   The  [1mModify  [22mbutton  changes a highlighted existing entry.
       The [1mDelete [22mbutton removes the highlighted  attributes.   The  [1mLoad  and[0m
       [1mSave  [22mbuttons  allow saving or reloading the whole attribute list to or
       from file.  The [1mOk [22mbutton registers the additional or modified  complex
       attributes with [4mge_qmaster[24m(8).

   [1mHost Config[0m
       Four  types of host related lists can be maintained via the [1mHost Config[0m
       dialogue:

              Administration Hosts
              Submit Hosts
              Host Groups
              Execution Hosts

       The host list to be manipulated is selected via clicking at one of  the
       tabs  named  correspondingly. The first two host lists only provide for
       adding or deleting entries, thereby allowing administrative  or  submit
       permission  for the hosts on the lists, or denying it otherwise respec-
       tively.  The host group list allows the manipulation  of  host  groups.
       Host  groups can reference either other host groups or hosts.  The exe-
       cution host list entries in addition  provide  the  ability  to  define
       scaling factors for the load sensors, consumable complex attributes and
       access  attributes  (access,  xaccess  and  projects,   xprojects)   as
       described  in  [4mcomplex[24m(5).  CPU, memory and I/O usage reported for run-
       ning jobs can be scaled in addition and the relative performance  of  a
       host   can   be   define  with  the  [1mResource  Capability  Factor  [22m(see
       [4mhost_conf[24m(5)).

   [1mCluster Config[0m
       This dialogue maintains the cluster global  configuration  as  well  as
       host  specific derivatives (see [4mge_conf[24m(5)).  When opened, the dialogue
       displays a selection list for all  hosts  which  have  a  configuration
       assigned.  The  special name "global" refers to the cluster global con-
       figuration. By pushing the [1mAdd/Modify [22mbutton a sub-dialogue is  opened,
       which  allows  for  modification of the cluster configuration. For host
       specific configurations the 'global' host specific configuration fields
       are set insensitive and only the allowed parameters can be manipulated.

   [1mScheduler Config[0m
       The [1mScheduler Configuration [22mdialogue provides the means to  change  the
       behavior  of  the  Grid  Engine  scheduler thread part of [4mge_qmaster[24m(8)
       process.  The dialogue contains a representation for all scheduler con-
       figuration  parameters as described in [4msched_conf[24m(5).  It is subdivided
       in the two sections [1mGeneral Parameters [22mand [1mLoad Adjustments  [22mwhich  can
       be  selected  via  the corresponding tabs.  The [1mOk [22mbutton registers any
       changes with [4mge_qmaster[24m(8).

   [1mCalendar Config[0m
       The [1mCalendar Config [22mallows the administrator to add new calendars or to
       modify  or  delete  existing ones (see [4mcalendar_conf[24m(5)).  The dialogue
       offers a selection list for the existing  calendars  and  displays  the
       configuration  of the one being selected. By pushing the [1mDelete [22mbutton,
       the selected calendar is deleted from the  configuration.  Pushing  the
       [1mAdd[22m/[1mModify  [22mbutton  will  open a calendar configuration dialogue, which
       allows to create new calendars or which provides the  means  to  change
       the  existing  ones. The [1mOk [22mbutton registers the additional or modified
       calendar with [4mge_qmaster[24m(8).

   [1mUser Config[0m
       User permissions are controlled via the [1mUser Config [22mdialogue.  The  tab
       widget in the left section of the dialogue allows for selecting between

              Configuration of [1mManager [22maccounts.
              Configuration of [1mOperator [22maccounts.
              Definition of [1mUsersets[22m.
              Definition of [1mUser [22maccounts.

       Those user accounts added to the list of manager or  operator  accounts
       are  given permission to act as managers or operators respectively when
       accessing Grid Engine under their own account.

       The userset lists are used together with the [1muser_lists [22mand [1mxuser_lists[0m
       host,   queue,   project  and  cluster  configuration  parameters  (see
       [4mqueue_conf[24m(5), [4mproject[24m(5) and [4mge_conf[24m(5)) to control access of users to
       hosts,  queues,  projects  and the entire cluster.  A userset is just a
       collection of user names and UNIX group names. Group names are  identi-
       fied  by  prefixing  them with a "@" sign. The already defined usersets
       are displayed in a selection list. These lists can be modified and  new
       lists can be created using the [1mUserset [22mdefinition dialogue.

       Usersets  can  be used as [1mAccess List [22mand/or as [1mDepartment [22mrequired for
       the so called [1mFunctional Policy [22mand [1mOverride Policy [22m(see [1mTicket  Config[0m
       below).

       User  names  can  be  added to the system as entries to the Grid Engine
       user database (see [4muser[24m(5)), This can be done with  the  [1mUser  [22msub-dia-
       logue.

       The [1mTickets [22mbutton in the button list on the right side of the dialogue
       opens the [1mTicket Config [22mdialogue (see below).

   [1mPE Config[0m
       Parallel environment (PE) interfaces can be configured with  this  dia-
       logue.   PE  interfaces  are necessary to describe the way how parallel
       programming environments like PVM (Parallel Virtual Machine), MPI (Mes-
       sage  Passing  Interface)  or  shared memory parallel systems are to be
       instantiated and to impose access restrictions onto the PEs.  When  the
       dialogue  is  opened  a list of the already configured PEs is displayed
       together with the current configuration (see [4mge_pe[24m(5)) of the  selected
       PE  interface.  To add new PE interfaces or to modify existing ones, an
       [1mAdd [22mand a [1mModify [22mbutton is available which opens a PE interface config-
       uration sub-dialogue. After applying the changes and quitting this sub-
       dialogue with the [1mOK [22mbutton, the new or modified PE interface is regis-
       tered with [4mge_qmaster[24m(8).

   [1mCheckpoint Config[0m
       Checkpointing  environment  interfaces can be configured with this dia-
       logue.   Checkpointing  environments  are  necessary  to  describe  the
       attributes  which the different checkpointing methods and their deriva-
       tives on various operating system platforms supported  by  Grid  Engine
       have.  When  the  dialogue  is  opened a list of the already configured
       checkpointing environments is displayed together with the current  con-
       figuration  (see  [4mcheckpoint[24m(5)) of the selected checkpointing environ-
       ment. To add new checkpointing environment or to modify existing  ones,
       an  [1mAdd  [22mand  a  [1mModify [22mbutton is available which opens a checkpointing
       environment configuration sub-dialogue. After applying the changes  and
       quitting  this  sub-dialogue  with  the  [1mOK [22mbutton, the new or modified
       checkpointing environment is registered with [4mge_qmaster[24m(8).

   [1mTicket Conf[0m
       This dialogue offers an overview  and  editing  screen  for  allocating
       tickets  to  the  share-based, functional and override scheduling poli-
       cies.

       The [1mDeadline Job [22mbutton opens  the  [1mUser  Conf  [22mdialogue  box.   Please
       change  to the Userset sub-dialogue and select the userset named "dead-
       lineusers".  Only users of this userset may submit deadline jobs.

       The [1mShare Tree Policy [22mbutton opens the dialogue for creating and  edit-
       ing  the  Grid  Engine share tree (see [4mshare_tree[24m(5) and [4mschedd_conf[24m(5)
       for a description of the configuration parameters).

       The [1mFunctional Policy [22mbutton opens the dialogue for creating and  edit-
       ing  the  allocation  of  the  functional  shares  (see  [4msched_conf[24m(5),
       [4maccess_list[24m(5), [4mproject[24m(5), [4mqueue_conf[24m(5) and [4muser[24m(5) for a description
       of  the  different  types  of  functional  shares  and the configurable
       weighting parameters).

       The [1mOverride Policy [22mbutton opens the dialogue for creating and  editing
       the  allocation  of  override  tickets (see [4maccess_list[24m(5), [4mproject[24m(5),
       [4mqueue_conf[24m(5) and [4muser[24m(5) for a description of the different  types  of
       override tickets).

   [1mProject Conf[0m
       This button opens a dialog for creating projects.
       The dialogue offers a selection list for the existing projects and dis-
       plays the configuration of the  one  being  selected.  By  pushing  the
       [1mDelete  [22mbutton, the selected project is deleted from the configuration.
       Pushing the [1mAdd[22m/[1mModify [22mbutton will open a  project  configuration  dia-
       logue,  which allows to create new projects or which provides the means
       to change the existing ones. Project  configuration  in  essence  means
       giving or denying access to a project for usersets (see [1mUser Conf [22mabove
       as well as [4mproject[24m(5)).  The Ok button registers the additional or mod-
       ified project with [4mge_qmaster[24m(8).

   [1mBrowser[0m
       The  [1mObject  Browser [22mdialogue's purpose is manifold: First of all, Grid
       Engine and [4mqmon[24m messages such as notification of error or success  con-
       cerning  a  previously  taken action can be displayed in the dialogue's
       output window.  Also the standard output and the standard error  output
       of [4mqmon[24m can be diverted to the [1mObject Browser [22moutput window.

       Additionally  the  [1mObject  Browser  [22mcan  be  used to display continuous
       information about Grid Engine objects as the mouse pointer  moves  over
       their representation as icons or table entries in other [4mqmon[24m dialogues.
       Currently, only the display of the configuration  of  two  Grid  Engine
       objects in two separate dialogues is supported:

       +o  Queue  configurations  are  displayed  as  soon as the mouse pointer
          enters a queue icon in the top level  [1mQueue  Control  [22mdialogue  (see
          above).  This  facility  is activated by pushing the [1mQueue [22mbutton in
          the [1mObject Browser [22mdialogue.

       +o  Detailed job information is printed as soon as the  user  moves  the
          mouse  pointer  over  a line in the [1mJob Control [22mdialogue (see above)
          being assigned to a running or pending job.

       +o  Additionally job scheduling information is displayed in the  browser
          if  the [1mWhy ? [22mbutton in the [1mJob Control [22mdialogue is pressed. In this
          case the Browser dialogue is opened implicitly  and  any  scheduling
          related information is displayed.

   [1mExit[0m
       The [1mExit [22micon button is not linked with a dialogue. Its sole purpose is
       to close all active [4mqmon[24m dialogues and to exit the application.

[1mRESOURCES[0m
       The available resources, their meaning and the syntax to be followed in
       order  to  modify  them are described in the default [4mqmon[24m resource file
       (see the section [1mFiles [22mbelow for the location of the resource file).

[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 [4mqmon[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.

[1mRESTRICTIONS[0m
       If the line to be entered in an editing window is longer than the width
       of the window, then the text just runs off the end of the window.

[1mFILES[0m
       [4m<ge_root>/qmon/Qmon[24m            [4mQmon[24m sample resources file
       [4m/usr/lib/X11/defaults/Qmon[24m     [4mQmon[24m system resources file
       [4m$HOME/Qmon[24m                     [4mQmon[24m user resources file
       [4m$HOME/.qmon_preferences[24m        [4mQmon[24m job/queue customization file


[1mSEE ALSO[0m
       [4mge_intro[24m(1), [4mge_conf[24m(5),  [4maccess_list[24m(5),  [4mge_pe[24m(5),  [4mcalendar_conf[24m(5),
       [4mcomplex[24m(5), [4mproject[24m(5), [4mqueue_conf[24m(5), [4msched_conf[24m(5), [4muser[24m(5), [4mge_qmas-[0m
       [4mter[24m(8).

[1mCOPYRIGHT[0m
       See     [4mge_intro[24m(1)     and     the     information     provided     in
       <ge_root>/3rd_party/qmon  for a statement of further rights and permis-
       sions and for credits to be given to public domain and freeware  widget
       developers.



GE 6.2u2                 $Date: 2008/05/05 09:03:33 $                  QMON(1)
