OSI/MHS Configuration and Management Manual

Managing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
7-29
Displaying Saved Event Messages
This command example runs a printing distributor to a terminal called $TERM1. The
source of the event messages is the collector $0 (the collector on your local system),
and the filter is the default filter, which accepts all event messages.
The distributor $DIST1 displays messages for all events reported from the time you
start the distributor until you stop it. This is an online printing distributor. The collector
forwards all the event messages to this distributor, which then formats and prints the
messages. The output from the printing distributor may be a disk file.
Since the distributor has been assigned a name, you can stop the process using that
name. As a general rule, you should name distributor processes.
You can use similar commands to run printing distributors to other terminals or printers
by substituting other names for $TERM1.
To stop the distributor, press the BREAK key on your terminal keyboard. Then,
assuming the distributor is the process you most recently started, use the TACL STOP
command to terminate it, or use the TACL STOP command with the distributor name to
stop it by name.
Displaying Saved Event Messages
You can run a printing distributor to display event messages saved in a previously
created log file. The TACL command is similar to the previous example. However, the
LOGFILE parameter replaces the COLLECTOR parameter, and a TIME parameter is
added to specify the generation time of the earliest message you want to display:
EMSDIST TYPE PRINTING, LOGFILE LOG1, TEXTOUT $TERM1, &
TIME 15 DEC 1994 7:30
This command runs a printing distributor to a terminal called $TERM1, using the
default pass-all filter to process event messages stored in the previously generated log
file called LOG1 and generated since 7:30 a.m. on December 15, 1994.
You can stop the distributor by pressing the BREAK key and using the TACL STOP
command, as before, or by letting the distributor run until it reaches the end of the log
file.
Creating Simple Event Filters
You can define a filter to specify which event messages a printing distributor should
print and which it should ignore. If you do not specify a filter, it uses its default filter,
which accepts all event messages.
If you write a filter, you must compile it to create a filter object file, then specify the
name of that file when you run the printing distributor.
The following steps compile a filter source file and start an EMS printing distributor.
The filter causes only OSI/MHS event messages to be printed.