Displays the contents of an export interchange (.rbr) file or a
    formatted .unl file created by the RMU Unload command. This is a
    useful debugging tool.

1  –  Format

  (B)0RMU/Dump/Export export_file

     Command Qualifiers                        x Defaults

     /[No]Data                                 x /Data
     /[No]Options[=options-list]               x /Nooptions
     /Output=file-name                         x /Output=SYS$OUTPUT

2  –  Parameters

2.1  –  export-file

    The .rbr file or formatted .unl file to be displayed.

3  –  Command Qualifiers

3.1  –  Data

    Data
    Nodata

    The Data qualifier specifies that the contents of segmented
    strings and tables are to be displayed in hexadecimal format
    along with the ASCII translation. Specifying the Nodata qualifier
    excludes the contents of segmented strings and tables from the
    display and generates much less output.

    The default is the Data qualifier.

3.2  –  Options=option-list

    Options=option-list

    The Options qualifier allows the user to modify the output from
    the RMU Dump Export command.

    If you specify more than one option, you must separate the
    options with a comma and enclose the options-list parameter
    within parentheses.

    -  ALLOCATION

       When importing databases for testing, the full allocation
       recorded in the interchange file is often not required. The
       clauses ALLOCATION and SNAPSHOT ALLOCATION are controlled by
       this option. The default is ALLOCATION. Use NOALLOCATION to
       omit these clauses from the generated SQL script. This option
       is ignored if NOIMPORT_DATABASE is specified or defaulted for
       the OPTIONS qualifier.

    -  FILENAME_ONLY

       When importing databases for testing, the full file
       specification for the database root, storage areas and
       snapshot areas recorded in the interchange file is often
       not required. The FILENAME clauses are controlled by this
       option which trims the specification to only the filename
       portion. The default is NOFILENAME_ONLY. Use FILENAME_ONLY to
       truncate the file specification in the generated SQL script.
       This option is ignored if NOIMPORT_DATABASE is specified or
       defaulted for the OPTIONS qualifier.

    -  HEADER_SECTION

       This option allows the database administrator to display just
       the header portion of the interchange file and avoid dumping
       the data or metadata for every row in the table.

    -  IMPORT_DATABASE

       This keyword requests that the output from RMU Dump Export
       be formatted as a SQL IMPORT DATABASE statement. It uses
       the database attributes present in the interchange file
       formatted as SQL clauses. Of particular interest are the
       CREATE STORAGE AREA clauses which are required to IMPORT the
       source interchange (.rbr) file.

       The keyword HEADER_SECTION is implicitly selected when IMPORT_
       DATABASE is used, limiting the I/O to the interchange file to
       the section containing the database attributes.

       The default is NOIMPORT_DATABASE.

3.3  –  Output

    Output=file-name

    Specifies the name of the file where output is sent. The default
    is SYS$OUTPUT. The default output file type is .lis, if you
    specify a file name.

4  –  Usage Notes

    o  You do not need Oracle RMU privileges to use the RMU Dump
       Export command. However, you must have OpenVMS read access to
       the .rbr or .unl file, or OpenVMS BYPASS privilege.

    o  If the source interchange file is created by RMU Unload, then
       it does not contain any IMPORT DATABASE information and the
       generated SQL script cannot be used to create a database from
       such an interchange file.

       $ RMU/DUMP/EXPORT/OPTION=IMPORT_DATABASE EMPLOYEES.UNL/OUT=EMP.SQL
       $ SQL$ @EMP.SQL
       SQL> IMPORT DATABASE
       cont>     from 'DISK1:[TESTING]EMPLOYEES.UNL;1'
       cont>     -- ident ' Load/Unload utility'
       cont>     -- backup file version 4
       cont>     -- database ident 'Oracle Rdb V7.2-131'
       cont>     filename 'DB$:MF_PERSONNEL'
       cont> ;
       %SQL-F-EXTRADATA, unexpected data at the end of the .RBR file
       $

    o  The IMPORT_DATABASE option is intended to create a SQL script
       as an aid to the database administrator. Some editing of the
       generated script may be required under some circumstances.

       Only a subset of the database attributes are dumped by RMU
       for the IMPORT_DATABASE output. Continue to use the RMU Dump
       Export Option=NOIMPORT_DATABASE to see all attributes recorded
       in the interchange file.

5  –  Examples

    Example 1

    The following is an example of the RMU Dump Export command using
    the default qualifiers:

    $ RMU/DUMP/EXPORT EMPLOYEES.UNL
 Example 2

    The following is an example of how to use the HEADER_SECTION
    option to display just the header portion of the interchange
    file, and avoid dumping the data or metadata for every row in the
    table.

    $ RMU/DUMP/EXPORT/OPTION=HEADER JOBS.UNL

    BEGIN HEADER SECTION - (0)
        NONCORE_TEXT HDR_BRP_ID - (20) :  Load/Unload utility
        CORE_NUMERIC HDR_BRPFILE_VERSION - (1) : 4
        NONCORE_TEXT HDR_DBS_ID - (18) : Oracle Rdb V7.2-10
        NONCORE_TEXT HDR_DB_NAME - (16) : DB$:MF_PERSONNEL
        NONCORE_DATE HDR_DB_LOG_BACKUP_DATE - (8) :  3-JUL-2006 16:52:32.83
        CORE_NUMERIC HDR_DATA_COMPRESSION - (1) : 1
    END HEADER SECTION - (0)

    In this example, the output describes the creator of the
    interchange file (RMU/UNLOAD), the version of Rdb used to create
    the file, the file specification of the database used, the date
    and time the interchange file was created, and an indication that
    compression was used by RMU Unload.