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

Parameter File Parser and Builder

IP.com Disclosure Number: IPCOM000116126D
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 4 page(s) / 78K

Publishing Venue

IBM

Related People

Newell, PN: AUTHOR [+2]

Abstract

A parameter file parse and build routine which parses parameter configuration file information for an earlier realease of a product and rebuilds the paramater files with updates and new parameter information for a new product release is disclosed.

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

Parameter File Parser and Builder

      A parameter file parse and build routine which parses parameter
configuration file information for an earlier realease of a product
and rebuilds the paramater files with updates and new parameter
information for a new product release is disclosed.

      The NetView Installation and Administration Facililty/2
(NIAF/2) provides for the migration of configuration settings of
previous releases of NetView.

      At a high level, NIAF/2 operates by using either the default
NetView parameters shipped with the product or parameters previously
defined by the customer.  These parameters are downloaded via a
Communications Manager emulator session, parsed into individual data
entities by the database application, and stored in Database Manager.
This is illustrated through the set of flows 16,14,12,9,8, in Fig. 1.
When a request to update the parameter information is made using the
Install process dialogs the order is essentially reversed.  The
individual data entities are pulled from Database Manager and are
plugged into predefined templates to create the actual parameters.
These parameters are then sent to the host via the Communications
Manager send process.  They are placed into the appropriate datasets
that have been defined by the customer in the profile.  This is
illustrated through the set of flows 6,4,7,10,11,13,15 in Fig. 1.
  (1) User selects Current NetView Configuration for priming NIAF2 |
       and is presented with a dialog box which asks for the datasets
to
       get the configuration information from.  This is then passed
on to
       the Database API using data flow 1.                          |
  (2) The Database API records the choice in the log and invokes   |
       Installation Services.  The Database API stores the request
into
    ...