Example of a ULOG Message
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:
- A 6-digit string (hhmmss) representing the time of day (in terms of hour, minute, and second)
- The name of the machine (as returned, on UNIX systems, by the uname -n command)
- The name and process identifier of the process that is logging the message. (This process ID can optionally include a transaction ID.) Also included is a thread ID (1) and a context ID (0).
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 name of the message catalog
- The message number
- The BEA Tuxedo system message
| The Tag Indicates |
The Text Indicates |
|
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.