IBM Support

Handling AIX fileset requisite issues.

Question & Answer


Question

What is the difference between Base and Update fileset ?
How to identify whether a fileset is base or update ?
When do I need an Update fileset / Install fileset ?
Which fileset type I need when getting a requisite failure ?
Where do I get the needed fileset once I determine if I need a base fileset or an update ?

This document’s purpose is to explain the differences between an update and a base fileset, including when each of them is used and how to resolve prerequisites errors requesting base or update fileset.

Answer

Introduction

This document will explain how to handle requisite issues and when to use base or update fileset type.
The following definitions will be used though out the document:
A software product installation package OR fileset is a backup-format file which contains the files of the software product, required installation control files, and optional installation customization files. The installp command is used to install and update software products.
Filesets can be installed either individually, or combined as is the case when performing a Technology Level or Service Pack update.

V.R.M.F. ( VERSION, RELEASE, MAINTENANCE LEVEL, FIX LEVEL ) which stands for:
For example V.R.M.F - V7 R2 M3 F2 = 7200-03-02
MAINTENANCE LEVEL is also referred to as Technology level.
FIX LEVEL is also referred to as Service Pack level.

What is the difference between Base and Update fileset ?

An installation package or base fileset contains one or more separately installable, logically grouped units called filesets.
Each fileset in a package must belong to the same product. For example all bos.net* packages are part of the bos.net base fileset.
A fileset update or update package is a package which contains modifications to an existing fileset and cannot be installed separately.
Base level filesets can be used to install software, reinstall existing fileset or downlevel existing file sets.
Base fileset can be force installed (-F flag with the installp command) to re-install a fileset or downlevel it. The –F flag cannot be used with an Update fileset.
Some fileset do not have a base level  version of the software, for example all the bos.rte.* filesets. These filesets come preloaded on the system and cannot be force overwritten or reinstalled. If there’s a problem with the update of such filesets, it needs to be investigated and identified what’s causing the update to fail and address the problem accordingly.
If a bos.rte.* fileset is missing from the system, this most likely means that someone manually removed it from that system’s ODM.
Uninstalling them is not something that can be done easily, as those filesets are mandatory for the Base Operating System (hence the bos. naming) and all have various non-deinstallable dependencies.
Update filesets will normally have a different naming convention while packed they usually have  U***** number and a .bff extension, for example:
U876244.bff
# installp -qld U876244.bff
  Fileset Name                           Level                     I/U    Q     Content
  ====================================================================
  devices.ethernet.lnc2.rte     7.2.2.15                   S        b     usr,root
#   10 Gigabit Ethernet PCI-Express Adapter Software
They can be renamed to their standard names with the "bffcreate" command.
 
The "bffcreate" command can be used to rename or copy while renaming .bff format files, for example if I have the U876248.bff update file set, I can use bffcreate to rename it
while adding a .I or .U  ( I = base level, U = update fileset ) extension at the end of the file name. Here's how its done:
 # ls
U876248.bff
# installp -qld U876248.bff
  Fileset Name                           Level                     I/U    Q     Content
  ====================================================================
  devices.pci.77102224.com    7.2.2.15                   S       b     usr,root
  #   PCI-X FC Adapter (77102224) Common Software
Run "bffcreate"
# bffcreate -cvXqd .
Note a table of content ( .toc ) file was created and the fileset was renamed to its normal name.
 # ls
.toc                                 devices.pci.77102224.com.7.2.2.15.U
This can be done for a entire Fix pack and its really helpful when trying to locate a specific file set.
This works only for .bff filesets and it won't work on base level filesets.
For reference, check the "bffcreate" man page: https://www.ibm.com/support/knowledgecenter/cs/ssw_aix_72/com.ibm.aix.cmds1/bffcreate.htm
Base filesets are available on the Base media for AIX. Downloaded AIX base iso images can be mounted and installable filesets can be found and used from there.

How to identify whether a fileset is base or update?

The easiest way to identify whether a fileset is a Base fileset or an Update fileset would be the name – installable fileset (base filesets) have the .I at the end of the fileset name, while the update ones have a .U at the end.
This is not always the case though – a fileset can be named with only it’s name and version, not including the .I or .U. The best way to identify a fileset and to confirm its type is to use the installp –qld command:
# installp -qld bos.mp64.7.2.2.15.I

  Fileset Name                Level                     I/U    Q     Content
  ====================================================================
  bos.mp64                    7.2.2.15                   I         b      usr,root
#   Base Operating System 64-bit Multiprocessor Runtime

