ViewPoint Manual

Definition of ViewPoint Screens
ViewPoint Manual—426801-001
3-13
Field Descriptions
Table 3-3 summarizes the acknowledgment process for critical and action events. If an
event is dimmed everywhere (that is, on all operator terminals running on this instance
of the ViewPoint application), it is not automatically dimmed on Alternate Events
screens that are opened after the dimming.
F5 Used in the following two ways:
•
Displays a particular DSM/PM screen. Type the name of the screen (or any
valid alias) on the option line, and press F5.
•
Submits events as problems. Mark the events by typing any character next
to them, and press F5.
For more information on submitting events as problems, see Section 2,
“Submitting Events as Problems or Problem Information Records.”
SF5 Used in the following two ways:
•
Sends an event marked on a ViewPoint event screen to DSM/PM as a
created problem requiring additional information. Mark the event by typing
any character next to it, and press SF5.
The object name associated with the event you mark is displayed as the
problem subject on the screen. DSM/PM does not automatically submit the
problem; it waits for you to take further action. For more information on
adding a marked event to DSM/PM see, Section 2, “Adding an Event
Without Submitting It.”
•
Sends multiple events marked on a ViewPoint screen to DSM/PM as
problem information records. Mark the events by typing any character next
to them, and press SF5.
The DSM/PM Create Problem screen displays the marked events appearing
as problem information records at the bottom of the screen. You can create a
problem using all the functions available on the screen. For more
information on submitting marked events as problem information records,
see Section 2, “Submitting Events as Problems or Problem Information
Records.”
F6 Acknowledges a critical or action event. The event message is dimmed to
indicate that it has been acknowledged. The message remains on the screen if
the view of critical and action events includes acknowledged events. The
highlighting is eliminated, and the message appears in dimmed (half-bright)
video display or in grey on a color display. Also, the event is no longer
considered outstanding for the line-25 count.
An action event is normally acknowledged by a completion message that is
triggered when you physically perform the requested action. The message is
acknowledged at all operator terminals.
However, when you use F6, the results are different depending on which screen
you are on when you press F6. If used on the Primary Events screen, the event is
acknowledged at all operator terminals; if on the Alternate Events screen, it is
acknowledged only at your terminal.
Table 3-2. Function Key Notes (Events Screen) (page 2 of 2)
Function
Key Special Requirements