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

Technique to Convert LAN Netview Start ASCII Database Files into a SQL Database

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

Publishing Venue

IBM

Related People

Shrader, TJ: AUTHOR

Abstract

This disclosure presents a technique by which users can follow to convert their LAN NetView Start* program data from ASCII files into a Database Manager SQL database.

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

Technique to Convert LAN Netview Start ASCII Database Files into a SQL Database

      This disclosure presents a technique by which users can follow
to convert their LAN NetView Start* program data from ASCII files
into a Database Manager SQL database.

     The LAN NetView Start product (Start) allows users to store
their networks, topologies, and workstations in either ASCII files,
managed by an internal ASCII database manager, or in a SQL database,
controlled by Database Manager (DBM), which is part of Extended
Services for OS/2*.  The two are not interchangeable.  Users cannot
save in ASCII and call up the data in SQL.  The way the data is
stored between the two may also be obscure, since there does not seem
to be a direct correlation between how data is stored by the ASCII
and SQL database managers.  With this disclosed technique, users can
convert their data from ASCII files to a DBM SQL database.

     The Start program makes use of several objects.  Network objects
are the top most in this tree of objects.  Within a network are
topologies and folders.  (Folders are treated like topology objects.)
Topologies can contain other objects as well, such as other
topologies, nodes, and transformers.

     ASCII files are stored in a single directory with an entire
network as the scope of the directory; thus different networks would
be stored in different directories.  The same is true of a DBM
database; each database represents a single network and all the
information contained in that network is stored in tables in the
database.  The ASCII and DBM databases diverge in how they store the
data.  For ASCII, the network and topology objects and their contents
are stored in separate files.  For the DBM, this information is
spread across tables.  There are fifteen SQL tables.  All topology
object information is stored in the TOPOLOGIES table, for example.

     This disclosure presents a way in which users can convert a
network and its topologies from ASCII files to a DBM database.  Each
network or topology file has a specific structure that is common to
all files of the same type.  As their filenames, network files have
their name along with a ".NET" extension.  Topologies have their
object ID number along with a ".TOP" extension as their filename.
Object IDs uniquely identify objects in a network and as such, they
are used as primary keys in each of the SQL tables.  Except for the
data lines after set names in the network file, each data row in an
ASCII file starts with the object ID of that object.  Note that
network and topology files are structured differently.  The following
is an example of an ASCII topology file:

 .NETWORKS
 .TOPOLOGIES
 18, 2, 2, "Topology", 0, 197640, "NODE****", "0006", "emlan", 1,...
 .FOLDERS
 .NODES
 150, 18, 18, 24, 0, "NODE0001", 1, 332, 8, "SERVER01", 0, 0, 16,...
 332, 18, 0, 150, 100, "NODE0001", 1, 0, 24, "SERVER01", 0, 0, 16,...
 32, 18, 18, 25, 0, "NODE0002", 1, 370...