Program Operation
DBINSTAL uses an interactive prompting sequence for initial prototyping
of the Omnidex indexes. For production operations, the input is generally
saved in separate script files for the indexing Install and the indexing
B (or Index) operations. DBINSTAL continues to prompt for additional Tables
and Columns until a '/' is specified as the table or column name. Installation
batch files must follow the prompting sequence exactly to avoid errors
during execution.
First run DBINSTAL:
osf> [/users/test]$ dbinstal orders.env
The DBINSTAL header is displayed followed by the Cmd: prompt.
Cmd:
Enter any database-level indexing options prior to beginning the installation.
To install indexes use the Install command followed
by table options and index options (on columns). The following illustrates
the DBINSTAL prompts:
- Enter a compiled Environment filespec. If the environment file suffix
is omitted, .env is assumed.
Database or Environment: /usr/disctest/orders.env
Cmd: Install
At the Cmd: prompt, enter any desired database-level options, Install
or I to begin the installation or ? or H for a list of valid commands.
Multi-Dimensional Keyword (MDK) Indexes are specified first.
- Enter a table name followed by the desired table options.
Table name? ORDERS
If the table entered is a child table, you will be prompted for a column
linking it to its parent. To index this table in its parent's domain,
enter the link column name or P=parentname.
Link Column 1: ACCT
or
Link Column 1: P=PROSPECTS
To index this table as both a child and a parent, enter $PK at the first
link column prompt and then the link column at the second prompt.
Link Column 1: $PK
Table will be indexed in its own domain
Link Column 2: P=PROSPECTS
Table will be indexed in the domain of PROSPECTS
Link Column 3: /
To index this table in its own domain and in its parent's domain, enter
the link column and then $DR.
Link Column 1: P=PROSPECTS
Table will be indexed in the domain of PROSPECTS
Link Column 2: $DR
Table will be indexed in its own domain
Link Column 3: /
To index this table in its own domain without also indexing it in its
parent's domain, enter a forward slash.
Link Column 1? /
- Enter the column name to be indexed followed by the desired indexing
options.
Column name: mycolumn;NP
To specify a composite index of multiple columns, specify a name with
the exclamation point:
Column name: CITY_STATE!
Component 1 (Column [, start, length]): City
Component 2 (Column [, start, length]): State
Component 3 (Column [, start, length]): /
- Enter an additional column or a slash to exit the current table when
all columns are specified.
Column name: /
- Enter an additional table name or a slash to exit the MDK installation.
Table name? /
Enter Aggregation/Sorted Keyword (ASK) Indexes next.
Table name? mytable
Column name: agg1!
Component 1 (Column [,start,length]): Account
Component 2 (Column [,start,length]): Trans_amount
Component 3 (Column [,start,length]): /
Column name: /
Table name: /
Proceed with installation [Y]?
Press return or enter 'Y' to install the indexes.
DBINSTAL will now create the empty index files.
Check the Status of Indexing Operations
When indexing in real time, DBINSTAL issues a status report of the tables
that have been processed, the number of keywords unloaded, and the number
of keywords loaded. When indexing in batch, the progress of the operation
is not automatically listed to the terminal.
To check the status of an indexing operation running in batch, or to
get a more detailed account than the online display, use the STATUS option.
The STATUS option causes DBINSTAL to list the progress of an indexing
operation to a file named ODXSTAT. DBINSTAL builds this file in the login
directory (or account). This file can be examined to check the status
of any INDEX or B operation being performed.
To use the STATUS option, append ;STATUS to the B command.
Cmd: B;STATUS
When the process is executing, examine ODXSTAT by using TYPE in DCL,
PRINT in MPE or more in UNIX.
Top
|