HP Integrity NonStop J-Series - Manual (Page 208)

Problem Resolution
HP NonStop AutoTMF Software User’s Guide—429952-017
C-2
Locking Problems
Other errors
Program failures can be caused by configuration problems, by defects in the runtime
library, or by defects in a program.
If the runtime library detects a configuration problem or a version conflict, the runtime
library sends a message to the home terminal of the program and to the EMS event
log, commits the outstanding automatic transactions and abends the program.
Likewise, if the runtime library causes a program to trap or if the runtime library detects
an irrecoverable internal logic error, the trap message and the stack trace are
displayed on the home terminal of the process and in the EMS event log. Always check
the home terminal or the EMS event log when program failures occur. See
EMS Log
below for ways to check for AutoTMF events.
Report any program failure that is caused by the AutoTMF runtime to HP product
support.
Error 75
Error 75 is returned when a “requesting process has no current process transaction
identifier”. Since AutoTMF is designed to provide transactions whenever they are
required, there are a few well-known causes for this error:
1. The monitor process is not running. To check on the state of the monitor process,
use the CI command STATUS MONITOR . To start the monitor process, use the
START MONITOR command.
2. The AutoTMF installation has not been licensed or a time–limited license has
expired. Use the MONITOR STATUS LICENSE command to check the state of the
AutoTMF license.
3. The program has not been prepared. To verify that a program has been prepared
successfully, use the CI command INFO PROGRAM . To prepare a program, use
the PREPARE command.
4. The configuration disables automatic transactions for the files being accessed or
for all files. Use the INFO ATMFFILESET , INFO ATMFPROGRAMS , and INFO
GLOBALS commands to verify the configuration parameters.
If the monitor process is running and healthy and the failing program is properly
prepared, then the program should be traced to examine the sequence in which the file
operations are performed and transactions are started and committed.
Locking Problems
Contention and Deadlocks
Audited files are subject to different locking protocols than non-audited files. When
accessing audited files, locking is enforced by TMF to maintain data integrity. An
application that was not designed for audited files may incur concurrency problems