TMF Planning and Configuration Guide (H06.05+)

Reconfiguring TMF Processes
HP NonStop TMF Planning and Configuration Guide—540136-002
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 (4,40). The ALTER PROCESS TMP,
EXTENDEDSEGSIZE (integer1,integer2) command has two parameters. The
following guidelines apply to these parameters:
•
Both integer1 and integer2 must be equal to or less than 128, and integer2 must
be a multiple of integer1.
•
integer1 is not used, but it must still be valid.
•
integer2 is used as the initial segment size (it is limited to 128). If the specified
number is less than 40, then 40 megabytes is used as the initial size.
•
The maximum segment size is 1,024 megabytes rounded down to be a multiple of
integer2. You cannot adjust this number. The TMP will try to grow the segment as
needed, until the segment size reaches this maximum or until all the available
Kernel-Managed Swap Facility (KMSF) swap space is used.
Changing the configured value for the TMP process requires a STOP TMF, ABRUPT
operation or a cold load of the system.