Transaction Restoration

Use the TLOG-RESTORE command to restore the contents of a transaction logging tape. All previously unrestored transactions can be restored, or individual transactions can be restored selectively. The account from which TLOG-RESTORE is run must have access to the LOCK-XREF, RESTORE-XREF, and PATH-XREF files, as well as to all data files where transactions are to be restored. All previously unrestored transactions on the backup medium can be restored, or individual transactions can be restored selectively. Transaction numbers are displayed on the screen as each transaction is restored.

There are five options available with the TLOG-RESTORE command:

D	Displays file paths and item-IDs in addition to transaction numbers as they are restored.
X	Enables display of file paths on the screen without restoring any transactions to disk. The X and D options together enable display of both file paths and item-IDs without restoring any transactions. The X option is useful to obtain a listing of what transactions are stored on the backup medium.
R	Allows the user to restore transactions to accounts whose names have been changed since the transactions were logged. Since the old name of the account is the one used on the transaction logging backup medium, a cross-reference file is needed to tell the transaction restoration processor what the new name of the account is. The PATH-XREF file contains items whose item-IDs are the names of old accounts. Attribute 1 of these items contains the new account names. When the R option is used, all new file references first attempt to translate the account-reference portion of the file path by finding an item with the old account name in the PATH-XREF file. If an item is found, the transaction is restored to the new account name specified in Attribute 1.
F	The F and S options provide two interactive methods of restoring transactions selectively. The F (file level query mode) option displays each transaction and then prompts the user either to restore it, not to restore it, or to restore it and all subsequent transactions on the backup medium.
S	Prompts the user to define specific criteria for selecting which transactions to restore.

If TLOG-RESTORE finds that the first transaction number in a session is not sequential to the last transaction restored in the previous session (taking into account the windowing), an error is reported, and the user has the option to continue or quit. For example:

>TLOG-RESTORE

BLOCK SIZE: 500

SESSION LABEL:

L 01F4 15:03:25 08 NOV 1999 TLOG 5 þ01 (5-00000000+) SYSPROG > JUNK > JUNK

WARNING!!! The transaction about to be restored does not follow the last transaction restored on this system.

Do you want to (C)ontinue or (Q)uit?

There are a few cases in which TLOG-RESTORE prints an error message that can be dismissed. If TLOG-RESTORE reads a transaction that was already restored in the previous session, and the file referenced was deleted in a later transaction, an error message displays. For example, the following error message displays:

Unable to open Destination File – Discarding.

As long as the error message is displays in the range of transactions already restored in a previous session, the error can be ignored.

For example, if transaction number 100 is the file: DELETED.FILE, and this gets dequeued in transaction logging session 1, the TLOG-RESTORE of this session deletes the file. If the transaction gets dequeued again in transaction logging session 2, when the TLOG-RESTORE of session 2 gets done, the DELETED.FILE is no longer on the system, and an error message is printed.