System and Application Softwares
Application Development Platforms
How to Read Tuxedo User Log (ULOG)?
The following is an example of a ULOG message.
121449.gumby!simpserv.27190.1.0: LIBTUX_CAT:262: std main starting
A ULOG message consists of two parts: a tag and text.
The tag consists of the following:
Note: Placeholders are printed in the thread_ID and context_ID field of entries for single-threaded applications. (Whether an application is multithreaded is not apparent until more than one thread is used.)
The text consists of the following:
The message was written into the log at approximately 12:15 P.M.
The machine on which the error occurred was gumby.
The message was logged by the simpserv process, which has a process ID of 27190.
The thread ID is 1.
The context ID is 0.
The message came from the LIBTUX catalog.
The number of the message is 262.
The message itself reads as follows: std main starting.
Note: For more information about a message, note its catalog name and number. With this information, you can look up the message in the appropriate catalog.
When userlog() is called within a tranasction, the line written to the ULOG includes 3 hexadecimal numbers representing the Tuxedo GTRID (global transaction ID.) If an error occurs during the transaction, Tuxedo may also write messages of its own to the ULOG, and these messages will also show the GTRID.
174304.test1!WSH.20044.1.0: gtrid x0 x47fb1049 x16e: WSNAT_CAT:1042: ERROR: tpcall() call failed, tperrno = 7
© 2018 Digcode.com. All rights reserved.