1
!!___INFO__MARK_BEGIN__
2
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
4
!! The Contents of this file are made available subject to the terms of
5
!! the Sun Industry Standards Source License Version 1.2
7
!! Sun Microsystems Inc., March, 2001
10
!! Sun Industry Standards Source License Version 1.2
11
!! =================================================
12
!! The contents of this file are subject to the Sun Industry Standards
13
!! Source License Version 1.2 (the "License"); You may not use this file
14
!! except in compliance with the License. You may obtain a copy of the
15
!! License at http://gridengine.sunsource.net/Gridengine_SISSL_license.html
17
!! Software provided under this License is provided on an "AS IS" basis,
18
!! WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
19
!! WITHOUT LIMITATION, WARRANTIES THAT THE SOFTWARE IS FREE OF DEFECTS,
20
!! MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NON-INFRINGING.
21
!! See the License for the specific provisions governing your rights and
22
!! obligations concerning the Software.
24
!! The Initial Developer of the Original Code is: Sun Microsystems, Inc.
26
!! Copyright: 2001 by Sun Microsystems, Inc.
28
!! All Rights Reserved.
30
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
32
Qmon*xmtHelpTitle: Qmon Graphical User Interface Help
34
No help available for this topic !
36
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
37
Qmon*MainControl.?.xmtHelpTitle: Main Control Help
38
Qmon*MainControl.?.xmtHelp: \
39
This is @fBQmon Main Control@fR click one of the icons to activate it.\n\
40
Use @fBHelp->Context Help@fR on the icons to get further information.
42
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
43
Qmon*JOB_CONTROL.xmtHelpTitle: Job Control Help
44
Qmon*JOB_CONTROL.xmtHelp: \
45
The @fBJob Control@fR dialogue is opened by pressing the @fBJob Control Icon@fR\n\
46
or by selecting @fBJob Control@fR in the @fBTask@fR menu.\n\
48
The purpose of this dialogue is to provide the means to monitor all running and\n\
49
pending jobs known to the Grid Engine system.\n\
51
The dialogue can also be used to manipulate jobs, i.e. to change their attributes,\n\
52
to suspend, resume and to cancel them.\n\
53
Three listings are displayed one for the pending jobs, one for the running jobs\n\
54
and one for recently finished jobs.
56
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
57
Qmon*QUEUE_CONTROL.xmtHelpTitle: Queue Control Help
58
Qmon*QUEUE_CONTROL.xmtHelp: \
59
The @fBQueue Control@fR dialogue is opened by pressing the @fBQueue Control Icon@fR\n\
60
or by selecting @fBQueue Control@fR in the @fBTask@fR menu.\n\
62
The @fBQueue Control@fR dialogue provides a quick overview of available queues, their\n\
63
state and the cluster activity. Here queues can be added, modified and deleted.\n\
64
It also provides the means to suspend/unsuspend and to disable/enable queues.
66
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
67
Qmon*SUBMIT_JOB.xmtHelpTitle: Submit Job Help
68
Qmon*SUBMIT_JOB.xmtHelp: \
69
The @fBJob Submission@fR dialogue is opened by pressing the @fBJob Submit Icon@fR\n\
70
or by selecting @fBJob Submit@fR in the @fBTask@fR menu.\n\
71
Another possibility to bring up the @fBJob Submission@fR dialogue, is to push the\n\
72
@fBSubmit@fR button in the @fBJob Control@fR dialogue.\n\
74
The @fBJob Submission@fR dialogue delivers a form to select a Grid Engine job script and to\n\
75
specify its special requirements. After filling in this form the job can be submitted\n\
76
to the Grid Engine system.
78
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
79
Qmon*COMPLEX_CONFIG.xmtHelpTitle: Complex Configuration Help
80
Qmon*COMPLEX_CONFIG.xmtHelp: \
81
The @fBComplex Configuration@fR dialogue is opened by pushing the @fBComplex Config Icon@fR\n\
82
or by selecting @fBComplex Config@fR in the @fBTask@fR menu.\n\
84
The @fBComplex Configuration@fR dialogue displays all defined Grid Engine complexes and their\n\
85
respective attributes. @fBComplexes@fR are used to attach special behavior to queues and\n\
88
Further information about the Grid Engine complex concept is documented in Chapter 12 of the\n\
91
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
92
Qmon*HOST_CONFIG.xmtHelpTitle: Host Configuration Help
93
Qmon*HOST_CONFIG.xmtHelp: \
94
The @fBHost Configuration@fR dialogue is invoked by pushing the @fBHost Config Icon@fR\n\
95
or by selecting @fBHost Config@fR in the @fBTask@fR menu.\n\
97
The @fBHost Configuration@fR dialogue serves to add or remove hosts to/from the\n\
98
@fBGrid Engine system@fR. There are four types of hosts available in Grid Engine.\n\
100
The @fBMaster Host@fR is central for the overall cluster activity. It runs the\n\
101
master daemon @fBsge_qmaster@fR.\n\
102
The master host requires no further configuration other than performed by the\n\
103
installation procedure.\n\
105
The @fBExecution Hosts@fR are nodes having permission to execute Grid Engine jobs.\n\
106
Therefore they are hosting Grid Engine queues and run the Grid Engine execution daemon\n\
109
@fBAdministration Hosts@fR are hosts to carry out any kind of administrative activities\n\
110
or interaction to Grid Engine. To perform administrative tasks it is necessary to do it from\n\
111
an @fBAdministration Host@fR.\n\
113
@fBSubmit Hosts@fR allow for submitting and controlling batch jobs.\n\
115
Choose the corresponding dialogue section through the option menu at the top of the\n\
116
dialogue to add and delete hosts of the corresponding category or to modify the scalings\n\
117
and the access of an execution host.
119
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
120
Qmon*CLUSTER_CONFIG.xmtHelpTitle: Cluster Configuration Help
121
Qmon*CLUSTER_CONFIG.xmtHelp: \
122
The @fBCluster Configuration@fR dialogue pops up on pressing the @fBCluster Config Icon@fR\n\
123
or by selecting @fBCluster Configuration@fR from the @fBTask@fR menu.\n\
125
The @fBCluster Configuration@fR dialogue allows the display and setting of site\n\
126
dependent configuration information like valid paths for programs such as @fBmail@fR\n\
127
or @fBxterm@fR and the setting of parameters to influence Grid Engine behavior.\n\
129
There is a @fBglobal@fR configuration, which is provided for the Grid Engine master host as\n\
130
well as every execution host. In addition, the Grid Engine system may be configured to\n\
131
use a configuration @fBlocal@fR to every execution host which overrides the entries in the\n\
132
global configuration.
134
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
135
Qmon*SCHED_CONFIG.xmtHelpTitle: Scheduler Configuration Help
136
Qmon*SCHED_CONFIG.xmtHelp: \
137
The @fBScheduler Configuration@fR dialogue pops up on pressing the @fBScheduler Config Icon@fR\n\
138
or by selecting @fBScheduler Configuration@fR from the @fBTask@fR menu.\n\
140
The @fBScheduler Configuration@fR dialogue allows the display and setting of scheduler\n\
141
specific parameters to influence the Grid Engine scheduler's behavior.
143
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
144
Qmon*CALENDAR_CONFIG.xmtHelpTitle: Calendar Configuration Help
145
Qmon*CALENDAR_CONFIG.xmtHelp: \
146
The @fBCalendar Configuration@fR dialogue is opened by clicking on the @fBCalendar Configuration Icon@fR\n\
147
or by selecting @fBCalendar Configuration@fR in the @fBTask@fR menu.\n\
149
@fBCalendar Objects@fR can be added, modified or removed from the Grid Engine system with the\n\
150
@fBCalendar Configuration@fR dialogue. They can be attached to queues to restrict queue accessibility\n\
151
to the calendar specified times.
153
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
154
Qmon*USER_CONFIG.xmtHelpTitle: User Configuration Help
155
Qmon*USER_CONFIG.xmtHelp: \
156
The @fBUser Configuration@fR dialogue is opened by clicking on the @fBUser Config Icon@fR\n\
157
or by selecting @fBUser Config@fR in the @fBTask@fR menu.\n\
159
@fBManagers, Operators and User Access Lists@fR can be added or removed from the\n\
160
Grid Engine system with the @fBUser Configuration@fR dialogue.\n\
162
There are four user categories in Grid Engine: @fBManagers, Operators, Owners, Users@fR.\n\
164
@fBManagers@fR have full capabilities to manipulate Grid Engine. By default the superuser\n\
165
of the master host and any machine hosting a queue have manager privileges.\n\
167
@fBOperators@fR can perform the same commands as managers except that they cannot\n\
168
add, delete or modify queues.\n\
170
@fBOwners@fR are restricted to suspending/unsuspending or disabling/enabling the owned\n\
173
@fBUsers@fR have certain access permissions (see User Access Permissions in the manuals)\n\
174
but no cluster or queue management capabilities.\n\
175
In @fBGrid Engine Enterprise Edition@fR mode useresets are used additionally as departments. Departments can contain\n\
176
tickets and influence therefore also the importance of a user's job in the Grid Engine Enterprise Edition system.\n\
177
For the Grid Engine Enterprise Edition case users have to be defined in the @fBUser@fR tab dialogue page. These users\n\
178
can then be added to the different @fBPolicy@fR dialogues and prioritized against other users.
181
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
182
Qmon*PE_CONFIG.xmtHelpTitle: PE Configuration Help
183
Qmon*PE_CONFIG.xmtHelp: \
184
The @fBPE Configuration@fR dialogue is opened by clicking on the @fBPE Config Icon@fR\n\
185
or by selecting @fBPE Configuration@fR in the @fBTask@fR menu.\n\
187
The @fBPE Configuration@fR dialogue serves to configure @fBparallel environments@fR\n\
188
for the Grid Engine system.\n\
190
The environments configured here can be used for submitting parallel jobs to one of the\n\
191
configured @fBParallel Environments@fR.
193
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
194
Qmon*PROJECT_CONFIG.xmtHelpTitle: Project Configuration
195
Qmon*PROJECT_CONFIG.xmtHelp: \
196
The @fBProject Configuration@fR dialogue is opened by clicking on the @fBProject Config Icon@fR\n\
197
or by selecting @fBProject Configuration@fR in the @fBTask@fR menu.\n\
199
The @fBProject Configuration@fR dialogue allows the definition and manipulation of Grid Engine Enterprise Edition\n\
202
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
203
Qmon*TICKET_OVERVIEW.xmtHelpTitle: Ticket Overview
204
Qmon*TICKET_OVERVIEW.xmtHelp: \
205
The @fBTicket Overview@fR dialogue allows the overview and manipulation of the\n\
206
ticket based scheduling policies of Grid Engine Enterprise Edition.\n\
208
From here access is available to the @fBShare Tree Policy@fR, to the\n\
209
@fBFunctional Policy@fR and to the @fBOverride Policy@fR dialogues.
211
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
212
Qmon*CKPT_CONFIG.xmtHelpTitle: Checkpointing Configuration
213
Qmon*CKPT_CONFIG.xmtHelp: \
214
The @fBCheckpoint Configuration@fR dialogue is opened by clicking on the @fBCheckpoint\n\
215
Config Icon@fR or by selecting @fBCheckpoint Configuration@fR in the @fBTask@fR menu.\n\
217
The @fBCheckpoint Configuration@fR dialogue provides the possibility to add and change\n\
218
Grid Engine checkpointing objects.\n\
219
Checkpointing is a facility to save the complete status of an executing program or job\n\
220
and to restore and restart from this so called checkpoint at a later point of time if the\n\
221
original program or job has been interrupted, e.g. by a system crash.\n\
223
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
224
Qmon*BROWSER.xmtHelpTitle: Qmon Browser Help
225
Qmon*BROWSER.xmtHelp: \
226
To open the @fBObject Browser@fR click on the icon or select @fBBrowser Dialog@fR\n\
227
in the @fBTask@fR menu.\n\
229
The @fBObject Browser@fR provides the possibility to show information\n\
230
about the Grid Engine objects Queue and Job, to show the output of stderr/stdout\n\
231
and to show messages of interactions of qmon with the Grid Engine system.\n\
232
Apart from that the @fBBrowser@fR is opened when the @fBWhy ?@fR button of the\n\
233
@fBJob Control@fR dialogue is pressed to show the reasons why a job cannot be scheduled.
235
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
236
Qmon*EXIT.xmtHelpTitle: Exit Help
238
Pressing the @fBExit@fR icon or selecting @fBFile->Exit@fR or simply pressing @fBCtrl + C@fR\n\
239
causes @fBqmon@fR to exit.
246
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
247
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
248
Qmon*qmon_job.job_main_layout*xmtHelpTitle: Job Control Help
249
Qmon*qmon_job.job_main_layout*xmtHelp: \
250
The @fBJob Control@fR dialogue permits the controlling and monitoring of all running\n\
251
and pending jobs known to the system. Here it is possible to influence the jobs in\n\
253
- open the @fBSubmit Dialogue@fR with the @fBSubmit@fR button\n\
254
- open the @fBTicket Overview@fR with the @fBTickets@fR button (only in Grid Engine Enterprise Edition mode)\n\
255
- @fBSuspend, Resume and Delete@fR jobs\n\
256
- ask for the reason @fBWhy ?@fR a job cannot be scheduled\n\
257
- change the hold state of jobs with the @fBHold@fR button\n\
258
- change the priority of pending jobs with the @fBPriority@fR button\n\
259
- change the attributes of pending jobs with @fBQalter@fR\n\
260
- clear job error states with @fBClear Error@fR\n\
261
- adjust the display behavior and the kind of jobs displayed with @fBCustomize@fR.\n\
263
Three list environments are displayed in a folder page.\n\
264
One for the still @fBPending Jobs@fR waiting to be dispatched to an appropriate resource.\n\
265
One for the already @fBRunning Jobs@fR showing jobs which are processing and their\n\
267
And the last folder page displays recently @fBFinished Jobs@fR.\n\
269
Without any customization the columns @fBJobId, Priority, JobName, Owner, Status@fR and\n\
270
@fBQueue@fR are displayed. In the @fBJob Customize@fR dialogue additional information\n\
271
about the job can be selected for display and a selection of jobs that shall be shown\n\
273
Instead of displaying additional fields permanently in the @fBJob Control@fR dialogue\n\
274
it is possible to use the @fBObject Browser@fR to view additional information about\n\
275
a job. To show up the @fBBrowser@fR push the @fBBrowser Icon@fR in the @fBMain Control Window@fR.\n\
276
In the @fBBrowser@fR dialogue toggle the @fBJob@fR button and point with the mouse to a\n\
277
job in the tabular areas in the @fBJob Control@fR dialogue.\n\
279
For most of the tasks jobs have to be selected first. To select a job the following\n\
280
key + mouse combinations are used:\n\
282
Enter the clicked to field (for columns Queue and additionally selected fields)\n\
283
@f[BI]Ctrl + Mouse1@fR\n\
284
Begin of selection, one row is selected, already selected areas are unselected.\n\
285
@f[BI]Shift + Mouse1@fR\n\
286
Extend of selection, select all rows between Begin of selection and the clicked to row.\n\
287
@f[BI]Ctrl + Shift + Mouse1@fR\n\
288
Toggle the selection, the clicked to row is selected if it was unselected and unselected\n\
291
The selected jobs can be manipulated by the buttons labeled @fBSuspend, Resume, Delete,\n\
292
Why, Priority, Qalter, Hold and Clear Error@fR at the right hand side of the window.\n\
294
Suspending a job means the equivalent to sending the signal @fBSIGSTOP@fR to the process\n\
295
group of the job with the @fBUNIX kill@fR command. I.e. the job is halted and does no\n\
296
longer consume CPU time. If a job is suspended it is displayed in a different color which\n\
297
can be configured in the application default file @fB$HOME/Qmon@fR.\n\
298
Here the entries @fBjob_suspend_color, job_suspend_on_subordinate_color, job_delete_color@fR\n\
299
define the used colors for suspended jobs, for jobs which ran in a queue which has been\n\
300
suspended on subordinate (see Queue Control Help and the User Manual) and for jobs that\n\
301
have been deleted. The default colors are turquoise for suspended jobs, magenta for\n\
302
jobs that are suspended on subordinate and orange for jobs that are marked for deletion.\n\
303
Additionally the status of the jobs is displayed as a letter combination as for\n\
304
@fBGrid Engine qstat@fR in the @fBStatus@fR column.\n\
305
Further information on the abbreviations and the meaning of the different states can be\n\
306
found in the @fBqstat@fR man page.\n\
308
Resuming the job sends the signal @fBSIGCONT@fR thereby resuming the job.\n\
310
The actions suspend, resume, delete, modify priority, modify hold and qalter may only be\n\
311
applied to a job by the @fBjob owner@fR or by @fBGrid Engine managers@fR and @fBoperators@fR.\n\
313
Suspension, Resume and Deletion can be forced, i.e. registered with @fBsge_qmaster@fR\n\
314
without notification of the @fBsge_execd@fR controlling the job(s), in case the corresponding\n\
315
@fBsge_execd@fR is unreachable, e.g. due to network problems.\n\
317
For the selected jobs the input of the priority popup is set as priority for the selected\n\
318
jobs and the pending jobs are sorted according to their new priority.\n\
320
To change the Hold state of pending jobs these are selected and pressing @fBHold@fR pops up\n\
321
a little dialog to set or reset the hold state. There are three different kinds of holds the\n\
322
user hold which can be set by the owner of the job, an operator or manager, the operator hold\n\
323
which needs at least operator privileges and finally the system hold which requires manager\n\
324
privileges to be changed.\n\
325
If only one job is selected the current hold state of the job is displayed otherwise this is\n\
326
not the case. Change the hold state and press @fBOk@fR to report it to the Grid Engine system or\n\
327
@fBCancel@fR to dismiss.\n\
329
To change other attributes of a pending job select this job and press @fBQalter@fR. This\n\
330
pops up the @fBJob Submission@fR dialogue in a restricted mode. If the changes are committed\n\
331
with the @fBQalter@fR button of the @fBJob Submission@fR dialogue, the dialogue closes and\n\
332
the changes are reported to the master and displayed in the @fBJob Control@fR dialogue.\n\
333
To leave the @fBJob Submission@fR dialogue without doing any changes press the @fBDone@fR button.\n\
335
The @fBCustomize@fR button allows the setting of the job attributes displayed and the\n\
336
specification of job filtering criteria. The @fBJob Customize@fR folder pops up.\n\
337
The @fBSelect Fields@fR dialogue is used to display additional job attributes.\n\
338
The @fBFilter Jobs@fR dialogue allows the selection of filtering criteria to restrict the\n\
339
number of jobs being displayed.\n\
340
The @fBFilter by Owner@fR input field allows the specification of a list of user names like\n\
341
@fBjoe sam jim@fR. Also wildcards are allowed like @fBj* sam@fR thus filtering out all jobs\n\
342
whose owner names don't match the specified names. @fBCompact Job array Display@fR collapses\n\
343
the display of job arrays. Otherwise every job array task is shown as a single line in the\n\
344
tabular areas of the @fBJob Control@fR dialogue.\n\
345
If one of the available resources is specified only those jobs are displayed whose resource\n\
346
requirements are fulfilled by the configured queues.\n\
347
The customization settings can be saved to $HOME/.qmon_preferences in order to keep them\n\
348
across qmon sessions.\n\
350
To keep the information being displayed up-to-date, qmon uses a polling scheme to retrieve\n\
351
the status of the jobs from sge_qmaster.\n\
352
A refresh can be forced by pressing the @fBRefresh@fR button.
355
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
356
Qmon*qmon_queue.queue_main_layout*xmtHelpTitle: Queue Control Help
357
Qmon*qmon_queue.queue_main_layout*xmtHelp: \
358
The purpose of the @fBQueue Control@fR dialogue is to provide a quick overview of the\n\
359
queues available and their state in the cluster.\n\
360
Furthermore new queues can be @fBadded@fR, existing queues can be @fBmodified or deleted@fR\n\
361
and they can be @fBsuspended and resumed or disabled and enabled@fR.\n\
362
If put into an error state they can be reactivated by @fBClear Error@fR.\n\
364
The main dialogue displays a @fBQueue Icon@fR for each queue in the Grid Engine system.\n\
365
If the main display area is empty no queues are configured or the @fBQueue Customize@fR\n\
366
hides the queues not fulfilling the @fIfilter criteria@fR.\n\
367
Each queue icon is labeled with the queue name, the name of the host on which the queue resides\n\
368
and the number of job slots occupied as used slots/free slots.\n\
369
If a @fBsge_execd@fR is running on the queue host and has already registered with\n\
370
@fBsge_qmaster@fR a picture on the queue icon indicates the queue host's operating system\n\
371
architecture and a color bar at the bottom of the icon shows the current status of the queue.\n\
372
A legend on the right side of the @fBQueue Control@fR dialogue displays the meaning of the\n\
373
colors. For the suspend state there has to be remarked that if a queue is suspended on\n\
374
subordinate only the bottom of the square is filled with color.\n\
376
The @fBLoad Information@fR can be popped up by pressing @f[I]Shift + Mouse1@fR over a\n\
379
To act on the queues they have to be selected. This is done by pressing the @f[I]Left Mouse@fR\n\
380
button over a queue. They are unselected by pressing the left mouse button again.\n\
381
Clicking the @f[I]Right Mouse@fR button brings up the action popup.\n\
383
Here or on the right side of the dialogue the manipulation of the selected queues can be\n\
385
The @fBDelete, Suspend/Resume and Disable/Enable and Clear Error@fR buttons perform the according\n\
386
action on the selected queues.\n\
387
The @fBSuspend/Resume or Disable/Enable@fR operation require notification of the\n\
388
corresponding @fBsge_execd@fR. If this is not possible (e.g. because the host is down) a\n\
389
@fBsge_qmaster@fR internal status change can be forced if the @fBForce@fR toggle is enabled.\n\
390
If a queue is suspended it is closed for further jobs and the jobs already running are\n\
391
suspended. The queue and it's jobs are unsuspended as soon as the queue is resumed.\n\
393
Queues which are disabled are closed, however the jobs executing in those queues are\n\
394
allowed to continue. To disable a queue is commonly used to "drain" a queue.\n\
395
The enable makes a queue eligible for job execution again. If a queue runs in an error\n\
396
state for a certain reason the Clear Error is used to reset the queue.\n\
397
To perform suspend/resume and disable/enable operations @fBowner@fR or @fBGrid Engine manager\n\
398
or operator@fR privileges are required.\n\
400
The information about queues is updated periodically. To force an instant update press\n\
401
the @fBRefresh@fR button.\n\
402
With the @fBDone@fR button the @fBQueue Control@fR dialogue is closed.\n\
404
The @fBAdd@fR button opens the @fBQueue Configuration@fR subdialogue in @fBAdd mode@fR\n\
405
to add a new queue to the Grid Engine system.\n\
406
The @fBModify@fR button opens the @fBQueue Configuration@fR subdialogue in @fBModify mode@fR.\n\
407
Here exactly one queue has to be selected and the @fBModify@fR button pops up the @fBQueue\n\
408
Configuration@fR dialogue with the the values of this specific queue set.\n\
409
In the @fBQueue Configuration@fR subdialogue the specific queue operations are performed.\n\
410
For further information on navigating this dialogue see the help there.\n\
411
The @fBCustomize@fR button allows the configuration of queue filtering.\n\
412
The customization settings can be saved to $HOME/.qmon_preferences in order to keep them\n\
413
across qmon sessions.
416
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
417
Qmon*qmon_queue.qc_dialog_shell*xmtHelpTitle: Queue Configuration Help
418
Qmon*qmon_queue.qc_dialog_shell*xmtHelp: \
419
The @fBQueue Configuration@fR subdialogue provides the means to @fBadd and modify@fR queues.\n\
420
It consists of two sections, the upper part shows two input fields for the @fIqueue name@fR\n\
421
and the @fIhost name@fR and the three buttons @fBClone, Reset, Refresh@fR.\n\
422
On the right there is the @fBOk, Cancel and Help@fR button.\n\
423
The lower part consists of a folder of configuration pages for the different categories of\n\
424
queue attributes. These categories of queue parameters are present:\n\
425
@fBGeneral Configuration, Execution Method, Checkpointing, Load/Suspend Thresholds, Limits,\n\
426
Complexes, Subordinates, User Access, Project Access (Grid Engine Enterprise Edition mode only) and Owners.@fR\n\
428
To @fIadd a queue@fR enter first the @fIqueue name and the hostname@fR of the new queue and\n\
429
change the queue attributes to your needs. To modify it only the attributes are editable.\n\
430
To report the changes to the Grid Engine system press @fBOk@fR after having finished filling\n\
431
in the different queue parameters.\n\
432
To quit the dialog without registering the changes with the Grid Engine system press\n\
434
The @fBClone@fR button allows to clone the attributes of a similar queue and to adjust only\n\
435
those attributes that are different.\n\
436
With @fBReset@fR the forms are reset to the values of the Grid Engine template queue,\n\
437
which serves as a standard queue. This values are also filled in when @fBQueue Configuration@fR\n\
438
is popped up in Add mode.\n\
440
The forms of the different attribute categories comprise the following fields, for a more\n\
441
thorough explanation of the meaning of the different parameters refer to the @fBqueue_conf@fR\n\
444
@fBGeneral Configuration@fR\n\
445
Sequence Nr allows the @fBSort by Sequence Number@fR sorting of queues during scheduling.\n\
446
Processor Range (s.th. like 1-4) that shall be used by the jobs running on the queue.\n\
447
Temporary directory path.\n\
448
Shell that shall be used to execute the job scripts. This can also be another command interpreter\n\
449
than a usual Unix shell.\n\
450
Shell Start Mode defines the way how shell scripts are handled by the Shell.\n\
451
Initial State defines if this queue is accessible for scheduling after startup.\n\
452
Calendar contains the name of the calendar attached to this queue to manage the accessibility of\n\
453
the queue based on date and time.\n\
454
Notify Time is the time that passes before a KILL signal is sent after sending user defined signals.\n\
455
Job's Nice is the UNIX nice value that the job is started with.\n\
456
Slots defines the maximum number of jobs that can run on this queue.\n\
457
Rerun Jobs defines that jobs that aborted on this queue are restarted automatically this may be useful\n\
458
for checkpointed jobs for example.\n\
459
Type defines the capability of the queue to handle special classes of jobs.\n\
461
@fBExecution Method@fR\n\
462
Prolog defines the prolog path. The prolog is executed before the job is executed.\n\
463
Epilog defines the epilog path. The epilog is executed after the job has been executed.\n\
464
Starter Method defines the executable that is used to start a job.\n\
465
Suspend Method, Resume Method and Terminate Method can be used as a replacement for the\n\
466
default mechanisms for suspension, release of a suspension and terminating a job.\n\
467
Per default the signals SIGSTOP, SIGCONT and SIGKILL are delivered which may not be\n\
469
It is either possible to define an executable path here to execute a\n\
470
corresponding command or to define a different signal as a positive number or with the SIG\n\
471
prefix. There are the following variables that can be used and that are expanded at runtime:\n\
472
@fI$host@fR: the name of the host on which the procedure is started\n\
473
@fI$job_owner@fR: the user name of the job owner\n\
474
@fI$job_id@fR: the actual job id\n\
475
@fI$job_name@fR: the job's name\n\
476
@fI$queue@fR: the name of the queue\n\
477
@fI$job_pid@fR: the UNIX pid of the job\n\
479
@fBCheckpointing@fR\n\
480
MinCpuTime is the periodical checkpoint interval.\n\
481
All time values can be set using the time input helper subdialogue.\n\
483
@fBLoad/Suspend Thresholds@fR\n\
484
The Load Thresholds prevent the scheduling of additional jobs to the queue. A threshold\n\
485
can be supplied for any load value.\n\
486
For entering load values see the remarks in @fBCheckpointing Parameters@fR above.\n\
487
If one of the load thresholds is exceeded the queue is set to the @fBalarm state@fR and\n\
488
no more jobs are scheduled to this queue.\n\
489
The Suspend Thresholds can be used to suspend jobs running on this queue if a load\n\
490
value is exceeded.\n\
493
The hard and soft limits which are imposed on the jobs running in the queue.\n\
494
To fill in values either @fBDouble Click@fR on the value fields of the table and enter them directly\n\
495
or use the helper dialogues by @fBDouble Clicking@fR again.\n\
498
The set of user defined complexes (see @fBUser Defined Complexes@fR in the manuals)\n\
499
being attached to the queue.\n\
500
There is a link to the @fBComplex Configuration@fR dialogue. Click the button to open\n\
501
it up. To see the changes made in the @fBComplex Configuration@fR dialogue in the\n\
502
@fBAvailable@fR list, press the @fBRefresh@fR button.\n\
503
Additionally @fBConsumable/Fixed Attributes@fR of the queue can be defined here.\n\
505
@fBSubordinates@fR\n\
506
The queues which are subordinated to the configured queue. Subordinated queues are\n\
507
suspended if the configured queue becomes @fBbusy@fR and unsuspended if the configured\n\
508
queue is no longer busy. The number of job slots which have to be occupied in the\n\
509
configured queue to trigger the suspend of an subordinate queue can be filled in in\n\
510
the column @fBMaxSlots@fR for every subordinate queue. If no value is given the\n\
511
subordinate queue is suspended if all slots of the configured queue are occupied.\n\
512
Subordinate queues can be used to implement high and low priority queues as well as\n\
513
stand-alone queues.\n\
516
The user access lists being attached to the allow or deny access lists of the queue.\n\
517
Users or user groups belonging to access lists which are included in the allow list\n\
518
have access to the queue. Those being associated with the deny list may not access the\n\
519
queue. If the allow list is empty access is unrestricted unless explicitly stated\n\
521
There is a link to the @fBUser Configuration Dialogue@fR where it is possible to setup\n\
522
user access lists. Click on the icon to go there.\n\
524
@fBProject Access (only in Grid Engine Enterprise Edition mode)@fR\n\
525
The project being attached to the allow or deny project access lists of the queue.\n\
526
Jobs running under a project belonging to the project allow list have access to the queue.\n\
527
Those being associated with the project deny list may not access the queue. If the allow list is\n\
528
empty access is unrestricted unless explicitly stated in the deny list.\n\
529
There is a link to the @fBProject Configuration Dialogue@fR where it is possible to setup\n\
530
projects. Click on the icon to go there.\n\
533
The list of queue owners. An owner of a queue is given permission to @fBSuspend/Resume@fR\n\
534
or @fBDisable/Enable@fR the queue.
536
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
537
Qmon*qmon_submit.submit_layout*xmtHelpTitle: Submit Job Help
538
Qmon*qmon_submit.submit_layout*xmtHelp: \
539
The @fBJob Submission@fR dialogue allows to submit jobs into the Grid Engine system.\n\
540
For general information on how to submit a Grid Engine job please refer to the examples given in\n\
541
the @fBGrid Engine User Guide@fR and the qsub(1) man page.\n\
543
To submit a job you first have to select the directive @fBPrefix@fR which is used to interpret\n\
544
@fBGrid Engine command directives@fR contained in the script file. The @fBprefix@fR defaults to\n\
545
@fB#$@fR if nothing is specified.\n\
546
The next step is to choose a script by either entering its name with absolute path or relative to\n\
547
the current working directory of qmon or by simply selecting the specific @fBJob Script@fR from\n\
548
the @fBFile Selection Box@fR popped up by pressing the icon right aside the @fBJob Script@fR input field.\n\
549
If there are any default files delivered which contain @fBGrid Engine command directives@fR or if\n\
550
the job script contains any @fBGrid Engine command directives@fR, they are evaluated. The settings\n\
551
that apply to the job are shown in the dialogue.\n\
553
There are three levels of default files possible and all of them are optional. The one with\n\
554
the lowest priority is stored under @fB$SGE_ROOT/$SGE_CELL/common/sge_request@fR, the\n\
555
second level is stored under @fB$HOME/.sge_request@fR and the third level with the highest\n\
556
priority of the default files is stored in the current working directory of qmon under\n\
557
@fB./.sge_request@fR.\n\
558
If there are any script file embedded Grid Engine commandline directives they override the settings\n\
559
of the default files.\n\
561
After the script has been selected one can adjust the requirements of the job to be submitted.\n\
562
@fBJob Tasks@fR allows the submission of job arrays. They are specified as min[-max[:step]][,...]\n\
563
e.g. 1-10:2,20,24-27.\n\
564
@fBJob Name@fR contains the name of the script file and can be overwritten.\n\
565
@fBJob Args@fR contains any arguments delivered to the job script. They are separated by\n\
566
blanks as on the command line.\n\
567
With the @fBPriority@fR spinbox the job gets an initial priority value. Users without manager\n\
568
or operator privileges may only lower their initial priority value.\n\
569
The @fBStart At@fR field sets the time when the job is considered eligible for execution.\n\
570
The @fBCurrent Working Directory@fR toggle button indicates whether the job is to be executed\n\
571
in the current working directory (for identical directory hierarchies between the submit and\n\
572
the potential execution hosts only). For qmon the current working directory is the directory where\n\
573
qmon has been started.\n\
574
The @fBShell@fR field specifies the command interpreter to be used to execute the job script.\n\
575
There can be different command interpreters specified in the form @fBhost:interpreter@fR in\n\
576
the input field or via the helper dialogue by filling in the corresponding matrix entries.\n\
578
The @fBMerge Output@fR flag enables/disables the combination of the job's stderr into its stdout.\n\
579
If @fBstdout, stderr@fR fields are empty, the output of the job is written to the\n\
580
files <job_name>.o<job_id>[.<array task_id>] or <job_name>.e<job_id>[.<array task_id>] in the user's\n\
582
Where <job_name> is the name of the job entered in @fBJob Name@fR and <job_id> is the Grid Engine\n\
583
job id under which the job is running. <array task_id> is the task id of the task of the job array\n\
584
and is therefore only present for job arrays.\n\
585
The standard output redirection can be used to write the output to another place. This is done\n\
586
in the input fields @fBstdout and stderr@fR and by the corresponding helper dialogues.\n\
587
If the specified path is a directory the output streams are put with the default names under\n\
589
There are also pseudo environment variables that are expanded at runtime that can\n\
590
be used to build pathnames.\n\
591
$HOME home directory on execution machine\n\
592
$USER user ID of job owner\n\
593
$JOB_ID current job ID\n\
594
$JOB_NAME current job name\n\
595
$HOSTNAME name of the execution host\n\
596
$TASK_ID job array task index number\n\
597
Alternatively to $HOME the ~ symbol can be used as in csh(1) or ksh(1), it works also with\n\
598
user names but the necessary write permissions must exist.\n\
600
With the @fBRequest Resources@fR button the @fBRequested Resources@fR dialogue is opened\n\
601
in order to specify the @fBResource Requirements@fR of the job. If resources are requested,\n\
602
the icon pins are displayed completely filled with color.\n\
604
The @fBRestart behavior option menu@fR defines the job's restart behavior.\n\
605
@fBNotify Job@fR defines that the job will receive warning signals before the\n\
606
real signal arrives this is useful for checkpointing jobs for example.\n\
607
With @fBHold Job@fR jobs and if specified only special tasks of a job array can be\n\
608
submitted as hold. So they are not eligible for execution until their hold has been\n\
609
released. This is done in the @fBJob Control@fR dialogue. The task range is specified\n\
610
as for the @fBJob Tasks@fR field.\n\
611
@fBStart Job Immediately@fR defines if the job has to be scheduled immediately. This is always\n\
612
true for @fBInteractive Jobs@fR.\n\
614
The button list on the right is used to perform different tasks concerning of job submission.\n\
615
The button labeled with @fBBatch@fR toggles between batch and interactive mode for submitting\n\
616
either batch or interactive jobs.\n\
617
The @fBSubmit@fR button submits the job into the Grid Engine system.\n\
618
The @fBEdit@fR button is used to edit a chosen job script.\n\
619
The @fBClear@fR button clears and resets all fields of the dialogue. One has to rechoose a Job Script.\n\
620
The @fBReload Button@fR discards any additional manually performed changes in the dialogue and restores\n\
621
the state of the dialogue after loading the Job script file merged with the default files if there were\n\
623
The @fBSave Settings@fR button can be used to write special submit configurations to a file.\n\
624
With @fBLoad Settings@fR these settings are loaded over a job setting the stored parameters\n\
625
for the chosen job.\n\
627
Under @fBAdvanced@fR more elaborate settings are available.\n\
628
The @fBParallel Environment@fR field allows the input of a parallel environment and the\n\
629
corresponding range specifications. A helper dialogue listing configured PEs is associated\n\
631
In the @fBEnvironment@fR field environment variables can be delivered.\n\
632
In the @fBContext@fR field context variables can be delivered.\n\
633
In the @fBCheckpoint Object@fR field a special checkpoint object can be requested.\n\
634
The @fBAccount@fR field contains a string which is stored in the accounting record for this\n\
636
The @fBMail@fR section contains the events when the user is notified by electronic mail and\n\
637
the mail addresses to which these notification is sent.\n\
638
In the @fBSoft/Hard Queue List@fR input fields the job can be directed to special queues.\n\
639
In the @fBJob Dependencies@fR field the job numbers that the current job depends on, can be\n\
641
In Grid Engine Enterprise Edition mode the @fBDeadline@fR field is present where the deadline when a job shall be fulfilled\n\
642
can be entered. This leads to an increase of the priority of this job when it approaches its deadline.\n\
643
Only @fBDeadline Users@fR can submit deadline jobs.\n\
646
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
647
Qmon*request_shell.request*xmtHelpTitle: Requested Resources Help
648
Qmon*request_shell.request*xmtHelp: \
649
The @fBRequested Resources@fR dialogue allows to specify the requirements a job has to fulfill.\n\
650
To enter a requirement double click on one of the available resources then you can enter\n\
651
the required value and depending on the @fBHard/Soft Request@fR radio buttons the item is\n\
652
added to the @fBHard/Soft Resources List@fR. To change one of the requirements double click\n\
653
it in the @fBHard/Soft Resources List@fR. To remove it select it and press the @fIRight Mouse@fR\n\
654
button or @fIClear@fR to remove all requested items.\n\
655
@fBOk@fR saves the requested resources for this job submission. @fBCancel@fR dismisses any change.
657
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
658
!Qmon*request_shell.request*xmtHelpTitle: Requested Resources Help
659
!Qmon*request_shell.request*xmtHelp: \
660
!When submitting a Grid Engine job a requirement profile of the job can be specified.\n\
661
!The user can specify attributes or characteristics of a host or queue which the job \n\
662
!requires to run successfully.\n\
663
!Grid Engine will map these job requirements onto the host and queue configurations of the Grid Engine\n\
664
!cluster and will so find suitable hosts for the job.\n\
665
!The available attributes to choose from are displayed in the @fBRequested Resources Dialogue@fR.\n\
666
!There can be queue properties, global or host specific load parameters as well as user defined\n\
667
!attributes available.\n\
668
!The Grid Engine administrator commonly chooses only a subset of all available attributes to be\n\
669
!requestable by the user.\n\
670
!The currently requestable resources are displayed in the @fBAvailable Resources@fR section of the\n\
671
!@fBRequested Resources Dialogue@fR. On the left hand side of the dialogue the user chosen resources\n\
673
!They are separated into the categories @fBHard Resources@fR which have to be fulfilled to get the\n\
674
!job running and @fBSoft Resources@fR which should be fulfilled but are not absolutely necessary for the\n\
675
!execution of the job.\n\
676
!The entries in the lists can be manipulated by @fBDouble Clicking@fR with the @fBLeft Mouse Button@fR on\n\
677
!the specific item. A type dependent helper dialogue opens up and permits the addition of an item to the\n\
678
!@fBHard Resources@fR list if @fBHard Request@fR is selected or to the @fBSoft Resource@fR list if \n\
679
!@fBSoft Request@fR is selected, and the double click occurs in the @fBAvailable Resources@fR section.\n\
680
!If the double click is performed in the @fBHard/Soft Resources@fR section, the item can be @fBchanged@fR.\n\
681
!To @fBdelete@fR an item from the @fBHard/Soft Resources@fR section click @fBRight Mouse@fR button over the\n\
682
!item to delete all items from one of the sections @fBHard/Soft Resources@fR choose the corresponding\n\
683
!type @fBHard/soft Request@fR and press @fBClear@fR.\n\
684
!To discard any changes to the requested resources press the @fBCancel@fR button. To keep them leave the\n\
685
!dialogue with @fBOk@fR. If there are any resources requested for the job the @fBRequested Resources@fR icon\n\
686
!in the @fBJob Submission Dialogue@fR changes color.
688
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
689
Qmon*qmon_cplx.cplx_layout*xmtHelpTitle: Complexes Configuration Help
690
Qmon*qmon_cplx.cplx_layout*xmtHelp: \
691
The definition of @fBcomplexes@fR provides all pertinent information concerning\n\
692
the resource attributes a user may request for a Grid Engine job and for the interpretation\n\
693
of these parameters within the Grid Engine system.\n\
695
To get general information about the @fBComplexes Concept@fR please refer to the\n\
696
@fBGrid Engine Installation and Administration Guide and complex(5)@fR.\n\
698
The @fBComplex Configuration@fR dialogue provides the abilities to introduce so\n\
699
called @fBUser Complexes@fR to the system and to remove or modify existing\n\
700
complexes of the @fBGrid Engine system@fR.\n\
702
On the left side of the dialogue a list of all currently available complexes is\n\
703
displayed. There should be at least the @fBhost@fR and the @fBqueue@fR\n\
704
complexes which are brought into the system by the installation procedure.\n\
705
The rest of the dialogue consists of a list of the attributes of the highlighted\n\
706
complex and the action buttons on the right.\n\
708
For the @fBqueue complex@fR only the @fBShortcut@fR, the @fBRelation@fR and the\n\
709
@fBRequestable@fR columns may be changed. No complex attributes may be added or deleted.\n\
710
The @fBhost complex@fR may be expanded by the @fBGrid Engine Administrator@fR in the course of\n\
711
adding or modifying @fBuser configurable loadsensors@fR.\n\
713
By setting up @fBuser defined complexes@fR the Grid Engine administrator has the ability to\n\
714
extend the set of requestable attributes in an arbitrary fashion. A user complex is\n\
715
just a named collection of attributes and the according definition how these\n\
716
attributes are to be handled by Grid Engine. These user defined complexes can be assigned to\n\
717
a queue in order to group them or to attach special attributes to them.\n\
719
To add a new complex to the system, press @fBAdd@fR to pop up the empty complex editor\n\
721
In the input field named @fBName of Complex@fR the new complex name is filled in.\n\
722
Now the complex attributes can be filled into the attribute matrix. It consists of\n\
723
eight fields. The first field is the @fBattribute name@fR, the second field is a\n\
724
@fBshortcut@fR for the attribute, the third field is the type of the attribute and tells\n\
725
the system how to interpret the delivered values. Allowed types are @fBSTRING, CSTRING,\n\
726
MEMORY, TIME, INT, BOOL, HOST and DOUBLE@fR. The fourth field specifies a pre-defined value\n\
727
which only has an effect if it is not overwritten while determining a concrete value for the\n\
728
attribute with respect to a queue, a host or the Grid Engine cluster. The value field can be\n\
730
- the queue configuration values of a referenced queue\n\
731
- host specific and cluster related load values\n\
732
- explicit specification of a value via the complex_values parameter in the queue or host\n\
734
The fifth field specifies the @fBrelation@fR to use in comparing user requested values with\n\
735
system delivered values.\n\
736
The sixth field decides if a complex attribute is @fBrequestable@fR by the user, here\n\
737
YES, NO and FORCED are allowed values. If FORCED is selected this atribute must be requested.\n\
738
The seventh field is the @fBCONSUMABLE@fR flag. It can be set to YES and NO where YES is only meaningful\n\
739
for numeric attributes (INT, MEMORY, TIME, DOUBLE). When set to YES the consumption of the\n\
740
resource can be managed by Grid Engine internal bookkeeping.\n\
741
The eighth field defines a @fBDEFAULT@fR value. This is only meaningful for consumable complex\n\
742
attributes. Grid Engine assumes the resource amount denoted in the default parameter\n\
743
implicitly to be consumed by jobs being dispatched to a host or queue managing the consumablei\n\
744
attribute. Jobs explicitly requesting the attribute via a Resource Request override this\n\
747
To enter a line to the matrix enter the information in the input fields and option menus\n\
748
and press @fBAdd@fR to put it into the @fBAttributes matrix@fR. To change or delete a\n\
749
line form the matrix select the line(s) with the mouse and press @fBDelete@fR or commit\n\
750
the changed attribute line with @fBAdd@fR.\n\
752
To load attributes from a complex file push the @fBLoad@fR button, select the complex file\n\
753
in the file selection box. This loads the values from the file into the matrix.\n\
754
To save your current matrix settings to file use the @fBSave@fR button.\n\
756
After filling in the complexes they are stored permanently in the system by pressing the\n\
757
@fBOk@fR button. If everything is all right the complex editor closes and the new complex\n\
758
appears in the @fBComplexes@fR list and its corresponding attributes show up in the\n\
759
@fBAttributesfR section.\n\
761
The @fBModify@fR button allows the change of an existing complex. It also opens the complex\n\
762
editor subdialogue, which is used in the same manner as for adding a new complex.\n\
764
The @fBDelete@fR button deletes the chosen complex after asking the user for confirmation.\n\
766
The @fBDone@fR button leaves the dialogue.
768
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
769
Qmon*qmon_host*xmtHelpTitle: Host Configuration Help
770
Qmon*qmon_host*xmtHelp: \
771
Grid Engine hosts are classified into four groups, depending on which Grid Engine daemons are running on\n\
772
the system and how the hosts are registered at @fBsge_qmaster@fR.\n\
773
The @fBMaster Host@fR is central for the overall cluster activity. It runs the @fBsge_qmaster@fR\n\
774
daemon which controls all Grid Engine components such as queues and jobs and maintains the status of the\n\
777
@fBExecution hosts@fR are nodes having permission to execute Grid Engine jobs and are therefore hosting\n\
778
Grid Engine queues. The @fBsge_execd@fR daemon runs on these hosts.\n\
779
@fBAdministration hosts@fR can carry out any administrative activity concerning the Grid Engine system.\n\
780
The @fBMaster Host@fR and the @fBExecution hosts@fR are automatically @fBAdministration hosts@fR.\n\
781
@fBSubmit Hosts@fR allow for submitting and controlling batch jobs only.\n\
783
@fBAdministration Host@fR\n\
785
The administrative host permission can be given to other hosts too. This is done by adding a host in\n\
786
the @fBHost Configuration@fR dialogue. Selecting @fBAdministration Host@fR from the folder shows the\n\
787
@fBAdministration Host@fR configuration page. Enter a hostname in the host field and press @fBReturn@fR\n\
788
or the @fBAdd@fR button, thus a new administrative host is added to the Grid Engine system.\n\
789
To remove administrative hosts from the Grid Engine system, select these hosts and press the @fBDelete@fR\n\
791
The @fBDone@fR button quits the dialogue.\n\
795
The submit host permission can be given to other hosts too. This is done by adding a host in\n\
796
the @fBHost Configuration@fR dialogue. Selecting @fBSubmit Host@fR from the folder shows the\n\
797
@fBSubmit Host@fR configuration page. Enter a hostname in the host field and press @fBReturn@fR\n\
798
or the @fBAdd@fR button, thus a new submit host is added to the Grid Engine system.\n\
799
To remove submit hosts from the Grid Engine system, select these hosts and press the @fBDelete@fR\n\
801
The @fBDone@fR button quits the dialogue.\n\
803
@fBExecution Host@fR\n\
804
The execution host permission can be given to any host. This is done by adding a host in\n\
805
the @fBHost Configuration@fR dialogue. Selecting @fBExecution Host@fR from the folder shows the\n\
806
@fBExecution Host@fR configuration page. This page consists of a list of configured execution host\n\
807
on the left and there corresponding configuration attributes in stacked attribute lists on the right.\n\
808
By selecting one of the execution hosts the corresponding attributes are displayed.\n\
809
To add a new execution host press @fBAdd@fR this pops up the execution host configuration editor.\n\
810
Here the hostname of the new execution host can be specified the @fBLoad Scaling@fR factors, the\n\
811
@fBAccess Attributes@fR, the @fBConsumables/Fixed Attributes@fR can be changed. In Grid Engine Enterprise Edition mode the\n\
812
@fBUsage Scaling@fR can be adjusted.\n\
814
The configuration helper dialogue consists of a folder with the categories @fBScaling@fR for\n\
815
@fBLoad Scaling, Usage Scaling@fR (Grid Engine Enterprise Edition mode only)\n\
816
settings, @fBConsumables/Fixed Attributes@fR for host based attachment of consumables and fixed attributes,\n\
817
@fBUser Access@fR for host based accessibility settings and in Grid Engine Enterprise Edition mode additionally @fBProject Access@fR\n\
818
for host based definition of project access.\n\
819
The scaling can be used to weight special load or usage values for better comparability of distinct\n\
820
cluster machine types. The other settings are mainly the counterpart too queue based configuration\n\
821
settings on the host level. So it is possible for example to attach for all queues residing on a\n\
822
special host the access permissions once on the host level.\n\
824
To modify an existing execution host press @fBModify@fR and proceed as with adding a host.\n\
826
To remove any execution host from the Grid Engine system, select this host and press the @fBDelete@fR\n\
829
With the @fBShutdown@fR button the corresponding @fBsge_execd@fR can be shut down.\n\
831
The @fBDone@fR button quits the dialogue.
833
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
834
Qmon*qmon_cluster.cluster_layout*xmtHelpTitle: Cluster Configuration Help
835
Qmon*qmon_cluster.cluster_layout*xmtHelp: \
836
The @fBCluster Configuration@fR combines from two parts, the @fBglobal configuration@fR and\n\
837
host specific @fBlocal configuration@fR.\n\
838
It reflects any site dependencies and general parameters of the Grid Engine cluster.\n\
839
The local configuration supersedes any parameters in the global configuration.\n\
841
The @fBsge_conf(5)@fR manual gives a detailed information about the configuration entries available.\n\
843
The @fBCluster Configuration@fR dialogue displays a list of all configurations available in the system.\n\
844
There is at least the @fBglobal configuration@fR available. @fBLocal configurations@fR are named by the\n\
845
corresponding host name.\n\
846
Selecting one of the configuration names in the @fBHost@fR list displays the corresponding configuration\n\
847
values. The actual configuration is build by merging the local and the global configuration where the\n\
848
local configuration overrides the corresponding entries of the global configuration.\n\
850
To modify a configuration select the corresponding configuration and press @fBModify@fR to bring the\n\
851
@fBCluster Settings@fR dialogue up.\n\
852
In the case of @fBglobal configuration@fR all fields are accessible. For @fBhost specific configuration@fR\n\
853
only parts of the dialogue can be edited. The dialogue consist of a folder with the sections\n\
854
@fBGeneral Settings@fR and @fBAdvanced Settings@fR.\n\
855
Pressing @fBOk@fR registers the changes with sge_qmaster. @fBCancel@fR dismisses any changes.\n\
857
To delete any host specific local configurations choose the appropriate hostname in the @fBHost@fR list\n\
858
and press the @fBDelete@fR button.\n\
860
The @fBDone@fR button leaves the dialogue.
862
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
863
Qmon*qmon_manop*xmtHelpTitle: User Configuration Help
864
Qmon*qmon_manop*xmtHelp: \
865
There are four user categories in Grid Engine, @fBManagers, Operators, Owners and Users@fR.\n\
866
@fBManagers@fR have @fBfull capabilities@fR to manipulate Grid Engine. By default the @fBsuperuser@fR\n\
867
or @fBadmin_user@fR of the master host and any machine hosting a queue have manager privileges.\n\
868
In Grid Engine Enterprise Edition mode the term @fBUser@fR is used additionally for registered users that can be manipulated in\n\
869
the different @fBTicket Policy@fR dialogues.\n\
871
The @fBUser Configuration@fR dialogue comes up as a folder with the following categories:\n\
872
@fBManager, Operator, Userset and User@fR (in Grid Engine Enterprise Edition mode only).\n\
874
To add any additional users as managers select the @fBManager@fR folder page and enter a valid\n\
875
username in the input field and press @fBReturn@fR or the @fBAdd@fR button. To remove any users\n\
876
from the manager list select these users in the list and press the @fBDelete@fR button.\n\
877
Manipulations of managers must be done on an @fBadministration host@fR.\n\
879
To add any additional users as operators select the @fBOperator@fR folder page and enter a valid\n\
880
username in the input field and press @fBReturn@fR or the @fBAdd@fR button. To remove any users\n\
881
from the operator list select these users in the list and press the @fBDelete@fR button.\n\
882
Manipulations of operators must be done on an @fBadministration host@fR.\n\
884
@fBUsersets@fR are either used as @fBAccess Lists@fR only in Grid Engine mode or as both @fBAccess Lists\n\
885
and Departments@fR in Grid Engine Enterprise Edition mode. Two usersets have special meaning in Grid Engine Enterprise Edition mode. @fBdeadlineusers@fR is\n\
886
used to define those users who are allowed to submit @fBDeadline Jobs@fR. The @fBdefaultdepartment@fR\n\
887
is attached to every user who is not a member of a administrator defined department. Users can only\n\
888
be members of one department. To add a new userset, press @fBAdd@fR. In the helper dialogue choose\n\
889
the type of userset (in Grid Engine Enterprise Edition mode only) and add any users. For access lists the @@<unix group> notation\n\
890
can be used to build an access list containing a UNIX group.\n\
891
@fBOk@fR registers the new userset at sge_qmaster and @fBCancel@fR dismisses any changes.\n\
892
For modification of an already existing userset select it, press @fBModify@fR and proceed as for\n\
894
To remove a userset select it and press @fBDelete@fR.\n\
895
In Grid Engine Enterprise Edition mode another category @fBUser@fR exists. Here you can add a user for the @fBGrid Engine Enterprise Edition Ticket\n\
896
Policies@fR and attach a default project to the user. Enter the user name in the input field\n\
897
and press @fBReturn@fR or @fBAdd@fR, this adds a new line to the matrix. If the @fIDefault Project@fR\n\
898
shall be changed, select those users and press the @fBDefault Project@fR title button to pop up\n\
899
a list of configured projects. Pressing @fBOk@fR in the helper changes the project entry for the\n\
902
The @fBDone@fR button leaves the dialogue. In Grid Engine Enterprise Edition mode the @fBTickets@fR button links to the\n\
903
@fBTicket Overview@fR dialogue.
905
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
906
Qmon*qmon_pe.pe_layout*xmtHelpTitle: Parallel Environment Configuration Help
907
Qmon*qmon_pe.pe_layout*xmtHelp: \
908
A parallel environment (PE) is a software package designed for concurrent computing in networked\n\
909
environments or parallel platforms. Examples for two of the most common message passing environments\n\
910
are PVM and MPI. All these systems show different characteristics and have segregative requirements.\n\
911
Arbitrary PE's can be interfaced by Grid Engine as long as suitable start-up and stop procedures are provided.\n\
912
For further information refer to the manuals.\n\
914
The @fBParallel Environment Configuration@fR dialogue displays a list of already configured PEs in the\n\
915
@fBPE List@fR on the left hand side of the dialogue. In the @fBConfiguration@fR section the currently\n\
916
configured values are shown.\n\
917
To add or modify a PE object press the @fBAdd@fR or @fBModify@fR button respectively. For the modify an\n\
918
existing PE has to be chosen from the @fBPE List@fR.\n\
919
The @fBPE modification dialogue@fR pops up having either a template PE entry or the PE to be modified.\n\
920
The @fBName@fR input field either displays the name of the PE to modify or has to be entered as name for\n\
921
the new PE. The @fBSlots@fR spinbox allows the input of the number of job slots in total which may be\n\
922
occupied by all PE jobs running concurrently.\n\
923
The @fBQueue List@fR section shows the queues which can be used by the PE. Modifying these resource is\n\
924
done by clicking on the lists icon to the right. In the subdialogue popped up the attached queues can be\n\
925
changed. The same procedure is taken to add or change the @fBUser Lists@fR and the @fBXuser Lists@fR which\n\
926
are allowed/denied to access the PE.\n\
927
In the @fBStart Proc Args and Stop Proc Args@fR the precise invocation sequence of the PE start-up and\n\
928
stop procedures is entered.\n\
929
The @fBAllocation Rule@fR entry defines the number of parallel processes to be allocated on each machine\n\
930
which is used by a PE.\n\
931
By pressing the @fBOk@fR button the added/modified PE configuration is checked and added to the Grid Engine\n\
932
system. The @fBCancel@fR button discards any changes.\n\
934
To delete a PE object, select it in the @fBPE List@fR and press @fBDelete@fR.\n\
935
The @fBDone@fR button quits the dialogue.
937
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
938
Qmon*qmon_ckpt.ckpt_layout*xmtHelpTitle: Checkpointing Configuration Help
939
Qmon*qmon_ckpt.ckpt_layout*xmtHelp: \
940
@fBGrid Engine@fR provides various levels of checkpointing support. The checkpointing\n\
941
environment described here is a means to configure the different types of checkpointing\n\
942
in use for your @fBGrid Engine@fR cluster or parts thereof.\n\
943
For that purpose you can define the operations which have to be executed in\n\
944
initiating a checkpoint generation, a migration of a checkpoint to another host or\n\
945
a restart of a checkpointed application as well as the list of queues which are\n\
946
eligible for a checkpointing method.\n\
948
The @fBCheckpoint Configuration@fR dialogue displays a list of already configured\n\
949
Checkpoint Objects in the @fBCheckpoint Objects@fR list.\n\
950
The corresponding configuration parameters are shown in the @fBConfiguration@fR section.\n\
951
To add or modify a checkpoint object press the @fBAdd@fR or @fBModify@fR button respectively.\n\
952
For the modify an existing checkpoint object has to be chosen from the @fBCheckpoint Objects@fR list.\n\
953
The @fBCheckpoint modification dialogue@fR pops up having either a template\n\
954
checkpoint object or the checkpoint object to be modified.\n\
955
The @fBName@fR input field either displays the name of the checkpoint object to be modified\n\
956
or has to be entered as name for the new checkpoint object.\n\
957
The @fBInterface@fR option menu allows the selection of a checkpointing interface.\n\
958
Currently the types HIBERNATOR and USERDEFINED are valid.\n\
959
The @fBQueue List@fR section shows the queues which can be used by the checkpoint object.\n\
960
Modifying these resource is done by clicking on the lists icon to the right. In the subdialogue\n\
961
popped up the attached queues can be changed.\n\
962
The @fBCheckpoint Command@fR is a command-line type command string to be executed\n\
963
by @fBGrid Engine@fR in order to initiate a checkpoint.\n\
964
The @fBMigration Command@fR is a command-line type command string to be executed\n\
965
by @fBGrid Engine@fR during a migration of a checkpointing job from one host to another.\n\
966
The @fBRestart Command@fR is a command-line type command string to be executed\n\
967
by @fBGrid Engine@fR when restarting a previously checkpointed application.\n\
968
The @fBCheckpointing directory@fR is a file system location to which checkpoints\n\
969
of potentially considerable size should be stored.\n\
970
The @fBCheckpoint Signal@fR specifies a UNIX signal to be sent to a job by @fBGrid Engine@fR\n\
971
to initiate a checkpoint generation. The value for this field can either be a\n\
972
symbolic name from the list produced by the -l option of the kill(1) command or\n\
973
an integer number which must be a valid signal on the systems used for checkpointing.\n\
974
The @fBCheckpoint When@fR specifies the points of time when checkpoints are\n\
975
expected to be generated.\n\
977
By pressing the @fBOk@fR button the added/modified Checkpoint configuration is checked and\n\
978
added to the Grid Engine system. The @fBCancel@fR button discards any changes.\n\
980
To delete a checkpoint object, select it in the @fBCheckpoint Objects@fR list and press @fBDelete@fR.\n\
981
The @fBDone@fR button quits the dialogue.
983
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
984
Qmon*sconf_shell*xmtHelpTitle: Scheduler Configuration Help
985
Qmon*sconf_shell*xmtHelp: \
986
The @fBScheduler Configuration@fR dialogue permits the setting of scheduler specific\n\
987
parameters. It is subdivided in @fBGeneral Parameters and Load Adjustment@fR.\n\
989
The @fBAlgorithm@fR field allows the setting of a different scheduling algorithm.\n\
990
The @fBSchedule Interval@fR specifies how often the scheduler is triggered.\n\
991
In Grid Engine Enterprise Edition mode the @fBSGEEE Schedule Interval@fR defines how often the Grid Engine Enterprise Edition scheduler is activated.\n\
992
The @fBMax. Jobs/User@fR specifies how many jobs per user\n\
993
should be scheduled. If the value is zero no restrictions apply.\n\
994
The queues can be sorted according to the @fBLoad Formula@fR when @fBSort by Load@fR is\n\
995
selected. If @fBSort by sequence number@fR is selected the queues are sorted according to\n\
996
the sequence number entered in the @fBGeneral@fR section of the @fBQueue Configuration@fR\n\
998
The @fBEqual Share Sort@fR enables the scheduler to equalize the jobs submitted for all\n\
999
users to avoid that one user can allocate all the system resources uniquely. This policy is\n\
1000
only available in Grid Engine mode. No suspend of already existing jobs takes place to achieve an\n\
1001
equal share for the different users.\n\
1002
The @fBJob Scheduling Information@fB part allows enabling/disabling of job scheduling information\n\
1003
for all or part of the jobs. The input field serves to enter a job range as min[-max][,...] to\n\
1004
define for which jobs scheduling information is requested.\n\
1005
The @fBLoad Formula@fR is the formula of load parameters which should be used by the\n\
1006
@fBSort by Load@fR method.\n\
1007
Because the load reports are delayed @fBLoad Adjustment@fR is the value which will be added to\n\
1008
the load for correcting this delay. The @fBLoad Adjustment Decay Time@fR specifies the time\n\
1009
during which the load correction is decreased to 0.\n\
1011
After having changed the scheduler configuration these changes are made permanent by pressing\n\
1012
@fBOk@fR. @fBCancel@fR dismisses any changes and quits the dialogue.
1014
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1015
Qmon*qmon_cal*xmtHelpTitle: Calendar Configuration Help
1016
Qmon*qmon_cal*xmtHelp: \
1017
The @fBCalendar Configuration@fR dialogue allows the configuration of Grid Engine calendars.\n\
1018
They are used to restrict the accessibility of Grid Engine queues to certain dates and times.\n\
1020
Press @fBAdd@fR to add a new calendar. This pops up the calendar definition helper dialogue.\n\
1021
Here you can enter a calendar entry according to the examples given there.\n\
1022
To modify an existing calendar select it in the @fBCalendars@fR list and press @fBModify@fR.\n\
1023
To delete one select it and press @fBDelete@fR. The current settings of the highlighted calendar\n\
1024
is shown in the @fBConfiguration@fR area.\n\
1025
@fBDone@fR quits the dialogue.
1027
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1028
Qmon*qmon_tov.tov_layout*xmtHelpTitle: Ticket Overview Help
1029
Qmon*qmon_tov.tov_layout*xmtHelp: \
1030
The @fBTicket Overview@fR dialogue allows the setting and manipulation of all\n\
1031
relevant tickets and shares of the Grid Engine system.\n\
1032
The main dialogue displays on the left side the currently active tickets and\n\
1033
allows to change the number of @fBTotal Share Tree Tickets, Total Functional Tickets@fR\n\
1034
and the number of @fBMaximum Deadline Initiation Tickets@fR.\n\
1035
If changes have been made in the @fBEdit Tickets@fR part, they are made permanent\n\
1036
by pressing the @fBApply@fR button.\n\
1038
From the @fBTicket Overview@fR the different Grid Engine policy dialogues can be reached.\n\
1039
It is possible to influence four different policies to change the overall scheduling behavior\n\
1041
The four policies are @fBShare-based Policy, Functional Policy, Initiation Deadline Policy\n\
1042
and Override Policy@fR.\n\
1043
Share-based and Functional Policy allow the long term adjustment of job scheduling\n\
1044
and resource management.\n\
1045
Initiation Deadline Policy and Override Policy are used to overrule the long term\n\
1046
policies under certain circumstances.\n\
1047
The ratio between the number of 'Total Share Tree and Total Functional Tickets' and the\n\
1048
number of 'Maximum Deadline Initiation Tickets' is important for the impact that a\n\
1049
deadline job has on the execution of other running jobs. If the number of 'Maximum Deadline\n\
1050
Initiation Tickets' is very high compared to the number of 'Total Share Tree and Total\n\
1051
Functional Tickets' deadline jobs get almost all the available resources as they approach\n\
1053
More details concerning the subdialogues are explained there. The different policies\n\
1054
are accessed via @fBShare Tree Policy, Functional Policy and Override Policy@fR.\n\
1055
In addition it is possible to go to the @fBUser Configuration@fR dialogue to\n\
1056
add or modify the users that are allowed to submit deadline jobs.\n\
1057
Users allowed to submit deadline jobs are registered in the special userset\n\
1058
@fBdeadlineusers@fR. This is done with @fBUsers Allowed To Submit Deadline Jobs@fR.\n\
1060
The @fBRefresh@fR button contacts the master daemon to get the freshest valid data.\n\
1061
With @fBDone@fR one quits the @fBTicket Overview@fR dialogue.
1064
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1065
Qmon*qmon_project.project_layout*xmtHelpTitle: Project Configuration Help
1066
Qmon*qmon_project.project_layout*xmtHelp: \
1067
The @fBProject Configuration@fR dialogue allows the definition and manipulation\n\
1068
of @fBGrid Engine@fR projects. A project can be attached to a Grid Engine job and enforces\n\
1069
or delays the execution of this job depending on the ticket share of this project.\n\
1070
The dialogue displays the currently available projects on the left. The right\n\
1071
part of the dialogue shows the according configuration values for the highlighted\n\
1073
To add a new project press the @fBAdd@fR button. A subdialogue pops up which\n\
1074
permits to enter the name of the new project and to attach certain access restrictions.\n\
1075
To allow access only to those users contained in a special userset, press the\n\
1076
list icon to the right of the 'User Lists' part and choose a userset. So the project\n\
1077
is only accessible by users in the chosen usersets.\n\
1078
To deny access to certain users the same procedure applies.\n\
1079
Pressing the @fBOk@fR button adds the new project permanently and the @fBCancel@fR button\n\
1080
dismisses the changes.\n\
1081
With @fBModify@fR the same subdialogue as for the @fBAdd@fR button appears with\n\
1082
the values filled in for the highlighted project.\n\
1083
The @fBDelete@fR button serves to remove the selected project from the system.\n\
1084
The @fBDone@fR button closes the @fBProject Configuration@fR dialogue.\n\
1086
To change the @fBOverride Tickets@fR or the @fBFunctional Share@fR of a project\n\
1087
the @fBFunctional Policy@fR and @fBOverride Policy@fR subdialogues from the\n\
1088
@fBTicket Overview@fR dialogue have to be used.
1091
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1092
Qmon*browser_shell.browser_layout*xmtHelpTitle: Qmon Browser Help
1093
Qmon*browser_shell.browser_layout*xmtHelp: \
1094
The @fBObject Browser@fR can be used to look at additional information for the Grid Engine objects\n\
1095
@fBqueue and job@fR, to display the @fBstdout/stderr@fR output of qmon and to view @fBqmon messages@fR\n\
1096
that are produced when a job is submitted or any administrative tasks are performed.\n\n\
1097
To enable the browsing of one of these categories press the corresponding button in the @fBObjects@fR\n\
1100
Any output can be cleared by pressing the @fBClear@fR button.\n\
1101
The @fBDone@fR button closes the @fBObject Browser@fR.
1104
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1105
Qmon*qmon_sharetree.sharetree*xmtHelpTitle: Share Tree Policy Help
1106
Qmon*qmon_sharetree.sharetree*xmtHelp: \
1107
The @fBShare Tree Policy@fR allows the Grid Engine manager to specify how system\n\
1108
resources should be shared among Grid Engine users and projects over a sliding\n\
1111
This is accomplished by setting up a share tree in which the available resources\n\
1112
are divided up among the nodes at each hierarchical level based on the number of\n\
1113
@fBshares@fR given to each node.\n\
1114
During scheduling, Grid Engine maps each active job to a node in the share tree.\n\
1115
Grid Engine tracks the actual usage for each node and compares this to the\n\
1116
@fBtargeted share@fR as defined by the number of shares assigned to each node.\n\
1117
Grid Engine will then assign an appropriate number of tickets to each active job\n\
1118
in order to meet the resource utilization goals defined by the share tree.\n\
1119
Each leaf node in the share tree may be a Grid Engine user or project.\n\
1120
Projects may also be specified as group nodes. A project may appear only once\n\
1121
in the share tree. A user may appear multiple times in the share tree, but only\n\
1122
once in a given project sub-tree and only once outside of any project sub-tree.\n\
1123
Each leaf node under a project group node must be a Grid Engine user. All jobs\n\
1124
which map to a project leaf node will equally share the shares defined in that node.\n\
1125
A user leaf node named "default" can be defined as a descendant of a project node in\n\
1126
the share tree. The default node defines how many shares users get who are running in\n\
1127
the project, but who are not explicitly specified as descendant user nodes of the project.\n\
1129
Shares are used to represent how resources should be divided up among sibling nodes.\n\
1130
If node A is given 100 shares and sibling node B is given 50 shares, the Grid Engine\n\
1131
manager is indicating that node A should get twice as much of the available system\n\
1132
resources as node B. Shares are only compared between sibling nodes.\n\
1133
They are only used to translate into targeted percentages of resources that Grid Engine\n\
1134
will try to deliver. Grid Engine looks at all the active jobs and divides up the tickets\n\
1135
allocated to the Share Tree Policy among the active jobs based on the share tree.\n\
1137
The share tree dialogue allows the setting and manipulation of the share tree policy.\n\
1138
The left side of the dialogue allows the current share tree to be displayed and edited.\n\
1139
The nodes of the share tree are hierarchically displayed in the scrollable window.\n\
1140
Lower levels of the share tree can be collapsed/exploded by pointing to a group node and\n\
1141
double-clicking with the left mouse button. The attributes of each node can be individually\n\
1142
displayed under the @fBNode Attributes@fR by highlighting the node.\n\
1144
To highlight an individual node, place the pointer on the node and click on the left mouse\n\
1145
button. The @fBIdentifier@fR attribute is the name of the node. The @fBShares@fR attribute\n\
1146
is the number of shares associated with the node. The @fBLevel Percentage@fR attribute is the\n\
1147
percentage of resources that the node should receive in comparison to the other sibling nodes.\n\
1148
The @fBTotal Percentage@fR attribute is the percentage of resources that the node should receive\n\
1149
in comparison to all the other nodes in the share tree. The @fBActual Resource Share@fR\n\
1150
attribute is the percentage of resources that the node is actually receiving over the sliding\n\
1151
window of time defined by the @fBHalftime@fR Share Tree Policy parameter.\n\
1152
The @fBTargeted Resource Share@fR attribute is the current percentage of available resources\n\
1153
that Grid Engine has targeted for the node based on the nodes in the share tree which have\n\
1154
active jobs. The @fBCombined Usage@fR attribute is the amount of combined CPU, memory, and I/O\n\
1155
usage which has been accumulated by the node.\n\
1157
The @fBRefresh@fR button refreshes the display with the freshest share tree values from Grid Engine.\n\
1158
The @fBApply@fR button registers any changes with Grid Engine.\n\
1159
The @fBDone@fR quits the dialogue without any additional action, so be aware and @fBApply@fR first.\n\
1161
The @fBAdd Node@fR and @fBAdd Leaf@fR buttons can be used to add new nodes to the share tree.\n\
1162
The @fBAdd Node@fR button adds a group node and the @fBAdd Leaf@fR button adds a leaf node.\n\
1163
To add a node, highlight the node under which you want to add a new node and click on the @fBAdd\n\
1164
Leaf@fR or @fBAdd Node@fR button. A helper dialogue will be displayed where you can enter the node\n\
1165
@fBName@fR and its @fBShares@fR. To modify the name or the number of shares of a node, highlight\n\
1166
the node and click on the @fBModify@fR button. The @fBCut@fR, @fBPaste@fR, and @fBCopy@fR buttons\n\
1167
can be used to prune and graft sections of the share tree. The @fBFind@fR buttons can be used to\n\
1168
locate a particular node in the share tree. The @fBFind@fR button accepts hierarchical\n\
1169
specifications. The use of a '/' in the specification represents a parent/child relationship.\n\
1170
For instance, "ProjectA/davidson" finds the "davidson" node which is a child of the "ProjectA" node.\n\
1171
The use of a '/' as the first character in a specification represents the "Root" node in the share\n\
1172
tree. The specification "/ProjectA/davidson" finds the "davidson" node which is a child of the\n\
1173
"ProjectA" node which is a child of the "Root" node. The use of a '.' in a specification\n\
1174
represents a descendant relationship, such that the specification "ProjectA.davidson" finds\n\
1175
the "davidson" node which is a descendant of a node "ProjectA". A '*' instead of a name represents\n\
1176
a wild-card and will match any node at the specified level. For instance, the specification\n\
1177
"/*/*/davidson" will find the first occurrence of the "node" davidson which is three levels below\n\
1178
the "Root" node. Any node names (not just users or projects) may be specified in a node\n\
1181
The Share Tree Policy Parameters portion of the dialogue is displayed by pressing the red arrow\n\
1182
button at the bottom of the dialogue. The @fBCPU@fR, @fBMEM@fR, and @fBI/O@fR slider bars determine\n\
1183
the composition of the @fBCombined Usage@fR displayed for each node in the share tree.\n\
1184
The @fBHalflife@fR parameter specifies how fast to decay usage in the share tree. Usage will be\n\
1185
decayed at a rate in which half the usage will be gone after the @fBHalflife@fR period of time.\n\
1186
This defines the sliding window of time over which usage is tracked for the share tree.\n\
1187
The @fBCompensation Factor@fR limits the amount of compensation that Grid Engine will give to a\n\
1188
user in order to reach their targeted resource share.
1190
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1191
Qmon*fticket_layout*xmtHelpTitle: Functional Policy Help
1192
Qmon*fticket_layout*xmtHelp: \
1193
The @fBFunctional Policy@fR dialogue allows the Grid Engine manager to specify how system\n\
1194
resources should be shared among Grid Engine @fBUsers, Departments, Projects, Job and Jobclass@fR,\n\
1195
where Jobclass is currently identical to a Grid Engine queue.\n\
1197
Selecting one of the categories listed above from the @fBoption menu@fR topleft displays all\n\
1198
configured objects of this kind in the matrix with their current settings. To change the number\n\
1199
of @fBFunctional Shares@fR click the cell in the @fBFunctional Shares@fR column and change the\n\
1200
number of tickets. This changes the objects percentage of the functional ticket share.\n\
1201
By pressing the @fBRed Arrow@fR at the bottom right it is possible to apply a weighting to\n\
1202
the different object types.\n\
1203
To register the changes with @fBsge_qmaster@fR press @fBApply@fR. The message area at the bottom\n\
1204
confirms either @fBSuccess or Failure@fR.\n\
1205
@fBDone@fR quits the dialogue.\n\
1206
The @fBTwisted Red Arrow@fR links to the corresponding object configuration dialogue.
1209
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1210
Qmon*oticket_layout*xmtHelpTitle: Override Policy Help
1211
Qmon*oticket_layout*xmtHelp: \
1212
The @fBOverride Policy@fR dialogue allows the Grid Engine manager to specify how shorttrem system\n\
1213
resources should be overridden among Grid Engine @fBUsers, Departments, Projects, Job and Jobclass@fR,\n\
1214
where Jobclass is currently identical to a Grid Engine queue.\n\
1216
Selecting one of the categories listed above from the @fBoption menu@fR topleft displays all\n\
1217
configured objects of this kind in the matrix with their current settings. To change the number\n\
1218
of @fBFunctional Shares@fR click the cell in the second column and change the\n\
1219
number of tickets. This changes the number of override tickets.\n\
1220
To register the changes with @fBsge_qmaster@fR press @fBApply@fR. The message area at the bottom\n\
1221
confirms either @fBSuccess or Failure@fR.\n\
1222
@fBDone@fR quits the dialogue.\n\
1223
The @fBTwisted Red Arrow@fR links to the corresponding object configuration dialogue.
added
removed
source/dist/locale/en/qmon_help.ad
