Browse Prior Art Database

Packaging Software Product Fixes

IP.com Disclosure Number: IPCOM000122774D
Original Publication Date: 1998-Jan-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 6 page(s) / 160K

Publishing Venue

IBM

Related People

Ascone, A: AUTHOR [+5]

Abstract

Once a software product has been delivered, that is in General Availability (GA), it may be replaced (or refreshed) with a more recent version or release containing new fixes but also new functionalities.

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

Packaging Software Product Fixes

      Once a software product has been delivered, that is in General
Availability (GA), it may be replaced (or refreshed) with a more
recent version or release containing new fixes but also new
functionalities.

      It is customary to produce a fixback, such as a Corrective
Service Diskette (CSD) which contains all new modules (executable
file, DLL file, etc.) released to solve problems discovered after GA
or REFRESH.

      For example, for the IBM product TME 10 NetFinity Server 4.0,
the fixpack includes the modules nvdm.exe and nvdmcli.dll.  Once
these modules are installed on a workstation where the GA of the
product has  been previously installed, the problem that "nvdm.exe
traps after installation" will never occur.

      The FIXPACK can thus be considered as a subset of modules for
the original product.  For this reason the FIXPACK can be applied
only on top of the GA or REFRESH code, so it is available only for a
customer that already has the product.

      Usually customers are informed of the availability of a fixpack
via Internet, from where it may be downloaded.

      The procedure typically followed to produce a fixpack is to
compare all files of GA code (or REFRESH code) with the "new" product
developed.  The comparison is based on the timestamps of modules.
The files included in the FIXPACK are all files with the timestamps
changed.  Another element to be considered is the existence of new
file (not present in the GA or REFRESH code) that must be added to
the FIXPACK.

      It is laborious to do this manually because of the number of
files normally present in a product and the possibility of error is
high.

      In addition the resulting fixpack is often too large to be
readily downloaded from Internet.

      The described procedure automatically collates a fixpack
containing all the fixes delivered after GA or REFRESH date.  First,
it checks if a file of the FIXPACK is present also in the GA or
REFRESH code.

      If not, it inserts the file into the fixpack.  If a file is
present the procedure checks the timestamps of the files:

      If the timestamps is different the procedure places the most
recent file in the fixpack.  At the end of this phase, the procedure
compresses the fixpack using an existing compression algori...