ALLBASE/SQL Reference Manual (36216-90216)

556 Chapter12
SQL Statements S - Z
START DBE NEW
ConnectionName must be unique for each DBEnvironment connection
within an application. If a
ConnectionName is not specified,
DBEnvironmentName is the default. ConnectionName cannot exceed 128
bytes.
MULTI indicates the DBEnvironment can be accessed by multiple users
simultaneously. If omitted, the DBEnvironment can be accessed only in
single-user mode.
DUAL LOG causes ALLBASE/SQL to maintain two separate logs, preferably on
different media. Keeping the log files on separate media ensures that a
media failure on one device leaves the other log undamaged. Each log
write operation is performed on both logs; if an error is detected, the write
continues on the good log only. Normally, only one log is read, but if an
error is encountered, ALLBASE/SQL switches to the other log. Data
integrity is maintained provided is at least one good copy of each log record
is on at least one of the logs.
AUDIT LOG identifies the DBEnvironment as one that will have audit logging
performed on it with the elements specified in the AUDIT ELEMENTS
clause. This causes ALLBASE/SQL to create audit log records as well as
normal log records in the log file so that the database can be audited.
DataBufferPages specifies the number of 4096-byte data buffer pages to be used. Data
buffer pages hold index and data pages.
You can request up to 50,000 data buffer pages. The minimum number of
data buffer pages is 15. The default number is 100. The total number of
data buffer pages and runtime control block pages cannot exceed 256
Mbytes.
LogBufferPages specifies the number of 512-byte log buffer pages to be used. You can
request from 24 to 1024 log buffer pages, limited by the amount of storage
available. The default number of log buffer pages is 24.
LANG specifies the language for the DBEnvironment. If the name of the
language contains a hyphen, use double quotes in specifying it, as in the
following (c-french means Canadian French):
LANG = "c-french"
MaxTransactions specifies the maximum number of concurrent transactions to be
supported. You can specify a value from 2 to 240. The default is 50. Any
attempt to start a transaction beyond the maximum limit waits for the
specified TIMEOUT and returns an error if TIMEOUT is exceeded. For
each user logged on to the system at any point in time you should allow 2
concurrent transactions for just being connected to the DBE.
MAXIMUM TIMEOUT specifies the maximum user timeout value that is stored in the
DBECon file. The default is the MAXIMUM.
DEFAULT TIMEOUT specifies the default user timeout value that is stored in the DBECon
file. The default is NONE (infinity).