openmpi/ompi/mpi/help-mpi-api.txt

# -*- text -*-
#
# Copyright (c) 2006      High Performance Computing Center Stuttgart,
#                         University of Stuttgart.  All rights reserved.
# Copyright (c) 2006-2015 Cisco Systems, Inc.  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for Open MPI.
#
[mpi-abort]
MPI_ABORT was invoked on rank %d in communicator %s
with errorcode %d.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
#
[MPI function not supported]
Your application has invoked an MPI function that is not supported in
this environment.

  MPI function: %s
  Reason:       %s
Add a check for now that invokes an MPI exception if you try to SPAWN[_MULTIPLE] from a singleton (and displays a pretty help message explaining that you need to use mpirun). This can be removed when fixes for ORTE come over that allow SPAWN[_MULTIPLE] from singletons. This commit was SVN r10898. 2006-07-20 18:27:13 +04:00			`# -- text --`
			`#`
Purge whitespace from the repo 2015-06-24 06:59:57 +03:00			`# Copyright (c) 2006 High Performance Computing Center Stuttgart,`
- Help message in case of MPI-application with two init or calling init functions after finalize. This commit was SVN r12858. 2006-12-14 22:58:04 +03:00			`# University of Stuttgart. All rights reserved.`
mpi: infrastructure to gracefully disable MPI dyn procs Add ompi_mpi_dynamics_disable() function to disable MPI dynamic process functionality (i.e., such that if MPI_COMM_SPAWN/etc. are invoked, you'll get a show_help error explaining that MPI dynamic process functionality is disabled in this environment -- instead of a potentially-cryptic network or hardware error). Fixes #984 2015-10-07 01:07:07 +03:00			`# Copyright (c) 2006-2015 Cisco Systems, Inc. All rights reserved.`
Add a check for now that invokes an MPI exception if you try to SPAWN[_MULTIPLE] from a singleton (and displays a pretty help message explaining that you need to use mpirun). This can be removed when fixes for ORTE come over that allow SPAWN[_MULTIPLE] from singletons. This commit was SVN r10898. 2006-07-20 18:27:13 +04:00			`# $COPYRIGHT$`
Purge whitespace from the repo 2015-06-24 06:59:57 +03:00			`#`
Add a check for now that invokes an MPI exception if you try to SPAWN[_MULTIPLE] from a singleton (and displays a pretty help message explaining that you need to use mpirun). This can be removed when fixes for ORTE come over that allow SPAWN[_MULTIPLE] from singletons. This commit was SVN r10898. 2006-07-20 18:27:13 +04:00			`# Additional copyrights may follow`
Purge whitespace from the repo 2015-06-24 06:59:57 +03:00			`#`
Add a check for now that invokes an MPI exception if you try to SPAWN[_MULTIPLE] from a singleton (and displays a pretty help message explaining that you need to use mpirun). This can be removed when fixes for ORTE come over that allow SPAWN[_MULTIPLE] from singletons. This commit was SVN r10898. 2006-07-20 18:27:13 +04:00			`# $HEADER$`
			`#`
			`# This is the US/English general help file for Open MPI.`
			`#`
LANL noticed that calling MPI_ABORT invokes opal_output(0, ...) unconditionally, which can result in a flood of messages to the user if all MPI processes invoke abort. Additionally, some users were confused because they saw the MPI_ABORT opal_output() messages from ''some'' MPI processes, but not ''all'' of them (despite the fact that every MPI process supposedly invoked MPI_ABORT). The reason is that calling MPI_ABORT triggers ORTE to kill all MPI processes, so it's a race condition as to whether a) all MPI processes actually invoke MPI_ABORT, and/or b) whether every process is able to opal_output() before they are killed. This commit does two simple things: * Now use orte_show_help() for the MPI_ABORT message, so they are aggregated. * Add a note in the message that calling MPI_ABORT kills all processes, so you might not see all output, yadda yadda yadda. This commit was SVN r19735. 2008-10-14 23:23:03 +04:00			`[mpi-abort]`
Purge whitespace from the repo 2015-06-24 06:59:57 +03:00			`MPI_ABORT was invoked on rank %d in communicator %s`
LANL noticed that calling MPI_ABORT invokes opal_output(0, ...) unconditionally, which can result in a flood of messages to the user if all MPI processes invoke abort. Additionally, some users were confused because they saw the MPI_ABORT opal_output() messages from ''some'' MPI processes, but not ''all'' of them (despite the fact that every MPI process supposedly invoked MPI_ABORT). The reason is that calling MPI_ABORT triggers ORTE to kill all MPI processes, so it's a race condition as to whether a) all MPI processes actually invoke MPI_ABORT, and/or b) whether every process is able to opal_output() before they are killed. This commit does two simple things: * Now use orte_show_help() for the MPI_ABORT message, so they are aggregated. * Add a note in the message that calling MPI_ABORT kills all processes, so you might not see all output, yadda yadda yadda. This commit was SVN r19735. 2008-10-14 23:23:03 +04:00			`with errorcode %d.`
- Help message in case of MPI-application with two init or calling init functions after finalize. This commit was SVN r12858. 2006-12-14 22:58:04 +03:00
LANL noticed that calling MPI_ABORT invokes opal_output(0, ...) unconditionally, which can result in a flood of messages to the user if all MPI processes invoke abort. Additionally, some users were confused because they saw the MPI_ABORT opal_output() messages from ''some'' MPI processes, but not ''all'' of them (despite the fact that every MPI process supposedly invoked MPI_ABORT). The reason is that calling MPI_ABORT triggers ORTE to kill all MPI processes, so it's a race condition as to whether a) all MPI processes actually invoke MPI_ABORT, and/or b) whether every process is able to opal_output() before they are killed. This commit does two simple things: * Now use orte_show_help() for the MPI_ABORT message, so they are aggregated. * Add a note in the message that calling MPI_ABORT kills all processes, so you might not see all output, yadda yadda yadda. This commit was SVN r19735. 2008-10-14 23:23:03 +04:00			`NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.`
			`You may or may not see output from other processes, depending on`
			`exactly when Open MPI kills them.`
mpi: infrastructure to gracefully disable MPI dyn procs Add ompi_mpi_dynamics_disable() function to disable MPI dynamic process functionality (i.e., such that if MPI_COMM_SPAWN/etc. are invoked, you'll get a show_help error explaining that MPI dynamic process functionality is disabled in this environment -- instead of a potentially-cryptic network or hardware error). Fixes #984 2015-10-07 01:07:07 +03:00			`#`
			`[MPI function not supported]`
			`Your application has invoked an MPI function that is not supported in`
			`this environment.`

			`MPI function: %s`
			`Reason: %s`