DSM Template Services Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Introduction

DSM Template Services Manual—427187-004

1-2

When Do You Need Template Services?

Most SPI messages are in a form that is efficiently interpreted by computers. That is,

separate pieces of information are packaged as tokens that together make up the

entire message. In order to put the tokenized messages in a form that people can read

easily, you need Template Services. Template Services lets you specify how you want

information displayed.

Template Services supports the Event Management Service (EMS), which, as part of

DSM, is also based on SPI. Template Services enables you to convert EMS event

messages to operator messages for display at a printer, terminal, or other device, or for

storage in a file.

Another function of Template Services is to list the tokens found in an event, command,

or response message, which is particularly useful for debugging. Template Services

displays the token name (or another customized label), followed by the token value, for

each token in a message.

When Do You Need Template Services?

There are five major reasons to use Template Services (see Table 1-1 on page 1-4):

•

Developing operator messages for EMS events

If you are designing new EMS event messages to be sent from a subsystem or

network management application, you should supply format templates so that

operators can see messages about these events. A format template specifies how

to translate an EMS event message into a displayable operator message.

•

Displaying operator messages for EMS events

Figure 1-2. Creating Text From Tokenized Event, Command, and Response

Messages

Listing of Token

Information

token 1: token_1_value

token 2: token_2_value

token 3: token_3_value

• • •

• • •token 1 token 2 token 3

Event Message

EMSTEXT

procedure

SPI_BUFFER_FORMAT

procedures

Operator Message