USERLOG
-write a message to the BEA TUXEDO system central event log
01
LOG-REC
.
COPY User data.
01LOGREC-LEN
PIC S9(9) COMP-5.
01TPSTATUS-REC
.
COPY TPSTATUS.
CALL "USERLOG" USINGLOG-REC
LOGREC-LEN
TPSTATUS-REC
.
USERLOG
() places LOG-REC
into a fixed output file--the BEA TUXEDO system central event log.
The central event log is an ordinary UNIX file whose pathname is composed as follows:
ULOGPFX
is set, its value is used as the prefix for the filename. If ULOGPFX
is not set, ULOG
is used. The prefix is determined the first time USERLOG
() is called.
hhmmss
), system name, process name, and process-id of the calling process. The tag is terminated with a colon (:
).
catalog>:number>:
format
specification is not a newline character, USERLOG
() appends one.
USERLOG
() is used by the BEA TUXEDO system to record a variety of events.
USERLOG
mechanism is entirely independent of any database transaction logging mechanism.
The If the variable is made at 4:22:14pm on the UNIX named If the message is sent to the central event log while the process is in transaction mode, the user log entry has additional components in the tag. These components consist of the literal If the shell variable It is recommended that applications' use of Portability
USERLOG
interface is supported on UNIX and MS-DOS operating systems. The system name produced as part of the log message is not available on MS-DOS systems; therefore, the value PC
is used as the system name for MS-DOS systems.
Examples
ULOGPFX
is set to /application/logs/log
and if the first call to USERLOG
() occurred on 9/7/90, the log file created is named /application/logs/log.090790
. If the call:
01
LOG-REC
PIC X(15) VALUE "UNKNOWN USER".
01 LOGREC-LEN
PIC S9(9) VALUES IS 13.
CALL "USERLOG" USING LOG-REC
LOGREC-LEN
TPSTATUS-REC
.
logsys
by the program whose process id is 23431
, the following line appears in the log file:
162214.logsys!security.23431: UNKNOWN USER
gtrid
followed by three PIC S9(9) COMP-5
hexadecimal values. The values uniquely identify the global transaction and make up what is referred to as the global transaction identifier. This identifier is used mainly for administrative purposes, but it does make an appearance in the tag that prefixes the messages in the central event log. If the foregoing message is written to the central event log in transaction mode, the resulting log entry will look like this.
162214.logsys!security.23431: gtrid x2 x24e1b803 x239: UNKNOWN USER
ULOGDEBUG
has a value of y
, the log message is also written to the standard error of the program named security
.
Errors
USERLOG
hangs if the message sent to it is larger than BUFSIZ
as defined in stdio.h
Diagnostics
USERLOG
() returns values include the inability to open, or write to the current log file. Inability to write to the standard error, when ULOGDEBUG
is set, is not considered an error.
Notices
USERLOG
messages be limited to messages that can be used to help debug application errors; flooding the log with incidental information can make it hard to spot actual errors.