1. Define the package definitions and naming conventions
2. Identify how software products and updates are installed and mananged on the system.
AIX Product Offerings:
LPPs – Licensed Program Product
AIX Toolbox for Linux
1. LPP:bos – Collection of Packages (Complete Product)
bos – Base Operation System
2. package: bos.INed, bos.adt (Collection of related Filesets)
3. fileset: bos.INed, bos.adt.lib, bos.adt.prof (Smallest Unit – Specific Function)
bos.terminfo.print.data – bos(LPP).terminfor(Package).print(Fileset).data(Suffix)
Note: You can choose to install an LPP, or just a single Package or Fileset.
A Bundle is a collection of packages and filesets suited for a particular environment.
Predefined system bundles in AIX 5.1 include:
-CDE (Common Desktop Environment)
# oslevel – Displays the current operating system level
Migration – Version & Release (Regular Install from CDs)
smit update_all – Modification & Fix (Different process)
1. Applied State (Saves old Version files)
FileSet 188.8.131.52 (Old Version)
FileSet 184.108.40.206 (New Version – Applied)
Commit or Reject – If the new applied version is not working correctly you can Reject it and the old version will be restored. If it is working correctly, then the new version will be committed and the old version will be deleted freeing up the disk space.
2. Committed State (Old Version Files deleted, New version committed)
Note: This only applies when you are updating software.
SMIT – Software Installation and Maintenance:
Install and Update Software
List Software and Related Information
Software Maintenance and Utilities
Network Installation Management
System Backup Manager
Install and Update Software
Update Installed Software to Latest Level (Update All)
Install Software Bundle
Update Software by Fix (APAR)
Install and Update from ALL Available Software
# smit list_installed
List Installed Software and Related Information
lslpp – list licensed program product
-L – lists the installed software
-h – shows the history of a software product
# lslpp -l bos.* – List Installed Software of the Base Operating System
Software Maintenance and Utilities:
# smit maintain_software
Note: This is where you go to commit applied software.
Installing a Fix:
1. Installs a fix
# instfix -k IX38794 -d /dev/rmt0.1
-k – install a fix
-d – device installing from
Note: IX38794 is an APAR or problem number.
2. Searches for a fix
# instfix -ik IX38794
-i – search for a fix
3. Searches for a fix by keyword
# instfix -s SCSI -d /dev/rmt0.1
-s – string to search for
Q: To install software, do I need to create a bundle?
A: No. You can create bundles if you want, but normally, administrators just select and install the filesets and packages without creating bundles.
Q: How do I know what part of a package to install in (root) /, usr or share?
A: You don’t need to worry about this. If you use SMIT or the installp command, the files will install in the correct location.
Q: Why would I want to install my software in the Applied State?
A: When it is in the applied state, the new version of the software is active but the old version is “archived” on the hard drive. If you start to test the new version and you don’t like it for whatever reason, you can reject it and the old version is unarchived and replaces the new version. This lets you more easily back out of a new software install.
Q: Applied sounds good! Why would I ever install directly to the committed state then?
A: Keep in mind that applied holds a copy of the old version as well as the new version. You must have the disk space to hold them both. If you don’t have enough disk space to do this, your only option is to install to the committed state. Also, if you have software in the applied state, you cannot install other version of the same software in the applied state. You must first commit the previously applied version. Lastly, if this is the first time installing this software product, it will automatically be installed as committed. If there isn’t an old version, there is no reason to be in the applied state.
Q: How do I install a fix?
A: You can use the instfix command or use SMIT. If you use the instfix command you can type: instfix -k IX38794 -d /dev/rmt0.1 The -k is the keyword, in this case the APAR (or fix) number. The -d is the device where the fix resides. In this case, the device is a tape device. If you want to check to see if a fix is installed already, you can use instfix also: instfix -i -k “IX38794”