We are interested in the I/U column. From the above output, you can see that the fileset is an I type – meaning installable or base. An update fileset will have the S value in this column, indicating Single Update:
# installp -qld bos.mp64.7.2.2.19.U
  Fileset Name                Level                     I/U    Q        Content
  ====================================================================
  bos.mp64                    7.2.2.19                   S        b         usr,root
#   Base Operating System 64-bit Multiprocessor Runtime
The output of this command provides other useful information – the Q column indicates whether installing this fileset requires a reboot (N for no reboot, b for reboot required); the Content column shows if this fileset has a USR,Root, shared part or a combination of the tree.
Regardless of whether or not a fileset has the .I or .U at the end, keep in mind this is only a name and everyone can rename a fileset, just as easy as renaming a single file on the system. To be absolutely sure what type the fileset is, the installp –qld  command should be used.

When do I need an Update fileset / Install fileset ?


Update filesets are located in the Technology Level / Service Pack update packages. All of the filesets provided by the Fix Packs are .U and can be used only for updating a fileset from one version to another (update_all).  Update filesets are mostly used to update the system and cannot be used for fixing existing issues with an installed fileset. They also cannot be used to install missing fileset – to be able to install a .U fileset, you need to have an earlier version of the fileset already installed on the system.
Base filesets are located on the AIX Base Media. If a fileset is missing from your system and you need to have it installed, you need to get it from the appropriate base media version. Base filesets can be used to fix problems with installed filesets – if a fileset is reported to be in broken state by "lppchk -v " or you need to downlevel a specific fileset, you can use the base level (.I) of this fileset and force install it over the old one.
Base media can be used to create NIM install resources (lpp_source and SPOT) to install other LPARs.
Update media can be used to create NIM lpp_sources that can be used only for updating the TL/SP of other LPARs.
Updating a system with Base filesets is possible, but not recommended. If you are planning on updating to a higher TL/SP and you have base media for this higher version, you should not use the base filesets to update the system - you should download the respective TL/SP package from FixCentral and do the update with the Update filesets.
Updating using base level fileset can only be done by committing the fileset and filesets in COMMITTED state cannot be rejected/down leveled without a full overwrite.
*Note: Updating from base level filesets can result in data loss as user configurable files delivered in the fileset will be restored to their original installed state.  i.e. resolv.conf, /etc/hosts, etc.
 
The delivered packages can be checked both from a already installed fileset and from a installable package ( both base and update filesets can be checked)
To check already installed package use the "-f" flag of the "lslpp" command:
# lslpp -f bos.games
  Fileset               File
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.games 7.2.3.0     /usr/games/lib/quiz/ucc
                        /usr/games/lib/quiz/areas
                        /usr/games/bj
                        /usr/games/lib/quiz/chinese
                        /usr/games/lib/quiz/babies
                        /usr/games/lib/quiz/inca
                        /usr/games/wump
........................................................
Path: /etc/objrepos
  bos.games 7.2.3.0     NONE
Or on a installable package:
# restore -Tqvf bos.games.7.2.3.0.I
New volume on bos.games.7.2.3.0.I:
 Cluster 51200 bytes (100 blocks).
    Volume number 1
    Date of backup: Wed Aug 22 15:45:23 CDT 2018
    Files backed up by name
    User BUILD
           0 ./
         324 ./lpp_name
           0 ./usr
           0 ./usr/lpp
           0 ./usr/lpp/bos.games
       15396 ./usr/lpp/bos.games/liblpp.a
           0 ./usr/lpp/bos.games/inst_root
       43358 ./usr/lpp/bos.games/inst_root/liblpp.a
           0 ./usr/games
       14028 ./usr/games/arithmetic
       30646 ./usr/games/back
        2018 ./usr/games/backrules
        7928 ./usr/games/bj
        6715 ./usr/games/craps
       14482 ./usr/games/fish
        8422 ./usr/games/fortune
..............................................................
Note: Using "restore" is not always accurate when checking base level packages because they contain multiple filesets and there is no way
to filter the output per fileset. You will be seeing the contents of ALL filesets in the package.

Which fileset type I need when getting a requisite failure ?


 
 AIX reports requisite failures in a few different ways. Normally it will tell you if it needs a base or update fileset, but there
 is an exception.
 
  •  Requiring base level file set at X.X.0.0 level.
 
 SELECTED FILESETS:  The following is a list of filesets that you asked to  install.  They cannot be installed until all of their requisite filesets
  are also installed.  See subsequent lists for details of requisites.
    bos.cifs_fs.rte 7.1.5.30                  # Runtime for SMBFS
  MISSING REQUISITES:  The following filesets are required by one or more of the selected filesets listed above.  They are not currently installed
  and could not be found on the installation media.
    bos.cifs_fs.rte 7.1.0.0                   # Base Level Fileset
    
    
