The RDO IMPORT statement replaces the RDO RESTORE statement.

 The IMPORT statement restructures an intermediate (RBR) file to a
 database (RDB) file according to the parameters you specify.  An
 EXPORT statement translates the definitions and data in a database
 into an intermediate form in a special type of RMS sequential file.
 The IMPORT statement reads the records in this file and uses them to
 create an Rdb/VMS database.

Additional information available:

MoreFormatExamples

 Use the EXPORT and IMPORT statements to:

  o  Restructure a Rdb/VMS single-file database into a multifile
     database
  o  Restructure a multifile database
  o  Migrate a database from one DSRI-compliant database management
     system to another
  o  Create a version-independent copy of the database for archiving
     purposes
  o  Change database and storage area characteristics that you cannot
     change with the CHANGE DATABASE statement


 The IMPORT and EXPORT statements are not intended for regular backups
 of the database.  For regular backups and restorations of Rdb/VMS
 databases, use the RMU/BACKUP and RMU/RESTORE commands.

 The IMPORT operation leaves you attached to the database, with a
 database handle equal to the name of the database.

 IMPORT ───> interchange-file-spec ───> typebox (I)typebox (N)typebox (T)typebox (O) ───> database-file-spec ──┐
 ┌──────────────────────────────────<──────────────────────────────────┘
 └─┬─┬──────────────────────>────────────────────┬──┬─> 
E
N
D 
I
M
P
O
R
T ──> .
   │ ├─> invoke-options ─────────────────────────┤  │
   │ ├─> db-wide-options ────────────────────────┤  │
   │ ├─> storage-area-options ───────────────────┤  │
   │ ├─> import-options ─────────────────────────┤  │
   │ └─> metadata-options ───────────────────────┘  │
   └──────────────────────────<─────────────────────┘

Additional information available:

interchange-file-specdatabase-file-specinvoke-optionsdb-wide-options
storage-area-optionsimport-optionsmetadata-options

 The name of the interchange file that IMPORT uses as a source to
 create the new database.  Use either a full or partial file
 specification or a logical name.  If you use a simple file name,
 Rdb/VMS looks for the interchange file in the current default
 directory.  You must specify a file that was created by the Rdb/VMS
 IMPORT statement or by the Rdb/ELN EBRP utility.  If you do not
 specify a file type, Rdb/VMS uses the default file type, RBR.

 The name of the Rdb/VMS database file you want to create from the
 interchange file.  Use either a full or partial file specification or
 a logical name.  If you use a simple file name, Rdb/VMS creates the
 database in the current default directory.  If you do not specify a
 file type, Rdb/VMS uses the default file type, RDB.

 invoke-options =

 ──┬───────────────────────────>──────────────────┬─────────────────>
   ├─────> 
D
B
H
A
N
D
L
E typebox (I)typebox (S) ───────> db-handle ───────┤
   └─────> 
D
B
K
E
Y 
S
C
O
P
E typebox (I)typebox (S) ──┬──> 
C
O
M
M
I
T ───┬──────┘
                            └──> 
F
I
N
I
S
H ───┘

Additional information available:

COMMITFINISH

 During the session of the user who entered IMPORT, specifies that the
 database key of each record used is guaranteed not to change during
 each transaction this user may execute.

 During the session of this user who entered IMPORT, specifies that
 the database key of each record used is guaranteed not to change
 until this user ends the RDO session or executes a FINISH statement.

 These options are the same database wide options that are available
 with the DEFINE DATABASE statement.

 db-wide-options =

 ─┬─┬──────────────────────────>─────────────────────────────┬─┬──>
  │ ├─> 
I
N ──────> path-name ────────────────────────────────┤ │
  │ ├─> 
D
E
S
C
R
I
P
T
I
O
N typebox (I)typebox (S) ───────> typebox (/)typebox (*) text */ ──────────────────┤ │
  │ ├─> 
