This appendix explains the syntax of the commands for running the installation and deinstallation scripts provided with PE.
PE provides the following two installation scripts, explained in the sections below:
You can use the PEinstallSP script to install any of the filesets on SP nodes through the use of the Distributed Shell (dsh). In order to run the PEinstallSP script, you must first set up a host list file of all nodes on which you want a particular fileset installed. The PEinstallSP script either mounts or copies the installation image to each node in the list, and then executes the proper installp command to install the product.
Since PEinstallSP makes extensive use of dsh, it can only be run on SP nodes. Also, you must ensure that you have executed the k4init command to obtain Kerberos authentication for accessing your nodes.
The PEinstallSP script has one required parameter and three optional parameters. The syntax is:
PEinstallSP image_name [host_list_file] [-f fanout_value] [-copy | -mount]
You can specify either -copy or -mount to instruct PEinstallSP to copy or mount the installation image to each node. The default is -copy. For more information on copying or mounting installation images, refer to "Copying the Installation Image" or "Mounting the Installation Image".
You can use the PEinstall script to install any of the PE filesets on IBM RS/6000 nodes using the Remote Shell (rsh).
To run the PEinstall script, you must first set up a host list file of all nodes on which you want to install a particular fileset, and you must have /usr resident. The PEinstall script either mounts or copies the installation image to each node in the list, and then executes the proper installp command to install the product.
The PEinstall script has one required parameter and two optional parameters. The syntax is:
PEinstall image_name [host_list_file] [-copy | -mount]
You can specify either -copy or -mount to tell PEinstall to copy or mount the installation image to each node. The default is -copy.
Using the -copy option (or allowing it as the default) informs PEinstallSP or PEinstall to copy the named image to each node using rcp. You are prompted for the following information when -copy is specified (or defaulted):
|Note:||To have the image copied to different directories, invoke PEinstallSP or PEinstall for each different location or set of locations. Your host.list file should reflect only those nodes that you want to use with -copy.|
The image is copied to the destination directory with the name specified as the image_name parameter. Be sure there is enough space in the destination directory file system for the image. Each image occupies approximately three megabytes.
Specifying the -mount option informs PEinstallSP or PEinstall to mount the named image to each node using dsh (for PEinstallSP) or rsh (for PEinstall). You are prompted for the following information when -mount is specified:
|Note:||To have the image mounted to different directories, invoke PEinstallSP or PEinstall for each different location or set of locations. Your host.list file should reflect only those nodes that you want to use with -mount.|
PEinstallSP or PEinstall issues a mkdir command for the directory name specified, followed by a chmod 777. To execute the installp remotely on a mounted image, the directory containing the image needs to have this permission.
To avoid creating the directory with world-writable permissions, do not use the -mount option of PEinstallSP or PEinstall.
When you install a PE fileset, you do so first on a single node (or the control workstation), and then propagate the installation image to the additional nodes in your system. When you remove a fileset completely from your system, you do the opposite:
Removing an installation of a fileset removes all files already installed for that fileset. As a result, the PEdeinstallSP/PEdeinstallscripts will be removed from each node the installp -u command is run against. For this reason, you may want to consider copying PEdeinstallSP/PEdeinstall from /usr/lpp/ppe.poe/bin to another location prior to rejecting the installation of the fileset. However, if you follow the previously mentioned sequence of removing a fileset from the other nodes first, and then removing it from the initial node last, these scripts will remain available until the fileset is removed from the initial node.
PEdeinstallSP issues the proper installp command using the Distributed Shell (dsh).
Before you execute the PEdeinstallSP, ensure that you have previously obtained Kerberos authentication (via k4init) for accessing your nodes.
PEdeinstall issues the proper installp command using the Remote Shell (rsh).
The scripts have the following syntax:
PEdeinstallSP image_name [host_list_file] [-f fanout_value]
PEdeinstall image_name [host_list_file]
For each node, PEdeinstallSP or PEdeinstall issues the following installp command:
installp -ugX image_name
This command removes both the user and root portions of all the products in the image specified.
If there is a problem removing an install on a node, an error message is issued and logged in a file named PEnode.log in the current working directory, and the install removals continue for the remaining nodes.