Table: Field Definitions: Administrator's History Log Screen; Report Results
|
Field Name |
Description/Procedure |
|
Problem Resource Type |
Where the event originated, for example:
- blank = At the console
- FC = By remote login
- AKS= By a program separate from AUDIX
|
|
Inst |
The instance of the remote
connection. Usually the first remote or LAN
connection is instance 1. Subsequent concurrent
logins are considered instance 2, 3, and so
on.
|
|
Location |
This field is not normally populated. |
|
Msg Typ |
EVN indicates a system event. |
|
Reporting Resource Type |
Where the event originated, for example:
- blank = At the console
- FC = By remote login
- AKS= By a program separate from AUDIX
|
|
Inst |
The instance of the remote
connection. Usually the first remote or LAN
connection is instance 1. Subsequent concurrent
logins are considered instance 2, 3, and so
on.
|
|
Source |
The name of the program
that generated the event information. You
might need to supply this information to Avaya
technical support personnel during a trouble
call.
|
|
App: |
The abbreviation for the application that was affected by the event. |
|
ID: |
Always displayed as ADMIN001. |
|
Date/Time Rec: |
The date and time that the event occurred, in mm/dd/yy hh:mm format. |
|
Cnt: |
The number of times that the exact message was received within one second. |
|
Text |
This field is not labeled, but is the last field in each event entry. The text field shows the exact command that was given to the system. The command information is enclosed in single quotation marks, such as: 'command information'.
The command could have
been provided by any of the following:
- AKS = An application external to AUDIX that performs administrative updating or reporting tasks
- API = An application external to AUDIX that interfaces with AUDIX through an application programming interface (API)
- FC = AUDIX
Forms Controller was logged in remotely
or via the LAN
- PNAME = A program
that was initated by support personnel
|
