ViewPoint Manual
Definition of ViewPoint Screens
ViewPoint Manual—426801-001
3-25
Field Descriptions
2. Subject. Name of the subject associated with these event messages. This is the
name you selected on the screen either by entering it on the option line or by
marking an event message with the cursor or a nonblank character. To change the
subject, type a new subject name on the option line and press F4.
The subject name you select refers to the subject token associated with that event.
(For an explanation of subject tokens, refer to the EMS Manual.) Each event can
have several different subject tokens associated with it. ViewPoint builds a database
of events based on particular subject tokens. Then, when you specify a particular
subject, ViewPoint looks in this database and displays all the event messages that
are listed for this subject.
To build each events database, ViewPoint scans each event to determine if it has one
of the following valid types of subject tokens associated with it: character, crtpid,
device, filename, fname32, unsigned integer, or transid. If none of these types of
subject tokens is found, the event is not entered in a database. For each subject
token that is found, the event is entered in the database of events for that subject
token.
ViewPoint follows these guidelines in determining suitable subject tokens and how
they are formatted on the screen:
•
If the subject token is a string of characters and there is a manager token (a
filename token), the subject token is formatted as follows:
\NODE.$MANAGERNAME.STRING
•
ViewPoint converts the subject tokens of types crtpid, device, and filename to
external form using the procedure FNAMECOLLAPSE. ViewPoint converts
the subject token fname32 to external form using the procedure
FNAME32COLLAPSE. ViewPoint formats any subject token of type filename
that is not qualified with a node name into the following format:
\NODE.$VOL.SUBVOL.FILENAME
If node names are not available, ViewPoint uses the three-digit system number
for the node. If the system is local and not part of a network, the system name
does not appear in the prefix.
•
An unsigned integer subject token is valid only if its token code is
ZEMS^TKN^LDEV or ZEMS^TKN^SYSPID. An ldev code is converted to a
device name using GETDEVNAME. If no device name is available, a device
number is used in the format
\NODE.$LDEV
A syspid code is converted to external form using FNAMECOLLAPSE and is
formatted as follows:
\NODE.CPU,PIN
The syspid token is present in SENDOPMSG events.
•
A transid subject is converted to external form using TRANSIDTOTEXT.