HP 3000 Manuals HP 3000 Manuals
Configuring a DBEnvironment: Task 1
This task describes how to configure a DBEnvironment so that you can
access your TurboIMAGE/XL database(s) with ALLBASE/SQL (see Task
Reference).
Getting Ready
* When all of the TurboIMAGE/XL databases to be attached to the
DBEnvironment are created by the same user in one group and account,
it is convenient to configure the DBEnvironment in this group and
account.
If this is not the case, several other issues should be considered.
The following considerations apply if the TurboIMAGE/XL database to
be attached exists in a different group and/or account than the
DBEnvironment:
* Turbo CONNECT supports standard MPE XL security rules. Make sure
correct user, group, and account capabilities are in place when
you plan to access a TurboIMAGE/XL database from a DBEnvironment
in a different account than the database.
* Make sure maintenance words exist for both database management
systems, because ATCUtil administrators often need to specify
DBEnvironment and TurboIMAGE/XL maintenance words if they are not
the creator.
* Be sure to grant DBA authority to everyone who will be
performing ATCUtil tasks (see Task Reference), because ATCUtil
administrators need DBA authority to perform most ATCUtil tasks.
* Make sure the TurboIMAGE/XL database and the DBEnvironment have the
same native language support (NLS) defined for them.
* When a DBEnvironment is configured, two files are created: DBEFILE0
and DBELOG1. Turbo CONNECT requires that these files be larger than
their defaults. Make sure these files are large enough to
accommodate Turbo CONNECT. In the example below, a file size of 500
pages is used for each of these files, but you may need to adjust
these sizes, depending on the size and number of TurboIMAGE/XL
databases you plan to attach (see Task Reference).
Performing the Task
Log on in the same group and account as the TurboIMAGE/XL database(s) and
run ISQL. At the ISQL prompt, enter the START DBE NEW command. For
example, to configure a DBEnvironment named PartsDBE, enter the
following:
_________________________________________________________
| |
| isql=> START DBE 'PartsDBE' MULTI NEW |
| > DBEFILE0 DBEFILE DBEFILE0 <===DBEFile0Definition|
| > WITH PAGES = 500, <=== . . |
| > NAME = 'PartsF0', <=== . . |
| > LOG DBEFILE DBELOG1 <===DBELog0Definition |
| > WITH PAGES = 500, <=== . . |
| > NAME = 'PartsLog'; <=== . . |
| isql=> EXIT; |
| : |
_________________________________________________________
If you forget the semicolon, ISQL prompts you with a right-angle bracket
(>). At this prompt, enter a semicolon and ISQL will execute the
command. The MULTI parameter is necessary if you plan on a multiuser
Turbo CONNECT environment.
To set a maintenance word for the newly configured DBEnvironment, use the
SETDBEMAINT command of SQLUtil. This utility prompts you for necessary
information, as in the following example.
_________________________________________________
| |
| :RUN SQLUTIL.PUB.SYS |
| >> SETDBEMAINT |
| DBEnvironment Name: PartsDBE |
| Current Maintenance Word: Carriage Return|
| New Maintenance Word: usr |
| Retype New Maintenance Word: usr |
| >> |
_________________________________________________
Once you have configured the DBEnvironment and set a maintenance word for
it, you are ready to attach TurboIMAGE/XL databases to it.
Task Reference
* No information is given here about considerations that may be
necessary when configuring a DBEnvironment which contains native
ALLBASE/SQL databases. Consult the ALLBASE/SQL Database
Administration Guide for more guidance in this area.
* The following summaries of ALLBASE/SQL commands will get you started.
Refer to the ALLBASE/SQL Database Administration Guide and the
ALLBASE/SQL Reference Manual for more information.
* The ALLBASE/SQL START DBE NEW command has the following syntax:
________________________________________________________________________
| |
| |
|START DBE 'DBEnvironmentName' [MULTI] NEW |
| |
|[DUAL LOG ] |
|[BUFFER = (DataBuffPages,LogBuffPages)] |
|[LANG = LanguageName ] |
|[TRANSACTION = MaxTransactions ]|,...| |
|[DBEFile0Definition ] |
|[DBELogDefinition ] |
________________________________________________________________________
Refer to the Performing the Task example for details of the
syntax for DBEFile0Definition and DBELogDefinition.
* The ALLBASE/SQL GRANT command has the following syntax for
granting DBA authority:
________________________________________________________________________
| |
| |
| {CONNECT } {DBEUserID} |
|GRANT {DBA } TO {GroupName} [,...] |
| {RESOURCE} {ClassName} |
________________________________________________________________________
* Use SQLUtil to set a DBEnvironment maintenance word. To access
SQLUtil, issue the following command:
_____________________________________
| |
| : RUN SQLUTIL.PUB.SYS |
| : |
_____________________________________
The SQLUtil SETDBEMAINT command is used to set a maintenance
word. The syntax for this command is as follows:
_______________________________________________________
| |
| >> SETDBEMAINT |
| |
| DBEnvironment Name: DBEnvironmentName |
| |
| Current Maintenance Word: OldMaintenanceWord |
| |
| New Maintenance Word: NewMaintenanceWord |
| |
| Retype New Maintenance Word: NewMaintenanceWord|
_______________________________________________________
When no current maintenance word exists, enter a carriage return at
the "Current Maintenance Word:" prompt.