5.5 PatchiX Training

• Both reactive and PowerPatch patches to be installed simultaneously.
• Customization of the patches delivered on the PowerPatch tape.
• Creation of the patch installation tape while users remain on the system.
• Creation of a CSLT only when necessary.
In this class you will learn how to take advantage of these and other key HP Patch/iX
features to improve the patch process in your environment.
Changes in Patch Delivery
When introduced, HP Patch/iX and its catalog will be delivered on every patch tape.
There will also be additional patch files delivered for use by HP Patch/iX. Two of these
files are the GENxxxxx and REFxxxxx files, where xxxxx is the last 5 characters of the
patch ID. The GENxxxxx file will be a binary file that contains information such as patch
component checksums, patch supersedes, patch-to-patch dependencies, and product
dependencies. This information will allow HP Patch/iX to make recommendations about
whether the patch can/should be installed on your system. The REFxxxxx file is an
ASCII text file that contains information about the patch, such as General Release(GR)
text and Special Instructions (SI) text. This file is used by HP Patch/iX to give you
detailed information about the patch.
These information files are important because in the near future you will be able to
download patches electronically or receive them via e-mail, and then use HP Patch/iX to
install them. By choosing electronic patch delivery you will have direct access to many
patches, but not necessarily know what is best for your system. The information files will
help HP Patch/iX make recommendations, and help you to understand the impact of the
patches you are installing on your system.
Separating Management and Installation
HP Patch/iX was designed to have two distinct phases that can be performed at different
times.
Phase I of HP Patch/iX is the patch management phase, and is performed using a screen
based management interface that can be run with users on the system. All activities are
performed in a staging area where copies of the system software are modified. The output
of the Phase I process is a tape that can be used at some later time to install the patches.
Phase II is the patch installation phase, and must be performed at the system console. In
many cases users must be logged off the system and the network must be brought down.
This phase is designed to mimic the old AUTOINST/HPINSTAL interface to provide a
simple approach to installing the patches, with minimal operator training. Phase II may or
may not require a system update depending on the set of patches. It will typically involve
updating the system, re-running HP Patch/iX to restore the patch store files, and stream
any patch installation jobs.