4
<!-- Manpage converted by man2html 3.0.1 -->
6
qmon - X-Windows OSF/Motif graphical user's interface for
13
<I>Qmon</I> allows administrators and users to manipulate the Grid
14
Engine system from an X-Window environment. <I>Qmon</I> provides
15
various dialogues linked together in multiple ways. For
16
each task the user wishes to accomplish via <I>qmon</I> a
17
corresponding dialogue is provided. There are multiple ways
18
to address the proper dialogue for a certain task:
20
<B>o</B> The <I>qmon</I> main window that comes up first on start-up con-
21
tains icon buttons for all major administrative and user
22
tasks. A functionality tooltip is displayed when pointing
23
at the different icons.
25
<B>o</B> A Task pulldown menu button appears in the <I>qmon</I> main win-
26
dow menu bar. Clicking on it opens a list of available
27
tasks. Selecting one of them opens the corresponding
30
<B>o</B> The Task pulldown menu also contains the key accelerators
31
which can be used to invoke the task dialogues directly
32
from the main window by pressing a certain button
33
sequence on the keyboard.
35
<B>o</B> While navigating through a certain dialogue and its
36
dialogue subhierarchy, links to other dialogues occur
37
whenever a connection between both dialogues is obvious.
38
Pushing the buttons that identify the links opens up the
42
The supported options are the standard X Toolkit options as
43
described in <B><A HREF="../htmlman1/X.html">X(1)</A></B> section Options. Furthermore, <I>qmon</I> sup-
47
Installs a private color map for <I>qmon</I>. This is some-
48
times useful if other applications have already allo-
49
cated lots of colors and if <I>qmon</I>, therefore, prints
50
corresponding error messages. Note, however, that using
51
a private color map will result in color map switches
52
whenever you enter or leave <I>qmon</I> windows.
54
-fontFamily {big|medium|small}
55
Notifies <I>qmon</I> to use different sized font families for
56
different resolution sizes.
59
Displays usage information.
66
The Job Control dialogue provides a folder of tabulated
67
lists of the still pending jobs, already running jobs and
68
recently finished jobs. The dialogue allows for detailed
69
information on the jobs as well as for the deletion and
70
suspension of jobs being selected. In addition the job con-
71
trol dialogue offers links to the Submit dialogue in order
72
to submit new jobs or to change attributes of pending jobs
73
(Qalter button). The shown displayed fields in the tabular
74
display and the jobs displayed can be customized by pressing
75
the Customize button. This customization can be saved to the
76
~/.<I>qmon</I>_<I>preferences</I> file and is used on following startups
77
for the initial configuration of the Job Control dialogue.
81
The Queue Control dialogue with its sub-dialogue hierarchy
82
enables the user to control the status of the Grid Engine
83
queues being actually configured in the system and allows
84
the administrator to add new queues or to modify or delete
85
already existing ones. The Queue Control dialogue shows a
86
tabbed view of Cluster Queues or their corresponding Queue
87
Instances in a tabular way.
89
By pushing the Add, Clone or Modify button, a sub-dialogue
90
for configuring Grid Engine queues is opened. A queue needs
91
to be selected to use the clone and modify operation. The
92
configuration sub-dialogue allows for definition of the
93
queue and its attributes. The configuration sub-dialogue
94
contains in the upper section the queue name and a list of
95
hosts or hostgroups for which this queue contains the confi-
96
guration. The lower section contains a list of hosts or
97
hostgroups at the left, where the default attributes are
98
shown when the "@/" entry is highlighted. These default
99
attributes can be overruled on a hostgroup or host basis by
100
enabling attributes and changing their values after this
101
hostgroup or host entry has been added in the "Attributes
102
for Host/Hostgroup" listbox. The queue configuration parame-
103
ters (see <B><A HREF="../htmlman5/queue_conf.html">queue_conf(5)</A></B>) are subdivided in different
104
categories (General Configuration, Execution Methods, Check-
105
pointing, Load/Suspend Thresholds, Limits, Complexes, User
106
Access, Project Access, Subordinate Queues, Owners) which
107
are selectable by the tab widget area presented in the lower
108
region of the queue configuration sub-dialogue. The adminis-
109
trator may select previously configured settings from
110
already existing queues (Clone button). By pushing the Ok
111
button, the definitions are registered with <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
112
The Queue Control dialogue can be customized in a similar
113
way as the Job Control dialogue. The settings applied here
114
are also saved in ~/.<I>qmon</I>_<I>preferences</I>.
117
The Job Submission dialogue serves for submitting batch and
118
interactive jobs and is also invoked when changing attri-
119
butes of pending jobs from the Job Control dialogue
120
explained above (Qalter button). To toggle between batch and
121
interactive jobs please use the Batch/Interactive button at
122
the top of the button column on the right side of the Job
125
The dialogue consists of a folder containing two job
126
preparation dialogue pages.The most frequently used parame-
127
ters in the course of a job submission are offered on the
128
General page. A job script has to be defined, all other
129
fields are optional. If the job demands for specification of
130
advanced requirements, the Advanced tab can be used to
131
switch to an enhanced parameter display.
133
If resource requirements are mandatory for the job, the
134
Request Resources icon button has to be used to pop up the
135
Requested Resources sub-dialogue. This sub-dialogue allows
136
for selection of the required resources of the job and for
137
definition of the quantities in which this resources are to
138
be provided. The Available Resources are constituted by
139
those complex attributes being declared <I>requestable</I> (see
140
<B><A HREF="../htmlman5/complex.html">complex(5)</A></B> for details). Resource requirements can be made
141
Hard, i.e. they must be met before a job can be started in a
142
queue, or Soft, i.e. they are granted on an as available
145
Closing the Requested Resources sub-dialogue with the done
146
button books the specified requirement for the job. Pushing
147
the Submit button on the top level Submit dialogue submits
151
The Complex Config allows the administrator to add new com-
152
plex attributes or to modify or delete existing ones (see
153
<B><A HREF="../htmlman5/complex.html">complex(5)</A></B>). The complex configuration dialogue provides a
154
tabulated list of the complex attribute entries and an input
155
region for the declaration of new or modified entries. The
156
Add button updates the tabulated list with a new attribute.
157
The Modify button changes a highlighted existing entry. The
158
Delete button removes the highlighted attributes. The Load
159
and Save buttons allow saving or reloading the whole attri-
160
bute list to or from file. The Ok button registers the
161
additional or modified complex attributes with
162
<B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
165
Four types of host related lists can be maintained via the
166
Host Config dialogue:
173
The host list to be manipulated is selected via clicking at
174
one of the tabs named correspondingly. The first two host
175
lists only provide for adding or deleting entries, thereby
176
allowing administrative or submit permission for the hosts
177
on the lists, or denying it otherwise respectively. The
178
host group list allows the manipulation of host groups. Host
179
groups can reference either other host groups or hosts. The
180
execution host list entries in addition provide the ability
181
to define scaling factors for the load sensors, consumable
182
complex attributes and access attributes (access, xaccess
183
and projects, xprojects) as described in <B><A HREF="../htmlman5/complex.html">complex(5)</A></B>. CPU,
184
memory and I/O usage reported for running jobs can be scaled
185
in addition and the relative performance of a host can be
186
define with the Resource Capability Factor (see
187
<B><A HREF="../htmlman5/host_conf.html">host_conf(5)</A></B>).
190
This dialogue maintains the cluster global configuration as
191
well as host specific derivatives (see <B><A HREF="../htmlman5/sge_conf.html">sge_conf(5)</A></B>). When
192
opened, the dialogue displays a selection list for all hosts
193
which have a configuration assigned. The special name "glo-
194
bal" refers to the cluster global configuration. By pushing
195
the Add/Modify button a sub-dialogue is opened, which allows
196
for modification of the cluster configuration. For host
197
specific configurations the 'global' host specific confi-
198
guration fields are set insensitive and only the allowed
199
parameters can be manipulated.
202
The Scheduler Configuration dialogue provides the means to
203
change the behavior of the Grid Engine scheduler daemon
204
<B><A HREF="../htmlman8/sge_schedd.html">sge_schedd(8)</A></B>. The dialogue contains a representation for
205
all scheduler configuration parameters as described in
206
<B><A HREF="../htmlman5/sched_conf.html">sched_conf(5)</A></B>. It is subdivided in the two sections General
207
Parameters and Load Adjustments which can be selected via
208
the corresponding tabs. The Ok button registers any changes
209
with <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
212
The Calendar Config allows the administrator to add new
213
calendars or to modify or delete existing ones (see
214
<B><A HREF="../htmlman5/calendar_conf.html">calendar_conf(5)</A></B>). The dialogue offers a selection list for
215
the existing calendars and displays the configuration of the
216
one being selected. By pushing the Delete button, the
217
selected calendar is deleted from the configuration. Pushing
218
the Add/Modify button will open a calendar configuration
219
dialogue, which allows to create new calendars or which pro-
220
vides the means to change the existing ones. The Ok button
221
registers the additional or modified calendar with
222
<B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
225
User permissions are controlled via the User Config dialo-
226
gue. The tab widget in the left section of the dialogue
227
allows for selecting between
229
Configuration of Manager accounts.
230
Configuration of Operator accounts.
231
Definition of Usersets.
232
Definition of User accounts.
234
Those user accounts added to the list of manager or operator
235
accounts are given permission to act as managers or opera-
236
tors respectively when accessing Grid Engine under their own
239
The userset lists are used together with the user_lists and
240
xuser_lists host, queue, project and cluster configuration
241
parameters (see <B><A HREF="../htmlman5/queue_conf.html">queue_conf(5)</A></B>, <B><A HREF="../htmlman5/project.html">project(5)</A></B> and <B><A HREF="../htmlman5/sge_conf.html">sge_conf(5)</A></B>)
242
to control access of users to hosts, queues, projects and
243
the entire cluster. A userset is just a collection of user
244
names and UNIX group names. Group names are identified by
245
prefixing them with a "@" sign. The already defined usersets
246
are displayed in a selection list. These lists can be modi-
247
fied and new lists can be created using the Userset defini-
250
Usersets can be used as Access List and/or as Department
251
required for the so called Functional Policy and Override
252
Policy (see Ticket Config below).
254
User names can be added to the system as entries to the Grid
255
Engine user database (see <B><A HREF="../htmlman5/user.html">user(5)</A></B>), This can be done with
256
the User sub-dialogue.
258
The Tickets button in the button list on the right side of
259
the dialogue opens the Ticket Config dialogue (see below).
262
Parallel environment (PE) interfaces can be configured with
263
this dialogue. PE interfaces are necessary to describe the
264
way how parallel programming environments like PVM (Parallel
265
Virtual Machine), MPI (Message Passing Interface) or shared
266
memory parallel systems are to be instantiated and to impose
267
access restrictions onto the PEs. When the dialogue is
268
opened a list of the already configured PEs is displayed
269
together with the current configuration (see <B><A HREF="../htmlman5/sge_pe.html">sge_pe(5)</A></B>) of
270
the selected PE interface. To add new PE interfaces or to
271
modify existing ones, an Add and a Modify button is avail-
272
able which opens a PE interface configuration sub-dialogue.
273
After applying the changes and quitting this sub-dialogue
274
with the OK button, the new or modified PE interface is
275
registered with <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
278
Checkpointing environment interfaces can be configured with
279
this dialogue. Checkpointing environments are necessary to
280
describe the attributes which the different checkpointing
281
methods and their derivatives on various operating system
282
platforms supported by Grid Engine have. When the dialogue
283
is opened a list of the already configured checkpointing
284
environments is displayed together with the current confi-
285
guration (see <B><A HREF="../htmlman5/checkpoint.html">checkpoint(5)</A></B>) of the selected checkpointing
286
environment. To add new checkpointing environment or to
287
modify existing ones, an Add and a Modify button is avail-
288
able which opens a checkpointing environment configuration
289
sub-dialogue. After applying the changes and quitting this
290
sub-dialogue with the OK button, the new or modified check-
291
pointing environment is registered with <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
294
This dialogue offers an overview and editing screen for
295
allocating tickets to the share-based, functional and over-
296
ride scheduling policies.
298
The Deadline Job button opens the User Conf dialogue box.
299
Please change to the Userset sub-dialogue and select the
300
userset named "deadlineusers". Only users of this userset
301
may submit deadline jobs.
303
The Share Tree Policy button opens the dialogue for creating
304
and editing the Grid Engine share tree (see <B><A HREF="../htmlman5/share_tree.html">share_tree(5)</A></B>
305
and <B><A HREF="../htmlman5/schedd_conf.html">schedd_conf(5)</A></B> for a description of the configuration
308
The Functional Policy button opens the dialogue for creating
309
and editing the allocation of the functional shares (see
310
<B><A HREF="../htmlman5/sched_conf.html">sched_conf(5)</A></B>, <B><A HREF="../htmlman5/access_list.html">access_list(5)</A></B>, <B><A HREF="../htmlman5/project.html">project(5)</A></B>, <B><A HREF="../htmlman5/queue_conf.html">queue_conf(5)</A></B> and
311
<B><A HREF="../htmlman5/user.html">user(5)</A></B> for a description of the different types of func-
312
tional shares and the configurable weighting parameters).
314
The Override Policy button opens the dialogue for creating
315
and editing the allocation of override tickets (see
316
<B><A HREF="../htmlman5/access_list.html">access_list(5)</A></B>, <B><A HREF="../htmlman5/project.html">project(5)</A></B>, <B><A HREF="../htmlman5/queue_conf.html">queue_conf(5)</A></B> and <B><A HREF="../htmlman5/user.html">user(5)</A></B> for a
317
description of the different types of override tickets).
320
This button opens a dialog for creating projects.
321
The dialogue offers a selection list for the existing pro-
322
jects and displays the configuration of the one being
323
selected. By pushing the Delete button, the selected project
324
is deleted from the configuration. Pushing the Add/Modify
325
button will open a project configuration dialogue, which
326
allows to create new projects or which provides the means to
327
change the existing ones. Project configuration in essence
328
means giving or denying access to a project for usersets
329
(see User Conf above as well as <B><A HREF="../htmlman5/project.html">project(5)</A></B>). The Ok button
330
registers the additional or modified project with
331
<B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
334
The Object Browser dialogue's purpose is manifold: First of
335
all, Grid Engine and <I>qmon</I> messages such as notification of
336
error or success concerning a previously taken action can be
337
displayed in the dialogue's output window. Also the stan-
338
dard output and the standard error output of <I>qmon</I> can be
339
diverted to the Object Browser output window.
341
Additionally the Object Browser can be used to display con-
342
tinuous information about Grid Engine objects as the mouse
343
pointer moves over their representation as icons or table
344
entries in other <I>qmon</I> dialogues. Currently, only the display
345
of the configuration of two Grid Engine objects in two
346
separate dialogues is supported:
348
<B>o</B> Queue configurations are displayed as soon as the mouse
349
pointer enters a queue icon in the top level Queue Con-
350
trol dialogue (see above). This facility is activated by
351
pushing the Queue button in the Object Browser dialogue.
353
<B>o</B> Detailed job information is printed as soon as the user
354
moves the mouse pointer over a line in the Job Control
355
dialogue (see above) being assigned to a running or pend-
358
<B>o</B> Additionally job scheduling information is displayed in
359
the browser if the Why ? button in the Job Control dialo-
360
gue is pressed. In this case the Browser dialogue is
361
opened implicitly and any scheduling related information
365
The Exit icon button is not linked with a dialogue. Its sole
366
purpose is to close all active <I>qmon</I> dialogues and to exit
370
The available resources, their meaning and the syntax to be
371
followed in order to modify them are described in the
372
default <I>qmon</I> resource file (see the section Files below for
373
the location of the resource file).
375
ENVIRONMENTAL VARIABLES
376
SGE_ROOT Specifies the location of the Grid Engine
377
standard configuration files.
379
SGE_CELL If set, specifies the default Grid Engine
380
cell. To address a Grid Engine cell <I>qmon</I> uses
381
(in the order of precedence):
383
The name of the cell specified in the
384
environment variable SGE_CELL, if it is
387
The name of the default cell, i.e.
392
If set, specifies that debug information
393
should be written to stderr. In addition the
394
level of detail in which debug information is
395
generated is defined.
398
If set, specifies the tcp port on which
399
<B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B> is expected to listen for com-
400
munication requests. Most installations will
401
use a services map entry instead to define
405
If the line to be entered in an editing window is longer
406
than the width of the window, then the text just runs off
407
the end of the window.
410
<<I>sge</I>_<I>root</I>>/<I>qmon</I>/<I>Qmon</I> <I>Qmon</I> sample resources file
411
/<I>usr</I>/<I>lib</I>/<I>X11</I>/<I>defaults</I>/<I>Qmon</I> <I>Qmon</I> system resources file
412
$<I>HOME</I>/<I>Qmon</I> <I>Qmon</I> user resources file
413
$<I>HOME</I>/.<I>qmon</I>_<I>preferences</I> <I>Qmon</I> job/queue customization file
417
<B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B>, <B><A HREF="../htmlman5/sge_conf.html">sge_conf(5)</A></B>, <B><A HREF="../htmlman5/access_list.html">access_list(5)</A></B>, <B><A HREF="../htmlman5/sge_pe.html">sge_pe(5)</A></B>,
418
<B><A HREF="../htmlman5/calendar_conf.html">calendar_conf(5)</A></B>, <B><A HREF="../htmlman5/complex.html">complex(5)</A></B>, <B><A HREF="../htmlman5/project.html">project(5)</A></B>, <B><A HREF="../htmlman5/queue_conf.html">queue_conf(5)</A></B>,
419
<B><A HREF="../htmlman5/sched_conf.html">sched_conf(5)</A></B>, <B><A HREF="../htmlman5/user.html">user(5)</A></B>, <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
422
See <B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B> and the information provided in
423
<sge_root>/3rd_party/qmon for a statement of further rights
424
and permissions and for credits to be given to public domain
425
and freeware widget developers.
478
Man(1) output converted with
479
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>