SRVn

−REMAIN

Except on Windows platforms when the database manager is auto-loaded it is loaded in such a way that it will terminate once at least one DP4 program has run against it, and there are no DP4 programs running any more. On these platforms if you want the DP4 database manager to stay loaded you should load it manually and supply the −remain command tail.

−NOREMAIN

Allows the database manager to unload when a DP4 program terminates (Windows versions only). On Windows platforms the database manager is loaded permanently by default.

−BUFFERS n

Sets the disk buffer to n Kb

−SMALL

Uses the least amount of memory possible, probably at the cost of impaired performance

−SHARELOG

Opens transaction log in shared mode

−EXTENDED

MS-DOS only. Puts buffers in extended memory

−EXPANDED

MS-DOS only. Puts buffers in expanded memory

−LOGIN name

For SRV9 only, forces the database manager to log on as a user to the file server. This limits DP4 to about 240 processes

−NODISABLE

For local resilience: application runs without server using local database if server is unavailable when program starts, but if server terminates while application is running, application will terminate.

−NOCRASH

For local resilience: application runs without server using local database, but if server terminates with current transaction, there will be a checkpoint failure

−NOFAIL

For local resilience: application runs without server on local database, and if server terminates during a transaction, there will not be a checkpoint failure

−READLOCAL

For local resilience: when used on requester, DBBACKUP and DBRESTOR work on the remote database

−AUX

Notifies Database manager that an Auxilary Database Controller (ADC) is being used. Refer to the ADC Developers' Manual for further information.

−230

Turns new features added since 4.420 to retain compatibility with older releases. In particular this makes the reuse of space occurpied by deleted records less efficient but speeds up deletion to some extent.