Browse Prior Art Database

Migration File Strategy for IBM LAN NetView Start and Other Network Configuration Programs

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

Publishing Venue

IBM

Related People

Bunce, JL: AUTHOR [+3]

Abstract

Disclosed is a strategy for handling open migration files in the IBM LAN NetView* Start (Start) product or in other network configuration/management products. Start provides users with the ability to represent and configure nodes within a network. Users can drag nodes from a template folder into a topology container object to create the workstation nodes representing their network, or they can take advantage of the product's migration feature to bring their existing nodes into the Start network. In Start version 1.1, users could run a discovery program (OCUNODE.EXE) on their target machines and generate a migration file containing information on the products that were installed on the machine, such as DFT and non-DFT 3270 emulator sessions, and LAN Server parameters. For Start 1.

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

Migration File Strategy for IBM LAN NetView Start and Other Network
Configuration Programs

      Disclosed is a strategy for handling open migration files in
the IBM LAN NetView* Start (Start) product or in other network
configuration/management products.  Start provides users with the
ability to represent and configure nodes within a network.  Users can
drag nodes from a template folder into a topology container object to
create the workstation nodes representing their network, or they can
take advantage of the product's migration feature to bring their
existing nodes into the Start network.  In Start version 1.1, users
could run a discovery program (OCUNODE.EXE) on their target machines
and generate a migration file containing information on the products
that were installed on the machine, such as DFT and non-DFT 3270
emulator sessions, and LAN Server parameters.  For Start 1.1, the
discovery program only allowed a limited set of information to be
migrated, because of the limitations of OCUNODE.EXE and the closed
support of products in Start.  This disclosure presents a solution
for using migration files in an application (whether Start or another
network configuration program) that supports open definitions of
products.

      In keeping the migration file format open, the network
configuration program would need to keep the format familiar to users
who are familiar with response files.  (Response files are part of
the Configuration, Installation, and Distribution (CID) strategy.

They allow users to define values for parameters in an ASCII file for
use in the installation and configuration process.)  This can be
accomplished by establishing the following rules:

o   Lines cannot be more than 255 characters.

o   Comments lines will have an asterisk or semicolon as their first
    non-white character.  White characters are defined as spaces and
    tabs.

o   Keyword and value assignments will conform many of the same rules
    set forth when including them in response files.  They cannot
    begin with a period.  Values cannot span multiple lines, and
    lists of keywords and values are not supported.

      The network configuration program could allow objects to
contain other objects.  For example, a node object can contain an
adapter object which can contain a protocol object.  A node object
can also contain an application object, like Communications Manager/2
1.0, which can contain an application support object, like a 3270
session definition.  The migration file format must be flexible
enough to allow users the freedom to represent these relationships.
Thus, objects in the file must be able to specify their parent.

      The following is a sample template migration file template for
use with the network configuration program.  Variables that the user
would need to complete are in all lower case.

 ; Comment line 1
 .BEGIN JFNode jfSymbolName nodename {NEW | CHANGE | DELETE}

 .CLASS ...