IBM Books

Installation


Chapter 6. How Installation of PE Alters Your System

This chapter describes how your system is altered when you install the various PE software filesets. It describes the directories and files created, the daemon processes created, and the links established by the installation process.


How Installing the poe Fileset Alters Your System

The poe fileset includes all the components of the Parallel Operating Environment, and consists of the:

Installing this fileset as described in "Step 2: Performing the Initial Installation", does the following:

  1. If migrating from a previous version or release of POE, the following occurs:

  2. Creates the directories and files detailed in the following table.

    Table 4. poe Directories/Files Installed
    Directory/File Description
    /usr/lib/nls/msg/en_US/mpci_err.cat

    /usr/lib/nls/msg/En_US/mpci_err.cat

    /usr/lib/nls/msg/C/mpci_err.cat

    Message catalog for Message Passing Client Interface
    /usr/lib/nls/msg/En_US/pedig.cat

    /usr/lib/nls/msg/en_US/pedig.cat

    /usr/lib/nls/msg/C/pedig.cat

    Message catalog for VT trace functions
    /usr/lib/nls/msg/en_US/pempl.cat

    /usr/lib/nls/msg/En_US/pempl.cat

    /usr/lib/nls/msg/C/pempl.cat

    Message Catalog for Message Passing Library
    /usr/lib/nls/msg/en_US/pepdbx.cat

    /usr/lib/nls/msg/En_US/pepdbx.cat

    /usr/lib/nls/msg/C/pepdbx.cat

    Message Catalog for pdbx
    /usr/lib/nls/msg/en_US/pepoe.cat

    /usr/lib/nls/msg/En_US/pepoe.cat

    /usr/lib/nls/msg/C/pepoe.cat

    Message catalog for POE
    /usr/lib/nls/msg/En_US/poestat.cat

    /usr/lib/nls/msg/en_US/poestat.cat

    /usr/lib/nls/msg/C/poestat.cat

    Message catalog for POESTAT
    /usr/lpp/ppe.poe/bin/dbe Parallel Debugger engine
    /usr/lpp/ppe.poe/bin/digd VT dig daemon
    /usr/lpp/ppe.poe/bin/dfsnum.exp Import file for building the poeauth command for DFS support
    /usr/lpp/ppe.poe/bin/makedfs Shell script for building the poeauth command for DFS support
    /usr/lpp/ppe.poe/bin/mpamddir Shell script for echoing an AMD mountable directory name
    /usr/lpp/ppe.poe/bin/mcp Executable for multiple file copy utility
    /usr/lpp/ppe.poe/bin/mcpgath Executable for parallel file copy gather utility
    /usr/lpp/ppe.poe/bin/mcpscat Executable for parallel file copy scatter utility
    /usr/lpp/ppe.poe/bin/mpcc Shell script for compiling parallel C programs
    /usr/lpp/ppe.poe/bin/mpcc_chkpt Shell script for compiling C programs for checkpoint/restart capability
    /usr/lpp/ppe.poe/bin/mpcc_r Shell script for compiling threaded parallel C programs
    /usr/lpp/ppe.poe/bin/mpCC Shell script for compiling parallel C++ programs
    /usr/lpp/ppe.poe/bin/mpCC_chkpt Shell script for compiling C++ programs for checkpoint/restart capability
    /usr/lpp/ppe.poe/bin/mpCC_r Shell script for compiling threaded parallel C++ programs
    /usr/lpp/ppe.poe/bin/mprcp Shell script for distributing files
    /usr/lpp/ppe.poe/bin/mpmkdir Shell script for making directories
    /usr/lpp/ppe.poe/bin/mpxlf Shell script for compiling parallel Fortran programs
    /usr/lpp/ppe.poe/bin/mpxlf90 Shell script for compiling parallel Fortran 90 programs
    /usr/lpp/ppe.poe/bin/mpxlf_chkpt Shell script for compiling Fortran programs for Checkpoint/Restart capability
    /usr/lpp/ppe.poe/bin/mpxlf90_chkpt Shell script for compiling Fortran 90 programs for checkpoint/restart capability
    /usr/lpp/ppe.poe/bin/mpxlf_r Shell script for compiling threaded parallel Fortran programs
    /usr/lpp/ppe.poe/bin/mpxlf90_r Shell script for compiling threaded parallel Fortran 90 programs
    /usr/lpp/ppe.poe/bin/pdbx Executable to run the command-line interface of the PE Debugging Facility
    /usr/lpp/ppe.poe/bin/PEdeinstall Shell script to remove an installation of PE on IBM RS/6000 nodes
    /usr/lpp/ppe.poe/bin/PEdeinstallSP Shell script to remove an installation of PE on SP nodes
    /usr/lpp/ppe.poe/bin/PEinstall Shell script to complete the installation process on IBM RS/6000 nodes
    /usr/lpp/ppe.poe/bin/PEinstallSP Shell script for installing PE on SP nodes
    /usr/lpp/ppe.poe/bin/pmadjpri Dispatching priority adjustment daemon
    /usr/lpp/ppe.poe/bin/pmarray The Program Marker Array program
    /usr/lpp/ppe.poe/bin/pmdv2 An Internet daemon process that runs on each of your processor nodes
    /usr/lpp/ppe.poe/bin/poe Partition Manager executable
    /usr/lpp/ppe.poe/bin/poe_dce_shr.o Shared object used at run time to resolve DFS/DCE functions
    /usr/lpp/ppe.poe/bin/poeauth.o Object version of poeauth command for DFS support
    /usr/lpp/ppe.poe/bin/poekill Shell script for terminating all POE started tasks
    /usr/lpp/ppe.poe/bin/poestat The System Status Array program
    /usr/lpp/ppe.poe/include Directory of header files containing declarations used by other installed files
    /usr/lpp/ppe.poe/lib/ip/libmpci.a Message Passing Client Interface library (IBM RS/6000 network cluster only)
    /usr/lpp/ppe.poe/lib/ip/libmpci_r.a Message Passing Client Interface library (IBM RS/6000 network cluster only) in a threaded environment
    /usr/lpp/ppe.poe/lib/libppe.a Archive library containing subroutines for POE and VT
    /usr/lpp/ppe.poe/lib/libmpi.a Archive library containing subroutines for parallel message-passing programs
    /usr/lpp/ppe.poe/lib/libmpi_r.a Archive library containing subroutines for parallel message-passing programs in a threaded environment
    /usr/lpp/ppe.poe/lib/libvtd.a VT tracing library
    /usr/lpp/ppe.poe/lib/libvtd_r.a VT tracing library in a threaded environment
    /usr/lpp/ppe.poe/lib/HPSOclk_chkpt.o Shared object used at run time to resolve checkpoint/restart clock functions
    /usr/lpp/ppe.poe/lib/pm_replaced.o POE exit object code
    /usr/lpp/ppe.poe/README/poe.README Memo to users relating to this release
    /usr/lpp/ppe.poe/samples Directory containing sample programs for the Program Marker Array and other samples
    /usr/lpp/ppe.poe/samples/mpif90/mpxlf90 Shell script for compiling parallel Fortran 90 programs
    /usr/lpp/ppe.poe/samples/mpif90/mpxlf90_r Shell script for compiling threaded parallel Fortran 90 programs
    /usr/lpp/ppe.vt/bin/dig VT Statistics Collector daemon
    /usr/lpp/ppe.vt/bin/rc.vtdig Shell script that starts the daemon
    /usr/man/cat1 Directory containing man page files for PE commands
    /usr/lpp/ppe.poe/include/thread/mpif.h Header file for compiling threaded MPI Fortran applications
    /usr/lpp/ppe.poe/samples/swtbl Directory containing sample code for running User Space POE jobs without LoadLeveler

  3. When the installp command successfully restores the POE's files from the distribution medium, the command looks at the ppe.poe.post_i file for post-installation steps. As part of these post-installation steps, ppe.poe.post_i sets up the following symbolic links:
    This link: To:
    /etc/digd /usr/etc/digd
    /etc/pmdv2 /usr/etc/pmdv2
    /etc/rc.vtdig /usr/lpp/ppe.vt/bin/rc.vtdig
    /usr/bin/mpcc /usr/lpp/ppe.poe/bin/mpcc
    /usr/bin/mpcc_chkpt /usr/lpp/ppe.poe/bin/mpcc_chkpt
    /usr/bin/mpcc_r /usr/lpp/ppe.poe/bin/mpcc_r
    /usr/bin/mpCC /usr/lpp/ppe.poe/bin/mpCC
    /usr/bin/mpCC_chkpt /usr/lpp/ppe.poe/bin/mpCC_chkpt
    /usr/bin/mpCC_r /usr/lpp/ppe.poe/bin/mpCC_r
    /usr/bin/makedfs /usr/lpp/ppe.poe/bin/makedfs
    /usr/bin/mpamddir /usr/lpp/ppe.poe/bin/mpamddir
    /usr/bin/mpmkdir /usr/lpp/ppe.poe/bin/mpmkdir
    /usr/bin/mprcp /usr/lpp/ppe.poe/bin/mprcp
    /usr/bin/mpxlf /usr/lpp/ppe.poe/bin/mpxlf
    /usr/bin/mpxlf_chkpt /usr/lpp/ppe.poe/bin/mpxlf_chkpt
    /usr/bin/mpxlf_r /usr/lpp/ppe.poe/bin/mpxlf_r
    /usr/bin/mpxlf90 /usr/lpp/ppe.poe/bin/mpxlf90
    /usr/bin/mpxlf90_chkpt /usr/lpp/ppe.poe/bin/mpxlf90_chkpt
    /usr/bin/mpxlf90_r /usr/lpp/ppe.poe/bin/mpxlf90_r
    /usr/bin/mcp /usr/lpp/ppe.poe/bin/mcp
    /usr/bin/mcpgath /usr/lpp/ppe.poe/bin/mcpgath
    /usr/bin/mcpscat /usr/lpp/ppe.poe/bin/mcpscat
    /usr/bin/pdbx /usr/lpp/pdbx/bin/pdbx
    /usr/bin/pmarray /usr/lpp/ppe.poe/bin/pmarray
    /usr/bin/pmdadjpri /usr/lib/ppe.poe/bin/pmdadjpri
    /usr/bin/poe /usr/lpp/poe/bin/poe
    /usr/bin/poekill /usr/lpp/ppe.poe/bin/poekill
    /usr/bin/poestat /usr/lpp/ppe.poe/bin/poestat
    /usr/etc/dbe /usr/lpp/ppe.poe/bin/dbe
    /usr/etc/digd /usr/lpp/ppe.vt/bin/digd
    /usr/etc/pmdv2 /usr/lpp/ppe.poe/bin/pmdv2
    /usr/lib/X11/app-defaults/PMarray /usr/lpp/ppe.poe/samples/marker/PMarray.ad
    /usr/lpp/poe/lib/ip/libmpci.a /usr/lpp/ssp/css/libip/libmpci.a (SP only)
    /usr/lpp/poe/lib/us/libmpci.a /usr/lpp/ssp/css/libus/libmpci.a (SP only)
    /usr/sbin/PEdeinstall /usr/lpp/poe/bin/PEdeinstall
    /usr/sbin/PEdeinstallSP /usr/lpp/poe/bin/PEdeinstallSP
    /usr/sbin/PEinstall /usr/lpp/ppe.poe/bin/PEinstall
    /usr/sbin/PEinstallSP /usr/lpp/ppe.poe/bin/PEinstallSP

  4. During installation, if an existing version of ppe.poe is installed, the following files are saved during installation of the new version in the /usr/lpp/save.config directory:
    /usr/lpp/ppe.poe/bin/mpcc
    /usr/lpp/ppe.poe/bin/mpCC
    /usr/lpp/ppe.poe/bin/mpxlf
    /usr/lpp/ppe.poe/bin/mpxlf90
    /usr/lpp/ppe.poe/bin/mpcc_r
    /usr/lpp/ppe.poe/bin/mpCC_r
    /usr/lpp/ppe.poe/bin/mpxlf_r
    /usr/lpp/ppe.poe/bin/mpxlf90_r
    /usr/lpp/ppe.poe/bin/mpcc_chkpt
    /usr/lpp/ppe.poe/bin/mpCC_chkpt
    /usr/lpp/ppe.poe/bin/mpxlf_chkpt
    /usr/lpp/ppe.poe/bin/mpxlf90_chkpt
    /usr/lpp/ppe.poe/bin/mpamddir
    /usr/lpp/ppe.poe/lib/poe.cfg
    

    If these files were previously modified, the older versions are preserved in the /usr/lpp/save.config directory and the new versions will need to be updated.

