Browse Prior Art Database

Strategy for Supporting CM/2 and DB/2 with IBM LAN NetView Start 1.1

IP.com Disclosure Number: IPCOM000112207D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 4 page(s) / 192K

Publishing Venue

IBM

Related People

Bunce, JL: AUTHOR [+3]

Abstract

Disclosed is a two pronged strategy to allow the user to incorporate CM/2 and DB/2 into their installation and configuration sequence using IBM LAN NetView* Start. The IBM LAN NetView Start 1.1 (Start) product currently supports the configuration keywords for the Communications Manager and Database Manager components of the Extended Services product. (Users can add installation parameters through the use of supplemental response files.) With this version of Start, the user does not have an efficient or convenient way of adding the new Communications Manager/2 (CM/2) and Database 2*/2 (DB2/2) products to their workstations.

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

Strategy for Supporting CM/2 and DB/2 with IBM LAN NetView Start 1.1

      Disclosed is a two pronged strategy to allow the user to
incorporate CM/2 and DB/2 into their installation and configuration
sequence using IBM LAN NetView* Start.  The IBM LAN NetView Start 1.1
(Start) product currently supports the configuration keywords for the
Communications Manager and Database Manager components of the
Extended Services product.  (Users can add installation parameters
through the use of supplemental response files.)  With this version
of Start, the user does not have an efficient or convenient way of
adding the new Communications Manager/2 (CM/2) and Database 2*/2
(DB2/2) products to their workstations.

      To support these products with Start 1.1, this disclosure
requires the implementation of two applet programs.  The first primes
the user's ASCII or SQL Start network database with the application
representations for CM/2 and DB2/2.  The second modifies the
generated LAN CID Utility (LCU) command files to remove references to

Extended Services, insure that CM/2 and DB/2 are installed, and use
the appropriate response file and code server aliases.

      PRIMING START - The first part of this strategy entails the
implementation of a program or applet (call it OCUADD1) that would
create templates of the CM/2 and DB2/2 applications objects in the
Start database.  These new application template objects would be
placed in the apps folder.  The applet would work on a user's ASCII
or SQL database differently.

      Whatever the database type, after OCUADD1 processed its command
line parameters, the applet would first ask the user for the
installation parameter values for the CM/2 and DB2/2 installation
programs.  This would give the user the chance to customize their
product parameters without having to open and modify the notebook
application object in Start.  Users could defer to default parameter
values as well.

      After this, the OCUADD1 applet would diverge in how it added
the products to the ASCII or SQL databases.

With an ASCII database, OCUADD1 would:

1.  Find the network data file.

2.  Backup the network data file.

3.  Find the newobjectid value from the networks data file, update
    this value by two, and store it away in the new network data
    file.  (The newobjectid value indicates the next unique objectid
    that can be assigned to an object in Start.)

4.  Find the applications topology file by searching through each
    topology file until locating it.

5.  Backup the application topology data file.

6.  Insert two new rows under the applications table entry in the
    applications topology file.  The first row represents specific
    values for CM/2, the second for DB2/2.  The contents of the row
    would be a combination of applet derived, defaulted, and
    user-specified values.

With a SQL database OCUADD1 would:

1.  Find the newobjectid value from the network...