The X.X.0.0 level is required when the fileset is not installed or is at a lower VERSION or RELEASE, in this case we require the cifs fileset to installed at V=7 R=1 M=X F=X.
And if we run a simple check we will either get:

# lslpp -l bos.cifs_fs.rte
lslpp: Fileset bos.cifs_fs.rte not installed.
OR
# lslpp -l bos.cifs_fs.rte
  Fileset                      Level  State      Description
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.cifs_fs.rte          6.1.9.315  COMMITTED  Runtime for SMBFS
Path: /etc/objrepos
  bos.cifs_fs.rte          6.1.9.315  COMMITTED  Runtime for SMBFS
    
In this case a base level fileset is needed to install or migrate the file set version/release to the desired level. It is best to obtain a base fileset
at the target level ( In this case we are trying to install 7.1.5.30 ) or lower. There is no need to seek the X.X.0.0, AIX reports the requisite
at the minimum required level, but installing the requisite at a higher level will satisfy the requisite.
    
    
    
    
  •  Requiring an update level file set:
 
  SELECTED FILESETS:  The following is a list of filesets that you asked to install.  They cannot be installed until all of their requisite filesets
  are also installed.  See subsequent lists for details of requisites.
    bos.adt.include 7.1.4.33                  # Base Application Development...
  MISSING REQUISITES:  The following filesets are required by one or more of the selected filesets listed above.  They are not currently installed
  and could not be found on the installation media.
    bos.mp64 7.1.4.32                         # Fileset Update
    
 In this case the system will report it needs a "Fileset Update" and will again specify the minimum required level, which in this case is 7.1.4.32.
 Running "lslpp" will show the file set is installed, but a lower FIX level then the required FIX level 32.
 
 # lslpp -l  bos.mp64
     Fileset                      Level        State             Description
  ---------------------------------------------------------------------------------------------
Path: /usr/lib/objrepos   
bos.mp64                  7.1.4.16  COMMITTED  Base Operating System 64-bit  Multiprocessor Runtime
Path: /etc/objrepos         
bos.mp64                  7.1.4.16  COMMITTED  Base Operating System 64-bit Multiprocessor Runtime
                                                
                                                
  •   Requesting for a base level file set when one is NOT required ( This is the exception ).
 
  SELECTED FILESETS:  The following is a list of filesets that you asked to install.  They cannot be installed until all of their requisite filesets
  are also installed.  See subsequent lists for details of requisites.
    bos.net.tcp.bind_utils 7.2.3.0            # TCP/IP BIND Utility Applicat...
  MISSING REQUISITES:  The following filesets are required by one or more of the selected filesets listed above.  They are not currently installed
  and could not be found on the installation media.
    bos.mp64 7.2.3.0                          # Base Level Fileset
    bos.net.tcp.client_core 7.2.3.0           # Base Level Fileset
    
    
 In this case, we have the system requisting a non X.X.0.0 level, but still requesting a base level fileset.
 The "lslpp" for one of the requisite filesets will show it is at a lower MAINTANENCE level. Since the fielset is already installed,
 base level is not actually needed, the update level for MAINTANENCE level 3 will satisfy the requisite.
    
     # lslpp -l bos.net.tcp.client_core
  Fileset                                    Level          State             Description
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.net.tcp.client_core   7.2.2.17  COMMITTED  TCP/IP Client Core Support
Path: /etc/objrepos
  bos.net.tcp.client_core   7.2.2.17  COMMITTED  TCP/IP Client Core Support

Where do I get the needed fileset once I determine if I need a base fileset or an update?

  • Base level fileets:
Base level filesets can be found in the base media ISO images for AIX.
Those can be downloaded from the Entitled Systems Support ( ESS ) site at http://www-304.ibm.com/servers/eserver/ess/index.wss
In some cases a FIX level ( Service Pack ) or a MAINTANENCE level ( Technology level) fix pack may contain a base level fileset,
but this is rare and is mainly when a new functionality is added.
 

Once in ESS, navigate to > My entitled software > Software downloads > AIX > Select the AIX version you wish to download > Click "Continue"

image-20190220213121-1

Next, if you want to download the latest media, select "Standard" or "Enterprise" edition and click Continue OR if you need an older AIX level, select the TL Support option and click continue.

