HP 3000 Manuals HP 3000 Manuals
Attaching a TurboIMAGE/XL Database: Task 2 This task describes how to attach a TurboIMAGE/XL database.
NOTE If you are attaching a database with the same name but in a different group and/or account as a database already attached to the DBEnvironment, you must specify an alternative owner name at attach time (see Task Reference). This is because in a mapped table, by default the owner name is the database name, and duplicate table names are not allowed within the same database. In any case, you cannot attach the same TurboIMAGE/XL database twice to the same DBEnvironment.
Getting Ready * It is convenient to have the TurboIMAGE/XL database and the DBEnvironment in the same group and account. If this is not the case, there are several issues to consider. The following considerations apply if the TurboIMAGE/XL database(s) to be attached exist(s) in a different group and/or account than the DBEnvironment: * Turbo CONNECT supports standard MPE XL security rules. Correct user, group, and account capabilities must be in place to use Turbo CONNECT to access a TurboIMAGE/XL database from a DBEnvironment in a different account than the database. * ATCUtil administrators often need to specify DBEnvironment and TurboIMAGE/XL maintenance words as a part of the SET command if they are not the creator. Because of this, it is recommended that maintenance words exist for both database management systems. * ATCUtil administrators need DBA authority to perform most ATCUtil tasks. Be sure to grant DBA authority to everyone who will be performing ATCUtil tasks (see Task Reference). * The TurboIMAGE/XL database and the DBEnvironment must have the same native language support (NLS) defined for them. * The ATTACH command requires that 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 are sure the appropriate SET commands have been specified and that the correct MPE XL security is in place, issue the ATTACH command. _________________________________________________________________ | | | >> ATTACH | | Split 1 compound source fields (ATCWARN 32063). | | Mapped 15 source table/source field names (ATCWARN 32062).| | Mapped 1 incompatible source types (ATCWARN 32061). | | >> | _________________________________________________________________ Messages issued at attach time inform you if any mapping has been done (see Task Reference). The SALES database is now a logical part of the PartsDBE DBEnvironment. Although the data remains in the TurboIMAGE/XL database, it can now be selected from mapped tables just as it would be selected from native ALLBASE/SQL tables. Task Reference * By default, ATCUtil uses the TurboIMAGE/XL database name as the owner name. You must specify an alternate owner name if you are attaching a TurboIMAGE/XL database with the same name as one already attached. To do this, use the WITH OWNER= parameter of the ATTACH command. * To specify a maintenance word, use the MAINT= parameter of the SET TURBODB or SET SQLDBE command. Refer to chapter 4, "Turbo CONNECT Command Syntax," for details about these commands and their parameters. * Use the DISPLAY MAP command to see detailed database mapping information. * When a TurboIMAGE/XL database is attached to a DBEnvironment, Turbo CONNECT performs the following tasks: * Makes a table entry in the system catalog of the DBEnvironment for each corresponding source data set. * Creates a column definition for each field in the source data set. (The NOT NULL option is used, because null values are not defined in TurboIMAGE/XL.) * Produces default mapping information which maps TurboIMAGE/XL data sets to ALLBASE/SQL tables and stores this information in the ATCINFO file. Specifically, mapping is done in the following areas: * Data item and data set names: Some characters allowed in TurboIMAGE/XL names (specifically: + - * / ? ' % & ) are not valid in ALLBASE/SQL names. Therefore, whenever ATCUtil encounters such a character in a TurboIMAGE/XL name, it converts it to an underscore (_). * Data types: TurboIMAGE/XL data types are mapped to ALLBASE/SQL data types. When inexact/imprecise mapping is necessary, an I appears in the NOTES section of the DISPLAY MAP display. When a compound field is split into separate mapped columns, an S appears in the NOTES section of the display. * User security: Initially, only the TurboIMAGE/XL database creator (DBC) is defined as a user in the DBEnvironment. For other users to access the attached database, the DBC must add users with ATCUtil's ADD USER command. (Refer to task 3, "Adding Turbo CONNECT Users," for more information.) * Once the database is attached, the DBC must add any additional Turbo CONNECT users. * It is desirable to update data types (task 4) and split mapped columns (task 5) before Turbo CONNECT users access the attached database. This is because whenever a mapped column is split or updated, any user-created views containing these mapped columns are dropped.