OSI/MHS Configuration and Management Manual

Managing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
7-35
Using the EMS Analyzer
When you run EMSA (by typing EMSA at the TACL prompt), it immediately loads the
EMSACSTM file. The custom file just defined:
1. Starts an EMS distributor in CPU 3 and designates $0 as the source of the event
log. (See the START DISTRIBUTOR command and the ALTER, EMSLOG
command that follows it, near the end of the custom file.)
To try this example in your own environment, replace $0, if necessary, with the
name of the primary collector you specified when you ran the MHS manager
process.
2. Sets the default start time for EMS messages to 00:00 hours (See the command
ALTER, STARTTIME TODAY.)
Once the distributor is running, you can use the following function keys and
abbreviations defined in the custom file:
•
The F1 function key issues a DUMPLOG command to EMSA to display all the
messages for the selected Accounting filter. If none are available, the DUMPLOG
command returns an error, meaning no event messages satisfied the filter.
•
The F2 function key selects filter for MHS accounting events. It points to an
alternate collector called $ALTC. To try this example in your own environment,
replace this name with the name of the alternate collector you are using.
•
The F3 function key selects the filter for other MHS events and for events from OSI
subsystems. It points to $0; change the name if necessary to reflect your
environment.
•
The F4 function key selects the filter for events from other subsystems. It points to
$0.
•
The abbreviation TODAY represents the command ALTER. STARTTIME TODAY.
•
The abbreviation NOW represents the command ALTER. STARTTIME NOW.
•
The abbreviation BOF represents the command ALTER, STARTTIME BOF. (BOF
means Beginning of File. It sets the pointer in the event log to the first record that
satisfies the filter.)
Suppose that after pressing F2 to select accounting messages, you wanted to view
any errors that were detected in the MHS subsystem. The F3 Function key selects the
MHS filter, which includes any OSI subsystem events. After you select that filter, you
can press F1 (DUMPLOG) to display the filtered events for the MHS subsystem.
Finally, if you press first F4 and then F1, you will view the events reported by
subsystems other than MHS: for example, events from Transfer, TMF, and disk
processes.
Note. The EMSACSTM file in this example assumes that the TEMPLATE file was built
correctly through use of INSTALL and includes all the template source for MHS, OSI, and the
accounting events.