N
U
M
B
E
R typebox (O)F 
U
S
E
R
S typebox (I)typebox (S) ──> number-users ─────────────────┤ │
  │ ├─> 
N
U
M
B
E
R typebox (O)F 
B
U
F
F
E
R
S typebox (I)typebox (S) ─────> number-buffers ──────────┤ │
  │ ├─> 
N
U
M
B
E
R typebox (O)F 
V
A
X
C
L
U
S
T
E
R 
N
O
D
E
S typebox (I)typebox (S) ──> number-nodes ──────┤ │
  │ ├─> 
N
U
M
B
E
R typebox (O)F 
R
E
C
O
V
E
R
Y 
B
U
F
F
E
R
S typebox (I)typebox (S) ───> recovery-buffers ─┤ │
  │ ├─> 
B
U
F
F
E
R 
S
I
Z
E typebox (I)typebox (S) ─────> buffer-blocks ──> 
B
L
O
C
K
S──────┤ │
  │ ├─> 
A
D
J
U
S
T
A
B
L
E 
L
O
C
K 
G
R
A
N
U
L
A
R
I
T
Y typebox (I)typebox (S) ─┬───> 
E
N
A
B
L
E
D ───┬───┤ │
  │ │                                   └───> 
D
I
S
A
B
L
E
D ──┘   │ │
  │ ├─> 
S
N
A
P
S
H
O
T typebox (I)typebox (S) ────┬─────> 
E
N
A
B
L
E
D ─┬─>  
I
M
M
E
D
I
A
T
E──┬─┬─┤ │
  │ │                   │                └─>  
D
E
F
E
R
R
E
D ──┘ │ │ │
  │ │                   └─────> 
D
I
S
A
B
L
E
D ───────────>──────┘ │ │
  │ └─> 
D
I
C
T
I
O
N
A
R
Y typebox (I)typebox (S) ───┬───> 
R
E
Q
U
I
R
E
D ───────┬─────────────┘ │
  │                      └───> 
N
O
T 
R
E
Q
U
I
R
E
D ───┘               │
  └───────────────────────────────<────────────────────────────┘

Additional information available:

ENABLED-IMMEDIATEENABLED-DEFERREDDISABLEDADJUSTABLE_LOCK
DICTIONARY

path-namenumber-buffersnumber-usersbuffer-blocksnumber-nodes
recovery-buffers

 The data dictionary path name for the dictionary entity where the
 database definition is stored.  Use this qualifier to store the data
 dictionary definitions for the database in a data dictionary
 directory other than the default directory.

 The number of buffers Rdb/VMS allocates per process using this
 database.  Specify an unsigned integer greater than zero.  The
 default is 20 buffers.

 The maximum number of users allowed to access the database at one
 time.  The default is 50 users.

 The number of blocks Rdb/VMS allocates per buffer.  Specify an
 unsigned integer greater than zero.  If you do not specify this
 parameter, Rdb/VMS uses a buffer size that is three times the PAGE
 SIZE value.

 Specifies that READ_WRITE transactions write copies of records to the
 snapshot file before those records are modified, regardless of
 whether a READ_ONLY transaction is active.  The default is SNAPSHOT
 IS ENABLED IMMEDIATE.

 You enable snapshot writing to all snapshot files for all storage
 areas when you specify the SNAPSHOT IS ENABLED clause.

 Specifies that READ_WRITE transactions not write copies of records
 they modify to the snapshot file unless a READ_ONLY transaction is
 active.  READ_ONLY transactions that attempt to start after an active
 READ_WRITE transaction begins must wait for all active READ_WRITE
 users to complete their transactions.

 You enable snapshot writing to all snapshot files for all storage
 areas when you specify the SNAPSHOT IS ENABLED clause.

 Disables snapshot transactions.  If you use the SNAPSHOT IS DISABLED
 clause to disable snapshots on a multifile database, writing to all
 snapshot files for all storage areas is disabled.

 Sets the upper limit on the maximum number of VAXcluster nodes from
 which users can access the shared database.  The default is 16.  The
 range is 1 to 64 nodes.

 The number of database buffers used during the automatic recovery
 process that is initiated after a system or process failure.  The
 default is 20 buffers.

 Specifies whether adjustable locking granularity is enabled or
 disabled.  The default is ENABLED.

 Determines whether the database must be invoked by path name for data
 definition changes to occur.  If you specify the DICTIONARY IS
 REQUIRED option, the database must be invoked by path name to change
 metadata and the data dictionary will be maintained.  If you specify
 the DICTIONARY IS NOT REQUIRED option, the database can be invoked by
 either file name or path name to change metadata.  The default is
 DICTIONARY IS NOT REQUIRED.

 These options are the same storage-area-options that are available
 with the DEFINE DATABASE statement.

 storage-area-options =

 ─┬┬──────────────────────────>─────────────────────────────────┬─┬──>
  │├─> 
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ───> number-pages ────> ──────── typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ────┤ │
  │├─> 
