Оценок - 0, средний балл: 0
(
)
)
|
К этому устройству также есть другие инструкции:
Компьютеры - HP Integrity NonStop H-Series (16.73 mb)
Компьютеры - HP Integrity NonStop H-Series (957.56 kb)
Компьютеры - HP Integrity NonStop H-Series (881.66 kb)
Компьютеры - HP Integrity NonStop H-Series (965.62 kb)
Компьютеры - HP Integrity NonStop H-Series (676.93 kb)
Компьютеры - HP Integrity NonStop H-Series (393.72 kb)
Компьютеры - HP Integrity NonStop H-Series (776.57 kb)
Фрагмент инструкции
SPI Programming Considerations for OSI/TS
Retrieving and Decoding Event Messages
The Event Management Service (EMS) Manual provides information on how to retrieve
tokens from an event message. The Communications Management Programming Manual
provides additional information, specific to data communications subsystems. Refer
to those manuals for details.
Event-Management
The overall goal of event reporting by OSI/TS is to allow the system operator or a
Considerations for OSI/TS
management program to monitor and control the operation of the subsystem. The
OSI/TS subsystem reports events to EMS but not to the Tandem Maintenance and
Diagnostic System (TMDS).
Most event messages (except the threshold messages and a few others) have the value
of the ZEMS-TKN-CONSOLE-PRINT token set to ZSPI-VAL-TRUE. This causes them
to be routed by the EMS compatibility distributor ($Z0) to the designated operator
console. The threshold event messages, of concern only to applications that monitor
thresholds, have ZEMS-TKN-CONSOLE-PRINT set to ZSPI-VAL-FALSE and so are
not sent to the console. You can override the value of ZEMS-TKN-CONSOLE-PRINT
using the OVERRIDE option of the DSM template compiler, as described in the DSM
Template Services Manual.
OSI/TS does not report any action events (normal occurrences that require operator
intervention).
The maximum buffer size needed for any OSI/TS event message is 1000 bytes.
The minimum buffer size for the OSI/TS threshold events is 512 bytes.
OSI/TS event messages do not contain extensible structured tokens; however, some do
contain error lists. In some event messages, these error lists contain information for
use by your application; in other event messages, the error lists contain information
the operator or programmer should report to their Tandem representative. The
descriptions of individual event messages in Section 6 explain what to do with each
error list.
Critical Events
Events reported by OSI/TS are divided into two classes: critical and noncritical.
Critical events can have serious consequences, such as the loss of a device or the
occurrence of errors. Noncritical events are less serious, such as a network-
management counter exceeding a threshold. The value of the event-message token
ZEMS-TKN-EMPHASIS indicates whether an event is critical. If the value is
ZSPI-VAL-TRUE, the message reports a critical event. If the value is ZSPI-VAL-
FALSE, the event is noncritical.
Filters
EMS provides you with the ability to create filters, which allow applications to select
particular event messages from among those reported. Filters select messages to be
returned to an application by examining the values of tokens in the messages. For
example, to select only event messages reported by OSI/TS, a filter would examine the
token that contains the subsystem ID of the issuing subsystem and then allow only
those messages containing the OSI/TS subsystem ID to pass.
You code a filter in the EMS filter language, compile the filter source file with the EMS
filter compiler, and load the resulting filter when you run the EMS consumer
distributor. You can replace filters online.
056786 Tandem Computers Incorporated
3–11
...Эта инструкция также подходит к моделям:
Компьютеры - HP Integrity NonStop J-Series (317.41 kb)
Компьютеры - HP NonStop G-Series (317.41 kb)
Компьютеры - HP NonStop L-Series (317.41 kb)