Originally posted by: Jack0fAll

Is there a command line switch that I can supply to installp so that it won't install certain filesets. For example, on some servers I don't want it to update the java/sdk/jre filesets as it can lead to application issues. What can I do to modify the behavior of installp or update_all so that either of them won't install java/sdk/jre filesets.

Originally posted by: AncientAIXer

You could build a listfile (use a -f with installp) for each type of server which contains the filesets you want to install.  You could build it from the .toc.

Originally posted by: Jack0fAll

Can you please provide me an example of how I'd do that.

Originally posted by: AncientAIXer

grep -e " I " -e " U " .toc | grep -v "{$" | sed 's/ ..*//' | sort -u > server1.filesets

grep -e " I " -e " U " .toc  = gets all lines with I (install) and U (update) fileset

grep -v "{$" = eliminate lines for bundles

sed 's/ ..*//' = parse only first "word" up to first space ( could also use awk '{print $1}' )

sort -u = eliminates duplicates

This will output all filesets.  You will then have to edit the file to remove those that you don't want to install.

Originally posted by: CaptSalty

Could this approach be used to correct an upgrade that failed? I was trying to go from 7100-01-00-0000 to 7100-05-00-1731 but the process failed with:

0503-466 installp: The build date requisite check failed for fileset bos.net.nfs.client.

Installed fileset build date is 1140. Selected fileset does not have a build date, but one is required.

installp: Installation failed due to BUILDDATE requisite failure.

The oslevel now reports 7100-01-10-1415.

Any suggestions for how to finish this upgrade?