As mentioned earlier, it is possible to use both TLOG-STATUS and TLOG-MONITOR to examine the status of the transaction logger. The TLOG-STATUS report shows the current status of both the update and the transaction loggers; the TLOG-MONITOR report shows a continuously updated status report of both loggers.
See Defining Files to be Logged for a sample TLOG-STATUS report The lower portion of this report, labelled TRANSACTION PROCESSOR, gives information about transaction logging. (Information in the upper portion has to do with update logging and is described previously.)
The first line of the report indicates whether the transaction logging process is ACTIVE or SUSPENDED and on which process, or whether it is INACTIVE. The rest of the report shows information about the two most recent transaction logging sessions, the first of which (LATEST) may be currently active. If the latest session is not currently active, it is the most recently dequeued session.
The Global Transaction Numbers of the last two sessions are shown, along with the date and time the transactions were queued. The last transaction number of the PREVIOUS session and the first transaction number of the LATEST session should be sequential, signifying that entries have not been lost between sessions.
As mentioned earlier, TLOG-MONITOR can be used to continuously monitor the status of both the update and the transaction logger. Include the number of seconds in the TLOG-MONITOR statement to specify the interval of time between updates of the status report.
Use the TLOG-BUFFERS command to monitor the amount of overflow in use by transaction buffers.
See Also
Starting the Transaction Logger
Stopping the Transaction Logger
Suspending and Resuming the Transaction Logging Process