A system management, System database, A. system management – HP Integrity NonStop J-Series User Manual
Page 175: Appendix a, system, Management, For further det, Appendix a, system management, System management
HP NonStop AutoTMF Software User’s Guide—429952-017
A-1
A
System Management
Configuring and Using an Alternate NonStop AutoTMF Environment
Migrating the NonStop AutoTMF Software Configuration to a New System
Host-language Runtimes in the Runtime Library
Executing Prepared Applications
System Database
The System Database (SysDB) consists of two SQL tables:
MAPDBS to store the description of map databases and associated monitor
processes.
REGISTRY to register a product license and other system-wide default
configuration parameters referred to as globals.
Normally, each system has a single SysDB in the $SYSTEM.ESCSYSDB subvolume,
but SysDB may also be stored on another volume. There should be only one SysDB
subvolume named ESCSYSDB.
You need write access to the SysDB to create or alter the map database, to specify the
product license or alter the default global parameters. You need read access to run
some commands, especially to start the monitor process. Application processes do not
access the SysDB, since application processes obtain all information through the
monitor process.
When AutoTMF needs to access the SysDB, AutoTMF looks first for SysDB tables in
$SYSTEM.ESCSYSDB. If the tables do not exist, AutoTMF then searches all disks for
a SysDB in the ESCSYSDB subvolume. If there is more than one SysDB, the
command interpreter will terminate with an error.
Although unusual, you can configure more than one SysDB to define different
AutoTMF environments on the same system. This is most commonly required on
development systems where different groups with very different requirements share a
system. See