INTEGRATE DATABASE ──────┐
 ┌────<───────────────────┘
 │
 ├─> 
P
A
T
H
N
A
M
E ─> path-name-1 ─┬─> 
A
L
T
E
R 
F
I
L
E
S ─────┬─────────┬─> typebox (;)
 │                            │                    │         │
 │                            └─> 
A
L
T
E
R 
D
I
C
T
I
O
N
A
R
Y ┘         │
 │                                                           │
 └─> 
F
I
L
E
N
A
M
E ─> file-name ─> 
C
R
E
A
T
E 
P
A
T
H
N
A
M
E ─> path-name-2 ┘

Additional information available:

ALTER_DICTIONARYALTER_FILESCREATE_PATHNAME

More Information

 Makes definitions in a database and in a data dictionary
 correspond by changing definitions in either the database or the
 dictionary.

 The INTEGRATE statement can also create database definitions in
 the data dictionary by copying from a database file to a
 specified data dictionary.

 NOTE:  Using the ALTER FILES clause may destroy data associated
 with definitions in your database file if those definitions are
 not defined in your data dictionary.  In this situation, you
 will lose real data.  Note, also, that altering the dictionary
 definitions with the ALTER DICTIONARY clause may affect other
 dictionary entities that refer to these definitions.  For these
 reasons, use these clauses with caution.

 Alters the database definitions in the dictionary so they are
 the same as those in the database.  This is useful if data
 dictionary definitions no longer match the definitions in the
 database file.  Note, though, that altering the database
 definitions may affect other applications that refer to these
 definitions.

 The dictionary must already exist and may contain definitions.

 Path-name-1 is the data dictionary path name for the dictionary
 database that SQL alters using the definitions in the database
 file as a source.  You can specify either a full data dictionary
 path name or a relative path name.

 Alters any table and domain definitions created with the CREATE
 TABLE FROM statement or the CREATE DOMAIN FROM statement so they
 match their sources in the data dictionary.  INTEGRATE...ALTER
 FILES has no effect on definitions not created with the FROM
 clause.

 This is useful if the database file definitions no longer match
 the definitions in the data dictionary.

 Path-name-1 is the data dictionary path name for the dictionary
 database that is the source for altering the definitions in the
 database.  You can specify either a full data dictionary path
 name or a relative data dictionary path name.

 Note:  Using the ALTER FILES clause may destroy data associated
 with definitions in your database file if those definitions are
 not defined in your data dictionary.  In this situation, you
 will lose real data.  For this reason, use the ALTER FILES
 clause with caution.

 Stores existing database system file definitions in the data
 dictionary for the first time.  Use the CREATE PATHNAME clause
 if you did not specify PATHNAME or the data dictionary was not
 installed when you created the database.

 If you use the CREATE PATHNAME clause, the data dictionary
 database node specified in the path name must not exist.  If
 older data dictionary definitions do exist with the path name
 you are specifying, specify a different data dictionary path
 name, placing the new database definitions elsewhere.

 The file-name clause is the full or partial VMS file
 specification that specifies the source of the database
 definitions.  You do not need to specify the VMS file extension.
 The database system automatically uses the database root file
 ending with the .RDB file extension.

 Path-name-2 is the data dictionary path name for the data
 dictionary where the INTEGRATE statement creates the database
 definitions (using the database system files as the source).
 You can specify either a full data dictionary path name or a
 relative data dictionary path name.  Note that this must be the
 path name, not the name of the database itself.