# ---------------------------------------------------------------------- # File information # ---------------------------------------------------------------------- File name: aixLppInstallHints.txt FTP Site: ftp.software.ibm.com Directory: /storage/adsm/3466 URL to access directory: ftp://ftp.software.ibm.com/storage/adsm/3466 Last Modification Date: 03/29/2000 # ---------------------------------------------------------------------- # General information # ---------------------------------------------------------------------- This document provides instructions on how to install an AIX fileset(s) from the standard system installation directory. The standard system installation directory is /usr/sys/inst.images # ---------------------------------------------------------------------- # Does the AIX fileset need to be installed? # ---------------------------------------------------------------------- It may not be necessary to install an AIX fileset since it may already exist at the required level or higher. When this is the case we may be able to quickly determine this and avoid the entire download/installation process. Filesets to be installed on AIX will have a package name and a level indicator. It is often times efficient to know if a current package is installed and if so, what level it is installed at. Let's look at a specific example: Fileset package name: nsm.3466 Fileset level: 3.1.0.40 If the package name is known the following command can be issued: lslpp -l nsm.3466 Here is the output on a system where the nsm.3466 package is not installed: lslpp: Fileset nsm.3466 not installed. Here is the output on a system where the nsm.3466 package is already installed at level 3.1.0.40 Fileset Level State Description ---------------------------------------------------------------------------- Path: /usr/lib/objrepos nsm.3466 3.1.0.40 COMMITTED 3466 Network Storage Manager - U.S. English Since the package level is already at 3.1.0.40 the package need not be installed. If you do not know the exact package name but have some idea you can issue a command like: lslpp -l | grep nsm If you have no idea what to look for you cannot avoid downloading the fileset to determine if it needs to be installed. If you are downloading a file from ftp.software.ibm.com/storage/adsm/3466 the package name and level should be identified: -- in the README.TXT file in the ftp directory -- "intuitively" by the fileset name. Example: nsm.3466.3.1.0.40.bff # ---------------------------------------------------------------------- # Preparing /usr/sys/inst.images prior to downloading the file # ---------------------------------------------------------------------- Before proceeding with the contents of the installation the directory /usr/sys/inst.images should be removed. Here are the steps to take: -- cd /usr/sys/inst.images -- ls Note: the directory may have contents. In general this directory should be used as a temporary location for installing filesets. If the directory has contents it may be advisable to ask the customer regarding contents. It is possible that contents are left in this directory from previous maintenance activity. If there is uncertainty regarding the content I recommend renaming the directory. Here is an example of the required steps: -- cd /usr/sys -- mv inst.images inst.images.on.03_29_2000 -- mkdir inst.images -- cd inst.images If the you are comfortable deleting the directory contents the folowing steps can be taken: -- ensure the current directory is /usr/sys/inst.images. The command prompt should display the current directory. If it does not, issue the command 'pwd' -- ls -- if you are certain you want to delete the contents of the directory, issue the following commands: -- rm * -- rm .toc (only required if it exists) -- if other files that start with a period exist they need to be deleted one by one -- ls (verify that the directory is empty) # ---------------------------------------------------------------------- # Installing the fileset from /usr/sys/inst.images # ---------------------------------------------------------------------- -- cd /usr/sys/inst.images -- ls the directory should be empty -- obtain the fileset(s) to install and put them in /usr/sys/inst.images the fileset is typically obtained by downloading from the 3466 ftp site this process is discussed in the following document: ftp.software.ibm.com/storage/adsm/3466/downloadHints.txt -- inutoc /usr/sys/inst.images this creates the .toc file which is used by the install process. -- installp -l -d /usr/sys/inst.images this lists the fileset(s) which exist in the installation directory. Verify the filesets to be installed are the required filesets and that they are at the expected level(s). This is a good time to re-verify if the fileset(s) are already at or greater than the required level. -- Here are the steps to perform the installation of filesets using smitty: -- smitty install -- position cursor on 'Install and Update Software' and hit ENTER -- position cursor on 'Install and Update from LATEST Available Software' and hit ENTER -- hit F4 to display selections at the prompt: INPUT device / directory for software [] -- position cursor on ' /usr/sys/inst.images (Installation Directory)' and hit ENTER -- typically hitting Enter to install 'all_latest' software is appropriate alternatively, place the cursor on all_latest and hit F4 to display selections. Entire filesets or portions of filesets can be installed by selecting entries with F7. Hit F3 to cancel if you want to return and install 'all_latest'. Note: it is appropriate to accept the defaults in all of the other fields unless you have specific knowledge why a field should be changed. # ---------------------------------------------------------------------- # Verifying that the install was successful # ---------------------------------------------------------------------- Browsing through the smitty install output prior to exiting the installation screen is the best method to determine if the fileset(s) were properly installed. Installations performed through smitty can be reviewed after the fact by inspecting the file /smit.log. The latest activity is at the bottom of the file. Using lslpp to inspect the current level of an installed dataset is another way to verify the fileset was properly installed: example: lslpp -l nsm.3466 Note: it is never a problem to try to install a fileset that is already installed. If it is already installed at the same level or higher level than the fileset in /usr/sys/inst.images a message will be issued: -- if /usr/sys/inst.images contains NO filesets that require installation the following message is issued: No installable software products were found on the media. This message can be confusing. It actually means all filesets in the current directory are already installed at the current or higher level -- if at least one fileset will be installed the installation will proceed. Information messages indicating that some filesets are already installed at the required level will be issued as appropriate.