Using and Administering

Example 2: Using LoadLeveler Variables in a Job Command File

Figure 15 shows how you can use LoadLeveler variables in a job command file to assign different names to input and output files. This example assumes the following:

• The name of the machine from which the job is submitted is lltest1
• The user's home directory is /u/rhclark and the current working directory is /u/rhclark/OSL
• LoadLeveler assigns a value of 122 to $(jobid).

In Job Step 0:

• LoadLeveler creates the subdirectories oslsslv_out and oslsslv_err if they do not exist at the time the job step is started.

In Job Step 1:

• The character string rhclark denotes the home directory of user rhclark in input, output, error, and executable statements.
• The $(base_executable) variable is set to be the "base" portion of the executable, which is oslsslv.
• The $(host) variable is equivalent to $(hostname). Similarly, $(jobid) and $(stepid) are equivalent to $(cluster) and $(process), respectively.

In Job Step 2:

• This job step is executed only if the return codes from Step 0 and Step 1 are both equal to zero.
• The initial working directory for Step 2 is explicitly specified.

Figure 15. Using LoadLeveler Variables in a Job Command File

# Job step 0 ============================================================ # The names of the output and error files created by this job step are: # # output: /u/rhclark/OSL/oslsslv_out/lltest1.122.0.out # error : /u/rhclark/OSL/oslsslv_err/lltest1_122_0_err # # @ job_name = OSL # @ step_name = step_0 # @ executable = oslsslv # @ arguments = -maxmin=min -scale=yes -alg=dual # @ environment = OSL_ENV1=20000; OSL_ENV2=500000 # @ requirements = (Arch == "R6000") && (OpSys == "AIX43") # @ input = test01.mps.$(stepid) # @ output = $(executable)_out/$(host).$(jobid).$(stepid).out # @ error = $(executable)_err/$(host)_$(jobid)_$(stepid)_err # @ queue # # Job step 1 ============================================================ # The names of the output and error files created by this job step are: # # output: /u/rhclark/OSL/oslsslv_out/lltest1.122.1.out # error : /u/rhclark/OSL/oslsslv_err/lltest1_122_1_err # # @ step_name = step_1 # @ executable = rhclark/$(job_name)/oslsslv # @ arguments = -maxmin=max -scale=no -alg=primal # @ environment = OSL_ENV1=60000; OSL_ENV2=500000; \ OSL_ENV3=70000; OSL_ENV4=800000; # @ input = rhclark/$(job_name)/test01.mps.$(stepid) # @ output = rhclark/$(job_name)/$(base_executable)_out/$(hostname).$(cluster).$(process).out # @ error = rhclark/$(job_name)/$(base_executable)_err/$(hostname)_$(cluster)_$(process)_err # @ queue # # Job step 2 ============================================================ # The names of the output and error files created by this job step are: # # output: /u/rhclark/OSL/oslsslv_out/lltest1.122.2.out # error : /u/rhclark/OSL/oslsslv_err/lltest1_122_2_err # # @ step_name = OSL # @ dependency = (step_0 == 0) && (step_1 == 0) # @ comment = oslsslv # @ initialdir = /u/rhclark/$(step_name) # @ arguments = -maxmin=min -scale=yes -alg=dual # @ environment = OSL_ENV1=300000; OSL_ENV2=500000 # @ input = test01.mps.$(stepid) # @ output = $(comment)_out/$(host).$(jobid).$(stepid).out # @ error = $(comment)_err/$(host)_$(jobid)_$(stepid)_err # @ queue