1APPSCHEMA(5)                   LAM FILE FORMATS                   APPSCHEMA(5)
2
3
4

NAME

6       appschema - LAM application schema format
7

SYNTAX

9       #
10       # comments
11       #
12       [<where>] [-np #] [-s <where>] [-wd <dir>] [-x <env>] <program> [<args>]
13       [<where>] [-np #] [-s <where>] [-wd <dir>] [-x <env>] <program> [<args>]
14        ...
15

DESCRIPTION

17       The application schema is an ASCII file containing a description of the
18       programs which constitute an application.  It  is  used  by  mpirun(1),
19       MPI_Comm_spawn, and MPI_Comm_spawn_multiple to start an MPI application
20       (the MPI_Info key "file" can be  used  to  specify  an  app  schema  to
21       MPI_Comm_spawn and MPI_Comm_spawn_multiple).  All tokens after the pro‐
22       gram name will be passed as command line  arguments  to  the  new  pro‐
23       cesses.   Ordering  of  the  other  elements on the command line is not
24       important.
25
26       The meaning of the options is  the  same  as  in  mpirun(1).   See  the
27       mpirun(1)  man  page  for a lengthy discussion of the nomenclature used
28       for <where>.  Note, however, that if -wd is  used  in  the  application
29       schema  file,  it  will override any -wd value specified on the command
30       line.
31
32       For each program line, processes will be created on LAM nodes according
33       to the presence of <where> and the process count option (-np).
34
35       only <where>  One process is created on each node.
36
37       only -np      The  specified  number  of processes are scheduled across
38                     all LAM nodes/CPUs.
39
40       both          The specified number of processes  are  scheduled  across
41                     the specified nodes/CPUs.
42
43       neither       One process is created on the local node.
44
45   Program Transfer
46       By  default,  LAM  searches  for executable programs on the target node
47       where a particular instantiation will run.  If the file system  is  not
48       shared, the target nodes are homogeneous, and the program is frequently
49       recompiled, it can be convenient to have LAM transfer the program  from
50       a  source  node  (usually  the local node) to each target node.  The -s
51       option specifies this behaviour and identifies the single source node.
52

EXAMPLE

54       #
55       # Example application schema
56       # Note that it may be necessary to specify the entire pathname for
57       # "master" and "slave" if you get "File not found" errors from
58       # mpirun(1).
59       #
60       # This schema starts a "master" process on CPU 0 with the argument
61       # "42.0", and then 10 "slave" processes (that are all sent from the
62       # local node) scheduled across all available CPUs.
63       #
64       c0 master 42.0
65       C -np 10 -s h slave
66

SEE ALSO

68       mpirun(1),        MPI_Comm_spawn(2),        MPI_Comm_Spawn_multiple(2),
69       MPIL_Spawn(2), introu(1)
70
71
72
73LAM 7.1.2                         March, 2006                     APPSCHEMA(5)
Impressum