If you receive 40 patches, you should receive 40 patch README files. You should consider reading all 40 README files. Important information to specifically look for includes: Automatic Reboot, Patch Dependencies, Hardware Dependencies, Other Dependencies, Warnings, and Special Installation Instructions. To retrieve the patch README file from the IPD, you can use the command swlist “a readme <patch> command.
A2:
You would adopt a proactive patching model. Proactive patching is where the current hardware and software configuration of a machine is analyzed against the current patch database. Any relevant patches are highlighted as potential candidates for installation. Reactive patching is where the solution to a specific current problem is identified as being the installation of at least one patch. A TAM / ASE / RACE / NRCE will adopt a proactive patching model.
A3:
Corrupt and transient both indicate that there were problems installing the patch, specifically during the execution phase of an swcopy or swinstall command. The difference between the two states is that with a transient patch, Software Distributor was not able to identify what caused the problem when it initially occurred. Patches in either a corrupt or transient state should not be used, but should be either reinstalled or removed.
A4:
The security_patch_check utility uses the security patch catalog (available from the ITRC via anonymous FTP). The security patch catalog is updated nightly. There is an argument that to remain as up to date as possible, the security_patch_check utility should be run every day.
A5:
When ProductX is installed, Patch 5 is the only patch that will be installed. Patch 5 contains the functionality provided by all previous patches. The Software Distributor options in question include autoselect_dependencies=true , autoselect_patches=true , and the superseded attribute.
