The :ULOG-ON command starts update logging; the :ULOG-OFF command stops update logging.
Format
|
:ULOG-ON :ULOG-OFF |
Description
:ULOG-ON generates update transactions which are queued to the transaction logger for processing. You must have SYS3 privileges to use these commands.
These updates to any file are logged:
New items.
Changes to existing items.
Deletions of items.
New files.
File clearings and deletions.
Account creations and deletions.
File updates caused by account-restores, and Spooler print jobs, are not logged.
|
NOTE |
This error message displays if an attempt is made to use the :ULOG-ON command during a clearing session initiated by the TLOG-CLEAR command:
|
Update transactions contain enough information to allow the updates to be recreated and reprocessed (see TLOG-RESTORE Command). Transactions are stored in special ABS buffers until the transaction logger dequeues them and writes them to backup medium. Each transaction is assigned a Global Transaction Number (see TLOG-STATUS Command). The only limit on the size of the update logging queue is the amount of available disk space.
|
NOTE |
Only updates to files whose pathnames are listed in the LOCK-XREF file are logged by the update logger. Use BUILD-LOCK-XREF to rebuild the LOCK-XREF file whenever you suspect that the LOCK-XREF file does not include pathnames of all the files whose updates you want to log. |
To check to see if update logging is active, use either the WHAT command or the TLOG-STATUS command. In the first line of the report displayed by the WHAT command, an asterisk at the right of the number of users currently logged on indicates that update logging is active.
Example
|
13:59:44 DD MMM YYYY MAXUSERS [4] CURRENT # USERS [2]* |