Friday, January 11, 2008
Q. How are TUXEDO service statistics activated?
A. Reporting can be turned on using the -r server option specified in the CLOPT parameter. The statistics are logged to standard error, so we typically use the -e server option to redirect stderr to some other filename rather than the default $APPDIR/stderr. The stats file produced becomes input to the Tuxedo reporting facility, txrpt. Cool stuff.
Q. In a TUXEDO application, calling a service using tpacall() (asynchronous request) makes the service go faster than when using tpcall(): True or False?
A. No, it doesn't. The service will not execute any faster, but the call to tpacall will return to the caller faster than tpcall. That's because tpcall performs a tpacall with an immediate call to tpgetrply. The service behaves the same, and does not realize if it is being requested asynchronously or synchronously.
Q. Legacy database Y is not XA-compliant (naturally), therefore I can't access it via TUXEDO:
A. Not true. TUXEDO can access any resource -- with XA or without.
Q. In a TUXEDO MP application, what happens if you don't start up tlisten on the MASTER node?
A. The application will run but a slave node cannot assume administrative responsibility You get a warning but everything works. If, however you migrate to a backup node you will have problems bringing up servers on the master. Nothing special...unless your backup master takes control as master and at some point needs to boot the original master machine.