POE Installation Effects

Also, as part of the post installation steps, the following occurs:

  1. The file /etc/services is modified in the following manner:

  2. The file /etc/inetd.conf is modified.

    An entry for the pmv2 service which spawns the /etc/pmdv2 daemon is created if no pmv2 entry exists.

  3. inetd is refreshed.

  4. POE's version of libc.a is created by extracting and replacing shr.o. The POE version of libc_r.a is a symbolic link to libc.a.

    A version of libc.a (and a link for libc_r.a) are also created in the /usr/lpp/ppe.poe/lib/profiled directory, if AIX Base Profiling Support is installed.

  5. The file /etc/inittab is modified using mkitab unless an entry already exists so that the /etc/rc.vtdig shell script runs when the system is restarted to start the VT tracing daemon called /etc/digd.

  6. The dig daemon is started.

  7. The existence of IP and US versions of libmpci.a and libmpci_r.a from CSS is verified.

  8. Executable versions of mcp, mcpgath, and mcpscat are created.

  9. For DFS systems, the executable version of poeauth is created.

How Installing the pedb Fileset Alters Your System

Note:In PE, Version 2 Release 2, xpdbx was renamed to pedb.
The pedb fileset is the X-Windows interface of the PE Debugging Facility. Installing it, as described in "Step 2: Performing the Initial Installation", does the following:

  1. If migrating from a previous version or release of xpdbx, the files installed from the Version 1 xpdbx fileset or Version 2 ppe.xpdbx fileset are removed. These filesets are changed to an OBSOLETE state in the SWVPD and ODM.

  2. Creates the files described in the following table.

    Table 5. pedb Directories/Files Installed
    Directories/File Description
    /usr/lib/nls/msg/En_US/pedb.cat

    /usr/lib/nls/msg/en_US/pedb.cat

    /usr/lib/nls/msg/C/pedb.cat

    Message Catalog for pedb
    /usr/lpp/ppe.pedb/bin Directory containing scripts called by debugger array visualization feature options
    /usr/lpp/ppe.pedb/bin/pedb X-Windows debugger executable
    /usr/lpp/ppe.pedb/bitmaps Directory containing dialog bitmaps
    /usr/lpp/ppe.pedb/defaults/Pedb.ad Defaults file for X-Windows and Motif resource variables
    /usr/lpp/ppe.pedb/README/pedb.README Installation README file
    /usr/lpp/ppe.pedb/samples Directory containing optional function, such as Data Explorer Visualization Tools. See IBM Parallel Environment for AIX: Operation and Use, Volume 2.

  3. The following symbolic links are made during the ppe.pedb fileset installation process:
    This link: To:
    /usr/bin/pedb /usr/lpp/ppe.pedb/bin/pedb
    /usr/bin/xpdbx /usr/lpp/ppe.pedb/bin/pedb
    /usr/lib/X11/app-defaults/Pedb /usr/lpp/ppe.pedb/defaults/Pedb.ad

