This chapter contains various procedures that are related to the PE installation procedure provided in Chapter 4. "Installing the PE Software".
During the installation process, you may decide to remove a fileset from the system. If you have already installed it on a number of nodes, you may wish to use one of the "deinstallation" scripts provided with PE:
For detailed information about these scripts and how to run them, see "Deinstallation Scripts".
If you install PE frequently, you may encounter an error such as:
0503-283 : Error in the Software Vital Product Data. The "usr" part of a product does not have the same requisite file as the "root" part. The product is: ppe.poe 22.214.171.124
This usually means there is an incompatibility in the Object Data Manager (ODM) as a result of installing a version of a product where prerequisites may have changed.
You need to remove the entries for a product from ODM. The following set of commands is one way to solve this problem (using POE as an example):
ODMDIR=/usr/lib/objrepos odmdelete -o product -qlpp_name=ppe.poe ODMDIR=/usr/lib/objrepos odmdelete -o lpp -qname=ppe.poe ODMDIR=/etc/objrepos odmdelete -o product -qlpp_name=ppe.poe ODMDIR=/etc/objrepos odmdelete -o lpp -qname=ppe.poe
Message cataloging is used by all PE filesets so that messages can be displayed in languages other than English. Each fileset has message catalogs installed in a directory located by the NLSPATH environment variable. The message catalogs are installed in three common English language paths and are in the format of <component>.cat. The paths are:
There are some restrictions and limitations in the MPI language bindings for Fortran 90.
For more information on the restrictions and implications of using MPI and the Fortran 90 compiler scripts, refer to the /usr/lpp/ppe.poe/samples/mpif90/README.mpif90 file after POE has been installed.
An MPI Fortran 90 language bindings header file (mpif90.h) is shipped as a sample file; if you have users with existing programs that depend on this file, you need to copy it to the usual location so that these users can continue to compile such programs with it.
With PE Version 2 Release 3, the mpif.h header file is formatted to work for both mpxlf and mpxlf90 compilation. Users writing new code should use mpif.h.
The CSS installation processing automatically establishes links to their
message passing libraries in place of those supplied by POE. For your
information, the following links are made when CSS is installed after
POE maintains copies of libc.a and libc_r.a, which are used to create the entry and exit points when a user's application is compiled with POE. In doing so, it creates a version of libc.a and libc_r.a for POE's use based on the system's copies.
As a result, when applying service that changes /usr/lib/libc.a and /usr/lib/libc_r.a, it is necessary to rebuild the POE version of libc.a. (In AIX Version 4.3, libc_r.a is a link to libc.a.) For this reason, POE ships a script called makelibc that automatically rebuilds its copies of libc.a and libc_r.a. Copies of libc.a and libc_r.a are also created in the /usr/lpp/ppe.poe/lib/profiled directory, if AIX Base Profiling Support is installed.
Any time you apply service that modifies /usr/lib/libc.a , you should run the makelibc script.
The makelibc script is in the /usr/bin path. You must run as root in order to run the script and rebuild the libraries.
This section contains the instructions for tailoring the Parallel Operating Environment and pedb for execution with the AFS file system. The source files settokens.c and gettokens.c are intended to be used with Transarc's Kerberos Authentication program, but should be usable as a guide for other environments.
The files needed for setting up the AFS execution are in the /usr/lpp/ppe.poe/samples/afs directory. They are:
Perform the following procedure as root for setting up POE and pedb for AFS execution:
|Note:||Before completing the following step, ensure that you have the following
amounts of available space in the current directory:
|Note:||If pedb is not currently installed, the steps to modify it for AFS execution are skipped.|