PARSEDB

To start PARSEDB, type the following statement from a command prompt:

 PARSEDB [path] DBTAGS.DAT [path] text_database [path] binary_database

where:

The text_database file is the main input file for PARSEDB that has to be created.

For example, type the following statement to create a new database named MYDATA.DAT:

PARSEDB E:\OS2\INSTALL\DBTAGS.DAT MYDATA.TXT MYDATA.DAT

Note that you must specify a file name for the binary database file to prevent the PARSEDB utility program from overwriting the default database file DATABASE.DAT.

When creating the text_database file, each program must have the following migration information:

NAME

Name of the file that runs the program.

Program object name that appears below the icon.

DOS, Windows or OS/2

File name associated with the file name specified in the Name field. Use this file name to uniquely identify the program.

Directory that the program is installed into.

ASSOC_FILE and DEF_DIR can have NULL values; NULL values must be included when defining the program if specific values for these fields cannot be provided.

When creating MYDATA.TXT, group the settings for a given program on consecutive lines. Use blank lines to mark the end of a program's settings. Begin non-blank lines with a token. The tag file DBTAGS.DAT defines valid token settings, limits, and default values for various DOS properties.

Here is the listing of DBTAGS.DAT: DBTAGS.DAT

The layout of each line in DBTAGS.DAT is as follows:

INDEX VALUE TYPE (optional comments)

where:

INDEX

Is a sequence number

Is the name of the setting

Is the type of the value.

TYPE is one of the following:

NOP

Comments; any line with this type is ignored

A string value

An integer value

Boolean, with value of ON or OFF

Program type, either DOS, OS/2, or Windows.

A multi-line string with component lines on individual lines in the text_database file.

Using these types, various settings for programs can be defined. Do not edit DBTAGS.DAT or create a new one; the tag file is available only as a reference when creating the MYDATA.TXT file.

PARSEDB checks the validity of all entries in MYDATA.TXT and compares them to the settings definitions in DBTAGS.DAT. If all entries are valid, PARSEDB creates a binary database named MYDATA.DAT.

Errors in the text file will cause PARSEDB to exit and display a message:

A message about an invalid setting indicates the use of a setting not found in DBTAGS.DAT. The message should include a line number and the name of the input file.

A message that an entry has missing parameters indicates the absence of the minimum settings for the entry.

PARSEDB does not check for duplicate entries in the input text file, nor does it require settings to be in any particular order. It is also not case sensitive, that is, "Off" is treated the same as "OFF".

We recommend that a copy of the input text file (DATABASE.TXT) for the default migration database file (DATABASE.DAT) be made and used as the template for your own input file. A sample input text file is listed below.

User Definitions for other Applications