EasyManua.ls Logo

Avaya Definity SI - List History

Avaya Definity SI
2968 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Maintenance Commands and Trouble-Clearing Aids
555-233-123
8-150 Issue 4 May 2002
list history
The list history command generates a log listing of the most recently completed
data affecting administration and maintenance commands. Data commands are
those administration and maintenance commands that change the data state
associated with any object and qualifier in the system. Administration data
commands affect translation data, while maintenance data commands affect state
information. For example, change station is a data command, whereas display
station is not.
All information in the transaction log is saved as translation data when the save
translation command is performed (LIFO order). When the switch COLD I starts
or reboots, the saved translation, and thus the transaction log, is loaded. This
way, the translation data and the data in the transaction log remain compatible.
Feature Interactions
The translation log is written to the memory card as translation data when the
save translation command is executed. The translation data is time stamped
when saved. This time stamp is noted when translation is loaded from the
memory card and included in all recent change history reports.
When a user requests a recent change history report, there could be other users
concurrently issuing data commands and altering the contents of the transaction
log. Therefore, if the user pages the entire way through the report, the oldest
entries in the transaction log (maximum 250 commands) may have been
overwritten by data commands issued by these other users. Should this occur, the
final entries of the report show the data commands issued by the other users
since the recent change history report was originally requested.
Action/
Object Qualifier Qualifier Description Logins Defaults
Feature
Interactions
list
history
print
schedule
Report sent to printer.
Command is validated and then a
scheduling form displays to
schedule execution of the
command. The command is then
placed in the command queue and
is executed at the specified time.
The information displayed by the
command is sent to the system
printer instead of the screen.
1
Examples:
list history
list history print
list history schedule
1 Refer to the Report Scheduler and System Printer feature specification for more details.
init
inads
craft
cust
browse
nms
none See below

Table of Contents

Related product manuals