P
A
G
E 
S
I
Z
E typebox (I)typebox (S) ────> page-blocks ─────> ──────── typebox (B)typebox (L)typebox (O)typebox (C)typebox (K)typebox (S) ───┤ │
  │├─> 
P
A
G
E 
F
O
R
M
A
T typebox (I)typebox (S) ──┬────> 
U
N
I
F
O
R
M ────┬────────────────────┤ │
  ││                    └────> 
M
I
X
E
D ──────┘                    │ │
  │├─> 
T
H
R
E
S
H
O
L
D
S typebox (A)typebox (R)typebox (E) ─> (─> val1─┬─────────────────────┬───> )─┤ │
  ││                              └─> ,val2 ─┬────────┬─┘       │ │
  ││                                         └>,val3 ─┘         │ │
  │├─> 
I
N
T
E
R
V
A
L typebox (I)typebox (S) ───────> number-data-pages ──────────────────┤ │
  │├─> 
E
X
T
E
N
T typebox (I)typebox (S) ────┬──> extent-pages ────> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ───┬─────────┤ │
  ││                 └──> (extension-options)─────────┘         │ │
  │├─> 
S
N
A
P
S
H
O
T
F
I
L
E
N
A
M
E 
I
S ────> file-spec ────────────────────┤ │
  │├─> 
S
N
A
P
S
H
O
T 
A
L
L
O
C
A
T
I
O
N typebox (I)typebox (S) ───> snp-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ────────┤ │
  │└─> 
S
N
A
P
S
H
O
T 
E
X
T
E
N
T typebox (I)typebox (S) ─┬─> extent-pages ────> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S) ─┬──────┘ │
  │                        └─> (extension-options) ──────┘        │
  └────────────<─────────────────────────────────────<────────────┘

Additional information available:

PAGE_FORMATTHRESHOLDS

