Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method to Reduce the Size or Number of FIX Media for Periodic FIX Updates

IP.com Disclosure Number: IPCOM000113565D
Original Publication Date: 1994-Sep-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 50K

Publishing Venue

IBM

Related People

Fisher, ME: AUTHOR [+2]

Abstract

For the problem of distributing periodic fixes for many software features to many customers, a method is disclosed that automatically determines what features customers are using so that the size and number of the fix media can be reduced.

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

Method to Reduce the Size or Number of FIX Media for Periodic FIX
Updates

      For the problem of distributing periodic fixes for many
software features to many customers, a method is disclosed that
automatically determines what features customers are using so that
the size and number of the fix media can be reduced.

      This invention describes how a company that supports a number
of software features on many different customer machines may
automatically collect data on what features its customers are
actually using.  (As used here, "features" can mean programs, tasks
or functional entities that are individually loaded or activated.)
This information may then be used as follows:
  o  To tailor periodic fix media (such as tapes) for customers and
so
     potentially reduce the number and size of media required.
  o  To determine which of the many features that are installed on
     customers' machines are actually being used and how often.

The invention is described as follows:

      (Note: It is assumed that software exists in the customer's
machine, provided by the software issuer, that loads or activates
individual features.  This is called the "loader" software.)
  1.  The "loader" software must create a "system feature use table".
      This table is a persistent object, such as a file, that must
      never be destroyed and that is periodically saved.  Each time a
      feature is loaded or activated, the loader will in...