EXPORT SCHEMA ─┬─> 
A
U
T
H
O
R
I
Z
A
T
I
O
N auth-id ─┬─┐
                ├─> 
F
I
L
E
N
A
M
E file-spec ────┤ │
                └─> 
P
A
T
H
N
A
M
E path-name ────┘ │
 ┌───────────────────────────────────────────┘
 └─> 
I
N
T
O file-spec ─┬───────────────────────────┬─> typebox (;)
                     └─ 
W
I
T
H ─┬─> 
E
X
T
E
N
S
I
O
N
S ───┬┘
                              └─> 
N
O
E
X
T
E
N
S
I
O
N
S ─┘

Additional information available:

AUTHORIZATIONFILENAMEPATHNAMEWITH_EXTENSIONS

INTO file-specMore Information

 Specifies the source database files to be compressed and written to
 an .RBR file.

 AUTHORIZATION specifies the authorization identifier of an
 already-declared schema.  If the schema you want to export is already
 declared, specifying AUTHORIZATION avoids the overhead of a second
 attachment to the schema and the locking that attachment entails.

 Specifies the source database files to be compressed and written to
 an .RBR file.

 FILENAME and PATHNAME both identify the database root file associated
 with the schema.  If you specify a data dictionary path name, the
 pathname indirectly specifies the root file.  EXPORT does not change
 any definitions in the data dictionary, so there is no difference in
 the effect of the PATHNAME and FILENAME arguments.

 Specifies the name for the .RBR file EXPORT creates.  Optionally, the
 file specification can include a device and directory specification.

 Makes a copy of a database in an intermediate, compressed form.  Use
 the IMPORT statement to rebuild an Rdb/VMS database from the
 compressed .RBR file created by EXPORT.

 You use EXPORT with IMPORT to make changes to Rdb/VMS databases that
 cannot be made any other way.  EXPORT unloads a database to an .RBR
 file.  IMPORT recreates the database with changes not allowed through
 ALTER statements:

  o  Convert a single-file database to multifile and vice versa

  o  Change root file parameters you cannot change with ALTER SCHEMA:

  o  Change storage area parameters you cannot change with ALTER
     SCHEMA

  o  Reload tables with existing rows to take advantage of
     newly-created hashed indexes

  o  Reload tables to take advantage of new or changed storage maps

  o  Convert a database from another DSRI-compliant implementation to
     an Rdb/VMS database.  For instance, the Rdb/ELN EBRP utility
     creates an .RBR file you can use with the IMPORT statement to
     create an Rdb/VMS database.

 Specifies the source database files to be compressed and written to
 an .RBR file.

 FILENAME and PATHNAME both identify the database root file associated
 with the schema.  If you specify a data dictionary path name, the
 pathname indirectly specifies the root file.  EXPORT does not change
 any definitions in the data dictionary, so there is no difference in
 the effect of the PATHNAME and FILENAME arguments.

 Specifies whether the .RBR file created by the EXPORT statement
 includes extensions that are compatible only with Rdb/VMS Version 3.0
 or later database systems.  WITH EXTENSIONS is the default.

 The only time you need to specify WITH NOEXTENSIONS is if the
 database system through which you will rebuild the .RBR file into a
 database is:

  o  Rdb/VMS Version 2.3 or earlier

  o  Any verson of Rdb/ELN