number-pagespage-blocksnumber-data-pagesfile-specsnp-pages
extent-pagesextension-options

 The number of database pages allocated to the database initially.
 Rdb/VMS automatically extends the allocation to handle the loading of
 data and subsequent expansion.  The default is 400 pages.

 The size in blocks of each database page.  Page size is allocated in
 512-byte blocks.  The default is two blocks (1024 bytes).  If your
 largest record is larger than approximately 950 bytes, allocate more
 blocks per page to prevent records from being fragmented.

 Specifies whether a storage area contains uniform or mixed pages.
 You can use the PAGE FORMAT option with multifile databases only.  In
 storage areas with uniform page format, all pages in a specific
 logical area contain records from the same relation.  In storage
 areas with mixed page format, pages can hold records from different
 relations.  The default is uniform.

 Specifies one, two, or three threshold values.  The threshold values
 represent a fullness percentage on a data page and establish four
 possible ranges of guaranteed free space on the data pages.  When a
 data page reaches the percentage defined by a given threshold value,
 the SPAM entry for the data page is updated to reflect the new
 fullness percentage and its remaining free space.

 The default thresholds are 70,85, and 95 percent.  If you specify
 only one or two values, unspecified values default to 100 percent.
 You can specify the THRESHOLDS option only on a storage area for a
 multifile database.  The storage area page format must be MIXED.

 Specifies the number of data pages between SPAM pages in the physical
 storage area file, and thus the maximum of data pages each SPAM page
 will manage.  The default, and also the minimum interval, is 256 data
 pages.  The first page of each storage area is a SPAM page.  The
 interval you specify determines where subsequent SPAM pages are to be
 inserted, provided there are enough data pages in the storage file to
 require more SPAM pages.

 You can specify the INTERVAL option only on a storage area for a
 multifile database.  The storage area page format must be MIXED.

 Provides a separate file specification for the snapshot file.  Do not
 specify a file extension other than SNP to the file specification.
 You cannot specify a global default for the SNAPSHOT FILENAME.  Thus,
 in a multifile database, the SNAPSHOT FILENAME option must be within
 a DEFINE STORAGE AREA definition.

 Specifies the number of pages allocated for the snapshot file.  The
 default is 100 pages.

 Specifies the number of pages of each extent.  The default is 100
 pages.

 Specifies the MIN, MAX, and percent growth of each database file
 extent.  Enclose the parameter list in parentheses.

 extension-options =

 ───>  (   ───>  
M
I
N
I
M
U
M typebox (O)F ──> min-pages ───> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S), ─┐
              ┌────────────────────────────────────────┘
              └──> 
M
A
X
I
M
U
M typebox (O)F ──> max-pages ──> typebox (P)typebox (A)typebox (G)typebox (E)typebox (S),─┐
              ┌────────────────────────────────────────┘
              └──> 
P
E
R
C
E
N
T 
G
R
O
W
T
H typebox (I)typebox (S) ───> growth ────>   )  ───>

Additional information available:

min-pagesmax-pagesgrowth

 Specifies the minimum number of pages of each extent.  The default is
 100 pages.

 Specifies the maximum number of pages of each extent.  The default is
 10,000 pages.

 Specifies the percent growth of each extent.  The default is 20
 percent growth.

 import-options =

 ───┬─┬────────────────────>───────────────┬─────>─────┬──────>
    │ │                                    │           │
    │ ├───┬──> 
A
C
L ────┬───────────────────┤           │
    │ │   └──> 
N
O
A
C
L ──┘                   │           │
    │ ├───┬──> 
B
A
T
C
H
U
P
D
A
T
E ──────┬────────┤           │
    │ │   └──> 
N
O
B
A
T
C
H
U
P
D
A
T
E ────┘        │           │
    │ └───┬──> 
C
D
D
L
I
N
K
S ─────┬────────────┘           │
    │     └──> 
N
O
C
D
D
L
I
N
K
S ───┘                        │
    └───────────────────────<──────────────────────────┘

Additional information available:

ACL_NOACLBATCH_UPDATENOBATCH_UPDATECDD_LINKS
NOCDD_LINKS

 Determines whether the previously defined ACLs are used in the
 imported version of the database (ACL) or whether the ACLs from the
 interchange file are not used (NOACL).  The default is ACL.  The
 NOACL option overrides the access control lists specified in the
 original database and uses the system default access control lists.

 Causes the IMPORT operation to run in BATCH UPDATE mode.  This is the
 default.  No recovery-unit journaling is performed in BATCH UPDATE
 mode.

 Overrides the default and causes the IMPORT operation to run in
 EXCLUSIVE, rather than BATCH UPDATE, mode.  This provides
 recovery-unit journaling so that you can recover your database in the
 event of a failure during the IMPORT operation.

 Causes the dictionary relationships to be preserved in the imported
 database.  If you specify CDD_LINKS, the IMPORT operation attempts to
 reconnect the fields and records to the dictionary pathname entities
 they reference.  If the dictionary entity no longer exists, you will
 receive a warning message.  The default is CDD_LINKS.

 Causes the IMPORT operation to run without preserving dictionary
 relationships in the imported database.  Fields and records are not
 reconnected to the dictionary pathname entities they reference.

 Allows you to define or delete storage maps, storage areas, and
 indexes.

 When you include a metadata statement within the IMPORT statement,
 the metadata statement is NOT terminated with a period.

 metadata-options =

 ─┬─┬─────────────────────────────>────────────────────────────┬──┬──>
  │ ├─>define storage map statement ───────────────────────────┤  │
  │ ├─>delete storage map statement ───────────────────────────┤  │
  │ ├─>define-storage-area-clause ─────────────────────────────┤  │
  │ ├─>
