ViewPoint Manual

Functional Description
ViewPoint Manual426801-001
5-22
Logging of Events
At this time, you can view this first page of historical events on your screen, if you
select alternate events (function key SF3). If the cache is not yet full, the display
continues to be updated with incoming messages until the cache is full. No further
pages can be retrieved. This is indicated by the word END displayed at the top right
corner of the Events screen. You can view only pages currently in the cache. To
retrieve succeeding or preceding pages from the cache, you would have to set a new
starting time on the Event Configuration screen and start over.
Logging of Events
Figure 5-16 begins a sequence of diagrams that explore the event reporting scheme step
by step, concluding with a composite view at the end of the section.
The first step, as illustrated in Figure 5-16, is the logging of event messages in a log file.
This step begins with the originating subsystem that detected the event. The subsystem
writes all pertinent information about the event into an event-message buffer. This
includes the subsystem ID and event number.
Much of the information in the event-message buffer is in the form of tokens, consisting
of a token code and a token value. The tokens indicate the following:
Time the event occurred
Network node number
Process identification (PID)
Figure 5-16. Logging of Events
CDT516cdd