TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-85
ALTER PROCESS
On NonStop S-series servers, the TMP always runs four concurrent backout processes
for each system, regardless of the number of processors on the system. These
backout processes are created whenever the START TMF command is issued. You
can change their processor assignment with the CPU parameter.
PRI Option Considerations
For the PRI parameter, you can specify values ranging from 1 through 199, except for
the TMP process type (which must be 204), the TMFMON process (which must be
211), and the TMFMON2 process (which must be 200). Applications must always be
run at a priority less than the PRI for these three processes.
EXTENDEDSEGSIZE Option Considerations
The EXTENDEDSEGSIZE option allows you to alter the initial size (integer1) and
growth limit (integer2) for a process type’s extended segment. For most process
types, the values you enter for integer1 and integer2 can range from 1 through
128; exceptions are noted later in this discussion. The integer2 value must be
greater than or equal to the integer1 value, and must be a multiple of integer1.
The EXTENDEDSEGSIZE default values are established for minimum (four-processor)
system configurations. You should review these settings as they apply to your actual
configuration, and assign new EXTENDEDSEGSIZE values accordingly. You must
make these adjustments in either of these cases:
•
If a TMF process fails repeatedly. Whenever a process fails because of insufficient
memory space, TMF periodically tries to restart that process. An increased
EXTENDEDSEGSIZE value usually resolves this situation.
•
If you receive these two EMS messages during processor reload or in periods of
high transaction activity:
*0277* TMP Process: Transactions DISABLED due to low
{TMP | TMFLIB} memory availability in CPU 0.
*0278* TMP Process: Transactions reenabled due to restored
memory availability in {TMP | TMFLIB} in CPU 0.
The condition reported by these messages is not fatal, but it can cause application
programs to experience Error Code 0086 (transaction processing is disabled either
by the operator or because one or more TMF limits have been reached).
If your TMF system services many volumes, you may need to adjust the
EXTENDEDSEGSIZE values for the recovery process types: BACKOUT,
VOLUMERECOVERY, and FILERECOVERY.
For the TMP and TMFMON process types, a precise calculation of the extended
segment size for a given transaction load cannot be done. This requirement rests
heavily on the size of the transaction control blocks (TCBs) needed to support
transaction processing at your site, which in turn depends on the size of your NonStop