# -*- text -*-
#
# Copyright (c) 2009-2010 The Trustees of Indiana University and Indiana
#                         University Research and Technology
#                         Corporation.  All rights reserved.
#
# Copyright (c) 2012 Cisco Systems, Inc.  All rights reserved.
# $COPYRIGHT$
# 
# Additional copyrights may follow
# 
# $HEADER$
#
# This is the US/English help file for Open MPI migrate tool
#
[usage]
ompi-migrate PID_OF_MPIRUN
  Open MPI Process Migration Tool

%s
#
[invalid_pid]
Error: The PID (%d) is invalid because either you have not provided a PID 
       or provided an invalid PID.
       Please see --help for usage.
#
[no_universe]
Error: Unable to find the contact information for PID %d.
       This could be due to one of the following:
        - The PID is not that of an active MPIRUN.
        - The application with this PID isn't migratable
        - The application with this PID isn't an Open MPI application.
       ompi-migrate attempted to find the session directory:
         %s
#
[unable_to_connect]
Error: Unable to connect to the Head Node Process to initiate the 
       migration of the application.
       This could be due to one of the following:
        - The PID is not that of an active MPIRUN.
        - The application with this PID isn't migratable
        - The application with this PID isn't an Open MPI application.
#
[not_impl]
The following feature was requested, but is not currently implemented.
     %s
If you require this feature contact the Open MPI development group.
#
[err-inprogress]
Error: The Job identified by PID (%d) is currently migrating other processes.
       Only one migration request can be processed at a time. Please try again
       later.
#
[err-other]
Error: The Job identified by PID (%d) was not able to migrate processes in this
       job. This could be caused by any of the following:
       - Invalid node or rank specified
       - No processes on the indicated node can by migrated
       - Process migration was not enabled for this job. Make sure to indicate
         the proper AMCA file: "-am ft-enable-cr-recovery".
