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

Implementing Scalable Softcopy Documentation

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

Publishing Venue

IBM

Related People

Birdsall, IP: AUTHOR [+2]

Abstract

Disclosed is a method for enabling users to selectively install individual or groups of InfoExplorer* softcopy databases. The ability to selectively install databases allows users to efficiently manage the amount of Direct Access Storage Device (DASD) required for softcopy by reducing a two-step process of installing all databases and removing selected ones to a one-step process of installing selected databases. The method involves the following activities.

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

Implementing Scalable Softcopy Documentation

      Disclosed is a method for enabling users to selectively install
individual or groups of InfoExplorer* softcopy databases.  The
ability to selectively install databases allows users to efficiently
manage the amount of Direct Access Storage Device (DASD) required for
softcopy by reducing a two-step process of installing all databases
and removing selected ones to a one-step process of installing
selected databases.  The method involves the following activities.

      The first activity requires the development group who has
responsibility for creating and packaging an InfoExplorer library to
identify the structure of the softcopy databases by product and user
groupings.  An example would be to take an information library that
supports a graphics Licensed Program Product (LPP) and a
communications LPP and to identify four groupings:  graphics end
user; graphics application developer; communications end user; and
communications application developer.

      The second activity is to review each softcopy database,
identify which grouping it belongs to, and package the identified
softcopy databases within the appropriate groupings.

      The third activity is to modify the install code to allow
installation of either individual softcopy databases or individual
groups of softcopy databases (as identified in the second activity)
based upon user selection during the installation process.

      A further re...