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

Preparing Programs
HP NonStop AutoTMF Software User’s Guide—429952-017
3-13
Diagnosing Preparation Errors
starting the NonStop AutoTMF preparation process, subsequent errors are more likely
caused by the preparation and not by the application’s setup.
Also, you should prepare all programs that are part of the application, even if you know
that some programs will not require automatic transactions. This configuration is simple
to manage and causes fewer errors when the application is run. Prepared programs
that do not require transactions to access audited files run like unprepared programs;
they do not generate additional transactions.
After you have prepared the object files, retest the application before auditing any
database files. At this time, you can experiment with the NonStop AutoTMF tracing
facility. For example, if you are testing a PATHWAY server or a batch program, enter
the following ESCORT CI command before the program starts:
Once the program has run, examine the trace file.
Diagnosing Preparation Errors
The INFO PROGRAM command displays the preparation status of each object file:

Unprepared Calls – Program calls to procedures that are normally intercepted by
AutoTMF are not retargeted. Either the program was not prepared, or was
prepared using an earlier release of AutoTMF. In either case, issue the
PREPARE
again.

No User Library – The program has no user library. Either the program was not
prepared or the user library was removed. In either case, issue the
PREPARE
again.

Invalid User Library – The user library does not contain the NonStop AutoTMF
runtime library procedures. Follow the procedures below for
Preparing Programs
that Have a User Library .

Intercept Conflict – The program has a procedure that has the same name as an
NonStop AutoTMF intercept procedure. NonStop AutoTMF procedure interception
would not be reliable if the program were prepared.

External Conflict – The program makes external calls to both prepared names and
unprepared versions of the same procedure name; this situation would lead to
duplicate externals (see next item) if the program were prepared.
External conflicts occur when prepared and unprepared objects have been bound
together; try to avoid this situation; however, if you need to bind prepared and
AutoTMF 1? trace to trcsv.myserver program data.srvobj.myserver;
Trace index 0
Tracing EXECution
Trace file $DATA.TRCSV.MYSERVER, Entry Seq, EOF=0 (0.0% full)
Trace expiration May 9 2007 12:45:29 (59 minutes remaining)
Trace owner 170,46 (USER.SALLY)
Tracing programs $DATA.SRVOBJ.MYSERVER