Table of Contents
Advertisement
Monitoring Event Messages
Operator Message Monitoring Tools
Several utilities on your system can help you monitor operator messages, including:
Event Management Service (EMS) provides event-message collection, logging,
and distribution facilities for the NonStop™ Kernel operating system. For more
information, see the EMS Manual.
TSM EMS Event Viewer helps you perform many of the tasks associated with
viewing and monitoring EMS event logs ($0 and $ZLOG). It enables you to search
for and view the log files in a variety of ways and retrieve events based on start and
end time, subsystem, source, and multiple or specific events. For more information,
see the TSM Online User's Guide and the TSM EMS Event Viewer Application
online help.
Operator Message Types
Message Type
Common
EMS
OSS
Subsystem
For more information, see the Operator Messages Manual.
Operator Messages Format
Operator messages are preceded by a header that contains:
Subsystem ID
Event number
Time the message was generated
Name of the system that sent the message
Process ID or processor number of the process that issued the message
Only portions of the subsystem ID and the event number are shown as header
information in this guide.
This example shows the format for Compaq Open Systems Interconnection/Message
Handling System (OSI/MHS) operator messages as they are sent to disk files, terminals,
or printers:
96-10-03 15:09:51 \NET.$FTI1
Definition
Messages "common" to several subsystems; they have negative event
numbers.
Messages sent under the Event Management Service (EMS) subsystem ID.
Messages sent under the Open System Services (OSS) subsystem ID.
DSM display format messages generated by a specific subsystem.
TANDEM.MHS.G01
MR.\NET.MRGRP1
problem with device \NET.$LAPX.#Z0004BW
on call APS_ASSOC_CONNECTREQ
with -1001, 140
Guardian User's Guide —425266-001
Operator Message Monitoring Tools
$RL11: OSI resource
17- 3
000023 $ZL1
returned
Advertisement
Table of Contents
