Newsgroups: comp.parallel.mpi,comp.sys.sgi.admin,comp.sys.sgi.app From: Annette Jaekel Subject: Problem: xmpi on origin200 Organization: TU Berlin, Germany Date: Thu, 22 May 1997 13:56:48 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <33843480.71E5@math.tu-berlin.de> Hi, I administer 2 origin200 connected via Fast Ethernet. Everyone is a 4 processor (R10000) machine, (configured in two modules). SGI Germany send me a tape with ARRAY Services 3.0 BETA2, including MPI 3.0., because official release isn't delivered yet. I configured a Fast Ethernet array and try xmpi, the graphical interface to MPI, neccessary for array access. ainfo and arraytest told me, everything in array is allright. But seems to me, xmpi doesn't work right: There's no possibility to see status of applications or trace applications (overview window is black all the time, no hexagons appears). Only some menus work: Application: build&run, Application:browse&run and clean. All other menus are grayed. A Testapplication runs, for the local machine and for the two machines, but xmpi can't successfully "run" MPI_FINALIZE(). (I kill every application with clean-button). "mpirun" on the local machine starts and finishes application right. I set MPI_BYPASS_OFF (because we have no HIPPI Interface) MPI_DSM_VERBOSE (to see something about placement) MPI_DIR=/xxx/yyy/zzz (to find the application) Has anyone experiences with Array Services 3.0 and MPI, especially xmpi? What the matter with xmpi? -> By the way: Has anyone a solution for stdoutput from processes under MPI running on the remote machines? SGI's MPI Implementation only can show stdout from local processes. Until now I redirect it to output files, but killing the application (s.a.) lets hang up writing. Thank you for help, Annette Jaekel. -- Annette Jaekel * jaekel@math.tu-berlin.de TU Berlin * Germany