To run a program several times, varying the initial conditions each time, you could can multiple LoadLeveler scripts, each specifying a different input and output file as described in Figure 15. It would probably be more convenient to prepare different input files and submit the job only once, letting LoadLeveler generate the output files and do the multiple submissions for you.
Figure 14 illustrates the following:
Assume that you created five input files and each input file has different initial conditions for the program. The names of the input files are in the form longjob.in.x, where x is 0-4.
Submitting the LoadLeveler script shown in Figure 14 results in your program running five times, each time with a different input file. LoadLeveler generates the output file from the LoadLeveler job step IDs. This ensures that the results from the different submissions are not merged.
Figure 14. Job Command File with Varying input Statements
# @ executable = longjob # @ input = longjob.in.$(stepid) # @ output = longjob.out.$(jobid).$(stepid) # @ error = longjob.err.$(jobid).$(stepid) # @ queue # @ queue # @ queue # @ queue # @ queue |
To submit the job, type the command:
llsubmit longjob.cmd
LoadLeveler responds by issuing the following:
submit: The job "ll6.23" with 5 job steps has been submitted.
The following table shows you the standard input files, standard output
files, and standard error files for the five job steps:
| Job Step | Standard Input | Standard Output | Standard Error |
|---|---|---|---|
| ll6.23.0 | longjob.in.0 | longjob.out.23.0 | longjob.err.23.0 |
| ll6.23.1 | longjob.in.1 | longjob.out.23.1 | longjob.err.23.1 |
| ll6.23.2 | longjob.in.2 | longjob.out.23.2 | longjob.err.23.2 |
| ll6.23.3 | longjob.in.3 | longjob.out.23.3 | longjob.err.23.3 |
| ll6.23.4 | longjob.in.4 | longjob.out.23.4 | longjob.err.23.4 |