GENERAL PARAMETERS¶

The -pretty and -parsable switches are used to select whether to display the output in "pretty" or machine-parsable format, respectively. If neither is specified, -pretty is the default.

The -arch switch will display the architecture that LAM/MPI was configured and compiled on.

The -config switch will display a set of configuration information about the MPI capabilities of LAM/MPI, such as whether there are C, C++, and Fortran MPI bindings available, whether there is MPI profiling support for C, C++, and Fortran, whether ROMIO support is available, whether IMPI support is available, whether debugging support is available (mostly for LAM/MPI maintainers), and whether LAM/MPI is "purify clean" (meaning that it is suitable for use with memory checking debuggers). Most of these are options to the LAM/MPI configure script, and are configure/compile-time selections that cannot be changed once LAM has been installed. While there is no fine-grained control to individually request each of these pieces of information, using -config in conjunction with -parsable and commands such as grep can return any individual piece of information.

PARAM PARAMETERS¶

The -param switch can be used to show available SSI parameters and their default values. The type and module arguments can be used to specify a particular SSI type and/or module, or use the special keyword "all" to indicate all available SSI types/modules (respectively).

Available SSI types are:

all

Show all SSI types

base

Intrinsic LAM/MPI parameters

boot

Boot modules (e.g., lamboot)

coll

MPI collectives

cr

Checkpoint / restart

RPI

MPI point-to-point.

The names of the modules that are available are dependant upon which modules are available for any given type. See EXAMPLES, below, for example usage.

PATH PARAMETERS¶

The -path switch returns various paths that were compiled into LAM/MPI. These were all decided when LAM was configured, and cannot be changed at run-time. However, knowing the location of these directories can be useful in order to find LAM data files, binaries, include files, etc. The -path switch takes a parameter: item. Possible values for item are:

prefix

Display the prefix directory for LAM/MPI

bindir

Display the directory where the LAM/MPI executables were installed

libdir

Display the directory where the LAM/MPI libraries were installed

incdir

Display the directory where the LAM/MPI include files were installed

pkglibdir

Display the directory where the LAM/MPI dynamic libraries were installed

sysconfdir

Display the directory where the LAM/MPI help and configuration files were installed

Note that although LAM's GNU configure script defaults to certain values for all of these directories based on the prefix (e.g., bindir is typically $prefix/bin), they can all be overriden by command line switches to configure, and should therefore never be assumed. Use laminfo to determine what values were selected at configure time.

VERSION PARAMETERS¶

Since each SSI module in LAM/MPI is an independant entity in itself, it may have an entirely different version number than LAM/MPI itself. Indeed, each SSI module has three version numbers: the version of the base SSI API that it supports, the version of the component type API that it supports, and its own version number. Most users will only care about the last one (the module's own version number).

The -path switch takes two parameters: item and scope.

The item can be the main LAM version itself, any of the SSI types, or a specific SSI module. There are currently four kinds of SSI modules that can be queried: boot, coll, rpi, and cr. Hence, the version numbers that can be obtained from the -version switch are:

lam

The version of LAM/MPI

boot

The three versions of each boot SSI module

boot:name

The three versions of a specific boot SSI module

coll

The three versions of each coll SSI module

coll:name

The three versions of a specific coll SSI module

rpi

The three versions of each rpi SSI module

rpi:name

The three versions of a specific rpi SSI module

cr

The three versions of each cr SSI module

cr:name

The three versions of a specific cr SSI module

The scope argument describes what part of the version number to display. This allows either the full version number to be displayed, or any specific individual component of the version number. Valid values for scope are:

full

Display the full version number (i.e., all components). A sequence of rules are used to run all the components together into a single string. Generally: major and minor are always displayed, but other components are only displayed if they are not zero.

major

Display the major version number

minor

Display the minor version number

release

Display the release version number

alpha

Display the alpha version number. In the full scope, if nonzero, this number will be preceeded by "a".

beta

Display the beta version number. In the full scope, if nonzero, this number will be preceeded by "b".

cvs

Display whether LAM was installed from a CVS checkout. In pretty mode, this will be the string "cvs" if true, or blank if false. In parsable mode, this will be 1 if true, 0 if false.