OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-3
Creating Simple Event Filters
Creating Simple Event Filters
You write filters to select the event messages you want to display or print. Filtering
strategies involve organizing the messages that are collected into logical groupings to
which you can refer. For example, you might want to select all the messages sent by
OSI/AS, OSI/TS, TLAM on D-series releases (or PAM on G06 and above releases), and
X25AM or only the OSI/AS event messages.
A printing distributor needs a filter to specify which event messages it should print and
which it should ignore. If you do not specify a filter, it uses its default filter, which
passes all event messages.
If you would like to try running a printing distributor with another filter and you do not
have access to a filter object file (a compiled filter specification), you can either write
your own or use one of the filters in Appendix B, Examples of EMS Filters
. Appendix B
contains four example event filters that you may adapt for your own subsystem. For
more information on printing distributors and writing filters, see the Event Management
Service (EMS) Manual.
Managing Configuration Files
Two types of configuration files are associated with an OSI/AS subsystem: a
configuration command file, and a MIB file:
•
A configuration command file (recommended)
Although it is possible to type in SCF commands to configure an OSI/AS
subsystem, it is more efficient to include such commands in a command file. A
command file is an EDIT file that contains sequences of commands. This could be a
TACL macro file containing SCF and non-SCF commands, which you invoke using
the TACL OBEY command, or an SCF command file containing only SCF
commands, which you invoke using the SCF OBEY command. The file can also
include comments to improve understandability.
You can set up as many command files as you wish. You might use one command
file to start up an OSI/AS subsystem from scratch; for example, when you first
install a subsystem. You might use other command files to build a MIB from
scratch, or to update (delete and re-add) an existing MIB.
•
A management information base (MIB) file (required)
This is a key-sequenced database file that the OSI manager process uses to store
configuration information. Whenever the OSI manager process changes from the
SUSPENDED state to the STARTED state, it reads this file to recover configuration
information.
These two files are related in the following way: the OSI manager process uses the
information that you provide in the configuration command file to build the MIB.