TMF Reference Manual (G06.24+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-002
3-65
ALTER BEGINTRANS
•
If no previous TMFCOM command specified the parameter, the originally assigned
default remains assigned.
For transaction processing to be reenabled after it has been disabled because one of
the upper limits set by ALTER BEGINTRANS has been reached, all of the following
conditions must exist:
•
TMF must be started.
•
No DISABLE BEGINTRANS operation must be in progress.
•
No audit trail must presently exceed its BEGINTRANSDISABLE threshold.
•
All ALTER BEGINTRANS command’s TRANSCOUNTTHRESH,
TMFLIBMEMTHRESH, and TMPMEMTHRESH parameters whose upper limits
have been exceeded must have subsequently fallen below their lower limits.
In very rare cases, increasing the TRANSPERCPU value could require increasing the
TMFMON process’ EXTENDEDSEGSIZE value as well. However, in most cases, the
default value assigned for the TMFMON EXTENDEDSEGSIZE parameter (12 MB) is
more than sufficient.
The value of the TMP process’ node disconnect timer, if modified through the SNOOP
utility, can impact the use of the AUTOABORT option in the ALTER BEGINTRANS
command. The disconnect timer specifies the maximum number of seconds that a
distributed transaction is allowed to exist without receiving any replies from a
participating node; when this time limit expires, the TMP terminates the transaction. If
you use the SNOOP utility to change the disconnect timer value and later issue a
TMFCOM ALTER BEGINTRANS command to set the AUTOABORT timeout
parameter lower than the new disconnect timer value, the ALTER BEGINTRANS
command fails and an error message appears. To correct this situation, you must
Note. You can specify multiple parameters in the ALTER BEGINTRANS command. You must
specify at least one parameter, or an error results.
Note. The RECRMCOUNT, RMOPENPERCPU, and BRANCHESPERRM options apply to
resource managers, which support heterogeneous transaction processing. Resource
managers are used in products such as NonStop TUXEDO. Although TMFCOM and the
TMFSERVE programmatic interface provide TMF commands and options for operating on
resource managers, system managers who use them do so in the context of issues involving
multiple software subsystems and inter-platform considerations. Complete discussion of
heterogeneous transaction processing and the context in which resource-manager commands
and options are used lies beyond the scope of the TMF manual library.
For more information about heterogeneous transaction processing, see the Open Group
TRANSACTION PROCESSING Publications, available from X/Open Publications at the
following Web location:
http://www.opengroup.org/pubs/catalog/tp.htm
These publications can also be ordered through many bookstores.