The following additional single-user controls are available. Server configuration file keywords are repeated prior to the method for implementing in single-user mode:
RECOVER_MEMLOG <# of logs to load>
In FairCom DB single-user, transaction processing mode, the global variable ctlogmem should be set to one (1), and ctlogmemmax should be set to the maximum number of logs to load into memory.
CHECKPOINT_INTERVAL <interval in bytes>
For example, adding CHECKPOINT_INTERVAL 150000 to the configuration file will cause checkpoints about every 150,000 bytes of log file.
In FairCom DB single-user, transaction processing mode set the LONG global variable ctlogchklmt to the desired value.
ctLOGIDX is only meaningful if the file mode also includes ctTRNLOG. Note that ctLOGIDX is intended for index files only! Do not use ctLOGIDX with data files.
ctLOGIDX must defined prior to building single-user FairCom DB library.
ctLOGIDX support may be forced on, off or disabled with the FORCE_LOGIDX server configuration file entry.
FORCE_LOGIDX <ON | OFF | NO>
In FairCom DB single-user transaction processing mode, set the global variable ctlogidxfrc as follows: 1 for ON, 2 for OFF and 0 for NO. If ctNOGLOBALS is in use, then either the CTVAR structure must be allocated, (typically by calling RegisterCtree()), prior to the FairCom DB initialization call, (so that the member corresponding to ctlogidxfrc can be set), or setting ctlogidxfrc must be delayed until after the initial call to FairCom DB. If delayed, then turning ctLOGIDX entries off (ctlogidxfrc == 2) cannot be done until after the initialization call and its possible need for automatic recovery.