Votos - 0, Puntuación media: 0
(
)
)
|
Otros manuales para este modelo:
Computadoras - HP Integrity NonStop H-Series (16.73 mb)
Computadoras - HP Integrity NonStop H-Series (957.56 kb)
Computadoras - HP Integrity NonStop H-Series (881.66 kb)
Computadoras - HP Integrity NonStop H-Series (965.62 kb)
Computadoras - HP Integrity NonStop H-Series (676.93 kb)
Computadoras - HP Integrity NonStop H-Series (393.72 kb)
Computadoras - HP Integrity NonStop H-Series (776.57 kb)
Resumen del manual
1 Introduction
Event Management Service (EMS) messages provide important information about
devices, subsystems, and applications. Tandem subsystems, such as Expand, Transaction
Monitoring Facility (TMF), Pathway, and NonStop SQL, as well as your own custom
applications, can generate thousands of event messages. EMS Analyzer enables you to
examine and analyze this information, which is saved in the EMS event log files.
Without EMS Analyzer, you need to write and compile your own EMS filters by using
the EMS filter language—a complicated and time-consuming task.
You use EMS Analyzer’s default parameterized filter to specify a set of search
parameters, or you can use your own custom filter with EMS Analyzer. The parameters
of EMS Analyzer’s default filter are start and stop time, event number, event type,
process ID, subsystem ID, logical device, system name, or text string. You can easily set
the search parameters by using EMS Analyzer’s conversational interface. The
conversational interface recognizes individual commands or function keys that you
optionally customize using the ALIAS command. Function keys can be used as
shortcuts for frequently used commands or command combinations. Based on the
parameters that you set, EMS Analyzer extracts information relating to critical events,
availability, and performance of subsystems and devices.
You can search for a diverse set of events, such as:
• Pathway servers timeout events
• SNAX lines incidents
• X.25 lines incidents
• Tape subsystem action event messages
• Expand critical messages
• Event messages from your own subsystems
EMS Analyzer gives you several ways to view the output. The output can be directed to
a terminal for viewing or to a spooler for printing. Additionally, you can design specific
reports with the output. You can direct the output to an Enscribe database or a Comma
Separated Values (CSV) file. A default DDL dictionary is created as part of the
installation procedure so that you can create Enform reports based on the Enscribe data
files. Sample Enform reports are provided to get you started (see Making Enform
Reports on page 3-32). If you direct EMS Analyzer output to a CSV file, you can use a
PC or Macintosh for analysis and reporting.
You can also use EMS Analyzer as a debugging tool for EMS event messages. When an
application generates EMS events, you can use EMS Analyzer to isolate and view a
specific event in a token format. EMS Analyzer provides a detailed view of the EMS
event by separating and identifying each token. An event can be displayed with or
without the header tokens.
Installing EMS Analyzer does not require a SYSGEN. You can install EMS Analyzer by
using a TACL routine supplied with the product and the step-by-step instructions
provided in Section 2, Installation (see Sample EMS Analyzer Installation on page 2-4).
Event Management Service (EMS) Analyzer Manual –133700
1 -1
...Otros modelos de este manual:
Computadoras - HP Integrity NonStop J-Series (479.95 kb)
Computadoras - HP NonStop G-Series (479.95 kb)
Computadoras - HP NonStop L-Series (479.95 kb)