HP NonStop G-Series - Manual (Page 54)

Configuring Automatic Transaction Processing
HP NonStop AutoTMF Software User’s Guide—429952-014
4-8
Audited Attribute Hiding
The only drawback to using nowait transactions is that the process continues to
perform work without knowing if a unilateral abort has occurred. A server process
replies to a requestor, but the database update operations the server process has
performed may be backed out by a system-level failure.
Batch processes that have multiple, separate, automatic transactions may have better
performance because the multiple transactions complete in parallel. The overall
performance, however, depends on the number of updates performed in each
transaction.
Each time an automatic transaction begins, any previous nowait transaction for the
same entity must be completed. Thus, a batch program that uses only the common
transaction may not benefit from nowait transactions, because the batch program
needs a new transaction as soon as the previous transaction is committed.
NonStop AutoTMF software notifies you if any automatic transaction (nowait or waited)
aborts by immediately abending the process with an explanatory message to the
process home terminal and to the EMS log.
Audited Attribute Hiding
Most legacy programs are unaware of auditing and simply access the database as if
the database were unaudited. Some programs, however, check the database and
terminate (or otherwise malfunction) if audited files are found. If you configure
HIDEAUDIT for a file, the following procedures will report that the file is not audited:
•
FILEINFO
•
FILERECINFO
•
FILE_GETINFO_
•
FILE_GETINFOBYNAME_
•
FILE_GETINFOLIST_ (first item only)
•
FILE_GETINFOLISTBYNAME_ (first item only)
Due to the complexity of locating a result item in a multi-item list request, the audit
attribute is hidden only if the first item number is for the audit attribute (66).
Audited File Creation
Some programs create files, but the files are not audited. NonStop AutoTMF software
allows you to configure file names to be created automatically as audited.
Note. The NonStop RDF product replicates the creation of an audited file on the backup node;
the NonStop RDF product does not create a file on the backup node if a file is created as
unaudited and is later altered to be audited.