D
E
L
E
T
E 
S
T
O
R
A
G
E 
A
R
E
A ───────────────>storage-area-name ──┤  │
  │ ├─>
S
E
G
M
E
N
T
E
D 
S
T
R
I
N
G 
S
T
O
R
A
G
E 
A
R
E
A typebox (I)typebox (S) ──>storage-area-name ──┤  │
  │ ├─>define index statement ─────────────────────────────────┤  │
  │ └─>delete index statement ─────────────────────────────────┘  │
  │                                                               │
  └──────────────────────────────<────────────────────────────────┘

Additional information available:

More

 For more detailed information about each of the statements in
 metadata-options, request HELP on the particular statement.

 Example 1

 The following example imports a database.  It also specifies the
 number of buffers and the length of each buffer in the imported
 database:


 RDO> IMPORT
 cont>  'DISK1:PERSONNEL.RBR'
 cont>   INTO 'DEPT3:NEW_PERSONNEL'
 cont>   NUMBER OF BUFFERS IS 10
 cont>   BUFFER SIZE IS 10 BLOCKS
 cont> END IMPORT.


 Example 2

 The following example imports a database from a magnetic tape:



 $ MOUNT MUA0:
 _Label:  PERS
 _Log name:
 $ RDO
 RDO> IMPORT
 cont>  'MUA0:PERSONNEL' INTO
 cont>  'DEPT3:PERSONNEL'
 cont> END IMPORT.

 This statement reads the export copy of the database from the
 magnetic tape volume labeled PERS, mounted on device MUA0:.  It
 creates a new database in DEPT3:PERSONNEL.RDB, where DEPT3 is a
 logical name for a device and directory.


 Example 3

 The following example uses the RMU/DUMP command to check the current
 value of the node count, and then uses the IMPORT statement with the
 NUMBER VAXCLUSTER NODES clause to lower the node count parameter.  In
 this case, the Local Area VAXcluster contains 22 nodes; the default
 maximum for the VAXCLUSTER NODES parameter is 16.  This example sets
 the upper limit of user access from VAX nodes at 20:


 $ RMU/DUMP ACCTING
          .
          .
          .

     Maximum node count is 22
          .
          .
          .

 $ RDO
 RDO> EXPORT ACCTING.RDB INTO ACCOUNTING_TEST.RBR
 RDO> IMPORT ACCOUNTING_TEST.RBR INTO ACCOUNTING_TEST.RDB
 cont> NUMBER OF VAXCLUSTER NODES IS 20
 cont> END IMPORT.

 Example 4

 The following example uses the IMPORT statement to restructure a
 single-file database into a multifile database.  This example does
 not include all the storage areas and storage maps that are in the
 sample multifile MF_PERSONNEL database.


 $  RDO
 !
 ! Invoke a command file that has the IMPORT statement in it
 !
 RDO>  @IMPORT_PERS.RDO
 !
 !
 IMPORT 'DISK$BACK:PERSONNEL.RBR' INTO 'DB_DISK:MULTI_PERSONNEL.RDB'
 !
 ! Specify database-wide characteristics
 !
      NUMBER OF USERS IS 40
      NUMBER VAXCLUSTER NODES 12
      SNAPSHOT IS ENABLED IMMEDIATE
      DICTIONARY IS REQUIRED
      NUMBER RECOVERY BUFFERS 200
 !
 !
 ! Specify global defaults to override Rdb/VMS defaults
 !   for all storage areas
 !
      ALLOCATION IS 500 PAGES
      PAGE FORMAT IS MIXED
      THRESHOLDS ARE (55,65,75)
      INTERVAL IS 300
 !
 !
 ! Define the default storage area
 !
 DEFINE STORAGE AREA RDB$SYSTEM
   FILENAME IS DISK1:PERS_DEFAULT
   PAGE FORMAT IS UNIFORM
   SNAPSHOT_FILENAME IS DISK2:PERS_DEFAULT
 END RDB$SYSTEM STORAGE AREA
 !
 !
 ! Define storage area for segmented strings
 !
 DEFINE STORAGE AREA PERS_SEGSTR
   FILENAME IS DISK1:PERS_SEGSTR
   PAGE FORMAT IS MIXED
   SNAPSHOT_FILENAME IS DISK2:PERS_SEGSTR
 END PERS_SEGSTR STORAGE AREA
 !
 ! Put the segmented strings in the named storage area
 !
 SEGMENTED STRING STORAGE AREA IS PERS_SEGSTR
 !
 !
 ! Define other storage areas
 !  Storage area parameters specified within the DEFINE STORAGE AREA
 !  clause override the global defaults, and the Rdb/VMS defaults
 !
 DEFINE STORAGE AREA EMPIDS_LOW
   FILENAME IS DISK3:EMPIDS_LOW
   SNAPSHOT_FILENAME IS DISK4:EMPIDS_LOW
 END EMPIDS_LOW STORAGE AREA
 !
 !
 DEFINE STORAGE AREA EMPIDS_MID
   FILENAME IS DISK5:EMPIDS_MID
   SNAPSHOT_FILENAME IS DISK6:EMPIDS_MID
 END EMPIDS_MID STORAGE AREA
 !
 !
 DEFINE STORAGE AREA EMPIDS_OVER
   FILENAME IS DISK7:EMPIDS_OVER
   SNAPSHOT_FILENAME IS DISK8:EMPIDS_OVER
 END EMPIDS_OVER STORAGE AREA
 !
 !
 DEFINE STORAGE AREA EMP_INFO
   FILENAME IS DISK1:EMP_INFO
 !  Local definition overrides the global default
   THRESHOLDS ARE (65,75,85)
   INTERVAL IS 400
   SNAPSHOT_FILENAME IS DISK2:EMP_INFO
 END EMP_INFO STORAGE AREA
 !
 !
 !
 DEFINE INDEX EMPLOYEES_HASH
   DESCRIPTION IS /* hashed index for employees relation */
   FOR EMPLOYEES
   STORE USING EMPLOYEE_ID
   WITHIN
    EMPIDS_LOW WITH LIMIT OF "00200";
    EMPIDS_MID WITH LIMIT OF "00500";
    EMPIDS_OVER
   TYPE IS HASHED.
   EMPLOYEE_ID.
 END EMPLOYEES_HASH INDEX
 !
 !
 DEFINE STORAGE MAP EMP_MAP
   DESCRIPTION IS /* Employees records partitioned by EMPLOYEE_ID */
   FOR EMPLOYEES RELATION
   STORE USING EMPLOYEE_ID
   WITHIN
    EMPIDS_LOW WITH LIMIT OF "00200";
    EMPIDS_MID WITH LIMIT OF "00500";
    EMPIDS_OVER
   PLACEMENT VIA INDEX EMPLOYEES_HASH
 END EMP_MAP STORAGE MAP
 !
 !
 !  End the IMPORT statement
 !
 END IMPORT.