image-20190220230746-2
 

If Standard/Enterprise is chosen, you will find the latest available ISO images for the selected AIX level, newer AIX
release will also have a "Flash" image which is simply DVD1 and DVD2 combined, where DVD2 contains mostly non US fonts
and character sets and is not needed for normal OS functionality.

image-20190220233036-1

You can refer to the Downloading an AIX ISO for a specific OSLEVEL Technical document for info on downloading specific OS level images.

Once you have selected your preferred OS image, you can click Continue on the bottom of the page and start downloading.
*Note that the ESS site and its functionality is out of the scope of support of AIX support. If you encounter issues during the above steps, please contact ESS support, you can find their contact information in the "Contacts" button on the left side or at:
Toll free +1 800 446 8989
Additional non toll free +44 2392 28959
Email: wwswkeys@dk.ibm.com

 

To access the ISO contents, you will need to mount it. In AIX this is easily done with the "loopmount" command.

# loopmount -i (path to .iso file) -o "-o ro -v udfs" -m /mnt

The filesets are located in the ./installp/ppc directory:
# loopmount -i AIX_v7.2_Install_7200-03-01-1838_flash_92018.iso -o "-o ro -v udfs" -m /mnt
# ls /mnt
.Version 7200-03 OSLEVEL README.aix RPMS bosinst.data image.data installp ismp license ppc root usr
# cd /mnt/installp/ppc


The filesets are usually packed, so to find for example bos.net.tcp.client you will need to search for the bos.net fileset package:
[root@LPAR1] /mnt/installp/ppc
# find . -name bos.net*
./bos.net

Then use the installp command to check the contents of the bos.net package, or directly to install the file set you need:

# installp -qld ./bos.net
  Fileset Name                Level                              I/U Q        Content
  ====================================================================
  bos.net.ate                      7.2.0.0                         I  N             usr
#   Asynchronous Terminal Emulator
  bos.net.ewlm.rte            7.2.3.0                        I  N            usr,root
#   netWLM
  bos.net.ipsec.keymgt    7.2.3.0                        I  N             usr,root
#   IP Security Key Management
  bos.net.tcp.client     7.2.0.0                     I  N           usr,root
#   TCP/IP Client Support
Or to install:

# installp -acgYXd . bos.net.tcp.client
* Note that some older images may require to be mounted as cdrfs, like this:
 

# loopmount -i (path to .iso file) -o "-o ro -v cdrfs" -m /mnt

  • Update filesets:
Update level filests can be obtained as Fix packs from the Fix Central site at http://www-933.ibm.com/support/fixcentral/
They usually come in a *.bff format and have a unique U#**** but can be converted to regular file names with the bffcreate command.
 
 

Once in Fix Central , navigate to Find Product > Select "AIX (IBM Operating System)" > Select the version you need > then Fix Pack: 



image-20190221173349-1
 

Then you should choose the Service pack or Technology level you wish to download and click continue:

  image-20190221182425-1
Either you will be prompted to choose Download options or you will have a button on the top right side of the screen for "Download options".
This is important because it lets you choose the preferred download method and if you should include prerequisites or not. Including prerequisite will add requisite fixes for the Fix pack you have selected, for example I have chosen Service Pack 2 ( 7100-03-02 )from AIX 7100 MAINTENANCE level 3, the requisite for Service pack 2, will be MAINTENANCE level 3 ( 7200-03-02 ).
image-20190221223130-1
* Note that downloading Fix packs requires valid entitlement, so you will be prompted to enter your machine type and serial number for the system you are downloading for.
If you encounter issues with Fix Central, please use the Feedback button on the left side of the screen to report an incident with Fix Central support.
* Note that issues with the Fix Central web site are out of the scope of support of AIX Software Support.

References:

Fix Central: http://www-933.ibm.com/support/fixcentral/
Entitled System Support: http://www-304.ibm.com/servers/eserver/ess/index.wss
Downloading an AIX ISO for a specific OSLEVEL: http://www-01.ibm.com/support/docview.wss?uid=isg3T1027277
Bffcreate command: https://www.ibm.com/support/knowledgecenter/cs/ssw_aix_72/com.ibm.aix.cmds1/bffcreate.htm
Installp command: https://www.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.cmds3/installp.html
Loopmount command: https://www.ibm.com/support/knowledgecenter/en/ssw_aix_71/com.ibm.aix.cmds3/loopmount.htm
Created by:
Nayden Stoyanov
Todor Todorov

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG10","label":"AIX"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
02 April 2019

UID

ibm10871636

Page Feedback