The section presents a series of simple tasks which a user might perform using commands. This section is meant for new users of LoadLeveler. More experienced users may want to continue on to Additional examples of building job command files.
Since you are not using the GUI, you have to build your job command file by using a text editor to create a script file. Into the file enter the name of the executable, other keywords designating such things as output locations for messages, and the necessary LoadLeveler statements, as shown in Figure 41:
Figure 41. Building a job command file
# This job command file is called longjob.cmd. The # executable is called longjob, the input file is longjob.in, # the output file is longjob.out, and the error file is # longjob.err. # # @ executable = longjob # @ input = longjob.in # @ output = longjob.out # @ error = longjob.err # @ queue |
You can optionally edit the job command file you created in step 1.
To submit the job command file that you created in step 1, use the llsubmit command:
llsubmit longjob.cmd
LoadLeveler responds by issuing a message similar to:
submit: The job "wizard.22" has been submitted.
Where wizard is the name of the machine to which the job was submitted and 22 is the job identifier (ID). You may want to record the identifier for future use (although you can obtain this information later if necessary).
For more information on llsubmit, see llsubmit - Submit a job
To display the status of the job you just submitted, use the llq command. This command returns information about all jobs in the LoadLeveler queue:
llq wizard.22
Where wizard is the machine name to which you submitted the job, and 22 is the job ID. You can also query this job using the command llq wizard.22.0, where 0 is the step ID. For more information, see llq - Query job status.
You can change the user priority of a job that is in the queue or one that is running. This only affects jobs belonging to the same user and the same class. If you change the priority of a job in the queue, the job's priority increases or decreases in relation to your other jobs in the queue. If you change the priority of a job that is running, it does not affect the job while it is running. It only affects the job if the job re-enters the queue to be dispatched again. For more information, see How does a job's priority affect dispatching order?.
To change the priority of a job, use the llprio command. To increase the priority of the job you submitted by a value of 10, enter:
llprio +10 wizard.22.0
For more information, see llprio - Change the user priority of submitted job steps.
To place a temporary hold on a job in a queue, use the llhold command. This command only takes effect if jobs are in the Idle or NotQueued state. To place a hold on wizard.22.0, enter:
llhold wizard.22.0
For more information, see llhold - Hold or release a submitted job.
To release the hold you placed in step 6, use the llhold command:
llhold -r wizard.22.0
For more information, see llhold - Hold or release a submitted job.
To display the status of the machine to which you submitted a job, use the llstatus command:
llstatus -l wizard
For more information, see llstatus - Query machine status.
To cancel wizard.22.0, use the llcancel command:
llcancel wizard.22.0
For more information, see llcancel - Cancel a submitted job.
Enter the llstatus command with the appropriate options to display the machine on which the central manager is running. For more information, see llstatus - Query machine status.
Public scheduling machines are those machines that participate in the scheduling of LoadLeveler jobs. The llstatus command can also be used to display the public scheduling machines.