pbsdsh(1b) [debian man page]

pbsdsh(1B)								PBS								pbsdsh(1B)

NAME

       pbsdsh - distribute task to nodes under pbs

SYNOPSIS

       pbsdsh [-c copies] [-o] [-s] [-u] [-v] program [args]
       pbsdsh [-n node] [-o] [-s] [-u] [-v] program [args]
       pbsdsh [-h nodename] [-o] [-v] program [args]

DESCRIPTION

       Executes (spawns) a normal Unix program on one or more nodes under control of the Portable Batch System, PBS.  Pbsdsh uses the Task Manager
       API, see tm_spawn(3), to distribute the program on the allocated nodes.

       When run without the -c or the -n option, pbsdsh will spawn the program on all nodes allocated to the PBS job.  The spawns take place  con-
       currently - all execute at (about) the same time.

       Users will find the PBS_TASKNUM , PBS_NODENUM , and the PBS_VNODENUM environmental variables useful.  They contain the TM task id, the node
       identifier, and the cpu (virtual node) identifier.

OPTIONS

       -c copies
	      The program is spawned on the first Copies nodes allocated.  This option is mutual exclusive with -n.

       -n node
	      The program is spawned on one node which is the node-th node allocted.  This option is mutual exclusive with -c.

       -h hostname
	      The program is spawned on the node specified.

       -o     Capture stdout of the spawned program.  Normally stdout goes to the job's output.

       -s     If this option is given, the program is run in turn on each node, one after the other.

       -u     The program is run once on each node (unique).  This ignores the number of allocated processers on a given node.

       -v     Verbose output about error conditions and task exit status is produced.

OPERANDS

       The first operand, program, is the program to execute.

       Additional operands, args, are passed as arguments to the program.

STANDARD ERROR

       The pbsdsh command will write a diagnostic message to standard error for each error occurrence.

EXIT STATUS

       Upon successful processing of all the operands presented to the command, the exit status will be a value of zero.

       If the pbsdsh command fails to process any operand, or fails to contact the MOM daemon on the localhost the  command  exits  with  a  value
       greater than zero.

SEE ALSO

       qsub(1B), tm_spawn(3B)

Local																	pbsdsh(1B)

APPSCHEMA(5)							 LAM FILE FORMATS						      APPSCHEMA(5)

NAME

       appschema - LAM application schema format

SYNTAX

       #
       # comments
       #
       [<where>] [-np #] [-s <where>] [-wd <dir>] [-x <env>] <program> [<args>]
       [<where>] [-np #] [-s <where>] [-wd <dir>] [-x <env>] <program> [<args>]
	...

DESCRIPTION

       The application schema is an ASCII file containing a description of the programs which constitute an application.  It is used by mpirun(1),
       MPI_Comm_spawn, and MPI_Comm_spawn_multiple to start an MPI application (the MPI_Info key "file" can be used to specify an  app	schema	to
       MPI_Comm_spawn  and  MPI_Comm_spawn_multiple).	All tokens after the program name will be passed as command line arguments to the new pro-
       cesses.	Ordering of the other elements on the command line is not important.

       The meaning of the options is the same as in mpirun(1).	Note, however, that if -wd is used in the application schema file, it  will  over-
       ride any -wd value specified on the command line.

       For each program line, processes will be created on LAM nodes according to the presence of <where> and the process count option (-np).

       only <where>  One process is created on each node.

       only -np      The specified number of processes are scheduled across all LAM nodes/CPUs.

       both	     The specified number of processes are scheduled across the specified nodes/CPUs.

       neither	     One process is created on the local node.

   Program Transfer
       By  default,  LAM searches for executable programs on the target node where a particular instantiation will run.  If the file system is not
       shared, the target nodes are homogeneous, and the program is frequently recompiled, it can be convenient to have LAM transfer  the  program
       from  a	source node (usually the local node) to each target node.  The -s option specifies this behaviour and identifies the single source
       node.

EXAMPLE

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

SEE ALSO

       mpirun(1), MPI_Comm_spawn(2), MPI_Comm_Spawn_multiple(2), MPIL_Spawn(2), introu(1)

LAM 6.5.8							  November, 2002						      APPSCHEMA(5)