Using and Administering

POE 2.4.0

Figure 17 is a sample job command file for POE 2.4.0.

Figure 17. POE 2.4.0 Job Command File - Multiple Tasks Per Node

# # @ job_type = parallel # @ environment = COPY_ALL # @ output = poe.out # @ error = poe.error # @ node = 8,10 # @ tasks_per_node = 2 # @ network.LAPI = switch,shared,US # @ network.MPI = switch,shared,US # @ wall_clock_limit = 60 # @ executable = /usr/bin/poe # @ arguments = /u/richc/My_POE_program -euilib "us" # @ class = POE # @ queue

Figure 17 shows the following:

• The total number of nodes requested is a minimum of eight and a maximum of 10 (node=8,10). Two tasks run on each node (tasks_per_node=2). Thus the total number of tasks can range from 16 to 20.
• Each task of the job can run using the LAPI protocol in US mode with an SP switch adapter (network.LAPI=switch,shared,US), and/or using the MPI protocol in US mode with an HPS adapter (network.MPI=switch,shared,US). Note that "switch" is an installation-defined network type which is used for css0 adapters in these examples.
• The maximum run time allowed for the job is 60 seconds (wall_clock_limit=60).

Figure 18 is a second sample job command file for POE 2.4.0.

Figure 18. POE Sample Job Command File - Invoking POE Twice

# # @ job_type = parallel # @ input = poe.in.1 # @ output = poe.out.1 # @ error = poe.err # @ node = 2,8 # @ network.MPI = switch,shared,IP # @ wall_clock_limit = 60 # @ class = POE # @ queue /usr/bin/poe /u/richc/my_POE_setup_program -infolevel 2 /usr/bin/poe /u/richc/my_POE_main_program -infolevel 2

Figure 18 shows the following:

• POE is invoked twice, via my_POE_setup_program and my_POE_main_program.
• The job requests a minimum of two nodes and a maximum of eight nodes (node=2,8).
• The job by default runs one task per node.
• The job uses the MPI protocol with an SP switch adapter in IP mode (network.MPI=switch,shared,IP).
• The maximum run time allowed for the job is 60 seconds (wall_clock_limit=60).