Attaches RdbALTER to a database, putting an exclusive update lock
    on the database. No other user can access the database while the
    RdbALTER ATTACH command is in effect.

    The database specified by the root-file-spec parameter is
    attached to RdbALTER. Then you can alter the pages of its
    storage area files. Area 1, page 1 of the database is fetched
    automatically and remains the current page until you issue an
    AREA . . . PAGE command.

1  –  Description

    If the RMU Alter command includes a root-file-spec parameter, the
    database to which this root-file-spec refers is attached to as
    part of the RdbALTER startup. In this case, the ATTACH command is
    unnecessary. Otherwise, no commands changing database pages are
    allowed until an ATTACH command naming that database is issued.

    You can use the ATTACH command to attach to only one database at
    a time. Before invoking another database for altering, you must
    use the DETACH command to detach from the current database. See
    the help entry for the DETACH command for more information.

2  –  Format

  (B)0ATTACH qq> root-file-spec qqqq>

3  –  Arguments

3.1  –  root-file-spec

    Specifies the database root (.rdb) file whose pages you want to
    alter. The default file type is .rdb.

4  –  Examples

    Example 1

    The following example enters RdbALTER command level, and then
    attaches to the PERSONNEL database:

    $ RMU/ALTER
    RdbALTER> ATTACH PERSONNEL
    %RMU-I-ATTACH, now altering database "DISK:[USER]PERSONNEL.RDB;1"

    Example 2

    The following example enters RdbALTER command level and attaches
    to the PERSONNEL database, using a single command:

    $ RMU/ALTER PERSONNEL
    %RMU-I-ATTACH, now altering database "DISK:[USER]PERSONNEL.RDB;1"