Guardian Application Conversion Guide

Converting Distributed Systems Management (DSM) Applications

Converting Other Parts of an Application

8–26 096047 Tandem Computers Incorporated

Handling Cross-Version Tokens

A D-series event-message header might contain a C-series header token (for example,

ZEMS-TKN-CRTPID), if the token can hold the required information. If the C-series

token cannot hold the required information, the subsystem omits the token from the

header. In this case, if your application tries to extract the token, it will receive the

missing token error (ZSPI-ERR-MISTKN). If necessary, modify your application to

handle the missing token error.

Whether your application is allowed to read tokens from or write tokens in an event

message depends on:

Whether your application runs on a C-series system or a D-series system

Whether the token is a D-series token or a C-series token

Whether the token is part of an event message header

Whether the token header is a D-series header or a C-series header

Table 8-5 summarizes the cross-version access restrictions for EMS tokens. The

column headers indicate whether you are trying to read or write a token and whether

your application is running on a C30 system or a D-series system.

Table 8-5. Cross-Version Access Restrictions for EMS Tokens

C30 System D System

Token to Access Read Write Read Write

Nonheader token in C-series message

Yes Yes Yes Yes

Nonheader token in D-series message

Yes Yes Yes Yes

C-Series token in D-series header Yes

Yes Yes

Yes

C-Series token in C-series header Yes Yes Yes Yes

D-Series token in D-series header No No Yes Yes

D-Series token in C-series header No No Yes No

1 For information about a nonheader token, refer to the management programming manual for the

subsystem that generated the event message.

2 If the data does not fit in the token, the token is omitted. The application receives the ZSPI-ERR-

MISTKN (-8) error.

3 The application receives the ZSPI-ERR-NOTIMP (-11) error.