HP 3000 Manuals HP 3000 Manuals
Configuring a DBEnvironment
This task describes how to configure a DBEnvironment so that you can
access your TurboIMAGE/XL database(s) with IMAGE/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:
* IMAGE/SQL supports standard MPE/iX 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 IMAGE/SQL utility
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 IMAGE/SQL utility tasks (see Task Reference),
because IMAGE/SQL utility administrators need DBA authority
to perform most IMAGE/SQL utility 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. IMAGE/SQL requires that these files be
larger than their defaults. Make sure these files are large
enough to accommodate IMAGE/SQL. 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).
[REV BEG]
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 MusicDBE, enter the
following:
________________________________________________________
| |
| isql=> START DBE 'MUSICDBE' MULTI NEW |
| > MAXIMUM TIMEOUT = 10 SECONDS |
| > DEFAULT TIMEOUT = 5 SECONDS |
| > DBEFILE0 DBEFILE DBEFILE0 <==DBEFile0Definition|
| > WITH PAGES = 500, <== . . |
| > NAME = 'MusicF0', <== . . |
| > LOG DBEFILE DBELOG1 <==DBELog0Definition |
| > WITH PAGES = 500, <== . . |
| > NAME = 'MusicLog'; <== . . |
| isql=> EXIT; |
| : |
________________________________________________________
If you forget the semicolon, ISQL prompts you. At this prompt, enter a
semicolon and ISQL will execute the command. The MULTI parameter is
necessary if you plan on a multiuser IMAGE/SQL environment.
To avoid deadlock situations when there are more than two connections,
you should either set the MAXIMUM TIMEOUT and DEFAULT TIMEOUT options
with the START DBE NEW statement or change them with the SQLUtil ALTDBE
command.
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 |
| |
| THU, APR 8, 1993, 10:26 AM |
| HP36216-02A.F0.52 DBE Utility/3000 ALLBASE/SQL|
| (C)COPYRIGHT HEWLETT-PACKARD CO. 1982,1983,1984,1985,1986,1987,1988, |
| 1989,1990,1991,1992,1993. ALL RIGHTS RESERVED. |
| |
| >>SETDBEMAINT |
| Environment Name: MUSICDBE |
| Current Maintenance Word: |
| New Maintenance Word: usr |
| Retype New Maintenance Word: usr |
| |
| Maintenance word changed. |
| >>EXIT |
________________________________________________________________________________
Listing the Newly Created Files
When you display the files in your current group, note that there are
three newly created files: MUSICDBE, DBEFILE0, and DBELOG1.
The first file is the DBECon file or DBEnvironment configuration file.
This has the same name you assigned to the DBEnvironment in the START DBE
command. The DBECon file contains startup parameters for the
DBEnvironment.
DBEFILE0 is a file containing the data for the SYSTEM DBEFileSet, which
contains the system catalog. (You'll examine the system catalog later.)
DBELOG1 is the log file, which records operations that modify the
database.
Once you have configured the DBEnvironment, set the timeout time, and set
a maintenance word for it, you are ready to attach TurboIMAGE/XL
databases to it, as shown in the next task.[REV END]
Task Reference
* No information is given here about considerations that may be
necessary when configuring a DBEnvironment that contains native
ALLBASE/SQL databases. Consult the ALLBASE/SQL Database
Administration Guide for more guidance in this area.
* The following summaries of IMAGE/SQL commands will get you
started. Refer to the ALLBASE/SQL Reference Manual for more
information.
* The ALLBASE/SQL START DBE NEW statement 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.
* 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|
| >>EXIT |
_______________________________________________________
When no current maintenance word exists, enter a carriage return
at the "Current Maintenance Word:" prompt.