HP 3000 Manuals

ALLBASE/Turbo CONNECT Administrator's Guide

Detaching a TurboIMAGE/XL Database:  Task 8 

This task describes how to detach a TurboIMAGE/XL database from a
DBEnvironment.

Getting Ready 

Before detaching a TurboIMAGE/XL database, do the following:

 *  Make sure the appropriate SET SQLDBE and SET TURBODB commands have
    been issued.  To check the status of these commands, use the DISPLAY
    OPTIONS command:
_________________________________________
|                                       |
|     >> DISPLAY OPTIONS                |
|     Current Turbodb :                 |
|     Current SQLDBE  :                 |
|     Echo            : ON              |
|     Command Logging : ON              |
|     Log File        : ATCLOG.SERED.ATC|
|     >>                                |
_________________________________________

 *  If necessary, issue the SET commands.  For example:
______________________________________
|                                    |
|     >>SET SQLDBE PARTSDBE.SERED.ATC|
|     >>SET TURBODB SALES.SERED.ATC  |
|     >>                             |
______________________________________

Performing the Task 

Once you have issued the appropriate SET commands, you are ready to
detach the database from the DBEnvironment.  For example:
_____________________________________
|                                   |
|     >>DETACH                      |
|     >>                            |
_____________________________________

This command detaches the SALES database from the PartsDBE DBEnvironment.
If SALES is the only database attached to PartsDBE, the ATCINFO file will
be deleted.  If PartsDBE is the only DBEnvironment to which SALES is
attached, the SALESTC file will also be deleted.

Task Reference 

 *  There are several reasons to detach a TurboIMAGE/XL database from a
    DBEnvironment:
     *  If the database is to be restructured.  (This includes
        restructuring with DBChange and other third-party restructuring
        tools.)
     *  If ALLBASE/SQL is to be migrated back to a version that does not
        support Turbo CONNECT.
     *  If you wish to reset all mapping information to default values.

 *  All mapped tables, all Turbo CONNECT views based on these tables, and
    all user-created views based on Turbo CONNECT views and tables are
    dropped when the database is detached.

 *  The ATCINFO file is purged when it no longer contains mapping
    information about any databases.

 *  The DBaseNameTC file is deleted when the database is no longer
    attached to any DBEnvironments.

MPE/iX 5.0 Documentation