Hi,
Is there any way one can group related filesets together. E.g i want
to have list of filesets related to network daemons or kernel filesets
etc..

TIA
Harshal

About the only thing I could suggest would be lslpp -p flag. It tells
you what the co-requisites and requisites are for a particular fileset.
For example, if you are interested in what else is required when the
TCP/IP Network Client is updated, you can issue:

# lslpp -p bos.net.tcp.client

You will get a list of filesets that need to co-exist with the one you
selected.

What are you trying to achieve here?

I am trying to segregate the patches delivered on AIX 5.1 for fileset
into groups, like Network Daemon patches, Security Patches, OS kernel
patches so on and so forth. I thought i could acheive it by clearing
identifying the purpose of the filesets and their by leading to
segregation of their patches.
I would even like to know if there's any other way to do the same.
TIA
Harshal

sjm wrote:

> What are you trying to achieve here?

harshal.borade@gmail.com wrote:
> sjm wrote:
>>What are you trying to achieve here?
> I am trying to segregate the patches delivered on AIX 5.1 for fileset
> into groups, like Network Daemon patches, Security Patches, OS kernel
> patches so on and so forth. I thought i could acheive it by clearing
> identifying the purpose of the filesets and their by leading to
> segregation of their patches.

There is no *formal* attribute that indicates why a particular patch
exists. You can informally tell a lot from the bff file's lpp_name file
or a .toc file. This file's format is documented pretty well, here
is an example:

$ restore -qvf ../bos.net.nfs.client.5.1.0.66.bff
$ pg lpp_name

4 R S bos.net {
bos.net.nfs.client 5.1.0.66 01 b B En_US Network File System Client
[
*ifreq bos.mp (5.1.0.0) 5.1.0.53
*ifreq bos.mp64 (5.1.0.0) 5.1.0.53
*ifreq bos.net.nfs.cachefs (5.1.0.0) 5.1.0.54
*ifreq bos.net.tcp.client (5.1.0.0) 5.1.0.54
*ifreq bos.up (5.1.0.0) 5.1.0.53
%
....
IY38434 4 SECURITY: Integer overflow in xdrmem_getbytes
....
]
}

This patch is probably related to security, network and even the OS
kernel too since it requires certain minimal levels for the kernel.

> I would even like to know if there's any other way to do the same.

I also still do not quite understand what you intend to do. However, I
collect all bffs related to AIX 5.1 in one directory (and those related
to AIX 5.2 in another directory) on a NIM server and offer these
directories to those machines that need to be upgraded. Usually I apply
all available fixes at the same time and do not worry about
dependencies. That's AIX's job

GG

Is there any IBM link which documents the BFF format.

harshal.borade@gmail.com wrote:
> Is there any IBM link which documents the BFF format.

Files in the bff format are produced by the backup command, so the AIX
man page should help with the raw bff format. Software packaging, which
uses backup/restore, is described in great length at this link:

Packaging Software for Installation
http://publib.boulder.ibm.com/infoce...w4_install.htm

HTH,
GG

thanx that did solve my problem.