ALLBASE/SQL Reference Manual (36216-90216)

564 Chapter12
SQL Statements S - Z
START DBE NEWLOG
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 after log initialization in
multiuser mode.
ARCHIVE causes ALLBASE/SQL to initialize a new log in archive mode. If you omit
this parameter, the log starts in nonarchive mode.
DUAL 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. Normally, only one log is read;
but if an error is encountered, ALLBASE/SQL switches to the other log.
Data integrity is maintained provided at least one good copy of each log
record is on at least one of the logs.
AUDIT 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 log buffer pages to be used. You as 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.
MaxTransactions specifies the maximum number of concurrent transactions to be
supported. You can specify a value from 2 to 240. The default is 50. This
value overrides the maximum value stored in the DBECon file. 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 one time, you should allow 2
concurrent transactions for just being connected to the DBE.
MAXIMUM TIMEOUT specifies the maximum user timeout value. This value temporarily
overrides the maximum stored in the DBECon file. When no value is
specified, the DBECon file value is the default.
DEFAULT TIMEOUT specifies the default user timeout value. This value temporarily
overrides the maximum stored in the DBECon file. When no value is
specified, the DBECon file value is the default.
TimeoutValue is an integer literal greater than zero. If the TimeoutValue is not
qualified by MINUTES, SECONDS is assumed. If representing seconds,
TimeoutValue must be in the range of 1 to 2,147,483,647. If representing
minutes,
TimeoutValue must be in the range of 1 to 35,791,394.