home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: InfoMgt
/
InfoMgt.zip
/
datagui1.zip
/
README.IVP
< prev
next >
Wrap
Text File
|
1994-05-13
|
7KB
|
140 lines
*********************************************************************
* DataGuide/2 Version 1.0 *
* *
* Licensed Materials - Property of IBM *
* 5622-487 *
* (C) Copyright 1994 IBM Corp. All Rights Reserved. *
*********************************************************************
Filename: README.IVP
Date: June 1994
DataGuide/2 Installation Verification Procedure (IVP) consists of
basic steps for creating/preparing a sample DataGuide/2 Information
Catalog "DGSAMPLE". This procedure is designed to help you verify
and exercise certain features and get familiar with DataGuide/2.
This README file consists of two major sections as follows:
1. Procedure to create the sample database DGSAMPLE
2. Background information for finalizing a TAG file
The first section prepares you to follow the specific instructions
in the column "Quick Install Verification for the Administrator" of
the "Installing DataGuide/2" card and Chapter 2 "Setting-up and
Starting DataGuide/2" of the "Managing DataGuide/2" publication.
After the sample Information Catalog DGSAMPLE is created/prepared
and used to explore various features of DataGuide/2, you may want
to read the second section to learn a scenario for designing a
SAMPLE.TAG file.
IVP related files are grouped as one component of 1.7MB; the created
DGSAMPLE is a DB2/2 database, requires 2.5MB. Installation of this
component is optional. After installation, IVP files reside at the
path .\DG2LIB\SAMPLE\IVP.
--Procedure to create the sample database DGSAMPLE----------------------
The following information complements the "Installing DataGuide/2"
and "Managing DataGuide/2" publications for creating/populating the
DGSAMPLE information catalog. Specific information on "Editing
SAMPLE.TAG" and on the "Loading the DB2/2 sample data" below provide
the necessary information to complete the procedure.
o Editing SAMPLE.TAG (as needed)
The provided SAMPLE.TAG contains fully-qualified file names in
many of its object instances. If your DataGuide/2 has the IVP
component installed in a path other than C:\DG2LIB\SAMPLE\IVP,
you must edit the SAMPLE.TAG file to make global changes to
specify the path which reflects your DataGuide/2 installation.
The provided SAMPLE.TAG also has defined USERID as the Sys-Admin ID
that created the database; DGSAMPLE is specified as the name of
the sample Information Catalog (a database) .see next step. If
your specific Sys-Admin ID and/or database is different, you must
edit the SAMPLE.TAG file to globally change the Sys-Admin ID
and/or database name.
The SAMPLE.TAG file also has references to PAS/2 sample data
with a path "C:\DSS\SAMPLES". If you have PAS/2 installed with
its sample data with a path other than C:\DSS, you will need
to make a global change on these references to your specific
path (e.g. E:\DSS\SAMPLE). You may want to leave these references
unchanged if you do NOT have PAS/2 sample data installed.
o Creating DB2/2 Information Catalog "DGSAMPLE"
This task creates a DB2/2 database with DataGuide/2 system tables
and binds the database with DataGuide/2. You can perform this
task via the command line or DataGuide/2 icons.
o Populating database DGSAMPLE with SAMPLE.TAG
Use the DataGuide/2 "import" function to populate DGSAMPLE with
the data contained in SAMPLE.TAG; you can perform this task via
the command line or DataGuide/2 icons/windows.
o Loading the DB2/2 sample data
Enter the following command from .\dg2lib\sample\ivp:
SAMPLOAD DGSAMPLE
SAMPLOAD uses the DB2/2 import function to load DB2/2 sample data
into DGSAMPLE.
IF DGSAMPLE is created on a DB2/2 server station, users at
DB2/2 client stations may now catalog this database and follow
examples in "Using DataGuide/2" to get familiar with browsing
and finding objects in this database.
--Background information for finalizing a TAG file----------------------
The Sundial Corporation, a ficti tious enterprise, has decided to
design/create/utilize its DataGuide/2 Information Catalog to make
easy access to their data/information. After analyzing their data/
information and the DataGuide/2-provided STARTSET.TAG (the start-set
definition file, residing at .\dg2lib\startset), they determined
the following object types are applicable to their situation:
o Because the Program Category is non-extendable for DataGuide V1.0,
while program launch was to be an important part of Sundial's
needs, they decided to use the DataGuide/2-provided "PROGRAMS"
object type as defined in the STARTSET.TAG without modification.
o A number of extracts would be utilized to extract information into
the tag format for later import into their DataGuide/2 database.
Sundial wanted to utilize extractors provided by DataGuide/2 to
extract the TABLE and COLUMN information from DB2 databases;
therefore, they elected to use the Table Object Type and Column
Object Type as provided in the DataGuide/2 STARTSET.TAG.
o Sundial preferred to write new extract utilities to access QUERY,
REPORT, CHART, and IMAGE information from a number of diverse
sources; therefore, they elected to create four new (user-defined)
object types that were tailored to their needs.
They decided to base these object types on the ANALYSIS (QUERY,
REPORT and CHART) and IMAGE object types from DataGuide/2
STARTSET.TAG with a reduced set of properties and descriptive
information based on their needs.
The ANALYSIS, IMAGE, and COMPLETED REPORT object types defined
in DataGuide/2 STARTSET.TAG would not be used.
o Sundial also decided to create user-defined object types to carry
GROUPING, CONTACT, DICTIONARY, and SUPPORT category information.
These object types would be defined based on those defined in the
DataGuide/2 STARTSET.TAG with a reduced set of properties and
simplified descriptive information.
The SAMPLE.TAG, as the result of their decisions, became the initial
set of data to be imported into the DataGuide/2 information catalog.
--End of README.IVP-----------------------------------------------------