Using EMS
Using Programmatic Interfaces
7–12
107365 Tandem Computers Incorporated
The following session shows sample output:
17>dumplog 16:50
92-05-28 16:51:22 \SYS.003,000 TANDEM.MSGSYS.C20 000104
Receive Queue for CPU 3,
PIN 50 Greater Than 10 LCBs
92-05-28 17:00:34 \SYS.004,013 TANDEM.EMS.C20 000165 LDEV
0056 CU %120 CSS SUBDEVICE ERROR,
CIU SUBDEV #000003 F, M=%043200
STATUS %000005
To generate a request for EMS, see the following subsection, “Using EMS.”
Using EMS
EMS provides a centralized event collection, logging, and distribution facility for
Tandem networks. Subsystems within the NonStop kernel environment can define
and generate tokenized event messages. For additional information about EMS, see
the Event Management Service (EMS) Manual.
Communicating With EMS
The built-in functions in Table 7-3 provide access to EMS.
Table 7-3. Functions That Support EMS
Function
Description
#EMSINIT(V)
Builds the header and initializes a STRUCT as an event message buffer,
so that you can use the STRUCT in calls to other #EMSxxx and #SSxxx
functions.
#EMSGET(V)
Retrieves token values from a buffer, converts them to external
representation, and returns the external representation as its result. This
function is similar to #SSGET.
#SSGET(V)
Retrieves token values from an SPI buffer, converts them to external
representation, and makes the results available. Use #SSGETV (instead
of #SSGET) for extensible structured tokens and tokens of type
ZSPI^TYPE^STRUCT.
#SSPUT
Converts token values from external representation to binary form and
puts them into an SPI buffer.
#SSPUTV
Converts token values in extensible structured tokens and tokens of type
ZSPI^TYP^STRUCT.
#SSNULL
Initializes a STRUCT and sets the values to null.
#SSMOVE
Copies tokens from one message buffer to another by performing a
sequence of #SSGETV and #SSPUTV operations.
#EMSTEXT(V)
Obtains information from an event buffer and makes it available in
printable text form.
#EMSADDSUBJECT(V)
Adds a subject token to an event message buffer.
Before communicating with EMS, you must:
Know the subsystem ID for EMS
Know the names of individual tokens of interest