HP 3000 Manuals HP 3000 Manuals
Using Timeouts to Tune Performance The first connection that attaches to a DBEnvironment defines a set of startup parameters for the DBEnvironment in shared memory. These parameters remain memory resident until the last connection to the DBEnvironment is terminated. ALLBASE/SQL associates each connection with a unique session ID. When a DBEnvironment connection is initiated with a STARTDBE NEW, SQLUtil ALTDBE, START DBE, or START DBE NEWLOG statement, any specified or default timeout values are in effect for this and all subsequent connections until there are no active connections to the DBEnvironment. The exception is the SET USER TIMEOUT statement. When an application executes this statement, any previously set timeout values are overridden for that particular session. (Note that an application specific timeout value cannot exceed a previously set DBECon file maximum timeout value.) During the execution of a given application, any application specific timeout values are valid for a specific DBEnvironment while the application executes, unless overridden by a subsequent SET USER TIMEOUT statement for the same DBEnvironment.