TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-64
ALTER BEGINTRANS
BRANCHESPERRM integer11
RESET BRANCHESPERRM
specifies the maximum number of transaction branches that can be concurrently
imported or exported by each recoverable or volatile resource manager. The
specified value is rounded to the nearest multiple of 16. The minimum value
allowed is 16, and the maximum is 1024. The default value is 128.
RESET BRANCHESPERRM selects the originally assigned default value for
integer11, which is 128.
Security Restrictions
You can issue the ALTER BEGINTRANS command only if you are a member of the
super user group.
TMF State Requirement
Before you can enter the ALTER BEGINTRANS command, TMF must be started.
Usage Guidelines
If you alter TRANSCOUNTTHRESH, TMFLIBMEMTHRESH, or TMPMEMTHRESH,
your changes take effect immediately. If you alter TRANSPERCPU, RECRMCOUNT,
RMOPENPERCPU, or BRANCHESPERRM, however, your changes do not take effect
until the next time a START TMF command is issued.
When the AUTOABORT timeout value is changed, new transactions become
subject to the new timeout value. However, currently active transactions remain
subject to the previously set timeout value.
TMF disables and reenables transaction processing by disallowing and allowing new
application calls to the BEGINTRANSACTION system library procedure. If
transactions are disabled, BEGINTRANSACTION returns File System Error 86.
Attributes that you do not specify remain unchanged. So, if you omit an optional
parameter, one of the following actions takes place:
•
If one or more previous TMFCOM commands (such as a previous ALTER
BEGINTRANS command) specified the parameter, the value entered in the last of
these commands remains assigned.
Caution. TMF aborts any transaction pinning the oldest MAT file if the file is pinned because
of currently active transactions and if audit information is filling 45% or more of the MAT
capacity. Beyond this, however, when the AUTOABORT feature is off (threshold set
to 0), there is no mechanism to abort runaway transactions automatically; if multiple runaway
transactions go unnoticed, they can cumulatively pin many audit-trail files, preventing them
from being recycled and prohibiting the start of new transactions.