ViewPoint Manual

Definition of ViewPoint Screens
ViewPoint Manual—426801-001
3-20
Field Descriptions
5. CPU or Process ID. This field can contain a process ID or a CPU number. The ID
or CPU number of the process that reports an event must match the specified ID or
CPU number to qualify that event to be selected or discarded by the filter. You
specify a process ID as a process name (1 to 5 alphanumeric characters preceded by
$) or as two integers (
cpu-the CPU number, and pin-the process ID number). If
you specify only one number, ViewPoint interprets the number as the CPU number
and compares it to the CPU number of the reporting process.
6. Subsystem ID. This field can contain a subsystem ID. The subsystem ID that
reports an event must match the specified ID to qualify that event to be either
selected or discarded by the filter. The comparison is not case-sensitive; that is,
uppercase and lowercase letters are searched as the same character. You specify the
subsystem ID in external format without version information. The format is:
owner.ss
owner is 1 to 8 alphanumeric characters or hyphens, and the first character must be
a letter.
ss is either the subsystem number or the subsystem name. A subsystem number is
a 16-bit signed integer; a subsystem name is 1 to 8 alphanumeric characters or
hyphens, the first of which must be a letter. Examples are:
TANDEM.PATHWAY
TANDEM.52
Note that the subsystem ID you specify in this field does not contain version
information; this differs from the subsystem ID in an SPI specification.
7. Event Number. This field can contain an event number. The event number of an
event must match the specified event number for that event to qualify to be selected
or discarded by the filter. You specify the event number as a signed or unsigned
16-bit integer of the form:
[ + / - ] [ % ] number
You can use the % prefix to specify an octal base. The value of number must be in
the decimal range -32768 to 32767.
8. Event Text. This field can contain event text. The text of an event must match the
specified text in order for the event to be selected or discarded by the filter.
ViewPoint compares the entered text to the text generated by EMSTEXT (less
header text) for the event. Enter the event text as any alphanumeric characters, with
or without enclosing quotation marks. If you do enclose the text within quotation
marks and the value contains quotation marks, you must double the contained
quotation marks. Trailing blanks are discarded unless the text containing the blanks
is enclosed within quotation marks. You can use an asterisk (*) to match zero or
more alphanumeric characters, and you can use a question mark (?) to match any
one character. The event text can be in uppercase or lowercase letters.
9. Custom Tokens. These fields contain values and types for up to four custom
parameters that can be passed to the current filter. The default filter, FLTRALT,
does not use these parameters unless logic has been added to the filter to test for the
custom parameters. If the logic to test these parameters is in a filter other than
FLTRALT, then that filter must be named on page 1 of the Event Configuration