Abbreviations used in the actions to be taken by the user

Recurring responses included in the messages are given in abbreviated form, their meanings are listed in the following table.

The earliest opportunity at which the database administrator may take the appropriate action is given in the column “At” of the table.

O	Immediately after an error message occurs, during the current session (online).
M	Still during the current session but not until after an appropriate release message has been issued (message).
I	During an interruption of the current session (interrupt).
S	Not until the current session is terminated normally (session end).

Abbreviation	At	Meaning
DIAG	O/I	Write error report; supply suitable documentation for diagnosis (dump, file excerpts, log of UDS/SQL messages, error history, BPSIA log for the database concerned, object listing of the application program concerned, etc.).
ERASE-RLOG	I	Due to various reasons (e.g. RLOG file error, database warm start given up by user) the RLOG file may contain logging data which is relevant to UDS/SQL, but no longer to the user. In order to prevent such files from being kept indefinitely, the user should erase them with /DELETE-FILE. As the RLOG files are protected using passwords assigned by UDS/SQL, they can only be deleted from the $TSOS user ID from the database administrator’s user ID after the relevant passwords have been sent using the RLOGPASS utility routine.
REPAIR-RLM	M	The realm concerned needs to be repaired, i.e. it must be reconstructed (using BMEND) from a copy and the ALOG files of the database it is part of. This operation cannot be started until the realm (or the database concerned) has been successfully detached from the session. After these recovery measures the realm can be processed again. When the database is reattached, the realm is reopened, or it can be attached to an active session via DAL if the corresponding database already or still is online.
RESET-DB	S	The database concerned must be restored from a backup with a consistent state. If there are consistency relationships between this database and other databases (this is not monitored by UDS/SQL), these must likewise be returned to the appropriate state. A warm start is often not performed when restoring databases from a backup. Therefore see also ERASE-RLOG.
RESTART	I	Restart the DBH without changing the database configuration.
START-UDS	I/O	Restart UDS/SQL, i.e. perform either session restart (RESTART), or start a new session after terminating the old session by invalidating the SLF (note the password; /DELETE-FILE configuration-name.SLF,DATA).

Table 3: Abbreviations used in the actions to be taken by the user