Pegasus InfoCorp: Web site design and web software development company

INTROU (1)

introduction to LAM user interface commands

LIST OF COMMANDS

    15 30 45
    Name Appears Description
         on Page
    bfctl   bfctl.1 Control message buffers.
    bfstate bfstate.1       Get message buffer status.
    doom    doom.1  Deliver a signal.
    fctl    fctl.1  Control remote file access.
    fstate  fstate.1        Get remote file status.
    hboot   hboot.1 Start LAM on a local node.
    hcc     hcc.1   Compile LAM C programs.
    hcp     hcc.1   Compile LAM C++ programs.
    hf77    hf77.1  Compile LAM F77 programs.
    lamboot lamboot.1       Start LAM.
    lamclean        lamclean.1      Clean all nodes.
    lamgrow lamgrow.1       Add a node.
    lamshrink       lamshrink.1     Remove a node.
    lamtrace        lamtrace.1      Unload trace data.
    loadgo  loadgo.1        Execute program.
    mpimsg  mpimsg.1        Display MPI buffered messages.
    mpirun  mpirun.1        Run an MPI application.
    mpitask mpitask.1       Display MPI processes.
    recon   recon.1 Verify LAM setup.
    state   state.1 Get process status.
    sweep   bfctl.1 Clean out message buffers.
    tkill   tkill.1 Terminate local node LAM session.
    tping   tping.1 Echo messages to a node.
    wipe    wipe.1  Terminate LAM.
    Target nodes are given on the command line.
    Nodes are generically identified as
      n<list> ,  
    where <list> can be a single node identifier or a list of node identifiers.
    For example:
    

      n1
      n1,3,5-10
      

    Node identifiers are established in the boot schema (see bhost(5)), and can be written in decimal or hexadecimal notation. In addition to explicit node identification, LAM has special mnemonics that refer to special nodes or a group of nodes.

    h

      the local node where the command is typed (as in "here")

    o

      the origin node where LAM was started with lamboot(1)

    N

      all nodes

    C

      all nodes intended for application computing LAM processes can be specified in two ways: by process identifier from the underlying operating system or by LAM process index. PIDs are written as p<list> , where <list> can be a single PID or a list of PIDs. Process indices are written as i<list> , where <list> can be a single index or a list of indices.