TMF Planning and Configuration Guide (H06.06+, J06.03+)

Reconfiguring TMF Processes
HP NonStop TMF Planning and Configuration Guide—540136-005
6-7
Changing Extended Segment Sizes
•
If your system configuration is large or contains high-speed processors
After a process failure due to insufficient memory space, TMF periodically tries to
restart the failed process.
The default extended segment size for each TMF process is a value chosen by the
process itself. The default values are sufficient for most configurations; however, for
large or high-speed configurations, the defaults can be insufficient and might need to
be increased.
The default extended segment size for the TMFMON and TMP processes is configured
for small (four-processor) systems of average speed. If your system contains more
than four processors or is a high-performance HP NonStop server, you should make
the extended segment sizes for the TMFMON and TMP processes larger than the
defaults. If you do not do so, you could see EMS event messages 277 and 278 from
the affected process during processor reload in periods of high transaction activity:
<process-name>: Transactions DISABLED due to low TMFLIB
memory availability in CPU 0.
<process-name>: Transactions reenabled due to restored memory
availability in TMFLIB in CPU 0.
The reported condition is not fatal, but it can cause application programs to receive file-
system error 86 (BEGINTRANSACTION is disabled either by the operator or because
one or more TMF limits have been reached).
The size of the extended segments for the TMFMON and TMP processes should be
based on your configuration and expected transaction load.
The default extended-segment size for TMFMON is (12,12). Changing the configured
value for the TMFMON process requires a cold load of the system.
•
The default extended-segment size for the TMP is (128, 1024). These values
cannot be changed.
When changing extended segmemt sizes, the minimum value that you enter cannot be
smaller than the processes' default minimum and the maximum that you enter cannot
be smaller than the processes' default maximum.
On systems with a large number of data volumes or a large number of files accessed
by a single transaction, the backout, volume recovery, or file recovery processes might
not be able to perform their recovery operations with the current memory allocation. In
relation to the default extended segment size, for example, 250 volumes could be
considered a large number of volumes. In such cases, you might need to increase the
extended segment size for these processes.
The default backout process extended segment size is (8,64). The default file recovery
or volume recovery process extended segment size is (8,64). Changing the configured
value for a recovery process requires manually stopping the process or a STOP TMF
operation.