How Installing the VT Fileset Alters Your System

The VT fileset is the Visualization Tool. Installing it as described in "Step 2: Performing the Initial Installation" does the following:

  1. If migrating from Version 1 of VT, the files installed from the VT fileset are removed. The fileset is changed to an OBSOLETE state in the SWVPD and ODM.

  2. Creates the directories and files detailed in the following table:

    Table 6. VT Directories/Files Installed
    Directory/File Description
    /usr/lib/nls/msg/En_US/pevt.cat

    /usr/lib/nls/msg/en_US/pevt.cat

    /usr/lib/nls/msg/C/pevt.cat

    Message Catalog for VT
    /usr/lpp/ppe.vt/Bitmaps Directory containing icon Bitmaps for each VT View. These icons appear in the View Selector window.
    /usr/lpp/ppe.vt/bin/digq Child process run when the Resource Manager is not used. Determines what nodes are available to monitor.
    /usr/lpp/ppe.vt/bin/dug Program used by VT during performance monitoring to communicate with the dig Statistics Collector daemon
    /usr/lpp/ppe.vt/bin/vt The VT program
    /usr/lpp/ppe.vt/Config Directory of configuration files used by the VT control code to initialize the Views for trace visualization
    /usr/lpp/ppe.vt/ConfigPM Configuration files used by the VT control code to initialize the Views for performance monitoring
    /usr/lpp/ppe.vt/CPBitmaps Directory of user interface bitmaps used to create the Trace Visualization window
    /usr/lpp/ppe.vt/include/pevt.cat Message catalog for VT
    /usr/lpp/ppe.vt/include/VT_mpi.h VT MPI header file
    /usr/lpp/ppe.vt/include/VT_trc.h VT trace header file
    /usr/lpp/ppe.vt/README/vt.README Installation README file
    /usr/lpp/ppe.vt/Resource/VT.ad Defaults file for X-Windows and Motif resource variables
    /usr/lpp/ppe.vt/samples Directory containing sample programs
    /usr/lpp/ppe.vt/ViewSelect/System.PMView Layout definition of View Selector Window for performance monitoring
    /usr/lpp/ppe.vt/ViewSelect/System.PView Layout definition of View Selector Window for trace visualization
    /usr/lpp/ppe.vt/util Trace file view utility files

  3. The following changes are made as part of the VT fileset installation process:

