HP Integrity NonStop H-Series - Manual (Page 43)

Preparing Programs
HP NonStop AutoTMF Software User’s Guide—429952-013
3-11
Tips for Preparing Programs
1. In binder, type the following commands:
2. At the TACL prompt, SQL compile escort:
3. Log on as SUPER.SUPER, and license escort:
If your site is not licensed to run NonStop SQL and you are running a version of
NonStop AutoTMF software that predates SPR T0581AAP, contact HP to request a
copy of the privileged ESCORT CI.
Tips for Preparing Programs
If you test NonStop AutoTMF software on a newly installed application, or on an
application duplicated from your test system or production system, you should fully test
that application before preparing the object files.
Newly installed applications or duplicated applications often fail because of errors in
the PATHWAY configuration, incorrect ASSIGNs and DEFINEs, bad user-library
pointers, and similar considerations. If you eliminate these sources of error before
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.
ADD * FROM escort
SET LIKE escort
ALTER CALLABLE^SET^LICENSE, CALLABLE ON
BUILD escort!
SQLCOMP/ IN escort/ NOREGISTER ON
FUP LICENSE escort
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