Browse Prior Art Database

Packaging and Required Type Updates

IP.com Disclosure Number: IPCOM000110069D
Original Publication Date: 1992-Oct-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 3 page(s) / 127K

Publishing Venue

IBM

Related People

Murphy, TR: AUTHOR [+2]

Abstract

Described is an enhancement to the selective fix feature of AIX* 3.2. While selective fix is supported by most IBM operating systems, two features of AIX 3.2 selective fix are potentially unique.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 50% of the total text.

Packaging and Required Type Updates

       Described is an enhancement to the selective fix feature
of AIX* 3.2.  While selective fix is supported by most IBM operating
systems, two features of AIX 3.2 selective fix are potentially
unique.

      Today, customers generally install from tape.  Contained on the
tape are installation images that relate to licensed program
products.  Also contained on the tapes are update images that modify
the operation of the licensed programs.  These updates usually
contain bug fixes.  At the initial release of the code, the update
images contain fixes to bugs found late in the development cycle
(golden updates).  During the life of the product, these initial
updates are supplemented with additional bug fixes found by
customers.  These bugs fixes are called corrective service updates.
Periodically, these corrective service updates are sorted into
pervasive and non-pervasive fixes.  The pervasive fixes are grouped
into preventative maintenance packages.  With any selective fix, the
customer has control of whether the fix should be applied or not
applied.

      Since there are multiple types of service updates available,
the process that the software uses to apply these fixes must be
correct for the type of update being processed. We have implemented a
mechanism to identify the types of updates so that the correct
procedure can be used to apply the fix.

      The first type to be described is the initial update (golden
update).  Since the customer has the option of selecting any or all
of the fixes, a unique problem exists with respect to the initial
(golden) updates.  If the customer fails to install the golden
updates, he/she will be installing a known defective level of
software.  An additional problem exists when a severe problem is
uncovered during the life of the product.  There was no mechanism to
enforce the installation of the fix for this severe problem.
Therefore, a mechanism has been implemented to cover these exposures.
This mechanism is referred to as the "Required update".

      This mechanism is implemented by a unique type indicator in the
update image.  This type indicator is "G".  The installation software
is also modified.  The modification is to insure that any
installation of an LPP will automatically include all related "G"
type updates as a part of the installation activity.  These "G"
updates can occur anywhere on the media and can be added at any time
during the life of the product.  These updates differ from the
standard update in that they are not optionally installable at the
customer's discretion.

      The second type to be described is the packaging update.  Since
each problem that is corrected will potentially result in a unique
fix, there is the potential to flood the users with hundreds of
fixes.  When these fixes are grouped into preventative maintenance
packages, there is no way of identifying these packages as separate
from a...