The initialize statement causes DMUTILITY to initialize all database files. If you also set the ZIP compiler control option, the WFL deck used to compile your database initiates DMUTILITY automatically. If you reset the ZIP compiler control option, you must initiate DMUTILITY manually. The initialize statement should be used only when creating a new database. It should not be present when the description of an existing database is being modified.
If you compile DASDL without using the UPDATE option and an initialize statement, DASDL responds as if you were compiling a new database and creates the following files:
-
A new description file
-
A new control file (if the DMCONTROL compiler control option is set)
-
New tailored software, for example, the DMSUPPORT library (if the ZIP compiler control option is set)
The database files are untouched. For more information about the UPDATE option, refer to UPDATE Option in Using the MODEL and UPDATE Options.
DMUTILITY is not initiated automatically if
-
The ZIP compiler control option is set.
-
The INITIALIZE statement is included in the DASDL symbol.
-
The BACKUPKEYSET is not reset.
-
DASDL contains at least one structure with STRENCRYPT set; the key set for the database must be backed up before the database is opened.
It is not necessary to initialize large object (LOB) files. However, if you do initialize a LOB file, use the AX command if you want to override the current initialized file.
The following diagram illustrates the syntax for initializing your database:
<initialize statement>
── INITIALIZE ─────────────────────────────────────────────────────────┤
Example
Include the following initialize statement to initialize all database files:
INITIALIZE; D DATA SET ( K NUMBER (4); ); S SET OF D KEY K;