This Link: To:
/usr/bin/digq /usr/lpp/ppe.vt/bin/digq
/usr/bin/dug /usr/lpp/ppe.vt/bin/dug
/usr/bin/vt /usr/lpp/ppe.vt/bin/vt
/usr/include/VT_trc.h /usr/lpp/ppe.vt/include/VT_trc.h
/usr/include/VT_mpi.h /usr/lpp/ppe.vt/include/VT_mpi.h
/usr/lib/X11/app-defaults/Vt /usr/lpp/ppe.vt/Resource/VT.ad

How Installing the Xprofiler Fileset Alters Your System

The Xprofiler fileset is the Xprofiler X-Windows Performance Profiler. Installing it as described in "Step 2: Performing the Initial Installation" creates the directories and files detailed in the following table:

Table 7. Xprofiler Directories and Files Installed
Directory or File Description

/usr/lib/nls/msg/En_US/xprofiler.cat

/usr/lib/nls/msg/en_US/xprofiler.cat

/usr/lib/nls/msg/C/xprofiler.cat

Message catalog for Xprofiler
/usr/lpp/ppe.xprofiler/defaults/Xprofiler.ad Defaults file for X-Windows and Motif resource variables
/usr/lpp/ppe.xprofiler/bin/.startup_script Startup script for Xprofiler
/usr/lpp/ppe.xprofiler/bin/xprofiler Xprofiler executable
/usr/lpp/ppe.xprofiler/help/en_US/xprofiler.sdl

