Map database, Monitor process, Configuring the monitor process – HP Integrity NonStop J-Series User Manual
Page 176
System Management
HP NonStop AutoTMF Software User’s Guide—429952-017
A-2
Map Database
Map Database
A Map Database (MapDB) contains AutoTMF configuration information for selected
files and programs. In this release, the MapDB subvolume contains three SQL tables:
ATMFATTR to store AutoTMF file configuration.
ATMFPROG to store AutoTMF program configuration.
REGISTRY to store NonStop AutoTMF default configuration parameter values
referred to as locals. Locals are analogous to globals, but apply to one MapDB
only.
Each MapDB table must be secured for read and write access by the users who run
AutoTMF configuration commands or who start the monitor process. Application
processes do not access the MapDB.
AutoTMF supports the creation of an alternate MapDB, primarily to provide separation
between production and development activities. Use of an alternate MapDB requires a
DEFINE for each process execution and is not recommended for production
applications. See section
Configuring an Alternate MapDB
on page A-5 for details on
configuring an alternate AutoTMF environments.
Monitor Process
The monitor process provides AutoTMF configuration information for application
processes; the monitor must be running to use NonStop AutoTMF services. Initially, the
monitor is started when the MapDB is created. The monitor is a fault-tolerant process
pair, so the monitor should not require restarting unless the monitor is stopped or a
system coldload is performed.
As described in
Update System Coldload Procedures
coldload procedures should start the monitor process. The monitor should be started
after TMF is up and before starting Pathway or the application programs.
The monitor process is quite efficient and can service many hundreds of requests per
second. The monitor should be run at high priority, since the monitor serves all
NonStop AutoTMF applications and does not run for long periods.
Configuring the Monitor Process
The monitor is configured and started when the MapDB is created with the
command. The monitor has an assigned process name, $ZESC, reserved for
AutoTMF.
The monitor is configured with the
command. You can configure
process priority, process CPUs, and the monitor event logging device.