SNAX/HLS Configuration and Control Manual
Reporting Events
Operating SNAX/HLS
104705 Tandem Computers Incorporated 5–13
The EMS Facility The primary EMS collector, and up to three alternate EMS collectors, are specified at
program initiation. The COLLECTOR option is available for specifying the primary
EMS collector, which defaults to $0 on the local node. The options COLLECTOR-1,
COLLECTOR-2, and COLLECTOR-3 are available for specifying the alternate
collectors. The default is to suppress EMS event generation to the alternate collectors, a
situation that can also be achieved by specifying the collector-
n
option with no
collector specified. Thus, a command that starts HLSOBJ of the form:
> RUN HLSOBJ/ . . . / . . .
has the effect of specifying $0 as the primary EMS event collector and suppressing
event generation to alternate EMS collectors. The EMS collector to which an EMS
event is generated is a function of the appropriate record in the HLSMSGS file. See
Section 3, "Installing SNAX/HLS."
You can use (SPI), which is described in the SNAX/HLS Management Programming
Manual, to reassign the EMS collectors. You can also use HLSCOM. For more
information on HLSCOM, refer to Section 6, “Using the HLSCOM Utility.”
The performance of SNAX/HLS is directly related to the location of the collector
selected. You should consider the following when selecting an EMS collector:
SNAX/HLS has no way to determine that the file name supplied as a collector is
indeed a collector.
The collector is accessed in a wait fashion.
Any error on the collector causes the collection of events to be discontinued, but
has no effect on logging.
As a result of these observations, it is clear that the following are the only meaningful
choices for EMS collection:
The local event collector that is, $0 on the system where the HLSOBJ file is running
An alternate event collector in the same system as the HLSOBJ file
Some collector on another node
Be careful, however, when selecting a collector on another node. Sending messages to
that collector requires use of the Expand network and is therefore subject to possible
delays. These delays can affect SNAX/HLS performance.