ALLBASE/SQL Reference Manual (36216-90216)

Chapter 12 553
SQL Statements S - Z
START DBE
See the "ALLBASE/SQL Limits" Appendix in the ALLBASE/SQL
Database Administration Guide.
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.
MaxTransactions specifies the maximum number of concurrent transactions that can be
concurrently active. You can specify a value in the range 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 point in 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 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.
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.
ControlBlockPages specifies the number of runtime control blocks allocated.
You can specify a value from 17 to 2,000 pages for this parameter. The
default is 37 pages. The total number of data buffer pages and runtime
control block pages cannot exceed 256 Mbytes.
Description
• Any parameters (except the MULTI option) not specified in the START DBE statement
are assigned values currently stored in the DBECon file (which has the same name as
the DBEnvironment name specified). The user mode in the DBECon file is
always
overridden by the user mode specified in the START DBE statement.
• Normally, if autostart mode has the value of ON, DBE sessions are established by using
the CONNECT statement. The START DBE statement is needed only to temporarily
override DBECon file parameters for the DBEnvironment, as when you need to start a
single-user DBEnvironment in multiuser mode or vice versa. When you issue the
CONNECT statement and autostart mode is on, ALLBASE/SQL executes a START DBE
statement on your behalf if no sessions for the DBEnvironment are active.
ALLBASE/SQL starts your session using all parameters in the current DBECon file.
• If autostart mode has a value of OFF, you always use the START DBE statement to start
up a DBEnvironment. If the MULTI option is not specified, the DBEnvironment is
started up in single-user mode. If the MULTI option is specified, the DBEnvironment is
started up in multiuser mode and other users can initiate DBE sessions by using the