HP NonStop G-Series - Manual (Page 113)

NonStop AutoTMF Software Commands
HP NonStop AutoTMF Software User’s Guide—429952-014
6-39
ALTER GLOBAL
ATMFSKIPNULLRECS
instructs the NonStop AutoTMF software runtime to ignore zero-length records
when reading sequentially through an audited entry-sequenced file.
If a record is inserted into an audited entry-sequenced file and subsequently
backed out because a transaction is aborted, a zero-length record is left in the
file where the record had been inserted. This cannot occur if the file is not
audited and can cause problems for programs that are not expecting to
encounter such records. Setting ATMFSKIPNULLRECS to ON shelters all
programs from reading unexpected null records in all entry-sequenced files.
Although automatic transactions are never aborted by NonStop AutoTMF
software, unilateral aborts could leave such gaps in an entry-sequenced file.
The default is OFF.
ATMFSTOPONTMF[ERR]
instructs AutoTMF to STOP a program that encounters a TMF environmental
error. By default, AutoTMF aborts a program that encounters a TMF error.
Setting this option causes the program to stop without creating an Inspect
saveabend file. A message describing the failure and the returned file system
error code is sent to the EMS log.
See Handling TMF Environmental Errors on page 4-10 for a list of the
applicable TMF errors.
The default is OFF.
ATMFTXHOLDOFF 0-to-n-seconds
Keeps automatic transactions active between requests received by a server if
the time between these requests is smaller than n seconds. The value of n
should be between 0 and 120.
The default is 0 seconds and automatic transactions are committed when a
server process replies to a request.
This feature is especially useful for certain types of batch processing that are
implemented as a master process that sends requests to server processes. In
these cases, if the batch process is restarted after a failure, some completed
server requests may be aborted.
When the master process stops sending work to the server, there may be an
outstanding active transaction, plus record locks and uncommitted updates. A
commit timer will commit the active transactions after a specified idle period.
The master process may send a terminating request to the servers but should
not stop the server processes.
Automatic transactions are committed in any of the following instances:
•
the process terminates (but not if the process is stopped).