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

Program Fix Delivery Customization by Customer Usage Profile

IP.com Disclosure Number: IPCOM000106171D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 4 page(s) / 115K

Publishing Venue

IBM

Related People

Gintowt, RT: AUTHOR [+6]

Abstract

Described is a method for tracking the actual use of a program package with more than one function and enabling a service provider to supply only those software updates (also referred to as software fixes) to those program functions that are actually being used by the customer computer. The invention is a product usage table that tracks usage of software products and features within products using program exits imbedded in critical but low usage modules (smallest replaceable unit) of a distinct feature of a program product.

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

Program Fix Delivery Customization by Customer Usage Profile

      Described is a method for tracking the actual use of a program
package with more than one function and enabling a service provider
to supply only those software updates (also referred to as software
fixes) to those program functions that are actually being used by the
customer computer.  The invention is a product usage table that
tracks usage of software products and features within products using
program exits imbedded in critical but low usage modules (smallest
replaceable unit) of a distinct feature of a program product.

      When an "order update" command is issued to request software
fixes (manually by the user or automatically by the system or
application program) the request will be combined with the product
usage table and transmitted to an intermediate server system.  The
server system would accept the order request and determine, based on
the data passed from the originating system, which software fixes
must be delivered.  A request would be issued to the fix distribution
system for the necessary fixes.  These software fixes would be
combined with information from data bases existing on the server
system into a customized fix package and returned to the originating
system.  The fix package is then applied using the normal fix
application mechanism.

      The Product Usage Table would be created by the system using
some or all of the following; Load on Demand data, Product - Load -
Option - Component data, Usage based pricing data, vital product
data.

      Fig. 1 describes the transmission of the product usage table to
request delivery of software fixes or program updates to the
customer.

      The product usage table is maintained by traps inserted in
certain modules defined by each product.  Each product is divided
into "features" that the customer understands as separate functions,
even if they are all part of the base product.  As an example, data
communications may be a "feature" that a customer may or may not use,
but it is part of the base microcode product.  The trap is inserted
in a low usage module that must be executed to use the feature.  Low
usage m...