It might be that the update requires a fileset to be installed which was not necessary before. Maybe this is the case here. Filesets come in two flavours: base level and update. Update-types you can only install if you meet the requirements (prerequisites, ...) and have the base-level fileset installed. Base-level filesets can only be installed from an installation disk (either directly, from the medium, or indirectly, from a copy of the medium you took - like when you put the content of the medium to a NIM server). Base level filesets cannot be downloaded via the internet, because you could then download AIX in an unlimited way.
Search your installation medium (or, see above, the copy you created) for the respective base level filesets, install these, then install update filesets until they are at the required level.
Michael, i respect your efforts to help others here. Still, if you look carefully at your answer you will notice that it is no answer to thread-o/ps question at all, but a work-around at best and an attempt to promote your site at worst.
There is nothing wrong with using SUMA (i haven't used it in my 20 years of AIX, but that doesn't mean anything - there are many ways to skin a cat) and there is nothing wrong with suggesting its usage - but as long as the underlying question ("why can't i ...") is not answered, basically with some "because of ...", suggestions of methods fall short.
We had people here who would invariably write "use SMIT" into almost any thread. While SMIT is surely a great tool and there is nothing wrong with using (or suggesting) it, every question deserves an answer which ideally makes the one asking understand why the described problem did occur and how to solve it.
I suggest you think over your intentions for being here: if you just want to advertise your site please talk to Neo and i am sure you can strike some deal. If you truly want to help others please give the substantial and educating explanations an expert like you is surely capable of. Thank you.
I hope this helps.
bakunin
/PS: Some info about installp-files, because the above might be a bit confusing.
bff-("Backup File Format")-files are of one of two types: "Single Update" and "Install". It is possible that for the same version/revision both types exist, which is why it isn't sufficient to know that a fileset is of a certain version. You still won't know what you can do with the fileset you have (install it anywhere or only update already installed filesets).
The difference between the two can be seen in the ".toc" file: to create it go to the directory where the fileset is stored and enter inutoc . to create it. The following is an example output, the relevant difference marked bold:
$ installp -ld . |grep -p fence.blade
rsct.opt.fence.blade 2.4.9.0 I N usr
# RSCT BLADE Fence Agent
$
$ cd ../update
$ installp -ld . |grep -p fence.blade
rsct.opt.fence.blade 2.4.9.0 S N usr
# RSCT BLADE Fence Agent
It is therefore good practice to always store packages under their full package name. This name will end with "I" for installable ones and "U" (or sometimes "S", for reasons unknown) for single updates. The following command will do this:
bffcreate -c -d <source_device/path>
I hope this helps.
bakunin