/usr/lpp/ppe.xprofiler/help/en_US/xprofiler_msg.sdl

/usr/lpp/ppe.xprofiler/help/en_US/graphics

Online help
/usr/lpp/ppe.xprofiler/README/xprofiler.README Installation README file
/usr/lpp/ppe.xprofiler/samples Directory containing sample programs

The following symbolic link is made during the ppe.xprofiler fileset installation process:
This link: To:
/usr/lib/X11/app-defaults/Xprofiler /usr/lpp/ppe.xprofiler/defaults/Xprofiler.ad
/usr/bin/xprofiler /usr/lpp/ppe.xprofiler/bin.startup_script


How Installing the pedocs Fileset Alters Your System

The pedocs fileset consists of man page files and the PE documentation in HTML and PDF format. Installing it as described in "Step 2: Performing the Initial Installation" creates the directories and files detailed in the following table.

Please note that when you migrate from Version 1, the files installed from the pedocs fileset are removed. The fileset is changed to an OBSOLETE state in the SWVPD and ODM.

Table 8. pedocs Directories/Files Installed
Directory/File Description
/usr/lpp/ppe.pedocs/graphics Directory containing HTML graphics files
/usr/lpp/ppe.pedocs/html Directory containing HTML versions of the online books
/usr/lpp/ppe.pedocs/html/pebooks.html Sample index file
/usr/lpp/ppe.pedocs/pdf Directory containing PDF versions of the online books
/usr/lpp/ppe.pedocs/README/pedocs.README File describing available PE documentation and how to access it
/usr/man/cat3 Directory containing man page files for API message-passing subroutines

Installing the ppe.pedocs HTML Files

The ppe.pedocs fileset includes HTML files that contain online versions of the PE publications. Once you have installed the ppe.pedocs fileset, the PE HTML publications will be located at /usr/lpp/ppe.pedocs/html. Because other parts of PE link to the HTML publications, these files should not be moved from the /usr/lpp/ppe.pedocs/html directory.

A sample index file, /usr/lpp/ppe.pedocs/html/pebooks.html has also been provided. It shows you how to set up a single launching point from which users can access all of the online books.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]